Intermediate

Operational checklist generation

Convert a procedure, policy or event plan into a usable checklist tuned to a specific role and moment.

How it works

## Why it works\nGood checklists are short, ordered, and verifiable. Asking the model to obey those constraints explicitly beats "make a checklist".\n\n## Structure\n1. Name the role and the moment (duty manager, Saturday morning).\n2. Cap the length.\n3. Require observable verification per item.\n4. Include an escalation path.\n\n## Adapt\n- Youth programme: cap MUST at 6 for a session lead.\n- Facilities: add a "sign and time" column.

Example prompt

From the procedure below, generate two checklists for a duty manager on a busy Saturday: (1) MUST-DO (max 10 items, in order, verifiable in under 30 seconds each). (2) SHOULD-DO (max 6 items). For each item: what to check, how to know it is done, who to escalate to if not. Procedure: <<<>>>