TemplateGo-Live Checklist
The gate every department passes before its Clones go live, covering readiness, security, people, comms and rollback in one signed checklist.
#What this is for
A go-live is the moment a Clone stops being a pilot and starts doing real work for a whole department. Most failed rollouts fail here: a connection nobody re-checked, a team that never heard the announcement, or no plan for what happens if something goes wrong on day two. This checklist makes launch a deliberate decision with named owners, not a date on a calendar.
#When to use it
Once per department, during the Launch stage of the six-week rollout cycle, after the pilot scorecard shows accuracy and adoption above threshold. Re-run it whenever a live Clone gets a new connection, a new channel or a new skill that touches production data.
#Who's involved
- Implementation Engineer completes the technical sections.
- Change & Enablement Lead and the department Champion complete the people and comms sections.
- InfoSec lead confirms security items and signs.
- Business owner makes the go / no-go call and signs.
#How to fill it in
- Copy the template into the department's workspace in the portal. The Project Clone pre-fills Clone names, skills and connections from the Clone Design Spec.
- Work through each section. Every item needs an owner and evidence (a link, a screenshot or a test result), not just a tick.
- Mark any item that cannot be met as a blocker or an accepted exception. Exceptions need a named owner and a date.
- Hold a 45-minute go / no-go review with the business owner, InfoSec lead, Champion and Implementation Engineer.
- Record the decision. On "go", the Project Clone opens the hypercare log and schedules the day-7 and day-30 checks.
#The template
#Launch summary
| Field | Entry |
|---|
| Department | Customer Support |
| Business owner | |
| Champion | |
| Clones going live | Support Triage Clone, Returns Clone |
| Starting autonomy level | Recommend (level 2) |
| Users in scope | 62 agents and 4 team leads |
| Channels | Slack, email, Clone Team Studio |
| Planned go-live date | |
| Hypercare window | 10 business days |
| Pilot scorecard link | /playbook/templates/pilot-scorecard |
#1. Readiness evidence
- Department Opportunity Brief approved and linked
- Clone Design Spec approved, version noted: __
- All test scenarios passed (link to test scenario pack results)
- Pilot accuracy at or above threshold: __% (threshold __%)
- Pilot adoption at or above threshold: ____% of pilot users active weekly
- Open defects from pilot: none above "minor", or each has an owner and date
- Baseline metrics captured for every metric on the scorecard
#2. Clone configuration
| Item | Clone | Status | Evidence | Owner |
|---|
| Role and instructions final | Support Triage Clone | Done | Spec v1.3 | Implementation Engineer |
| Knowledge loaded and current | | | | |
| Skills enabled match the design spec (nothing extra) | | | | |
| Skill versions pinned for production | | | | |
| Schedules set and tested | | | | |
| Approval rules match the autonomy level | | | | |
| Escalation owner set and reachable | | | | |
#3. Security and access
- Every connection on the Connections & Permissions Plan is approved by InfoSec
- Connections use least-privilege scopes; no personal admin tokens in production
- User access is set by role (who can chat with, configure or administer each Clone)
- Single sign-on enforced for all users in scope
- Audit logging confirmed on for every Clone going live; test entry located
- Data the Clone must never touch is listed in the Governance Charter and tested
- AI Risk Register updated for this department's use cases
#4. People and training
- Champion has completed Champion certification
- Department role training scheduled or complete: ____% of users trained
- Team leads briefed on approvals, overrides and how to report a problem
- Office hours booked for the first two weeks
- How-to videos for the top three tasks published
#5. Communications
- Launch announcement drafted and approved by the sponsor or business owner
- "Capacity, not replacement" FAQ shared with the department
- Where to get help is clear: Champion, channel, office hours
- Launch date shared with adjacent teams who receive handoffs
#6. Operations and rollback
| Item | Detail | Owner |
|---|
| Hypercare contact (first 10 days) | | |
| How to pause a Clone | Business owner or org admin pauses; Implementation Engineer notified | |
| How to revoke a connection | | |
| Rollback plan | Revert to previous pinned skill version; drop to Assist level | |
| Incident severity scale agreed | Per Governance Charter | |
| Day-7 check booked | | |
| Day-30 check booked | | |
#7. Blockers and accepted exceptions
| # | Item | Blocker or exception | Mitigation | Owner | Due |
|---|
| 1 | Returns Clone ERP write scope pending | Exception: Returns Clone launches read-only | Write scope reviewed at day 30 | IT lead | Day 30 |
#Go / no-go
| Question | Yes / No |
|---|
| Are all blockers closed? | |
| Is every exception owned and dated? | |
| Does the department know it is launching and where to get help? | |
| Can we pause or roll back within one business hour? | |
#Good looks like
- Every tick has evidence behind it. "Done" with no link is not done.
- The starting autonomy level matches what the pilot proved, not what the department hopes for.
- Rollback has been rehearsed once, not just written down.
- Exceptions are rare, named and dated. A list of ten exceptions is a "no-go".
- Adjacent teams are told. Handoff surprises are the most common day-two complaint.
- Common mistake: launching with skills enabled "just in case". Ship only what the design spec approved.
#How Clone helps
The Project Clone pre-fills the checklist from the design spec and pilot scorecard, chases owners for missing evidence, and records the decision in the portal, where the department's status moves to "Live". The GRC Clone cross-checks connections and audit log status against the Connections & Permissions Plan and flags any gap to the InfoSec lead. The Enablement Clone reports training completion for the people section.
#Sign-off
| Role | Name | Date | Decision |
|---|
| Business owner | | | Go / No-go / Go with exceptions |
| InfoSec lead | | | Approved / Not approved |
| Champion | | | Ready / Not ready |
| Implementation Engineer | | | Ready / Not ready |