Implementation Guide

System / change being rolled out: [What is being implemented] Audience: [Who follows this guide] Owner: [Name, role] Sponsor / approver: [Name, role] Version: [Guide version] Last reviewed: [Date]

---

1. Overview and prerequisites

[In 2-3 sentences: what is being rolled out, to whom, and the headline risk. Then list what must already be true before anyone starts.]

Prerequisites:

• [Access and admin rights for every system the steps touch]
• [Key decisions settled (chosen tool, agreed configuration)]
• [Source data, credentials, and inputs gathered and validated]
• [Target environment exists and is reachable]
• [Restore point / known-good state captured]
• [Owners named for each phase; go / no-go approver identified]

2. Roles

Role	Name	Responsibility
Implementation owner	[Name]	[Runs the procedure, makes go / no-go calls]
Technical lead	[Name]	[Configuration and migration]
Validator	[Name]	[Runs acceptance checks]
Approver / sponsor	[Name]	[Signs off cutover]
Operating team contact	[Name]	[Receives handover]

3. Step-by-step phases

[Each row is one step, in order, with an owner and the result that proves it worked.]

Phase	Step	Action	Owner	Expected result
Prepare	1	[e.g. Provision accounts and licences]	[Name]	[All users can sign in]
Prepare	2	[e.g. Capture restore point]	[Name]	[Backup confirmed]
Configure	3	[e.g. Apply agreed settings]	[Name]	[Settings match Section 4]
Migrate	4	[e.g. Load source data]	[Name]	[Record counts reconcile]
Validate	5	[e.g. Run acceptance checks]	[Name]	[All checks in Section 5 pass]
Cut over	6	[e.g. Move pilot group, then widen]	[Name]	[Pilot users working, no blockers]
Stabilise	7	[e.g. Monitor for settling period]	[Name]	[No new blockers for N days]

4. Configuration checklist

Setting	Required value	Confirmed
[Setting name]	[Value it should hold]	[ ]
[Setting name]	[Value it should hold]	[ ]
[Setting name]	[Value it should hold]	[ ]

5. Validation / acceptance criteria

[The specific, observable checks that prove the system is fit to use. Define pass in advance.]

• [A real user can sign in]
• [A record saved appears correctly]
• [A migrated record matches its source field for field]
• [A key report returns the expected numbers]
• [Integrations exchange data as expected]

6. Training and handover

Training:

Group	Focus	Format	When
Day-to-day users	[The few tasks they perform]	[Session / guide]	[Before cutover]
Support / operators	[How it runs and how to fix it]	[Session / docs]	[Before handover]

Handover checklist:

• [Documentation delivered, including this guide and any operation manual]
• [Accounts and ownership transferred to the operating team]
• [Support routes and escalation path agreed]
• [Open issues listed honestly with owners]
• [Named person on each side confirms handover complete]

7. Troubleshooting

Symptom	Likely cause	Fix
[What the reader sees]	[Why it happens]	[What to do]
[What the reader sees]	[Why it happens]	[What to do]

8. Rollback

Trigger: [The condition that means stop and revert, e.g. validation fails for a critical check.]

Steps to revert:

1. [Return to the known-good state captured in the prepare phase]
2. [Restore source-system access for affected users]
3. [Any data clean-up the revert requires]

Notes: [Irreversible steps, data risks, and who authorises a rollback.]