One rulebook, not sixteen
Approval thresholds, delegation rules and escalation are declared once and apply to every document type, instead of being configured again inside each module.
PLATFORM CAPABILITY · WORKFLOW
Your process, running exactly as you wrote it down.
One workflow engine shared by every module: design flows by dragging, approve by threshold and delegation, and leave evidence at every step.
Built for: Executives · Internal control · Department heads · Implementation teams · IT
WHY THIS IS NOT ANOTHER MODULE
Workflow owns no document — it makes every document move.
A leave request belongs to HR, a purchase request to Procurement, a contract to Contract Management. Split workflow out as its own module and you get two places talking about the same form — and when they disagree, nobody knows which one is right. So it is not the seventeenth module: it is the layer all sixteen stand on.
Purchasing modulePurchase request
- draft
- pending approval
- approved
- ordered
workflow layer
Policy gate — who approves, at which threshold, how many rounds, within how long
Once it is approved, the work waiting in another module unlocks itself
The status chain of a document belongs to the module that owns it. The workflow layer clamps onto the one transition that needs a decision — which is why it owns no document, and has nothing to contest with a module.
Follows the org chart, not a list of names
Approval routing reads the job title and unit held in HRM. When someone moves department the route moves with them — you do not edit each procedure one by one.
The evidence sits with the document
Who submitted, who approved, when, on which version, and on what authority — kept on the document itself, so an audit question does not start a reconstruction.
THE LIFE OF A REQUEST
From the moment someone hits send to the moment there is evidence to reconcile against.
One machine, every kind of document. Below, a purchase request runs all four stages — and stops where it is waiting.
ONE REQUEST, RUNNINGPR-1042v2took the branch · over the thresholdwaiting on an approver
Purchase request
Routeover the thresholdcapital, urgenteverything else
Executive boardthreshold matrixin orderSLA 48h6h left
in parallel
Financeany one signsSLA 24h
Department headby org chart
both must finish
Line managerby org chart
Evidence
AUDIT LOG
- 09:12Requestersubmitted the request
- 09:12Flowrouted by threshold
- 11:04Chief accountantasked for a second quote
- 01
Raise
Someone fills an e-form on the organisation's own template, or the business document raises the request itself when it hits a condition.
- 02
Route
Rules read value, document type, unit and threshold to pick the right approver — in parallel when several opinions are needed, in sequence when order matters.
- 03
Approve
Approvers act inside the workspace or on mobile, can ask for more, can delegate while away — and the SLA escalates if the step runs late.
- 04
Evidence
The decision is written onto the source document with a full log, and the next business step unlocks — nobody re-keys anything into another system.
The diagram is one worked example so the machine can be read; the figures in it are illustrative. Thresholds, approval levels and escalation timers are configured against each organisation's own rules and settled during implementation. The software helps enforce the rules; it does not replace them.
WHAT IS IN IT
Designed by dragging, run on real data.
Design & forms
- No-code flow designerBuild a flow by dragging on a canvas: steps, conditions, branches and loops — no code required.
- E-formsFields, validation and attachments on the organisation's own templates, wired straight into the raise step.
- Versions & dry runsEdit a live flow on a draft, test it, then publish; requests already in flight keep running on the old version.
Routing & approval
- Conditions, thresholds, delegationBranch on value, document type or unit; exceed a threshold and a level is added automatically; delegate while someone is away.
- Parallel and sequential approvalSeveral units weigh in at once where they do not depend on each other, and in order where a later level needs to see the earlier decision.
- SLA & escalationEvery step has a clock; overdue steps are chased, then escalated upward exactly as the rules declare.
Evidence & operations
- A complete logEvery action records the person, the moment, the document version and the reason — enough to answer an audit question two years later.
- Tracking and bottlenecksSee where a request sits, who it waits on, and for how long; the steps that jam repeatedly surface as numbers.
- Runs on documents from every moduleThe same engine serves a leave request, a purchase request, a contract, a goods issue or an adjusting entry.
THE BOUNDARY WITH THE AGENT LAYER
An agent acts INSIDE the flow — it does not replace the flow.
A fair question once an organisation has agents: if the AI can do the work, what is the process for? It is what makes delegating to an agent safe in the first place.
The flow decides who may do what
An agent runs within the rights of the account that called it, and the delegated scope is declared on the flow itself — there is no shortcut around the process.
Work that needs approval still passes a person
The agent pre-fills, and writes what it was delegated to write; beyond that scope it stops at a proposal with citations, and the approval step stays an approval step.
The log records the agent too
The trail states which agent acted, under whose delegation, and who approved — in the same log as everything a person does.
FAQ
The boundaries of the workflow layer.
Is this another module?
No, deliberately so. A module owns one kind of business record; the workflow layer owns none — it makes the records of the other sixteen move. Splitting it out would create two places describing the same form.
How is it different from document signing in Digital administration?
Digital administration is a DOMAIN of documents: incoming and outgoing correspondence, seals, records retention. The workflow layer is the engine that domain — and every other — runs on. A document signing route is one specific flow built with this engine.
Can someone who does not code edit a flow?
The designer is drag-and-drop on a canvas, so people who know the business can build and change flows without writing code. Who may edit which flow is a permissions decision, and that rule is settled during implementation.
Can a step call an external system?
A step can call another system through an API to fetch data or push a result. Which systems are connected and how they authenticate is settled per project — the integrations page lists the classes of system supported.
Bring a process that is stuck to the demo.
Pick one real approval flow from your organisation — the demo rebuilds exactly that on sample data, with your current thresholds and approval levels.