Autonomy Promotion Evidence Pack
The evidence and dual sign-off a Clone workflow needs to move up one level on the autonomy ladder, from Assist through Orchestrate.
What this is for
Autonomy is earned. A Clone gets more independence only when the evidence shows it is ready and two accountable people agree: the InfoSec lead, who owns the risk, and the business owner, who owns the work. This pack is the record of that decision. It turns "it seems to be working" into numbers on accuracy, overrides and exceptions, gives auditors a clean trail, and gives a cautious organization a reason to say yes.
When to use it
Every time a specific workflow on a specific Clone is proposed for the next level. Promotions are per workflow, not per Clone: a Support Clone can be at Execute within limits for ticket routing and at Recommend for refunds. One step at a time; no skipping levels.
Who's involved
- Business owner proposes the promotion and signs.
- InfoSec lead reviews risk and controls and signs.
- Champion gives the team's view on trust and readiness.
- GRC Specialist and the GRC Clone assemble and check the evidence.
- Implementation Engineer confirms configuration changes for the new level.
How to fill it in
- Confirm the workflow has met the minimum time at its current level (section 2).
- Pull the evidence for the review window from the audit log, approvals history and Adoption Dashboard (section 3). Use the full window, not the best week.
- Compare against the thresholds for this step (section 2). Thresholds start from the suggested values below and are set for your organization in the Clone Governance Charter.
- Write the exception history (section 4), including every override and escalation above the agreed severity.
- Define what changes at the new level: new limits, new approvals removed, monitoring added (section 5).
- Agree demotion triggers (section 6) before the promotion, not after something goes wrong.
- Both signatories sign. If either declines, the workflow stays at its current level and the pack records why.
The template
1. Promotion request
| Field | Entry |
|---|---|
| Clone | AP Intake Clone |
| Department | Finance & Accounting |
| Workflow | Code and post vendor invoices under the PO match rule |
| Current level | 3 – Execute with approval |
| Proposed level | 4 – Execute within limits |
| Date at current level since | Day 68 |
| Review window | Day 68 to Day 124 (8 weeks) |
| Volume in window | 1,140 invoices |
| Requested by | Business owner, Finance |
| Governance Charter version | v1.2 |
2. Evidence required per ladder step
Suggested starting thresholds. Your Governance Charter sets the binding numbers; record them in the "Your threshold" column.
| Step | Minimum time at current level | Accuracy | Override rate | Exception history | Other evidence | Your threshold |
|---|---|---|---|---|---|---|
| 1 Assist → 2 Recommend | 4 weeks and 50+ tasks | 90%+ on test scenarios; 85%+ drafts accepted with light or no edits | n/a (no actions taken) | No incidents above agreed severity | Users report drafts as useful (pulse ≥ 3.5 / 5) | |
| 2 Recommend → 3 Execute with approval | 4 weeks and 100+ recommendations | 92%+ recommendations correct on sample review | 15% or less of recommendations overridden | All overrides categorized; no repeated failure pattern | Named approvers and approval channel set | |
| 3 Execute with approval → 4 Execute within limits | 8 weeks and 200+ approved actions | 97%+ actions approved without edit | 5% or less rejected or edited | Zero incidents above agreed severity; every exception escalated correctly | Written limits (amounts, counts, data types); clean audit log review by InfoSec; escalation path tested | |
| 4 Execute within limits → 5 Orchestrate | 12 weeks at level 4 | 98%+ on monthly sampled audit | 2% or less overridden on sampled actions | No missed escalations; exceptions trending flat or down | Monitoring and human override tested end to end in Commander; reviewed at the quarterly business review with InfoSec |
3. Evidence for this request
| Metric | Threshold | Result in window | Met? | Source |
|---|---|---|---|---|
| Time at current level | 8 weeks / 200 actions | 8 weeks / 1,140 actions | Yes | Portal autonomy history |
| Accuracy (approved without edit) | 97% | 98.4% | Yes | Approvals history |
| Override rate (rejected or edited) | ≤5% | 1.6% | Yes | Approvals history |
| Incidents above agreed severity | 0 | 0 | Yes | Incident log |
| Exceptions escalated correctly | 100% | 100% (23 of 23) | Yes | Audit log |
| Audit log review | Clean | Clean, reviewed Day 120 | Yes | InfoSec review note |
| Sample audit size | 5% or 50, whichever is more | 60 | Yes | GRC sample |
4. Exception history
| Date | What happened | Severity | Caught by | Root cause | Fix | Recurred? |
|---|---|---|---|---|---|---|
| Day 81 | Invoice coded to wrong cost center; approver edited | Low | Approver | New cost center missing from knowledge | Knowledge updated Day 82 | No |
Summary of overrides by category:
| Category | Count | % of overrides | Action taken |
|---|---|---|---|
| Missing or stale knowledge | |||
| Ambiguous source document | |||
| Judgment call the person preferred to make | |||
| Clone error |
5. What changes at the new level
| Item | Current | Proposed |
|---|---|---|
| Who approves each action | AP Manager, every invoice | None within limits; AP Manager for exceptions |
| Limits | n/a | Invoices ≤ the agreed amount, PO matched within 2% tolerance, existing vendors only |
| Escalates to a person when | n/a | Outside any limit, new vendor, bank detail change, duplicate suspected |
| Never allowed (unchanged) | Change vendor bank details; approve payment runs | Same |
| Monitoring | Approval queue | Weekly 5% sample audit; daily exception digest to AP Manager |
| Configuration changes | Approval rule removed for in-limit invoices; limits set; audit sample scheduled |
6. Demotion triggers
The workflow drops back one level automatically, pending review, if any of these occur:
- Any incident above the agreed severity
- Override rate on sampled actions above ____% for two consecutive weeks
- A missed escalation (an out-of-limit action taken without escalating)
- A material change to the connected system, skill version or data source that has not passed testing
- Either signatory requests it
7. Team view
| Question | Champion's answer |
|---|---|
| Does the team trust the Clone at the next level? | |
| What would make them more confident? | |
| Has the team been told what will change? |
Good looks like
- Both signatures, every time. Neither the InfoSec lead nor the business owner can sign for the other, and either can decline.
- Evidence covers the whole review window and a meaningful volume, not a cherry-picked week.
- Overrides are categorized. "The person preferred to decide" is different from "the Clone was wrong".
- Limits are written in numbers and data types, not "low-risk items".
- Demotion triggers are agreed before promotion, so stepping back is routine, not a crisis.
- Common mistake: promoting a whole Clone. Promote one workflow at a time.
How Clone helps
The GRC Clone assembles the pack from the audit log, approval history and incident log, computes accuracy and override rates for the window, flags any threshold not met, and drafts the exception summary. The portal records each promotion against the workflow's autonomy history, blocks the level change until both sign-offs are recorded, and shows autonomy level by department in the steering pack. The Project Clone schedules the review and the post-promotion check at 30 days.
Sign-off
Both signatures are required. A promotion is not approved until both are recorded.
| Role | Name | Date | Decision | Conditions |
|---|---|---|---|---|
| InfoSec lead | Approve / Decline / Approve with conditions | |||
| Business owner | Approve / Decline / Approve with conditions | |||
| GRC Specialist (evidence verified) | Verified |
Effective date of new level: ____ · 30-day post-promotion review date: ____