SOP drafting vs SOP maintenance: choosing the right workflow
Compare sop drafting and sop maintenance using the same inputs, distinct worked outputs, complete briefs, and a practical decision test.
Quick answer
Draft an SOP when a process needs its first usable instructions; maintain an SOP when an accepted procedure needs a controlled update. Both can use the same incident notes, but their review questions differ.
Two outputs from the same inputs
Sop drafting: A proposed procedure that assembles the trigger, steps, evidence, ownership, and stopping conditions.
SOP maintenance: A change proposal against an identified accepted revision, with affected steps and the reason for each edit.
Both start from the same approved process notes, accepted procedure revision, and exception log. Choose the purpose before asking Righthand to prepare the result; otherwise a polished draft can answer the wrong question.
Worked comparison
The following records are synthetic examples. They illustrate output differences, not product test results or customer outcomes.
| Shared input | Sop drafting output | SOP maintenance output |
|---|---|---|
| Exception E8: a return lacks its original order ID | Add an identification step before preparing a return | Change revision 4 step 2; preserve the existing approval step |
| E9: staff use two names for the same queue | Define the queue name in the first draft | Replace the obsolete term in steps 1 and 5; show both edits |
| E10: approval owner changed this week | Propose the current role as reviewer | Update the owner reference and confirm its effective date |
Brief A: prepare the first workflow
Use the approved process notes, accepted procedure revision, and exception log for October 12–16, 2026. Source fields: procedure ID, revision, step number, exception ID, observation date, owner, proposed change. At Monday 9 AM America/Los_Angeles, prepare the sop drafting output shown above as source-linked Markdown in my private review thread. Preserve original record IDs and mark uncertainty. I review the draft against the first table column’s purpose. Do not publish, send external messages, change source records, or spend money. Result check: each entry matches its source and the intended first-workflow output.
Brief B: prepare the second workflow
Use exactly the same input slice, fields, date window, and timezone. Prepare the sop maintenance output shown above instead. Keep the underlying observations separate from interpretation, with a named owner for unresolved questions. Return the draft to the same review thread for my approval. Apply the same action boundaries. Result check: compare each output with the third table column; do not merely relabel Brief A’s artifact.
Righthand can help with both preparation jobs when the sources are supplied or accessible through verified assigned connections. An explicit export is a valid input route; it does not promise a native connector or continuous synchronization. See the Righthand documentation for setup and Features for task fit.
Choose by the decision ahead
Choose drafting when there is no accepted procedure or the current instructions cannot describe the job. Choose maintenance when the team can point to the authoritative revision and needs a specific change. An update should not silently rewrite unrelated steps. If the accepted baseline is unknown, locate it before describing a change as maintenance.
Failure checks and a first-run test
A polished new procedure may invent an approval rule. A maintenance draft can conceal a removed safeguard by presenting only the clean final text. Require the owner to review the baseline, proposed edits, and untouched dependencies together. Keep exceptions distinct from approved process changes.
Use the missing-order-ID return as a walkthrough. The new draft must show where work stops; the maintenance proposal must name the exact affected step and confirm that the reviewer requirement remains. Publish a revision only through the team’s approved document process. Keep the accepted source system authoritative, and record any approved change there through its supported process. A comparison draft is evidence for your decision, not permission to alter the workflow on its own.
Review Pricing against the actual preparation and review workload. The useful evaluation is whether the accepted artifact reduces work for its intended reader, including correction effort.