Source of truth
One working record is authoritative for current state.
The Operaitions method
Start with the operating model. Automate only inside its boundaries.
Reliable workflow systems make state, ownership, due work, decisions, and evidence visible. The technology serves that model—not the other way around.
Explicit state
Work moves through named states rather than implied progress.
Named ownership
Every queue item and decision has a responsible operator.
Due work
Dates create a visible queue instead of relying on memory.
Grounded drafting
Drafts use recorded facts and expose missing context.
Proportional approval
Higher-risk actions receive stronger human control.
Exception handling
Conflicts and failures pause safely and stay visible.
External action control
Human sending remains explicit where relationships matter.
Audit history
Evidence records what changed, when, and why.
Safe recovery
Retries avoid duplicate effects and preserve prior evidence.
Delivery sequence
Five stages, with working rules defined before live use
Each implementation centres on one operational loop. Checks cover the normal route and the points where work should pause.
- Understand current workMap the source, real states, owners, dates, channels, and known failure points.
- Define the control modelAgree what can be prepared, what needs approval, what stays manual, and what evidence closes each step.
- Configure the workflowBuild the queue, transitions, drafts, exception paths, and audit write-back around the existing tools.
- Run acceptance checksTest normal cases, missing data, duplicates, failed actions, retries, and recovery.
- Handover and reviewGive the operator a runbook, then inspect real use before widening scope.
A critical distinction
Approved is not sent
A draft can be approved and still require a manual external action. The state changes to sent only when there is send evidence. The next action is then dated so the relationship never disappears from view.
Draft readyApprovedManual sendEvidence loggedNext action
Exceptions and recovery
When context is missing, the workflow pauses and shows the reason.
Conflicting records, duplicate candidates, and failed updates stay attached to the affected item for review.
- Pause the affected item while the rest of the queue continues
- Show the reason to the named owner
- Retry only when it cannot create duplicate work
- Preserve the earlier record when the current view changes
- Resume from the last confirmed step
See the method applied