Deployment Playbooks: What Goes in One

A deployment playbook is the written method that lets two crews who've never met produce installations you can't tell apart. Without one, your rollout is a series of personal interpretations; scale that across 300 sites and you've deployed 300 opinions. Here's what a real playbook contains.

1. Scope and site typology

What this playbook covers, and the site types it applies to. Large programs run one playbook per format, small store, flagship, office, because pretending formats don't differ is how steps get skipped.

2. Prerequisites

What must be true before the crew travels: site certified ready, kit delivery confirmed, access arranged, store notified, exceptions from the audit resolved. A crew dispatched against unmet prerequisites is a revisit being scheduled.

3. The method, step by step

Sequenced tasks with enough precision to exclude interpretation: mounting positions and heights, cable routing and dressing standards, labelling conventions, configuration steps that remain on-site (ideally none), and timings per step. Written for the engineer at 2 am, not the architect at their desk: short sentences, photos of done-right, warnings where sites bite.

4. Test and acceptance criteria

Exactly what gets tested and what passing looks like: transactions end to end, network checks, failover, printing. Binary criteria. A site passes or it isn't finished, and the playbook is where "finished" is defined.

5. The rollback

The step-by-step return to yesterday's working state, with its own test criteria and the decision rule for invoking it. A rollback that exists only as an intention is not a rollback.

6. Evidence requirements

Which photos from which angles, which results recorded, where it's all submitted. Evidence is how the program knows the playbook was followed, and how drift gets caught in week three instead of week thirty.

7. Exception handling

The pre-decided responses: site doesn't match audit, DOA device, access failure, time window collapsing. Each with an action and an escalation contact. Exceptions handled by rule cost minutes; exceptions improvised at 2 am cost the morning.

8. Communication scripts

Who the crew calls, what the store manager gets told at arrival and completion, what next-morning follow-up looks like. Consistent installations with inconsistent manners still generate complaints.

Keeping it alive

A playbook is a living document with a version number. The pilot writes its first real draft; every wave debrief revises it; every deviation logged in evidence is a proposed edit. Playbooks that stop changing while the program is live aren't stable, they're being ignored, and the evidence packs will show it if anyone looks.

The playbook is one of the four controls behind consistent deployment. It's also the cheapest: a document, maintained with discipline, standing between you and 300 opinions.

Want your next program run from a script? Speak to an expert.