We are updating this website. The free pack and the library work as normal. If something looks wrong, tell us.

Blog · SOPs and manuals

One-Page SOP Template (Simple and Free)

By the SystemaFlow team · Updated November 2026 · Share this

Someone's asked you to write up how new enquiries get answered. It's a ten-minute job, and the SOP template you've found starts with a page of version control.

A one-page SOP, sometimes called a mini SOP or quick SOP, puts everything someone needs for one job on a single page: the task, the owner, what starts it, what done looks like, up to seven steps and the mistakes to avoid. Here's a layout you can copy now.

The one-page SOP template

Copy this into Word, Google Docs, Notion or wherever your team will open it during the job.

TASK:            [Name it by what gets done, e.g. Send Client Invoices]
OWNER:           [One named person]         BACKUP: [One named person]
STARTS WHEN:     [The event or date that triggers it]
DONE WHEN:       [How you know it's finished and right]
TIME EACH TIME:  [Your real figure]
WHAT YOU NEED:   [Tools, files, who to ask, where it's kept. Never passwords.]

STEPS (one action each, seven at most)                        TIME
1. [Start with a verb]                                        [   ]
2.                                                            [   ]
3.                                                            [   ]
4.                                                            [   ]
5.                                                            [   ]
6.                                                            [   ]
7.                                                            [   ]

WHAT CAN GO WRONG              HOW TO AVOID OR HANDLE IT
[A mistake you've made]        [What to do]
[Another one]                  [What to do]

LAST CHECKED: [Date]           NEXT CHECK: [Date]

Each line is there for a reason.

LineWhy it's on the pageCommon slip
TaskTells people they've opened the right pageNaming a department, such as "Finance"
Owner and backupSomeone keeps it right, and someone can step inWriting "the team"
Starts whenMeans nobody has to rememberWriting "as needed"
Done whenGets everyone to the same finishLeaving it out because it seems obvious
TimeShows what the job really costsGuessing low
What you needSaves a hunt before step onePasting in logins
StepsThe job itselfPutting two actions in one step
What can go wrongPasses on what experience taught youSkipping it. It's often the most useful part
Checked datesStops the page going quietly out of dateSetting no next date

A filled-in one-page SOP example

This one's adapted from a Starter Task Card in The Business Operating Manual, the free pack from SystemaFlow™. The names and times are typical examples, so replace them with your own.

  
TaskReply to a New Enquiry
Owner and backupOffice manager; account lead as backup
Starts whenA new enquiry arrives in the shared inbox
Done whenThe person has a helpful reply within one working day, and the enquiry is logged
Time each time15 minutes
What you needThe shared inbox, your standard reply, your list of services and your diary for booking a call
StepWhat to doTime
1Read the enquiry and note what they're asking for3 min
2Check it's work you do and can take on3 min
3Reply using your standard note, adding their name and need5 min
4Offer two times for a short call2 min
5Log the enquiry and set a follow-up date2 min
What can go wrongHow to avoid it
The reply takes days and they go elsewhereAgree who checks the inbox each day, and who covers them
It reads like a stock answerAlways mention one detail from their message
Nobody follows upSet a reminder for three working days if there's no reply

How to fill it in quickly

Do the job and write as you go. Talk through what you're doing, and write down what you say. Writing from memory is how the steps you do without thinking go missing.

Fill in Done when before the steps. If you can't say what finished looks like, the steps won't be any clearer. Then add the mistakes you've already made on this job, while you can still remember them.

Our free pack allows about 20 minutes for a first card. A one-pager is meant to be quick to write, so if you're still at it an hour later, you've probably got two jobs on one page. For the full method, read how to write an SOP that actually gets used.

Is your one-page SOP ready?

Run through these with your finished page. Better still, ask someone who doesn't do the job.

Is your one-page SOP ready?

Take one page you've written and tick what's true.

0 of 8. Worth another pass. Start with the first gap, then test it on someone new. Split it. Give each job its own page and a name that starts with a verb.

When is one page not enough?

A one-pager suits a job with a mostly fixed order that one person carries out. It starts to struggle in a few situations.

If the job...Use instead
Is well known and only needs nothing missedA checklist
Changes route depending on what happensA simple flow
Moves across several people or teamsA fuller SOP with who does each step
Has a format set by a regulator, insurer or clientTheir format

Not sure? The picker in best SOP templates for small teams will help you choose. If you want to see other jobs written up, try SOP examples for small business, and for the standard to aim at, read what makes a good SOP.

A page doing its job still needs a place in the team's routine, or it'll end up forgotten like any other document. That's the subject of why SOPs alone don't work.

The free version of this template is the Task Card, which also has a section for handing a job over in three stages. Like all SystemaFlow systems, it's a done-for-you template in Word and PDF, not software.

Want the full version?

When a job runs across several people, the Standard Operating Procedure in the Business Essentials pack takes it further, with who does each step, what correct looks like, exceptions and training sign-off. It's in the Business Foundations Core Vault.

See what's in the Business Foundations Vault →

Or get all 352 systems, and every one we add later, with Masterworks: $999, paid once.

Was this helpful?

Know someone who'd find this useful?

Frequently asked questions

What is a mini SOP?
A short standard operating procedure that fits on one page. It gives the task, who does it, what starts it, the steps and what finished looks like. It's also called a quick SOP or one-page SOP.
What should a simple SOP include?
The task name, one owner, what starts it, what done looks like, what you need, up to seven numbered steps, the common mistakes and a next check date.
How many steps should a one-page SOP have?
We work to a limit of seven, each with a single action. If you need more, you've usually got two jobs, and you can split them onto two pages.
When is a one-page SOP not enough?
When several people or teams share the job, when there are many decision points, or when a regulator or client sets the format. Use a fuller SOP or a flow for those.
Is a mini SOP the same as a checklist?
Not quite. A checklist reminds someone who already knows the job. A mini SOP also says who owns it, when it starts, what's needed and what can go wrong, so someone new can do it.
Can I use this template in Google Docs or Notion?
Yes. The layout is just a set of headings and a table, so copy it into whatever your team opens during the job.

Where to go from here