How Aquil keeps teams in sync: inside the process workflow engine
An ISMS only works when several teams do. Incident response spans IT and security. Employee onboarding spans HR, IT and the hiring manager. A supplier review pulls in legal, procurement and the system owner. These processes are usually documented carefully, and then executed over email, chat and good intentions.
That gap between the documented process and the executed process is where things fall through: the handoff nobody saw, the step everyone assumed someone else did, the evidence that was never written down. Aquil's process workflow engine closes it by making the diagram itself the thing you run.
From diagram to running process
In the Process Builder you draw your processes as flowcharts, or let the AI generate a first draft from a title or an existing procedure document. The difference from a wiki diagram is that any process in Aquil can be started as an interactive execution: steps become a live checklist, and decision nodes become real yes/no choices that route the run down the right branch.
The process stops being a picture of how work should happen and becomes the place where the work happens.
Handoffs that don't drop the ball
Coordination lives or dies on handoffs. When a run reaches a step that belongs to another team, you hand it off: the recipient gets an in-app notification and an email, and the run appears in their execution overview with full history. You can also assign colleagues when starting a run, so a cross-team process has all its participants from step one.
Everyone involved sees the same state: what's done, what's next, who has it. No forwarded threads, no "where are we on this?".
The right resource at the right step
Process steps link directly to the things they concern: a register to update, a report to fill in, a document to consult, even a nested process to run. The person executing a step lands on exactly the right artifact and returns to the run when they're done, instead of hunting through folders mid-incident.
Visibility without micromanagement
The executions dashboard shows every running process with progress at a glance, so a CISO can see that onboarding, incident response and supplier reviews are actually moving without asking anyone. Each run has its own visibility scope, and runs that touch personal data can be flagged as confidential: restricted to their participants and never reachable through a shared link.
Along the way, participants leave comments on steps about what was done and decided, and what evidence exists. The coordination and the documentation happen in the same motion.
An audit trail as a by-product
Because every start, step, decision, comment and handoff is recorded, the question "how do you know the process was followed?" has a boring answer: here is the run. Completed executions remain visible as evidence, and auditors can be given read-only access to review them. No reconstruction from memory, no screenshot archaeology.
Your AI agents can follow the process too
With the MCP / API add-on, the same engine is available to AI agents: an agent can read a process step by step, start a run, advance steps and leave comments, under exactly the permissions of the user it acts for and with every action attributed and logged. The process you designed for people coordinates your automation as well.
Teams don't drift apart because they don't care; they drift apart because coordination is invisible work. Put the process where the work happens and make every handoff explicit, and staying in sync stops requiring effort.