Create SOP Amendment Proposal 500 Words

Task Library

Turn a real-world SOP failure into a ≤500-word amendment proposal – problem, affected SOP, exact proposed language, and at least two real examples – ready for weekly senior review.

Category: Knowledge System Maintenance

Use this when you hit a point in real work where an SOP is wrong, outdated, or missing a step – and you can point to at least two real occurrences, not one bad day.

Inputs

  • The affected SOP's name and the exact section that failed
  • At least two real examples of the failure (dates, clients, runs, or links)
  • The shared SOP Amendment Proposal location (see create-shared-location-for-sop-amendment-proposals)

Steps

  1. Confirm the trigger is real: the SOP failed, drifted from reality, or lacked a needed step in at least two actual runs. One occurrence may be noise – log it as a Knowledge Capture Note and wait for a second before proposing.
  2. Draft the proposal with exactly four parts: (a) the problem – what failed or drifted, stated plainly; (b) the affected SOP – name plus the specific section/step; (c) proposed language – the exact replacement or added text, ready to paste in; (d) examples – at least two real cases with dates/links where the current SOP failed.
  3. Write the proposed language in the SOP's own voice: imperative, concrete steps. Respect Platform Portability Discipline (Process 4) – keep methodology (what/why) separate from tool-specific implementation (how).
  4. Enforce the budget: 500 words maximum across all four parts. Cut backstory and justification prose; keep the problem, the text, and the proof. If it cannot fit, you are proposing more than one amendment – split it.
  5. Self-check against the reviewer's criteria: Would the proposed text drop into the SOP without breaking surrounding steps? Do the examples actually demonstrate the problem?
  6. Save the proposal to the shared location, then hand off to tagging and queueing (tag-proposal-with-affected-sop-and-queue-for-review). Do not edit the live SOP yourself – that is the reviewer's call.

Definition of done (QA checklist)

  • All four parts present: problem, affected SOP + section, paste-ready proposed language, ≥2 real examples with dates/links
  • Total length ≤500 words (counted, not eyeballed)
  • Proposed language is imperative, concrete, and preserves methodology/implementation separation
  • Exactly one SOP and one coherent change per proposal
  • Filed in the shared location; live SOP left untouched pending review
  • Linked back to the definitive article and relevant siblings
  • Complies with Blog Posting Guidelines (if it publishes content)

Example(s)

  • /knowledge-system-maintenance – Process 2 defines this exact format (≤500 words: problem, SOP, proposed language, ≥2 real examples) as the only entry path for SOP changes.
  • Example needed – run the Meta-Article Prompt (/meta-article-prompt-template) after the first approved amendment and link the meta-article here.

File in the zip: skills/knowledge-system-maintenance/create-sop-amendment-proposal-500-words.md. Download the Task Library zip.

Index: Task Library. Article guidelines.

Scroll to Top