AI prompts for drafting standard operating procedures

Fill in the blanks below, or click a highlighted word in the prompt.

You are drafting a standard operating procedure. The reader is
competent and new — they can follow instructions but have never
done this task and cannot ask anyone.

Task: {{what the procedure covers, and where it starts and ends}}
Who performs it: {{role, training level, certifications
  required}}
Frequency: {{how often}}
Equipment and tools: {{list, with any calibration requirements}}
Materials and consumables: {{list, with specifications}}
PPE: {{list}}
Inputs: {{what must be true before starting}}
Outputs: {{what exists at the end, and to what specification}}
Draft steps from the expert: {{paste — however rough}}
Known failure modes: {{what goes wrong, and how it shows}}
Escalation: {{who, in what circumstances, how contacted}}
Records required: {{what gets recorded, where, by whom}}
Regulatory or standard requirements: {{any}}

Fill in the blanks below, or click a highlighted word in the prompt.

Produce the SOP with:

1. PURPOSE — one sentence.
2. SCOPE — where this starts and stops, and what it does not
   cover.
3. PREREQUISITES — a checklist of what must be true before
   step 1, including equipment state, calibration currency,
   materials and PPE.
4. THE STEPS — each numbered, each one action, each with:
   - the action, in the imperative
   - the acceptance criterion: how you know it worked, as an
     observable or a number
   - the branch: what to do if it does not meet the criterion
5. STOP CONDITIONS — the circumstances in which the operator
   must stop and escalate, with who to contact.
6. RECORDS — what is recorded, where, when and by whom.
7. REVISION — version, date, author, next review date.

Rules:
- Every step is one action. Split any step containing "and"
  or "then".
- Every step has an acceptance criterion. If the input does
  not supply one, write [CRITERION NEEDED: how does the
  operator know this step worked?] and continue.
- Every threshold needs a number, a unit and a tolerance.
  Replace every "correctly", "properly", "as required",
  "sufficient", "appropriate" and "until it looks right" with
  [VALUE NEEDED: what number?].
- No step may reference knowing, recognising or judging
  something without saying what it looks like.
- Never invent a number, tolerance, torque, temperature, time
  or setting. Flag it.
- Add a one-line reason to any step whose purpose is not
  self-evident.
- Reading age 12. Short sentences. No nominalisations.

Fill in the blanks below, or click a highlighted word in the prompt.

You are producing interview questions to extract a procedure
from someone who performs it expertly and has never documented
it.

Task: {{what it is}}
Expert: {{role, years doing this}}
Rough outline if any: {{paste}}
What we already know goes wrong: {{list}}

Produce questions that surface tacit knowledge. Include:

- "Walk me through the last time you did this. What did you do
  first, physically?"
- For each step they describe: "How do you know that worked
  before moving on?"
- "What do you check that isn't on any list?"
- "What does it look like when it's going wrong, before it has
  obviously gone wrong?"
- "What do you do differently on a Monday, or on the first run
  of the day, or after a changeover?"
- "What would a new person get wrong here that you would spot
  immediately?"
- "Which steps do people skip, and what happens when they do?"
- "When do you stop and get someone?"
- "What have you changed about how you do this in the last
  two years, and why?"

Rules:
- Ask about the last actual instance, not about the general
  case. Generalised answers lose the branches.
- Follow every judgement word with a question asking what is
  observed.
- Ask what they check that is not written down. This is where
  the value is.
- Do not ask them to write anything.

Fill in the blanks below, or click a highlighted word in the prompt.

You are documenting a safety-critical procedure or step. The
consequence of error is injury, exposure or major loss.

Task and hazard: {{what, and what can go wrong}}
Risk assessment reference: {{document}}
Control measures: {{engineering, administrative, PPE}}
Legal or standard requirements: {{regulation, standard}}
Competence required: {{training, certification, authorisation}}
Isolation or permit requirements: {{detail}}
Emergency response: {{what to do, who to call}}

Produce the procedure with:
1. HAZARD AND CONSEQUENCE — stated plainly, first. Operators
   comply with controls whose purpose they understand.
2. AUTHORISATION — who may perform this, and how they
   demonstrate it.
3. PRE-WORK CONTROLS — isolation, permits, lock-off, testing
   dead, area controls. Each with verification.
4. THE STEPS — as standard, with acceptance criteria.
5. HOLD POINTS — steps that require a second person to verify
   before proceeding. Name them explicitly.
6. STOP CONDITIONS — unambiguous, with authority to stop
   stated as belonging to anyone.
7. EMERGENCY RESPONSE.

Rules:
- Never soften a hazard statement.
- Never write a control measure without its verification.
- Do not reorder steps for readability. Sequence in a
  safety-critical procedure is a control.
- Flag anything that appears to conflict with the stated risk
  assessment or the regulation. Do not resolve it.
- State explicitly that anyone may invoke a stop condition.
- This output is a draft for review by a competent person. Say
  so at the top.

Fill in the blanks below, or click a highlighted word in the prompt.

You have never done this task. You are competent, careful, and
alone. Read the SOP below and stop at every point where you
could not proceed with confidence.

Output:

1. CANNOT PROCEED — every step you could not perform without
   asking someone. Quote it and say what you would need.
2. JUDGEMENT WORDS — every instance of correctly, properly,
   appropriate, sufficient, as required, carefully, normal,
   good, clean, tight, until ready. Quote each with what it
   should be replaced by.
3. MISSING CRITERIA — every step with no way to verify it
   worked.
4. MISSING BRANCHES — every step with no instruction for
   failure.
5. UNDEFINED TERMS — every piece of jargon, part name,
   abbreviation or internal shorthand not defined.
6. UNSTATED PREREQUISITES — anything a step assumes was done
   earlier that is not in the procedure.
7. MULTI-ACTION STEPS — every step containing more than one
   action.
8. NO STOP CONDITION — whether it is clear when to stop and
   who to call.

Do not rewrite. Only find the gaps.

SOP: {{paste}}

Fill in the blanks below, or click a highlighted word in the prompt.

You are drafting {{n}} related standard operating procedures
as a set.

Site and context: {{operation, shift pattern, competence
  framework}}
Common elements: {{PPE, isolation, escalation, records,
  document control}}
Procedures: {{table — task, performer, frequency, equipment,
  expert draft, failure modes}}

For each, produce the SOP in the established format.

Rules for the set:
- Common elements are worded identically in every procedure.
  List any place the source drafts contradict each other on a
  common element — that inconsistency exists in the plant
  today and is worth more than the documents.
- Use one term per thing across the whole set. Output a
  glossary of every term where the drafts disagree.
- Identify handoffs: where one procedure's output is another's
  input, and whether the acceptance criteria match. Mismatched
  handoffs are a common defect source.
- Consolidate every [VALUE NEEDED] and [CRITERION NEEDED]
  across all procedures into one list, grouped by who can
  answer it.
- Flag any procedure whose steps imply a competence not in
  the framework.