Operations · SOPs
Write the runbook for the moment someone has to use it.
Most SOPs describe the organization. A runner facing an unfamiliar key, a full lane, or a damage report needs something else: recognition, one clear next action, and a fast path to the person authorized to decide.
The test
A new hire on a third shift should be able to act without translating policy prose.
The runbook is not a substitute for training or judgment. It is the memory aid that preserves the normal path and keeps an exception from becoming an improvisation contest.
Write for action
Organize around moments, not departments
Give every procedure the same five anchors
Trigger
When do I use this?
Name the visible condition: a guest reports damage, the lot enters constrained status, or a key leaves normal storage.
Owner
Who acts first?
Use a shift role, not a person's name that will be wrong next month.
Action
What happens now?
Lead with the first irreversible or time-sensitive step; enrich the record after the guest is stabilized.
Stop
When do I escalate?
Define the boundary beyond the role's authority and the named role that takes over.
Done
What closes the procedure?
A verbal promise is not done. Name the recorded state, acknowledgment, count, or handoff that completes it.
Turn policy into a decision path
→If a step contains “as appropriate,” the runbook has handed the decision back to the least experienced reader.
Keep the core procedures close to where they happen. A one-page opening checklist belongs at the stand; an incident flow belongs inside the reporting path; a vehicle-specific handling note belongs with that session. The full policy can remain available for managers without forcing every employee to search it under pressure.
Test an SOP by observing someone use it. Give a trained but unfamiliar employee a realistic scenario and stay quiet. Note where they hesitate, what word they search for, and which step assumes knowledge not on the page. Rewrite the procedure, not the employee.
Version the runbook lightly: owner, last reviewed date, and the operational change that triggered the revision. Retire duplicate copies. The most dangerous SOP is not obviously wrong; it is confidently followed from an old binder.
