SOP templates format: step columns, numbering and the print question

Start with the decision that changes the page: where the task happens, how many actions it contains, whether readers may lose their place, and whether the instructions will be printed or viewed on a screen. Follow the matching route below, then test the resulting layout before release.

If the task needs a fixed shape before writing

If work happens at one fixed station and has eight steps or fewer, choose a card. For a typical procedure, choose a page; for work spanning several roles and long stages, choose a manual. Make each role section in a manual follow the same shape as a page procedure.

Set the shape before drafting: turning a page procedure into a card requires cutting material, often while the person responsible for layout is under time pressure. Physical dimensions also need to suit the task, as they do for business card formats, where use determines the finished format.

Rule of thumb: Choose a card, page, or manual from the task's location, length, and role structure before drafting, so converting the finished procedure does not force content cuts under layout pressure when time for careful revision is limited.

If pages may be separated or a reader may lose their place

If loose pages may be separated, identify each one; if a reader may pause and return, make the step numbers easy to find. A complete header and footer protect document identity, while a separate number column gives the eye a stable place to resume.

Put the full header block on page one and repeat a footer on every sheet. Include the procedure title, version, page number in x of y form, and owner role. When the document passes two pages, add a narrow strip at the top of each page with its title and section, so a handover reader arriving on page three can identify it.

That repeated identifier gives a person joining a handover on page three enough context without sending them back to the first sheet. A similar identity strip is used in meeting documents format, but here the essential test is that a loose page still names its procedure.

If readers look away from a task and return, place step numbers in a slim column and align the instruction text at a fixed left edge. At the available screen width, keep each instruction on one line and prevent its text from flowing beneath the number.

  1   Open the supplier record from the Suppliers menu.
      -> The record header shows the supplier name and
         a status of Draft.

  2   Enter the registered name exactly as it appears
      on the supplier's own invoice.
      -> No warning appears under the field.

  3   DECISION  Is there a bank detail already saved?
      Yes -> step 4
      No  -> step 6

This alignment lets a returning reader land on a number instead of dropping into the middle of a paragraph. Put a confirmation directly beneath its instruction, and make a decision step visibly unlike an ordinary action, so neither needs to be found by rereading the whole page.

Choose any confirmation marker that suits the procedure, but apply it consistently across all procedures. Readers can learn a recurring convention once; keep every confirmation visually attached to the step it checks, rather than letting it resemble an additional instruction in the sequence.

Rule of thumb: Make every loose page name its procedure, version, position, and owner, then keep the action, confirmation, and decision cues in fixed places so readers can resume after interruption without reconstructing the sequence from surrounding prose.

If the actions must happen in a particular order

If actions depend on sequence, use numbers, not bullets, because bullets suggest items can be done in any order. Keep the procedure in one column; a second column belongs only where two kinds of reference information need to be read together.

A two-column table can pair symptoms with responses, for example, but should not make readers guess which side contains the next action. State a condition as an explicit decision rather than hiding it in parentheses, where relevant readers may miss it and others may be distracted.

Clear order matters in operational checklists too. For an SOP, the page must communicate which action follows, without asking the reader to infer a continuation from a second column or decide whether an optional note applies.

A contents list belongs in a manual, not on a page procedure: there, it pushes step one below the fold. Keep the page focused on its actions, and use a contents list only when navigating a manual, rather than making the reader pass an unnecessary navigation block before starting the task.

Rule of thumb: Number actions when order matters, write conditions as explicit decisions, and use a second column only for paired reference material, so the reader never has to infer which item comes next or whether it applies from formatting alone.

If the procedure will be used on paper, laminate, or a phone

If one procedure has to serve paper, laminate, and a phone, plan for each version separately and inspect the one people will use. A screen design does not automatically transfer: print needs hand clearance, lamination prevents edits in place, and a phone needs a narrow readable flow.

For paper, leave margins wide enough for a hole punch at the binding edge and a thumb along the outside. Judge the printed copy itself, because that is the version used in practice; a screen preview cannot confirm how the page works in the hand.

Because lamination prevents edits in place, seal a procedure only after performance has verified it. Make the version number readable from a distance and put a review date on the face, so an outdated card is visibly outdated; complete these checks before the sheet is sealed.

For a phone, use one column, avoid tables that need side-scrolling, and make steps short enough to read without pinching. Test the oldest device the team actually uses. The same tension between completeness and readability matters in operational checklists format.

Rule of thumb: Check the actual paper, sealed, and phone versions people will use, accounting for print clearance, blocked edits, narrow screens, and the oldest device in the team before relying on the procedure.

If the reading conditions make instructions harder to follow

If someone may read at arm's length, in poor light, with gloves on, or while holding another object, set body type one size larger than for desk reading. Leave a blank line after every step and remove filler rather than compressing the instructions to fit.

For each step, either bold its first verb or use no bold at all. Scattered emphasis within a sentence can prompt readers to skip words that are not highlighted. Keep lines short as well: a step wrapping three times may be read once, then passed over.

Do not make color carry meaning by itself. A red warning panel may disappear in a photocopy or monochrome display, and some readers may not see it; pair each color cue with a word or shape. Federal guidance for accessible documents follows the same principle for material sent beyond the room.

Rule of thumb: Make signals readable in difficult conditions, and ensure meaning never depends on color alone, scattered emphasis, or compressed instructions that readers may skip.

If a published instruction needs to change

If an instruction changes after release, protect the numbers readers may cite in a handover or incident report. Existing steps should remain plain integers; when a change requires a numbering adjustment, tell readers rather than silently changing references already in circulation.

Add the new action as 6a or 6.1, or renumber the sequence and record that choice in a change note. Keep in mind that handovers and incident reports may refer to step numbers, so the note needs to make the numbering change visible to people using the revised procedure.

Before relying on an authoring tool, check that its version history displays every renumbering note. Sub-steps can reveal an instruction doing too much; when genuinely needed, indent and letter them below the parent, with only one level. A procedure numbered 4.2.1 is a manual pretending to be a card. The need to preserve record history also appears in meeting documents mistakes.

Rule of thumb: Keep existing references stable where possible, show every numbering change in a note, and limit necessary sub-steps to one indented level so readers can still follow the procedure.

If a visual could make a difficult target clearer

If a location or control is genuinely hard to describe in words, use a visual to point it out, but do not make the instruction depend on that image. Crop a screenshot to the relevant control and put its written instruction above it.

Screenshots can become outdated faster than any other component of a procedure, so make sure the written step still works if the image no longer matches what people encounter. Keep the text complete, and treat the picture as support rather than the only source of an instruction.

Write instructions to remain usable after a screenshot becomes stale. With more than two decision points, place a flow diagram at the front as a route map and put the numbered instructions behind it. If a route ends in escalation, state in writing the person or role who receives it.

Published technical procedures separate these layers too: quality-system documents maintained by the Environmental Protection Agency keep narrative apart from controlled steps. That separation lets one component be revised without automatically requiring a matching change to the other.

Rule of thumb: Use pictures to identify difficult targets, but keep complete instructions in text and let a diagram support the route rather than replace the numbered steps or written escalation destination.

If the draft is ready to issue

If the layout appears ready, test the document under conditions readers will face before issuing it. Check page orientation and identity, whether steps depend on images, line wrapping, and phone readability; the final pass must test both the sheet and the individual instructions.

Layout checks cannot repair incorrect content. For a different kind of fix, SOP templates mistakes points to document-control errors; release the procedure only after the print and phone versions both pass, and after confirming no instruction exists solely inside an image.

Rule of thumb: Release only after the printed and phone versions pass their checks, every page remains identifiable, and no instruction depends on an image alone or disappears through excessive line wrapping.