How to write SOPs as a set rather than one at a time, and what the set costs to develop

How to write SOPs, plural, is a different question from how to write one: it is a programme with an order and a cost. List the tasks that need a procedure. Order them by how often they run and how expensive their failures are. Walk and size each. Write in that order, one procedure per sitting, signing each before the next. And cost the set before starting, because a set of thirty procedures at an hour's walkthrough plus writing plus training is a figure the owner should see first. The SOP development cost calculator on this site prints it.

List and order the tasks

Every repeatable task with a trigger and an end state is a candidate. Order them by runs per week times the cost of a failure; order dispatch and complaint handling come first in most small businesses, and the annual tasks last. Writing in that order means the procedures that matter exist even if the programme stalls.

Size each before writing

Each task gets a walkthrough with the person who does it best, and its counts, steps, roles, decision points and systems, go into the standard operating procedure template, which prints its sections, reading time and training minutes. Sizing the set first tells the owner how many sittings the programme is and which tasks are two procedures.

Cost the set

The SOP development cost calculator takes the number of procedures, the hours per walkthrough and per write, the hourly cost of the people involved and the team size for training, and prints what the set costs to develop and what it costs to train. That figure, set against the cost of the failures the procedures prevent, is the business case.

Write, sign, review, in order

One procedure per sitting, signed by its approver and read-signed by its doers before the next begins, each with a review date. A set written in a burst and left unsigned is a set of drafts. RunbookDesk Pro keeps the set with its versions, sign-offs and review dates, and prints how many reviews a year the set will generate.

Questions people ask about how to write sops

How many SOPs does a small business need?

As many as it has repeatable tasks whose failure costs something. Twenty to forty is common; the ordering matters more than the number.

Should one person write them all?

The process owner for each, with the doer reading. One writer for the set gives consistency; one writer with no walkthroughs gives fiction.

Is the cost calculator free?

Yes, without an account, as are the template and the example builder. Keeping the set is the paid product.

Sources

Related answers

Start RunbookDesk ProGet RunbookDesk Pro, $99 a month