Clone Solutions
Template

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

FieldEntry
Clone nameBilling Clone
DepartmentFinance & Accounting
Role / purposeResearches billing disputes and issues credit memos within limits
Business owner
Escalation ownerAR Manager
Champion
Technical owner (org admin / CoE)
Created fromMarketplace template + 1 custom skill
Autonomy level(s) by workflowCredit memos within limits: 4; write-offs: 2
ChannelsSlack #ar-billing, email, Commander handoffs
Governance Charter entryLink
Design spec versionv2.1

2. Configuration

Skills

SkillSourceVersion (pinned)PurposeTest pack
ERP AR PostingCustom (SkillForge)v1.1Create credit memos12 scenarios
HelpdeskMarketplacev2.3Read dispute tickets6 scenarios

Connections

SystemAccount typeScopeApproved byReview due
ERPService accountAR read; credit memo create; no paymentsInfoSec lead

Knowledge

SourceWhat it coversOwnerRefresh
Credit policy v4Limits, reasons, approvalsControllerOn change

Schedules and triggers

NameWhenWhat it does
Morning dispute sweepWeekdays 7:00Pulls new billing tickets and prepares research
Handoff from Support CloneEventStarts dispute workflow

3. Limits and boundaries

ItemEntry
Acts on its own whenCredit within agreed threshold, existing customer, invoice under 120 days, one credit per invoice
Asks a person whenAnything outside a limit; customer mentions legal action
Never allowedChange bank details; issue payments; write off balances
Data it must not useCard numbers; employee data

4. Routine operations

TaskFrequencyStepsHealthy looks likeOwner
Check Clone HealthDaily (weekdays)Open the Clone in Clone Team Studio; review health and failed tasksNo failed tasks older than 1 dayOrg admin
Review exception digestDailyRead digest in #ar-billing; resolve or reassignAll exceptions actioned same dayAR Manager
Sample auditMonthlyPull 5% of within-limits actions; check against policy; log result98%+ correctAR Manager + CoE
Power Rating and usage reviewMonthlyReview trend; note drops; check credit usageStable or rising; usage in line with volumeCoE
Knowledge freshnessQuarterly or on policy changeConfirm sources are current; updateNo stale policyBusiness owner
Connection and access reviewQuarterlyConfirm scopes and users match the planNo driftInfoSec + org admin

5. Troubleshooting

SymptomLikely causeCheckFixEscalate to
Clone says it cannot reach the ERPExpired or revoked connectionConnection status in settingsReconnect with the approved service accountIT lead if account locked
Wrong cost center or reason codesStale knowledgeCompare to current credit policyUpdate knowledge; re-run test scenariosBusiness owner
Skill errors after a system upgradeUpstream API changeSkill error message; recent system changesRoll back to prior pinned version or pause workflow; raise with lead builderLead builder
Clone acted outside a limitLimit misconfigured or new edge caseAudit log entryPause the workflow; apply demotion trigger; incident reviewInfoSec lead + business owner
Scheduled task did not runSchedule disabled or creditsSchedule settings; credit balanceRe-enable; review credit settingsOrg admin
Users say answers are vagueInstructions or knowledge gapRead recent conversationsTighten instructions; add examplesChampion

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 actionHowWho can do it
Revert a skillRe-pin previous versionLead builder / org admin
Reduce autonomyRestore approval rule; drop one levelOrg admin, on request of InfoSec or business owner
Pause the ClonePause in Clone Team Studio; notify Champion and escalation ownerOrg admin, InfoSec lead, business owner
Cut accessRevoke the connectionOrg admin, IT lead

Change log:

DateChangeVersionApproved byTestedRollback to

7. Contacts

NeedWhoHow
Business question about the Clone's workBusiness owner
User helpChampion
Technical fixOrg admin / CoE
Security concern or incidentInfoSec lead
Platform supportClone supportsupport.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

RoleNameDateDecision
Business ownerPurpose and limits confirmed
CoE leadAccepted for operation
Org adminHandoff verified
Implementation EngineerHanded over