A runbook template for recurring agency jobs

An SOP says what the job is. A runbook says what to do, step by step, when it breaks, for the person who has never done it.

Operations · 4 min read · Updated 2026-10-07

Fields to fill

  • Job name and the one result it produces.
  • Trigger: the date, time or event that starts the job, in the client's time zone.
  • Timing: how long the job takes, and the latest time it can finish before a deadline.
  • Inputs and access: the exact sheet, account or tool, and who grants the access.
  • Steps: numbered, one action each, with the check that proves the step is done.
  • Rollback: how to undo a step when its check fails, and who approves the undo.
  • Escalation: who to tell, through which channel, and after how long without an answer.
  • Log entry: where the run is recorded and what one line must contain.

Writing the steps

  • Start each step with a verb and keep one action per step.
  • Put the check on the same line as the step, not in a separate section.
Made-up scenario: a daily pull of store orders into the reporting sheet. Step 4 compares the row count with the store admin count for the same day. If they differ, the runbook says to keep the old sheet and tell the account lead before 10:00.

Testing it

  • Have someone who did not write it run the job from the page alone. Each question they ask marks a missing line.
  • Review the runbook after each incident, and at least once a quarter.

Tick it off

Your ticks stay in this browser only.

Built for shop owners, creators and agencies. Stock photos, not customers.

Run the next client review from one screen.

We open one agency at a time, with your own accounts connected read-only first.

Request access

How we plan to price it