SOP & Process Kit — Micro‑SOP Templates

Micro‑SOPs: Capture repeatable work without the bureaucracy

Micro‑SOPs are intentionally short, actionable operating notes you can follow, teach, and automate. They exist to enable delegation, reduce mistakes, and make work reproducible — not to create bulky manuals that nobody reads.

This kit helps you decide when a micro‑SOP is the right tool, provides a one‑page template you can copy, shows a fast process for turning a workflow map into a concise SOP, and offers tagging/versioning rules so your small library stays useful.

When to use a micro‑SOP (vs. a full SOP)

• Routine tasks that are short, repeatable, and performed by one person or a small role. Example: "Process new client payment" or "Prepare weekly status report."
• Tasks you expect to update frequently or improve iteratively.
• Processes you want to delegate quickly or automate with a script/agent.
• Not ideal for highly complex, multi‑team processes that require formal controls, legal language, or extensive compliance evidence — those belong in full SOPs.

What a good micro‑SOP contains

Keep each micro‑SOP to one page when possible. Clear, specific steps are more valuable than long background sections.

• Title: short, searchable, and action‑oriented (verb first).
• Purpose: one sentence — why this exists.
• Scope / When to use: who does it and when.
• Owner: who maintains it and who performs it.
• Steps: the heart — numbered, concise, each step 1–2 lines.
• Inputs / Outputs: what you need and what you deliver.
• Tools & Links: links to templates, forms, scripts, or dashboards.
• Exceptions / Escalation: short guidance for common variations.
• Tags: 3–5 tags for quick filtering (see Tagging guidance).
• Version & Date: small version string and last updated date.

One‑page Micro‑SOP template

Short SOP checklist (author & reviewer)

• Does the title start with a verb and match search terms your team uses?
• Can someone unfamiliar complete the task using only these steps?
• Is every step actionable and measurable (e.g., "Send email" vs "Prepare welcome")?
• Are links to templates and tools included?
• Has the owner verified the steps by performing them once?
• Is the micro‑SOP tagged and added to the library index?
• Is it marked as an automation candidate if repeatable and rule‑based?

Tagging & versioning guidance

Tags make a small library discoverable. Use a short controlled vocabulary and limit tags to 3–5 per SOP.

Suggested tag taxonomy:

• Function: finance, sales, ops, support, marketing
• Process type: onboarding, billing, reporting, maintenance
• Frequency/urgency: daily, weekly, monthly, ad‑hoc
• Capability: manual, partially‑automated, automated

Simple versioning policy:

• Use Major.Minor (e.g., v1.0). Increment Minor for edits/clarifications that don’t change the outcome.
• Increment Major when the process materially changes or when converting to a full SOP. Record a short changelog entry in the library index.

When to create a full SOP

Convert a micro‑SOP into a full SOP when any of the following are true:

• The work crosses multiple teams or departments and requires formal handoffs, controls, or evidence for compliance.
• The task requires multiple supporting documents, forms, or approvals that cannot be cleanly referenced in one page.
• Risk or regulatory exposure is high and you need traceability, training records, or audit trails.
• The micro‑SOP consistently grows beyond one page in practical use — start a full SOP and keep the micro version as a "Quick Steps" summary inside it.

Converting a workflow map into a 1‑page micro‑SOP — a fast process

1. Open the workflow map and identify the core happy‑path: the steps that normally complete the task without exceptions.
2. Choose the role that performs the majority of steps and write a title from their perspective.
3. List only the essential actions from the happy‑path as numbered steps (aim for 4–8 steps).
4. Add inputs/outputs and links to the workflow map for visual detail. Keep the SOP text focused on execution.
5. Summarize common exceptions in one short paragraph with escalation instructions.
6. Assign an owner, publish to the library, and ask one colleague to follow the SOP while you observe — revise where they get stuck.

Example micro‑SOP (filled out)

Small SOP library index — example structure

A compact index enables quick discovery and supports light governance. Store this as a simple table or searchable list in your knowledge tool.

• Title | Owner | Tags | Version | Last reviewed | Location/Link | Notes
• Send new client welcome email | Client Success | onboarding, client | v0.2 | 2026‑06‑15 | /sops/welcome‑email | automation candidate
• Process invoice payment | Finance | billing, weekly | v1.1 | 2026‑05‑01 | /sops/invoice‑payment | references full SOP
• Prepare weekly status report | Ops | reporting, weekly | v0.3 | 2026‑06‑01 | /sops/weekly‑status | low risk

Lightweight governance & review rules

• Owners should review micro‑SOPs every 6 months (or after a major change to tools/processes).
• Mark SOPs as "automation candidate" if steps are rule‑based and occur frequently.
• Archive SOPs not used in 12 months after owner confirmation.
• Keep a one‑line changelog entry in the library index when updating version numbers.

Tips to avoid bureaucratic SOPs

• Write as you would speak to a new hire doing the task for the first time.
• Prefer links to detailed documents rather than copying every policy into the micro‑SOP.
• Test every micro‑SOP by observation: one new person follows it — where do they pause?
• Keep the changelog tiny: date, editor, one‑line reason.
• Lean into automation: if the steps are deterministic and frequent, automate and store the script link in Tools.

Next steps — how to operationalize this kit

1. Copy the one‑page template into your knowledge base and create 5 micro‑SOPs for the most frequent tasks this week.
2. Assign owners and run one observed trial for each micro‑SOP in the first 7 days.
3. Tag and add entries to the library index; set calendar reminders for review dates.
4. Mark automation candidates and prioritize 1 for scripting or low‑code automation each quarter.

Capability suggestions (how THE could make this kit even more useful)

Consider converting templates into interactive forms that guide authors and store SOP metadata (tags, owner, version) automatically. Use the platform's submission storage to track changes, usage, and review status. Package the kit as an adaptive domain or toolkit teams can acquire, copy, and tailor.

Final note

Micro‑SOPs are a practice, not a one‑time document. Start small, measure usage, and let the library evolve. The goal is not perfection — it’s consistent, reliable work people can follow, improve, and automate over time.