A practical Markdown template for documenting recurring work in a small team. It keeps the procedure, quality gate, exception path, and field checklist in one version-controlled format.
Fictional new client intake SOP
Prefer one ZIP delivered by email? Preview the included files and controls, then get the starter free on Payhip. It requires an email address but no payment details.
Prefer a guided worksheet? Open the free browser SOP builder. It generates the same kind of Markdown locally without submitting or storing the entries.
Already have a draft? Run the free ten-point SOP quality checklist to check for missing ownership, triggers, completion evidence, exceptions, and revision controls. Pasted text stays in browser memory.
- Click Use this template on GitHub or copy
SOP-TEMPLATE.md. - Replace every
{{placeholder}}with information from the real workflow. - Give the draft to someone who did not write it and run a cold-read test.
- Fix every step that requires verbal explanation.
- Copy the final action checks into
FIELD-CHECKLIST-TEMPLATE.mdfor repeated use.
| File | Purpose |
|---|---|
SOP-TEMPLATE.md |
Controlled procedure with ownership, steps, checks, exceptions, and revision history |
FIELD-CHECKLIST-TEMPLATE.md |
Short operator-facing checklist for repeated execution |
EXAMPLE-CLIENT-INTAKE.md |
Filled fictional example showing the expected level of detail |
SECURITY.md |
Safe handling rules for source material and finished procedures |
- What event starts the procedure?
- Who owns the result?
- What must be true before work begins?
- What action happens at each step?
- How does the operator know the step is complete?
- What must be checked before the workflow is closed?
- What happens when the normal path fails?
- When should the document be reviewed or retired?
- Assign one document owner.
- Describe observable actions, not intentions.
- Put explanations in the SOP and short checks in the field checklist.
- Record exceptions where they occur instead of relying on tribal knowledge.
- Set a review date and archive stale versions.
Do not put passwords, private keys, recovery codes, banking data, payment-card data, or unredacted customer records in an SOP repository. See SECURITY.md before adding screenshots or examples.
Mackanic Technologies can turn notes, transcripts, or redacted screenshots into a controlled SOP and field checklist. A single-workflow test starts at 35ドル.
View the work sample and fixed scopes
The 15ドル SOP Template Pack adds a process backlog, ownership map, revision log, and implementation guide for teams documenting more than one workflow.
MIT. See LICENSE.