# Clone Runbook

The operating manual for one production Clone, covering what it does, how it is configured, routine checks, common failures, change control and who to call.

## What this is for

When the Clone team steps back, your people need to run every production Clone confidently: know what it is supposed to do, spot when it is not, fix the common problems and change it safely. A runbook per Clone makes that possible. It is written for the org admin or CoE builder who was not in the room when the Clone was designed, and it is the core of the handoff documentation at Month 12.

## When to use it

Start a runbook at each Clone's go-live; the go-live checklist already captures most of section 2. Complete and verify all runbooks in Months 10–12. Update a runbook whenever the Clone's skills, connections, schedules or autonomy level change.

## Who's involved

- **Implementation Engineer** writes the first version.
- **Org admin** and **CoE builders** become the owners and verify it by running it.
- **Business owner** confirms purpose, limits and escalation.
- **Champion** adds the common user questions.

## How to fill it in

1. Copy the template for each production Clone.
2. Fill in sections 1–3 from the Clone Design Spec, Governance Charter and Integration Architecture. Link rather than duplicate where you can, but keep the essentials here.
3. Write routine operations (section 4) as steps someone can follow without help.
4. Build the troubleshooting table (section 5) from real issues seen in pilot and hypercare.
5. Record change control and rollback (section 6).
6. Verify: a CoE member runs one routine check and one troubleshooting step using only the runbook. Fix whatever they had to ask about.

## The template

### 1. Clone profile

| Field | Entry |
|---|---|
| Clone name | _Billing Clone_ |
| Department | _Finance & Accounting_ |
| Role / purpose | _Researches billing disputes and issues credit memos within limits_ |
| Business owner | |
| Escalation owner | _AR Manager_ |
| Champion | |
| Technical owner (org admin / CoE) | |
| Created from | _Marketplace template + 1 custom skill_ |
| Autonomy level(s) by workflow | _Credit memos within limits: 4; write-offs: 2_ |
| Channels | _Slack #ar-billing, email, Commander handoffs_ |
| Governance Charter entry | _Link_ |
| Design spec version | _v2.1_ |

### 2. Configuration

**Skills**

| Skill | Source | Version (pinned) | Purpose | Test pack |
|---|---|---|---|---|
| _ERP AR Posting_ | _Custom (SkillForge)_ | _v1.1_ | _Create credit memos_ | _12 scenarios_ |
| _Helpdesk_ | _Marketplace_ | _v2.3_ | _Read dispute tickets_ | _6 scenarios_ |

**Connections**

| System | Account type | Scope | Approved by | Review due |
|---|---|---|---|---|
| _ERP_ | _Service account_ | _AR read; credit memo create; no payments_ | _InfoSec lead_ | |

**Knowledge**

| Source | What it covers | Owner | Refresh |
|---|---|---|---|
| _Credit policy v4_ | _Limits, reasons, approvals_ | _Controller_ | _On change_ |

**Schedules and triggers**

| Name | When | What it does |
|---|---|---|
| _Morning dispute sweep_ | _Weekdays 7:00_ | _Pulls new billing tickets and prepares research_ |
| _Handoff from Support Clone_ | _Event_ | _Starts dispute workflow_ |

### 3. Limits and boundaries

| Item | Entry |
|---|---|
| Acts on its own when | _Credit within agreed threshold, existing customer, invoice under 120 days, one credit per invoice_ |
| Asks a person when | _Anything outside a limit; customer mentions legal action_ |
| Never allowed | _Change bank details; issue payments; write off balances_ |
| Data it must not use | _Card numbers; employee data_ |

### 4. Routine operations

| Task | Frequency | Steps | Healthy looks like | Owner |
|---|---|---|---|---|
| Check Clone Health | Daily (weekdays) | _Open the Clone in Clone Team Studio; review health and failed tasks_ | _No failed tasks older than 1 day_ | _Org admin_ |
| Review exception digest | Daily | _Read digest in #ar-billing; resolve or reassign_ | _All exceptions actioned same day_ | _AR Manager_ |
| Sample audit | Monthly | _Pull 5% of within-limits actions; check against policy; log result_ | _98%+ correct_ | _AR Manager + CoE_ |
| Power Rating and usage review | Monthly | _Review trend; note drops; check credit usage_ | _Stable or rising; usage in line with volume_ | _CoE_ |
| Knowledge freshness | Quarterly or on policy change | _Confirm sources are current; update_ | _No stale policy_ | _Business owner_ |
| Connection and access review | Quarterly | _Confirm scopes and users match the plan_ | _No drift_ | _InfoSec + org admin_ |

### 5. Troubleshooting

| Symptom | Likely cause | Check | Fix | Escalate to |
|---|---|---|---|---|
| _Clone says it cannot reach the ERP_ | _Expired or revoked connection_ | _Connection status in settings_ | _Reconnect with the approved service account_ | _IT lead if account locked_ |
| _Wrong cost center or reason codes_ | _Stale knowledge_ | _Compare to current credit policy_ | _Update knowledge; re-run test scenarios_ | _Business owner_ |
| _Skill errors after a system upgrade_ | _Upstream API change_ | _Skill error message; recent system changes_ | _Roll back to prior pinned version or pause workflow; raise with lead builder_ | _Lead builder_ |
| _Clone acted outside a limit_ | _Limit misconfigured or new edge case_ | _Audit log entry_ | _Pause the workflow; apply demotion trigger; incident review_ | _InfoSec lead + business owner_ |
| _Scheduled task did not run_ | _Schedule disabled or credits_ | _Schedule settings; credit balance_ | _Re-enable; review credit settings_ | _Org admin_ |
| _Users say answers are vague_ | _Instructions or knowledge gap_ | _Read recent conversations_ | _Tighten instructions; add examples_ | _Champion_ |

### 6. Change control and rollback

- [ ] Every change goes through the CoE change review (skill version, connection, schedule, limits, instructions)
- [ ] Skill upgrades are tested against the test pack before production
- [ ] New connections and scope changes are approved by InfoSec
- [ ] Autonomy changes require an evidence pack and dual sign-off (InfoSec lead and business owner)

| Rollback action | How | Who can do it |
|---|---|---|
| Revert a skill | _Re-pin previous version_ | _Lead builder / org admin_ |
| Reduce autonomy | _Restore approval rule; drop one level_ | _Org admin, on request of InfoSec or business owner_ |
| Pause the Clone | _Pause in Clone Team Studio; notify Champion and escalation owner_ | _Org admin, InfoSec lead, business owner_ |
| Cut access | _Revoke the connection_ | _Org admin, IT lead_ |

Change log:

| Date | Change | Version | Approved by | Tested | Rollback to |
|---|---|---|---|---|---|
| | | | | | |

### 7. Contacts

| Need | Who | How |
|---|---|---|
| Business question about the Clone's work | Business owner | |
| User help | Champion | |
| Technical fix | Org admin / CoE | |
| Security concern or incident | InfoSec lead | |
| Platform support | Clone support | _support.clone.org_ |

### 8. Handoff verification

- [ ] A CoE member ran one routine check using only this runbook
- [ ] A CoE member resolved one troubleshooting scenario using only this runbook
- [ ] Rollback rehearsed in a test or low-risk window
- [ ] All links work and owners are current

## Good looks like

- Written for someone who was not there. If a step needs a verbal explanation, the step is incomplete.
- Troubleshooting comes from real incidents, not imagined ones.
- Limits and "never allowed" are repeated here, not only in the charter. Operators need them at hand.
- Rollback is specific and has been rehearsed.
- Owners are people with names, not teams.
- Common mistake: one runbook for "all Clones". Each production Clone needs its own; shared procedures can be linked.

## How Clone helps

The **Enablement Clone** drafts each runbook from the design spec, Governance Charter, Integration Architecture and hypercare log, and keeps it current when configuration changes. It also answers operators' how-to questions with the runbook as its source. The **Project Clone** tracks runbook completion and handoff verification per Clone in the portal, which feeds the Handoff Documentation deliverable.

## Sign-off

| Role | Name | Date | Decision |
|---|---|---|---|
| Business owner | | | Purpose and limits confirmed |
| CoE lead | | | Accepted for operation |
| Org admin | | | Handoff verified |
| Implementation Engineer | | | Handed over |

## Related

- [Integration Architecture](/playbook/templates/integration-architecture)
- [Clone Design Spec](/playbook/templates/clone-design-spec)
- [CoE Charter](/playbook/templates/coe-charter)
- [When a skill isn't working](https://support.clone.org/articles/when-a-skill-isnt-working)
- [How credits work](https://support.clone.org/articles/how-credits-work)

---
From the Clone Solutions Playbook: https://solutions.clone.org/playbook/templates/clone-runbook
