Clone Solutions
Template

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

FieldEntry
CloneAP Intake Clone
DepartmentFinance & Accounting
WorkflowCode and post vendor invoices under the PO match rule
Current level3 – Execute with approval
Proposed level4 – Execute within limits
Date at current level sinceDay 68
Review windowDay 68 to Day 124 (8 weeks)
Volume in window1,140 invoices
Requested byBusiness owner, Finance
Governance Charter versionv1.2

2. Evidence required per ladder step

Suggested starting thresholds. Your Governance Charter sets the binding numbers; record them in the "Your threshold" column.

StepMinimum time at current levelAccuracyOverride rateException historyOther evidenceYour threshold
1 Assist → 2 Recommend4 weeks and 50+ tasks90%+ on test scenarios; 85%+ drafts accepted with light or no editsn/a (no actions taken)No incidents above agreed severityUsers report drafts as useful (pulse ≥ 3.5 / 5)
2 Recommend → 3 Execute with approval4 weeks and 100+ recommendations92%+ recommendations correct on sample review15% or less of recommendations overriddenAll overrides categorized; no repeated failure patternNamed approvers and approval channel set
3 Execute with approval → 4 Execute within limits8 weeks and 200+ approved actions97%+ actions approved without edit5% or less rejected or editedZero incidents above agreed severity; every exception escalated correctlyWritten limits (amounts, counts, data types); clean audit log review by InfoSec; escalation path tested
4 Execute within limits → 5 Orchestrate12 weeks at level 498%+ on monthly sampled audit2% or less overridden on sampled actionsNo missed escalations; exceptions trending flat or downMonitoring and human override tested end to end in Commander; reviewed at the quarterly business review with InfoSec

3. Evidence for this request

MetricThresholdResult in windowMet?Source
Time at current level8 weeks / 200 actions8 weeks / 1,140 actionsYesPortal autonomy history
Accuracy (approved without edit)97%98.4%YesApprovals history
Override rate (rejected or edited)≤5%1.6%YesApprovals history
Incidents above agreed severity00YesIncident log
Exceptions escalated correctly100%100% (23 of 23)YesAudit log
Audit log reviewCleanClean, reviewed Day 120YesInfoSec review note
Sample audit size5% or 50, whichever is more60YesGRC sample

4. Exception history

DateWhat happenedSeverityCaught byRoot causeFixRecurred?
Day 81Invoice coded to wrong cost center; approver editedLowApproverNew cost center missing from knowledgeKnowledge updated Day 82No

Summary of overrides by category:

CategoryCount% of overridesAction taken
Missing or stale knowledge
Ambiguous source document
Judgment call the person preferred to make
Clone error

5. What changes at the new level

ItemCurrentProposed
Who approves each actionAP Manager, every invoiceNone within limits; AP Manager for exceptions
Limitsn/aInvoices ≤ the agreed amount, PO matched within 2% tolerance, existing vendors only
Escalates to a person whenn/aOutside any limit, new vendor, bank detail change, duplicate suspected
Never allowed (unchanged)Change vendor bank details; approve payment runsSame
MonitoringApproval queueWeekly 5% sample audit; daily exception digest to AP Manager
Configuration changesApproval 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

QuestionChampion'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.

RoleNameDateDecisionConditions
InfoSec leadApprove / Decline / Approve with conditions
Business ownerApprove / Decline / Approve with conditions
GRC Specialist (evidence verified)Verified

Effective date of new level: ____ · 30-day post-promotion review date: ____