SOP & Process Templates Collection

SOP & Process Templates Collection

Purpose: Provide concise, usable micro‑SOPs that a one-person business can adopt quickly to stabilize delivery, delegate tasks to contractors, and enable automation. Each SOP is short, action-focused, and designed to be copied and adapted.

How to use this collection

Pick the micro‑SOP that matches a recurring workflow. Copy it into your SOP folder, update owner, tools, and links, run the process once, then iterate. Keep SOPs short enough that a new contractor, assistant, or automation can follow them without asking for clarifications.

Micro‑SOP format (recommended)

Each SOP in this collection follows a compact structure so users can find essential information immediately.

• Title — short, clear.
• Purpose — one sentence: why this SOP exists.
• Scope — when to use it, what it includes/excludes.
• Owner — who is accountable (person or role).
• Frequency / Trigger — when to run it.
• Estimated Time — realistic minutes/hours.
• Inputs & Tools — what you need (files, platforms, templates).
• Outputs / Acceptance criteria — how you know it was done correctly.
• Step-by-step tasks — 5–12 discrete steps, each with clear expected result.
• Escalation & Exceptions — quick guidance for common problems.
• Related Docs — links to templates, scripts, or other SOPs.
• Version history — date, author, short note.

Example: Client Onboarding (Micro‑SOP)

Title: New Client Onboarding — Basic

Purpose: Start a new client relationship with clear expectations, access, and billing setup so delivery can begin within 48 hours.

Scope: Applies to standard paid engagements (projects and retainers), not to trial consultations.

Owner: Owner / Account Manager

Trigger: Signed contract received and initial payment confirmed.

Estimated Time: 60–90 minutes

Inputs & Tools: Contract, client intake form, CRM record, invoicing tool, project management board, welcome email template.

Outputs / Acceptance criteria: Client record created, invoice recorded, welcome packet sent, initial project card created with first task assigned.

1. Create or update client record in CRM. (Result: contact fields filled; company name standardized.)
2. Record payment and attach receipt to client record. (Result: payment status = Paid.)
3. Create project board/card in PM tool and add initial deliverables. (Result: card created with due date and owner.)
4. Send welcome email and attach onboarding questionnaire. (Result: email sent; questionnaire link included.)
5. Schedule kickoff call with client and internal notes. (Result: calendar invite sent; agenda attached.)
6. Confirm all required accesses (files, accounts). If access not obtained in 3 business days, escalate to Owner. (Result: access confirmed or ticket opened.)

Escalation: If payment not posted within 48 hours, pause onboarding and notify owner.

Related Docs: Welcome email template; onboarding questionnaire; contract template.

Example: Delivery Handoff (Micro‑SOP)

Short checklist to ensure consistent delivery and handoff to client or platform:

• Confirm final deliverable meets acceptance criteria.
• Generate deliverable package (files, README, notes).
• Upload to agreed location and confirm permissions.
• Notify client with download link and change log.
• Record delivery in billing/CRM system, mark milestone complete.

Example: Billing & Invoicing (Micro‑SOP)

Key steps to keep cash flow steady and reduce disputes:

1. Ensure contract terms and invoice schedule documented in client record.
2. Create invoice from template including payment terms and reference.
3. Send invoice via agreed channel and log transmission.
4. If unpaid after X days, follow the defined polite reminder cadence (templates provided).
5. Record payment; update client status and trigger follow-up deliverables.

Example: Content Publishing (Micro‑SOP)

Use for repeatable content workflows (blog, newsletter, social):

1. Draft content in CMS using content brief template.
2. Run basic editing checklist (clarity, CTA, SEO headline, images alt text).
3. Schedule publish date and distribution channels.
4. Publish and confirm analytics tags are present; record publish event.
5. Promote according to promotion plan; capture performance after 7 days.

Folder naming convention

Keep SOPs discoverable and versioned in a simple, consistent folder structure. Example:

• /SOPs/{Category}/{YYYYMMDD}_{ShortName}_v{major}.{minor}.md

Examples:

• /SOPs/Clients/20260510_NewClientOnboarding_v1.0.md
• /SOPs/Billing/20260302_InvoiceAndReminders_v1.2.md

Lightweight versioning policy

• v1.0 — initial publish.
• v1.x — minor edits, clarifications, small improvements (increment minor digit).
• v2.0 — significant changes to steps or acceptance criteria (increment major digit).
• Always add one-line note to Version history with date and author.

Checklist template (compact)

• Task completed by: __________
• Date completed: __________
• Outcome meets acceptance criteria: Yes / No
• If No, brief note and next steps: __________

Writing tips for one-person businesses

• Keep SOPs scannable: use short sentences, bullets, and clear expected results for each step.
• Capture decisions: note any judgment points and the rule of thumb to use there.
• Design for handoff: include links, filenames, and exact platform names so contractors need minimal context.
• Automate where it helps: mark steps that could be automated and list the tool or script if available.
• Test and revise: run each SOP end-to-end at least once with a contractor or assistant; time it and adjust estimated time.
• Prefer acceptance criteria over vague instructions: describe the result, not just the action.

Common malfunctions (anti-patterns) and how to avoid them

• Too long: break long SOPs into smaller micro‑SOPs that map to a single recurring outcome.
• Missing tools/links: end-of-process delays often come from absent access—list required accesses up front.
• Vague owners: assign a role or person and include a fallback for absence.
• No acceptance criteria: without this you'll get rework—be explicit about what "done" looks like.

Next steps & capability suggestions

Start by copying 2–3 SOPs into your SOP folder and running them once. After you have stable SOPs, consider converting high-value ones into interactive checklists or task templates in your project management tool so completion is tracked automatically.

If you want to make this collection more powerful on the platform: convert SOPs into interactive checklists (so completions can be recorded), add an intake form for new SOP requests, and implement a simple dashboard tracking last-run date and owner. See CapabilityEnhancementNotes for possibilities.

Templates included in this collection

• New Client Onboarding — Micro‑SOP (example above)
• Delivery Handoff — Checklist
• Billing & Invoicing — Micro‑SOP + Reminder Cadence
• Content Publishing — Micro‑SOP
• SOP Authoring Template — blank copy ready to customize

Version history

2026-05-XX — Author: Collection created, expanded with examples and folder/versioning guidance.