uControlApproval, Sign-off & Audit Trail
Approval, Sign-off & Audit Trail
The four states
Every section walks through the same four-state lifecycle:
Draft | Editable. Editors can change anything. Submit when ready. |
|---|---|
Submitted | Locked for editing. The customer’s Manager is the next reviewer. |
Manager Approved | Still locked. The Partner reviewer is the next sign-off. |
Final | Fully signed off and locked. Only a Reject can reopen it. |
Who can do what
| Edit (Draft) | Approve manager step | Approve Partner step |
|---|---|---|---|
Viewer | — | — | — |
Editor | Yes | — | — |
Manager | Yes | Yes | — |
Partner | Yes | Yes | Yes |
Administrator | Yes | Yes | Yes |
The Reject action
Either reviewer can reject a section back to Draft. The reject form requires a\nshort reason — the editor sees this reason on the section page and a copy lands\nin the audit trail. Rejecting clears the previously-recorded approver details so the\nnext round of approval starts clean, but historical approvals stay in the audit log\nforever.
Approval on the Workflows section
The Workflows section is special — sign-off happens per-workflow, not\nsection-wide. Open each workflow’s detail page to submit, approve and finalise\nit individually. The engagement overview shows the section as an X of Y\napproved roll-up.
Approval notes
Both approval steps (Manager Approved and Final) accept an optional note. Common\nuses:
“Holiday list cross-checked against the 2026 calendar — confirmed.”
“Approved subject to the additional row added on 2026-05-15 going through\n on the next round.”
“Pre-prod environment validated.”
Notes are visible alongside the approver’s name on the section’s\nApproval card.
The audit trail
Every state change, every edit, every approval and every rejection is captured with:
Actor — the logged-in user.
Timestamp — second-precision UTC.
Entity — what changed (Section, Workflow, Category row,\n etc.).
Action — create / update / submit / approve / reject /\n delete / ai-apply / etc.
Before / After — the full previous and new values for\n updates.
Notes — any reviewer note or AI rationale.
The 20 most recent audit entries are shown on the engagement’s overview page.\nThe full log is reachable from there.
Reading the audit trail
The audit trail is the source of truth for “who did what, when”. When\nthe customer asks how a particular SLA target got set, search the audit log for the\nSLA row’s id — you’ll see the create, every update, the submit, both\napprovals, and any subsequent reject / re-approve cycles.