What starts a workflow
- a schedule - a weekly report, an access review, a monthly summary;
- an event in a system - a new ticket, an alert, a document in a repository;
- a person - one click in the interface or an instruction in chat.
How a workflow is built
Workflows are designed visually: blocks, connections, conditions. No code is needed to add a step or change the order. Every workflow can have an approval gate - without it nothing moves on.
Input
A document, a ticket, data from a system, a message.
Model work
Reading, classification, summarisation, drafting a reply.
Approval
The responsible person checks the result and accepts it or sends it back.
Output
An entry in a system, a sent document, a report, a filing.
What the auditor gets
Every workflow run leaves a full record: what came in, which model was used, what it proposed, who approved it and when. That makes any decision reconstructable months later.