# 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

1. Confirm the workflow has met the minimum time at its current level (section 2).
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.
3. 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.
4. Write the exception history (section 4), including every override and escalation above the agreed severity.
5. Define what changes at the new level: new limits, new approvals removed, monitoring added (section 5).
6. Agree demotion triggers (section 6) before the promotion, not after something goes wrong.
7. 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: ________

## Related

- [Clone Governance Charter](/playbook/templates/clone-governance-charter)
- [AI Risk Register](/playbook/templates/ai-risk-register)
- [Pilot Scorecard](/playbook/templates/pilot-scorecard)
- [Audit Evidence Pack](/playbook/templates/audit-evidence-pack)
- [Security & Governance at Clone Solutions](https://clone.org/solutions/security-governance)

---
From the Clone Solutions Playbook: https://solutions.clone.org/playbook/templates/autonomy-promotion-evidence-pack
