Agency SOP Starter Pack (free, complete)

1 New client onboarding 2 Monthly reporting 3 Publishing content 4 Technical issue triage 5 Client escalation

SOP 1 — New client onboarding

4 tasks · phase 1 of 5

Trigger: contract signed
Steps: the onboarding checklist above, as a numbered procedure
Owner: account lead · Time budget: 5 working days
Done when: baseline saved, access complete, plan in the client's board

SOP 2 — Monthly reporting

4 tasks · phase 2 of 5

Trigger: 1st of the month
Steps: pull data → headline bullets → work summary → send by the 5th
Owner: each PM for their accounts
Done when: report link sent and logged on the client's project

SOP 3 — Publishing content

4 tasks · phase 3 of 5

Trigger: draft approved
Steps: on-page checklist → schema → interlinks → publish → submit URL
Owner: content lead
Done when: live URL passes the per-piece checklist

SOP 4 — Technical issue triage

4 tasks · phase 4 of 5

Trigger: audit finding or client report of a problem
Steps: reproduce → severity (traffic at risk?) → ticket with evidence → fix window by severity
Owner: whoever triages, explicitly named that week
Done when: verified fixed and noted on the client's board

SOP 5 — Client escalation

4 tasks · phase 5 of 5

Trigger: unhappy email/call, or two missed responses
Steps: acknowledge same day → facts before promises → call, not email → recovery plan in writing
Owner: account lead + one level up
Done when: client confirms the plan, follow-up dated

Make it run itself

A template on a page is a start. A template that assigns itself is a system.

Copy this into any tool you like — it's yours. But the failure mode of every checklist is the same: it lives in a doc nobody opens on the day the work happens. In PeakKR this template is a phased project: phases unlock in order, each task lands on a real person with a due date, and your client watches the phases complete on their own hub link instead of emailing "where are we?"

Create a project from the template — the phases and tasks above appear on the board, in order.
Assign the phase owners once. New tasks default to the project's PM; recurring ones respawn on schedule.
Share the client hub link. Progress, wins and reports at the same URL all engagement — no status meetings required.

FAQ

Using this template well

What makes a good SOP different from documentation?

A trigger and a definition of done. Documentation describes a system; an SOP says "when X happens, do these steps, and it's finished when Y is true." The five here all follow that shape — trigger, steps, owner, done — which is why they get used instead of archived.

Who should write the SOP — the owner or the person doing the work?

The person who does the work drafts it (they know the real steps); the owner edits for what "done" must mean. An SOP written top-down describes an imaginary process; the team quietly works around it within a month.

How do we keep SOPs from going stale?

Attach them where the work happens. An SOP linked on the actual recurring task gets re-read — and corrected — every time it runs; an SOP in a wiki folder is stale in a quarter. In PeakKR, SOPs attach directly to tasks so the current version is always one click from the person executing it.