Free SOP template for small shops
One page, seven sections, ready to fill in. Turn "that's how we do it here" into a procedure anyone can follow.
If a job only lives in one person's head, your shop is one sick day away from a problem. A written procedure fixes that. It makes training faster, mistakes rarer, and audits calmer.
I have 10+ years of GMP and GDP experience in regulated manufacturing quality assurance, where a procedure had to work the first time a new person read it. I've used that same simple structure on every SOP since, and I've put it here for you to use for free.
You don't need special software. Copy the template below into Word or Google Docs, fill in one task, and hand it to someone who has never done that job. If they can follow it without asking you questions, it's done. If they get stuck, that's the step to fix.
I work with small manufacturers, food producers, farm packers and local businesses in Homestead, South Dade and across Miami-Dade. If you'd rather not write it yourself, I can turn your rough notes or a quick walk-through into a clean, finished SOP.
SOP TITLE: [Task name, e.g., "Opening the shop" or "Cleaning the mixer"]
Document no.: [SOP-001] Version: [1.0] Effective date: [MM/DD/YYYY] Owner: [Name]
1. Purpose
Why this procedure exists, in one or two sentences. Example: "To make sure every batch is mixed the same way so the product is consistent and safe."
2. Scope
Where and when it applies, and what it does not cover. Example: "Applies to all staff on the day shift using Mixer 1. Does not cover deep cleaning."
3. Roles
- Who does the task: [Role]
- Who checks it: [Role]
- Who to call if something goes wrong: [Name / phone]
4. Materials
- Equipment and tools: [list]
- Supplies and PPE: [list]
- Forms or logs used: [list]
5. Steps
- [Start with a verb. One action per step.]
- [Next action.]
- [Next action. Add a short note on why if it is not obvious.]
- [Continue until the task is complete.]
Safety note: [Anything that could hurt someone or ruin the product.]
6. Quality checks
- What "done right" looks like: [measurable result, photo, or reading]
- When to stop and fix it: [limit or sign of a problem]
- Record it here: [log name or initials/date]
7. Revision log
| Version | Date | What changed | Changed by |
|---|---|---|---|
| 1.0 | [date] | First release | [name] |
Tips: One step, one action. Start every step with a verb. Keep the "why" in a short note, not in the step.
Want me to build yours?
Send me your rough notes or a photo of the old checklist. I'll turn it into a clear, finished SOP your team can use.
Serving Homestead, Florida City, South Dade and all of Miami-Dade.