Process automation in ComplyTrain: processes that start themselves and act
See how the autumn 2026 release lets a process notice its own trigger, run the routine steps and chase people, with an owner consenting to every automatic step and the AI handing decisions to a person when they matter.
In the autumn 2026 release a process in ComplyTrain can notice the event that should start it, do the routine steps, and chase the people involved by itself. A documented process says what should happen. Whether it happens has usually depended on somebody noticing the event, remembering the steps, and following up. The release removes that dependency. This article is part of the series on what is new in ComplyTrain.
Triggers: the process notices the event
A process can now start from an event in the system:
- a risk is created or its score changes,
- an incident is registered,
- a control test fails, becomes overdue, or its evidence stops arriving,
- a training event occurs,
- a tender reaches a stage,
- a form is submitted, including from an external system through a signed webhook,
- a Media Monitoring watch matches an article,
- another process run reaches a step,
- a schedule comes due.
One run starts per event, so nothing depends on a person spotting it.
Actions: the process does the routine work
Steps can be automatic. They come from one shared library:
- send a notification or call a webhook,
- create a task, a corrective action, a risk or a treatment plan,
- create or update a stakeholder,
- assign training,
- open a tender workspace or an incident,
- start a document review,
- start a child process.
Around these you have the control-flow steps you would expect: ask a person, wait, deadlines, retries, for-each, decision rules, votes and delegation.
An owner consents to every automatic step
Automation that nobody approved is a risk in itself. Each process has an automation owner, who consents to each automatic step before it can run. The process page has a "Ready to publish?" card that lists what is still missing.
AI steps, with a hand-off
A step can ask the AI to assess or decide. An AI decision has a confidence threshold. Below it, the step is handed to a person instead of being decided. After repeated failures the step is handed over as well.
This is the pattern we use everywhere: the AI takes the first pass, and a named person decides when it matters.
Try it before it is real
A process can be run as a test run. Test runs are marked as such and kept apart from real runs, so you can see what a trigger would do before publishing it.
Ready-made templates
You do not have to start from an empty canvas. The template gallery includes:
- Incident follow-up. The incident owner investigates the root cause within five working days; management is asked whether to extend or take over when it runs late. Major and critical incidents get a corrective action before management closes them.
- Supplier onboarding. A new supplier answers your questionnaire, the AI rates the risk from the answers, a high-risk supplier is audited on site, and quality approves or rejects.
- Document review with several approvers. The document is published once at least two of the reviewers have approved.
- Risk-driven document review. When a risk score changes, the AI lists the documents that control the risk, the risk owner confirms the list, and each document is reviewed by its owner.
- Quarterly site contingency test. Each site runs its test and records the evidence within two weeks. A failed or missed test logs a risk.
- Tender intake from a news announcement. The AI checks whether an announcement is a tender you can bid for, the bid manager decides within three working days, and a tender workspace is opened.
- Assess news for business opportunities. The AI judges whether a news story about an expansion or an investment is an opportunity for what you offer.
The last two build on Media Monitoring and tender discovery.
Templates per standard
A standard can bring its own process templates, shown in the gallery by the standards you hold. When a further standard touches a process you already run, you get an amendment proposal that the AI merges into your process, which you apply or decline.
Save and share your own
Save one of your own processes as a template and share it with another organisation on ComplyTrain, for example a subsidiary or a supplier. If you mark it "Followed as written", the receiver's copy is locked and updates when yours does.
Describe it, and let the AI draft
Two shortcuts get you to a first version:
- Describe what to automate. Write what should happen in your own words, and the AI drafts the process.
- Automate this. From a procedure document, the AI drafts a process from the document's text.
You review and adjust the draft on the canvas before publishing.
A process you can show an auditor
The process page has tabs for the Map, Automation, Runs, Compliance and Approval and review. Every run records what each step did, by whom or by what, and when. The map exports to SVG, PNG or PDF, and a process can be shown as a live diagram inside a controlled document.
Where to start
Pick a process that depends on someone remembering to act. For many organisations that is incident follow-up or supplier onboarding. Start from the template, run it as a test, and publish when the automation owner has consented to its steps.
Processes sit in the QMS module and work with Risk Management, Forms and Vendor Management.
To see one of your own processes automated, book a demo.
