1. Pick one process people actually ask about
Start with a repeated question, a missed handoff, or work that different people do differently. Choose a process with a clear beginning and end, rather than trying to document an entire department.
Illustrative example: material receiving begins when a delivery arrives and ends when the delivery is checked, recorded, and handed over for storage. Keep purchasing and installation in separate documents.
2. Name an owner
Choose a role or person who understands the work and can approve changes. The owner keeps the SOP current; they do not need to perform every step.
Record the owner near the title and make the contact route clear. If the owner leaves or changes roles, transfer responsibility instead of leaving the document unattended.
3. Write the purpose and scope
Use the purpose to explain what a successful result looks like and why the procedure exists. Use the scope to state when the procedure applies and what it does not cover.
For an illustrative end-of-day closeout SOP, the purpose could be to leave the work area secure and ready for the next shift. The scope could cover the assigned work area while excluding equipment maintenance covered by another procedure.
4. List the roles
Identify who performs the work, who checks it, and who receives the handoff. Use job roles where possible so the document survives personnel changes.
Replace vague instructions such as “get approval” with the responsible role and the point at which approval is needed. Confirm that each role has the required authority and training.
5. Break the work into ordered steps
Watch someone do the work or ask them to walk you through it. Write one action per step, start with a verb, and keep the order the same as the real task.
Include the information needed at the moment of action: the form name, the location of a control, or the record to complete. If a step contains several independent actions, split it up. Put detailed instructions for a specialist task in a linked work instruction.
6. Put safety and quality notes where they matter
State prerequisites before the steps, then place specific warnings immediately before the action they affect. Refer to approved site rules, manufacturer instructions, and applicable requirements rather than inventing a generic safety procedure.
Describe quality checks in observable terms and reference the approved acceptance criteria. For example, an illustrative receiving step can ask the receiver to compare delivered items with the order and record damage before accepting the handoff. A qualified person must review safety-critical content.
7. Review it with someone who does the work
Ask a person who performs the task to follow the draft without filling in missing details from memory. Note where they hesitate, ask questions, or need a different order.
Resolve the gaps with the owner and relevant reviewers. A desk review alone cannot tell you whether instructions are usable at the work location.
8. Publish where the team looks
Put the approved version in the place the team uses to find procedures. Give it a searchable name and make the current version easy to distinguish from old copies.
For field work, check access on the device and connection people actually have. If a printed copy is needed, include its revision and a way to confirm whether it is still current.
9. Set a review date
Record the last review date and the next review date. Choose the interval based on how often the process changes and the consequences of stale instructions.
Also review after a change in equipment, software, site requirements, or the actual sequence of work. Keep a short revision history explaining what changed and who approved it.
Common mistakes to avoid
Too long: separate background information from the steps and move single-task detail into work instructions. No owner: assign someone who can maintain and approve the procedure.
Buried in a shared drive: test whether a teammate can find the current SOP by its process name. Never updated: add a review date and make it easy for the people doing the work to flag a problem.