To create an SOP template in ClickUp Docs, write a Doc with fixed sections (purpose, scope, owner, review date, steps, exceptions), save it as a Doc template, then start each new SOP from it. Brain AI drafts the steps from rough notes through the Brain button or /write, and you edit before publishing.
The Complete Excel Course with AI Integration
From formulas and pivot tables to Power Query, DAX, VBA and AI with Copilot, ChatGPT and Claude — hands-on from the first lesson.
By Sagnik Bhattacharya and Virginia Thorn, Primetime Emmy Award winner
Buy nowBrain writes fluent steps that may be wrong for your business, so the template matters more than the AI. A good template forces the questions that make an SOP usable: who owns it, when it was last checked, what triggers it, and how someone knows they are done. ClickUp's own documentation guidance says the same about its AI: treat Brain's output as a first draft, and have a person review it before the procedure goes live.
Which ClickUp plans include Docs, wikis and Brain for SOPs?
ClickUp Docs and Doc templates are available on every plan, including Free; Brain AI is not included on Free, and wikis are capped at one on Free, Core and Business.
ClickUp's help centre and pricing page, read on 22 November 2026, give this picture. Prices are per user per month on yearly billing; on monthly billing the pricing page lists Core at $12 and Business at $25.
| Plan | Docs and Doc templates | Wikis | Private Docs | Brain and AI credits |
|---|---|---|---|---|
| Free Forever ($0) | Yes | 1 maximum | No | Brain not included; no credits |
| Core ($9) | Yes | 1 maximum | No | Extended trial use of Brain models; 1,000 credits per seat |
| Business ($17) | Yes | 1 maximum | Yes | Unlimited standard models, 1X premium; 1,500 credits per seat |
| Business Plus | Yes | Unlimited (help centre) | Yes | 2X premium; 2,000 credits per seat |
| Enterprise | Yes | Yes, with protected Docs | Yes | 5X premium; 3,000 credits per seat |
Docs can be shared with guests too: ClickUp says everyone, including guests, can use Docs, and guests need edit or full permission to use Doc templates. The ability to protect Docs and pages against unwanted changes is on Business Plus and above according to the help centre (the pricing page lists Protect Docs from Enterprise), which matters once you have SOPs that must not be edited casually. On Core, rely on page history instead: open a page, use the ellipsis menu, choose This page, then Show page history, to see changes and restore an earlier version.
What should an SOP template contain?
A usable ClickUp SOP template has eight sections: header lines (owner, reviewer, version, review dates), purpose, scope, before you start, steps, exceptions, related tasks and Docs, and a change log. Each part answers a question a new starter would otherwise ask.
| Section | What goes in it | Why it is there |
|---|---|---|
| Header lines | Owner, reviewer, version, last reviewed, next review | Shows who is accountable and when it goes stale |
| Purpose | One sentence: what this achieves and what goes wrong without it | Lets a reader decide in five seconds if it is the right page |
| Scope | Who follows it, when it starts, when it does not apply | Stops the SOP being used for the wrong case |
| Before you start | Access, tools, forms, information needed | Prevents steps that stall halfway |
| Steps | Numbered, one action each, with who and how to check it | The procedure itself |
| Exceptions and escalation | What to do when it goes wrong, and who decides | Where the real value of an SOP sits |
| Related tasks and Docs | Links to the task template and other SOPs | Connects procedure to work |
| Change log | Date, change, who | Shows the SOP is alive |
The owner and the review date are what separate an SOP from an old Word file. ClickUp Docs has owners and contributors built in: an owner is the person who created the Doc or anyone added as an owner, and a contributor is someone who edited it or was added. ClickUp's Docs help describes owners, contributors and page history but no review-date setting, so keep a "Next review" line in the header and back it with a recurring task, as described below.
How do you build the SOP template in ClickUp Docs?
Build a ClickUp SOP template by creating a Doc with the headings and placeholder text, then saving it as a Doc template. New SOPs are then created from that template, so every procedure has the same layout.
- Create a Doc. You can create one from the Home Sidebar, Spaces Sidebar, Views bar, location header, toolbar or Docs Hub, or with a slash command in any text area. Name it "SOP template - do not edit".
- Write the header lines as plain text: Owner, Reviewer, Version, Last reviewed, Next review.
- Add the sections from the table above as headings, with a short instruction in each, such as "One action per step. Start with a verb."
- Add contributors and owner. Click the owner's avatar at the top of the Doc and choose Add new to name the owner.
- Save as a template. Click the ellipsis in the upper-right corner, choose Save as template, name it, adjust the settings and click Save template. It is saved with your other templates. A Doc template copies the whole Doc, including settings and pages; page history is not included.
- Use it. Create a new Doc from the template, or apply it to an existing Doc: ellipsis, then the Entire Doc tab.
If you want one page per procedure inside a single Doc, use pages and subpages: you can drag pages into a hierarchy, and page templates let you save a single page's layout. For a wiki of twenty procedures, one Doc with a page per SOP keeps them in one place; for procedures with different owners, separate Docs let you set separate permissions.
If you would like help turning your own procedures into a set that stays current, I offer one-to-one AI consultations for small businesses.
How do you draft the steps with Brain AI?
Draft SOP steps with ClickUp Brain by opening the SOP Doc, clicking the Brain button in the upper-right corner or typing /write, and giving it the audience, purpose and rough notes. Then select the draft and refine it with the writing tools.
ClickUp's help centre lists the options. After /write you can choose Custom Prompt, Edit a draft, or Use writing tools (Write a description, Create a plan, Generate action items). You can pick a tone, and a creativity level; low creativity is probably best for professional writing. When text is selected, Improve or Edit gives tools including Improve writing, Fix spelling and grammar, Make longer, Make shorter, Simplify writing and Generate action items. After Brain responds you can Replace with this answer, Insert below, Copy or continue in the Brain sidebar. ClickUp advises including context about the audience, purpose and scope, and treating the result as a first draft.
A prompt that produces usable steps from rough notes:
Write the Steps section of an SOP for: handling a damaged-parcel claim.
Audience: a new customer-service starter on day three.
Rough notes from me:
- customer emails a photo
- check delivery record
- if parcel insured, start claim, otherwise offer a partial refund
- tell the customer the next step within one working day
Rules: numbered steps, one action each, start each with a verb. After each step add "Check:" with how the person knows it is done. Put decisions in "If ... then ..." form. Do not invent amounts, limits or system names; if something is missing, list it under "Questions for the owner".
An illustrative result: "1. Open the claim email and save the photo to the claim record. Check: the photo is attached and the claim reference is noted. 2. Look up the delivery record. Check: delivery date and signature status are visible. 3. If the parcel is insured, start an insurer claim; if not, go to step 5. ... Questions for the owner: What is the maximum partial refund a starter can approve? Which system holds the insurer form?" What you fix in it: the questions are the real output. Answer them yourself, or Brain's next draft will smooth over the gaps with plausible-sounding invention.
Use a second pass to find weak spots, with the Doc open:
Read this SOP as a new starter. List every step that could be read two ways, every missing "who", and every term that is not explained. Do not rewrite the SOP; give me the list.
This audit prompt is more valuable than the draft, because it finds what the author is too close to see. Brain can also generate action items from a Doc, so ask for a checklist version of the steps for use in task templates.
A worked example: a courier firm's damaged-parcel claim SOP
Take an illustrative courier firm with twelve staff. Its damaged-parcel procedure lives in two people's heads, and claims are inconsistent. The owner records the steps in notes, drafts them with Brain, and files them in a Doc built from the template.
The filled header reads: Owner, customer-service lead. Reviewer, operations manager. Version 1.0. Last reviewed, 22 Nov 2026. Next review, 22 May 2027. Purpose: "Make sure every damaged-parcel claim is acknowledged within one working day and decided within five." The one and five days are illustrative; the firm sets its own targets.
The scope line says the SOP applies to claims received by email or the web form, and does not apply to lost parcels, which have their own SOP. The Steps section has nine numbered actions, each with a Check line. Exceptions cover three cases: a claim over the amount a starter can approve goes to the operations manager the same day; a missing photo triggers a standard request; a claim from a repeat customer is flagged to the owner. A change log gets its first row.
Time and cost: drafting took about forty minutes, including answering Brain's questions, versus the half day the firm expected to spend writing from scratch. The drafting draws on Brain's usage allowance, not on the AI credit pool: ClickUp tracks Brain usage separately from credits, and on Core that allowance is only an extended trial, so a firm drafting dozens of SOPs a month should price Business. Treat the time figures as illustrative.
Notice that a document alone did nothing until the firm connected it to the work, which is the next section.
How do you link an SOP to tasks and checklists?
Link a ClickUp SOP Doc to the tasks where the work happens with Relationships, and turn its steps into a checklist in a task template so each job starts from them. A Doc that sits apart from the work gets ignored.
- Relationships. ClickUp lets you create Relationships between Docs and tasks, so a claim task shows its SOP and the SOP shows related tasks. Put the link in the task template.
- Create a task from a Doc. Select text in a Doc and create a task from it, handy when a step needs a one-off job.
- Task template with a checklist. Save a task template for "Damaged-parcel claim" with the checklist copied from the SOP steps. Apply it by hand, or with an automation using the Apply a template action. ClickUp warns that applying a template that creates subtasks from a Task created trigger can cause a loop, so test it.
- Checklist trigger. The Checklists resolved trigger fires when all checklists on a task are resolved, so you can move the task to a review status automatically.
- Intake. When claims arrive through a form, a ClickUp form creates the task and applies the template on submission.
Keep the checklist short and the SOP long. The checklist is the reminder; the SOP is the explanation for the edge cases. If they drift apart, trust the SOP and update the template.
How do you keep the owner and review date honest?
Keep an SOP's owner and review date honest by pairing the Next review line with a recurring ClickUp task, so someone is assigned and the date shows up in their work list. A date written in a Doc triggers nothing by itself.
- Create a task "Review SOP: damaged-parcel claim", assigned to the owner, with the Doc linked as a Relationship.
- Make it a recurring task, repeating every six or twelve months. ClickUp's documentation guidance suggests a recurring task for auditing pages on a cadence, such as quarterly for high-traffic pages.
- Put an AI step in the review: open the Doc, click Brain and ask it to summarise what has changed since the last review, as ClickUp's documentation guidance suggests, then check its answer against page history and run the audit prompt again.
- When reviewed, update Last reviewed and Next review, add a change-log row, and close the task.
Page history helps with accountability: it shows what changed, who changed it and when, and lets you restore a version. Add yourself and the reviewer as contributors so edits are visible.
Should an SOP be a Doc or a wiki?
An approved SOP should be a ClickUp wiki when people will ask questions about the procedure, because Brain treats a wiki as the source of truth and prioritises wikis when answering. Keep drafts as ordinary Docs until they are approved.
To convert, open the Doc, click the ellipsis in the upper right and switch Mark Doc as wiki on. You can also create a wiki from Docs Hub with the plus icon and Create wiki. A wiki shows a badge, and you can find wikis in the Wiki card in Docs Hub. Wikis created in Docs Hub are private by default on the Business Plan and up, and Brain only shows a wiki to people who have permission to open it.
The limit to plan around is one wiki on Free, Core and Business, because saving a wiki as a template counts as creating one. On those plans, put all SOPs as pages inside one wiki Doc rather than one wiki per SOP. Ask Brain a question such as "How do I handle a damaged parcel?" and, if the wiki has the answer, it should use it; test with five real questions before you rely on it.
Three more SOP examples to copy from
The same template fits very different jobs. Here are three short, illustrative examples, one per business type.
- Small manufacturer, end-of-shift line clearance. Purpose: nothing from one batch reaches the next. Steps: stop the line, remove product and packaging, wipe contact surfaces, record the batch number, sign off. Exceptions: a mixed-up label stops the line until the supervisor decides. Task template: the five steps as a checklist, applied every shift by a recurring task.
- Catering company, allergen check before each event. Purpose: no guest receives an allergen they declared. Steps: collect the declarations, compare them with each dish, mark the dishes on the service plan, brief the team, label the buffet. Exceptions: a late declaration goes to the head chef before service. Review cycle: every six months and after any near miss.
- Translation agency, onboarding a new client. Purpose: every client has agreed terms, a contact and a glossary before the first job. Steps: send the welcome pack, collect the glossary and style notes, set up the client in the CRM List, create the first job from the request form. Review cycle: yearly.
For each, ask Brain for a first draft from your own notes, then run the audit prompt. The quality of the examples will depend on the notes you feed it, so spend your time on the notes. For a broader look at the method, see writing SOPs with AI from rough notes, and for a different input, creating SOPs from screen recordings.
What does a finished steps section look like?
A finished Steps section reads like a checklist someone could follow with the Doc open beside the task. Here is an illustrative extract from the courier firm's damaged-parcel SOP, after Brain's draft was corrected by the owner:
| Step | Action | Who | Check |
|---|---|---|---|
| 1 | Open the claim email and save the photo to the claim task | Starter | Photo attached; claim reference noted |
| 2 | Look up the delivery record | Starter | Delivery date and signature status visible |
| 3 | If the parcel was insured, open an insurer claim; if not, go to step 5 | Starter | Insurer reference written on the task |
| 4 | Send the acknowledgement template to the customer | Starter | Reply sent within one working day |
| 5 | If the claim is under the starter limit, approve it; if over, assign the task to the operations manager | Starter or manager | Decision written in a comment |
| 6 | Send the decision and next step to the customer | Starter | Customer reply received or task set to Waiting on client |
Three details make this version better than the raw draft. Each action starts with a verb. Each decision is an if-then with an explicit destination. And each row names who acts and how to tell it is done, which is the part Brain rarely supplies without being told. The starter limit is deliberately not given a number here: it is the owner's decision, and the SOP should state it once the owner has set it.
What can you ask Brain once the SOPs exist?
ClickUp Brain can answer questions from the SOP wiki, summarise a long SOP for a new starter, and turn a Doc into a checklist. Useful prompts once the SOP Docs above exist:
- "Summarise the damaged-parcel SOP in five bullets for a starter's first day." Brain can summarise a Doc, and the help centre notes this suits onboarding new team members.
- "Which of our SOPs mention the operations manager?" Useful when someone leaves and you need to reassign ownership.
- "Turn the Steps section into a checklist I can paste into a task template." Brain's Generate action items tool produces a checklist from a Doc's content.
Check answers against the Doc the first few times. If Brain cites the wrong version, the fix is in the Docs: archive old versions so there is one source of truth.
Mistakes that turn SOPs into shelf-ware
Most SOP projects fail for reasons that have nothing to do with the tool. Watch for these.
- Publishing the AI draft unchanged. Brain does not know your refund limits or system names. ClickUp's guidance says a human review pass is always needed before documentation goes live.
- No owner. A Doc owned by everyone is owned by no one. Name one person in the header and in Docs' owner field.
- Steps with two actions. "Check the record and email the customer" hides a failure point. Split it.
- No exception path. The case that went wrong last year should be written in, with who decides.
- Too many SOPs too soon. Start with the five procedures that cost you most when they go wrong, not fifty.
A register to track every SOP
A simple sheet shows which procedures exist and which are overdue for review. One row per SOP, with its owner, version, last review, next review, linked task template, and a column for status:
| SOP | Owner | Version | Next review | Task template | Status |
|---|---|---|---|---|---|
| Damaged-parcel claim | Customer-service lead | 1.0 | 22 May 2027 | Yes | Current |
| Lost parcel | Operations manager | 0.9 draft | Not set | No | Needs owner |
| New driver induction | Depot supervisor | 1.2 | 15 Dec 2026 | Yes | Review due |
If a conditional format that turns the Next review column red when the date has passed is the part you are stuck on, try The Complete Excel Course with AI Integration on Coding Liquids.
Once the register exists, the quarterly routine is short: filter for dates in the next 30 days, make sure each has a recurring task, and open the oldest SOP. When your team asks Brain about a procedure, use the answer to test the wiki: wrong answers point at SOPs that are vague, missing or out of date. For the plan-by-plan costs of the AI features you are using, ClickUp Brain pricing for a ten-person team sets out the credit and add-on options.
Questions about SOPs in ClickUp Docs
Can ClickUp Brain write an SOP for me?
It can write a first draft from your notes. Open a Doc, use the Brain button or type /write, give it the audience, purpose and rough steps, and ask for a numbered procedure. ClickUp's own guidance is to treat the output as a starting point and have someone who does the job check every step before it is used.
Do I need a paid plan to use Docs for SOPs?
No for Docs and Doc templates: ClickUp's help centre says both are available on every plan. Brain AI is not included on Free, Core has only an extended trial of Brain, and Business and above include unlimited standard-model use. Wikis are limited to one on Free, Core and Business, with unlimited wikis on Business Plus.
How do I make sure an SOP is reviewed every year?
Add a Next review line to the template, then create a recurring task linked to the Doc. ClickUp's AI documentation page suggests a recurring task to audit pages on a cadence, such as quarterly for busy ones. The task has an assignee and a due date, which a Doc alone does not.
What is the difference between a Doc and a wiki in ClickUp?
A wiki is a Doc marked as the source of truth. Brain prioritises wikis when it answers questions, so a wiki is the better home for procedures people will ask about. You turn a Doc into a wiki from its ellipsis menu with the Mark Doc as wiki toggle, and can turn it back.
Can I turn an SOP step into a task?
Yes. ClickUp lets you create a task from any text in a Doc, and you can link Docs and tasks with Relationships so each shows the other. For repeatable work, build the checklist into a task template and apply it, so every job starts with the same steps.
Further reads
- ClickUp or Notion: Which Is Better for a Small Team? — ClickUp or Notion for docs and tasks together.
- Can ClickUp AI Notetaker Turn Meeting Notes Into Tasks? — Meeting notes that can become new procedure steps.
- Restaurant SOP Template: Opening and Closing Checklists With AI — A worked opening and closing SOP template with AI.
- Asana to ClickUp Migration: How to Move Projects and What Breaks — A practical Asana-to-ClickUp cutover plan covering importer mapping, missing behaviours and a two-week parallel run.
Browse all AI-for-business tutorials
Sources: ClickUp help-centre articles on Intro to Docs, Create Doc templates, Create a wiki, Write with Brain AI, Manage Docs with Brain AI, Use AI for documentation and ClickUp Brain availability and limits, and the ClickUp pricing page (read on 22 November 2026).
