Document workflow automation and approval chains

A workflow template describes the steps a document type must pass through and who approves each one. Configure it once and every document of that type follows the same path, which is the point: consistency is what an auditor samples for, and consistency is impossible when each approval is arranged individually.

Templates are built visually rather than in configuration files, so the person who owns the process can change it without raising a ticket. That matters because a process that is hard to change is a process that gets bypassed.

A step can require one named approver, anyone holding a role, or several approvers in sequence or in parallel. Sequential chains suit escalating authority — a manager then a director then a committee. Parallel steps suit independent review, where legal and technical sign-off do not depend on each other and forcing them into a queue only adds days.

Approval thresholds can vary by a metadata value, so an invoice under a limit clears with one approval while one above it routes to a second. Encoding the threshold in the workflow rather than in a policy document is the difference between a rule and a hope.

Each document running through a template is an instance with its own state. The instance records who acted at each step, when, what they decided and any comment they left. Reassignment is explicit and logged, which is how you handle the reality of holidays and leavers without the trail going quiet.

Every user has a personal queue of the instances waiting on them. A workflow whose participants have to go looking for their tasks is one that stalls, and stalled approvals are the reason document control projects lose credibility in their first quarter.

Reminders go out on a schedule you set per template, and an unactioned step can escalate to a named alternative. This is unglamorous and it is where most of the value sits: the difference between a two-day approval and a two-week one is almost never the approver’s decision time.

Notifications arrive in the application in real time over WebSocket and by email, and users can watch a document to receive updates without being a participant in its workflow.

Acknowledgement is a workflow with one step repeated across a population: publish a policy version, require every affected user to attest they have read it, and track completion. The record is per named user against a specific version, which is what makes it evidence rather than a claim that "the policy was circulated".

When a policy is superseded, the acknowledgement requirement can be reissued automatically, because an attestation against version 3 says nothing about version 4.

A workflow does not stop at approval. Retention policy automation attaches the appropriate retention rule when a document reaches its approved state, sets the disposition review date, and raises a review task when that date arrives rather than deleting silently.

Treating retention as the last step of the workflow rather than a separate administrative exercise is what keeps a retention schedule accurate a year after it was written.