Free SOP Checklist Template: Standard Operating Procedure with Steps, Daily Opening and Closing Checklist, and an SOP Review and Sign-Off Log (PDF, Word, Excel)

What is on the page

SOP number and version

A short code (such as SOP-FIN-06) and a version number that goes up each time the procedure changes, so everyone knows they have the current one.

Purpose and scope

Why the procedure exists and which situations it covers, in two or three sentences.

Steps and key points

Numbered actions in the order they are done, each starting with a verb, with the reason or the thing to watch for beside it.

Opening and closing initials

The person on shift initials each task for each day, which shows at a glance what was missed.

Review and training sign-off

When each SOP was last checked and who has been trained on it, with a signature.

Writing a good SOP

Write the procedure with the person who does the job best, while they do it. Number the steps, start each with a verb ("Open", "Check", "Send") and keep each to one action. The key point column is what makes an SOP useful rather than a list: it says why a step matters or what usually goes wrong, so people can handle situations the steps don't cover. Keep it to one page if you can; a longer procedure is often two procedures. Add photos or screenshots in the Word version for steps on software. The sample was written straight after the invoicing change on the process improvement worksheet which is the right moment: when an improvement works, write it down so it sticks.

Daily checklists

Opening and closing are where small businesses lose money quietly: an unlocked back door, a till not counted, heating left on all weekend. A checklist with initials for each day makes these tasks visible without needing a manager to check. Keep it on a clipboard by the door or till, and change it to match your own routine. Use the notes column to pass problems to the next shift, then copy anything that needs fixing to a maintenance request.

Keeping SOPs up to date

An SOP that no longer matches what people do is worse than none, because new staff follow it and get it wrong. Keep the register, review each SOP at least once a year or whenever the process, the software or the law changes, and raise the version number. When an SOP changes, everyone who does that job should read the new version and sign the training log; this matters for food safety, health and safety and audits, where you may need to show who was trained and when. The training checklist covers new staff training more broadly.

Editing the files

The PDFs are fillable. Word is best for writing longer SOPs with pictures; Excel suits the register, where you can sort by next review date.

Questions

What is an SOP?

A standard operating procedure: written step-by-step instructions for a task that's done regularly, so it's done the same way every time.

What should an SOP include?

Title, number and version, purpose and scope, who does it, what is needed, numbered steps with key points, safety notes, and approval and review dates.

How long should an SOP be?

As short as possible; one page is ideal for routine tasks. Split long procedures into smaller ones.

How often should SOPs be reviewed?

At least once a year, and whenever the process, equipment, software or regulations change.

What is the difference between an SOP and a checklist?

An SOP explains how and why to do each step; a checklist is a short list for confirming each step was done. Many businesses use both.