One-Page SOPs: Make Good Work Repeatable

The business problem

When work depends on one person's memory, a holiday or resignation becomes an operational incident. A standard operating procedure is not a decorative manual. It is a shared agreement about how recurring work is performed, who owns each step, and what completion means.

Warning signs

Inspect weekly routines such as customer intake, expense approval, complaints, or invoice entry. If people execute the same process differently, managers answer repetitive questions, or handoffs regularly fail, the company probably lacks an agreed operating standard.

A practical implementation plan

Start with one consequential process and define its beginning and end. Interview the employee doing the work, including exceptions and recurring errors. Compress the procedure into one page containing purpose, inputs, owner, steps, approval points, and the expected output.

• Select one frequent or high-risk workflow.
• Define its owner, inputs, steps, and approvals.
• Test the document on real cases for two weeks.
• Assign version ownership and a monthly review.

Related perspective: Sales Are Up, Cash Is Late: Fix Collections Workflow

An SME example

Consider an illustrative 18-person service company losing client requests between sales and delivery. A six-step workflow covering registration, validation, quotation, approval, handoff, and closure gives new employees a reliable reference without forcing every decision through the founder.

How to measure results

Track requests returned for missing information, lead time from intake to completion, and escalations to management. Review these weekly and revise the procedure when actual operations differ from the document. Adoption matters much more than document count.

Mistakes to avoid

Common mistakes include writing procedures without observing work, copying generic templates, adding unnecessary approvals, and leaving no person responsible for maintenance. An SOP that nobody follows is a neglected document, not an operating control.

Your next action

Choose one process creating delays today. Draft it with its actual owner, test it for two weeks against real transactions, and then approve the stable version. Define where it lives and how newcomers learn it. This is a practical foundation for repeatable operations.