---
title: ClickUp SOP & Template Pattern
type: article
created: '2026-04-05'
updated: '2026-04-05'
source_docs:
- raw/2025-10-21-clickup-blueprint-feedback-business-development-95678463.md
tags:
- clickup
- sop
- workflow
- operations
- templates
- service-delivery
layer: 2
client_source: null
industry_context: null
transferable: true
---

# ClickUp SOP & Template Pattern

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.

## The Core Distinction

| 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.

## Workflow Pattern

For any recurring service (e.g., landing page, SEO, blog post, Google Ads setup):

1. **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

2. **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.

3. **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

4. **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).

## Why This Matters

Without this pattern, quality depends on individual memory and tribal knowledge. With it:

- Every team member executing a blog post or landing page follows the same steps
- New hires can onboard to a service type by reading the SOP and template
- Account managers reviewing deliverables see a consistent structure every time
- Past work is reusable — briefs and templates can be cloned and adapted rather than rewritten from scratch

> "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

## Implementation Priority

Start with the **top 10 most frequently delivered services**. Candidates identified in discussion:

- Landing pages
- Foundational SEO
- Blog posts
- Google Ads campaign setup
- Social media content
- Web design / CRO
- Content production (images, visual design)

Melissa Cusumano is responsible for finalizing this list. See action items in [[meetings/2026-04-05-clickup-blueprint-feedback-business-development]].

## SOP Storage in ClickUp

SOPs live in the **Resources folder** within the Operations space. The blueprint distinguishes between:

- **Active SOPs** — approved, in-use procedures
- **SOP Pipeline** — SOPs currently being drafted or under review

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.

## Related

- [[meetings/2026-04-05-clickup-blueprint-feedback-business-development]]
- [[knowledge/project-management/clickup-client-folder-structure]]
- [[knowledge/project-management/clickup-sprint-automation-pattern]]