A pattern for standardizing recurring service delivery by pairing each service type with two linked artifacts: an SOP (the how-to guide) and a task template (the what-to-do checklist). Together they ensure consistent quality and execution across team members and client engagements.
| Artifact | Purpose | Owned By |
|---|---|---|
| SOP | How to do the work — technique, tools, standards | Operations / team lead |
| Task Template | What to do — subtasks, checklist, fields, links back to SOP | Account Manager / ops |
| Brief | Why this instance exists — client context, objective, traffic source, keywords | Account Manager |
The SOP and template are reusable across all clients. The brief is written fresh for each engagement and lives inside the task.
For any recurring service (e.g., landing page, SEO, blog post, Google Ads setup):
Account Manager writes a brief in the task description. At minimum it should cover:
- Client and objective
- Desired outcome
- Traffic source (Google Ads, Meta, organic, etc.)
- Key products, keywords, or content focus
AM schedules a 15-minute kickoff call with the team members who will execute. The Fathom recording is attached to the task. The brief and kickoff notes become the governing documents for the project.
Team executes against the task template, which contains:
- Subtasks covering every required step
- Assignee fields per subtask
- A link to the relevant SOP for reference
- The brief in the task description
Completed work lives in the client folder, making it findable and cloneable for future related work (e.g., a LinkedIn ad that needs to match a prior landing page's messaging).
Without this pattern, quality depends on individual memory and tribal knowledge. With it:
"If somebody pays us for SEO, there's 10 tasks that we need to do and we need to do those 10 tasks every time — to a certain level of quality every time." — Mark Hope
Start with the top 10 most frequently delivered services. Candidates identified in discussion:
Melissa Cusumano is responsible for finalizing this list. See action items in [1].
SOPs live in the Resources folder within the Operations space. The blueprint distinguishes between:
Each SOP entry should track: document link, last updated date, and owner.
As of the blueprint review meeting, SOPs for landing pages and blog posts were confirmed complete and shared with the ClickUp implementation team.