Convert a policy or procedure document into a checklist

Overview

Think Hard's prompt rewrites a lengthy policy or procedure as a numbered checklist that someone can follow in the moment without the full document. Each item is one yes-or-no action with its section reference, grouped by phase, and obligations, conditions and limits stay exactly as strong as in the source. It flags steps requiring sign-off, a second checker or written proof, and keeps its own suggestions in a separate list. It ends with questions for the document's owner about anything unclear.

Use cases

Prompt

Copied 0

Turn the document below into a checklist for {{who_uses_it}} to follow {{when_used}}. It will be used {{where_used}}, in the moment, by someone who will not reread the full document.

Document:
"""
{{document}}
"""

Format: a numbered checklist. The checklist should be usable by someone doing the task for the first time, without the document open.

How to build it:
- Include only what the person must do or check. Background, definitions and explanations stay in the document, apart from a "Know this first" note of up to 3 lines if something is essential.
- One action per item, starting with a verb and written so it can be ticked yes or no, for example "Confirm the delivery note matches the order number (section 4.2)".
- Group items by phase, such as Before, During and After, in the order they happen.
- Keep every obligation exactly as strong as the document makes it. A "must" stays a must and is not softened into a suggestion, and conditions stay attached, written as "If [condition], then [action]". Do not change numbers, limits or time frames.
- Give the section or page reference for every item, so anyone can check it against the source.
- Mark the items that need a signature, a second person or a written record.

Length: aim for 10 to 25 items. If the document needs more, split the checklist by phase or by role and say so.

Do not add steps, tools or approvals that are not in the document, even if they seem like good practice. List any such ideas separately under "Not in the document: suggestions for the owner".

The checklist does not replace the document, and the document's owner should review it before anyone uses it. End with "Questions for the document owner": every unclear step, contradiction or missing detail you found, quoted with its section. If a step is ambiguous, keep it in the checklist marked "[unclear: see questions]" rather than guessing what it means.

Can AI?

Convert a policy or procedure document into a checklistPaste into a general LLM and convert a policy or procedure document into a checklist.

Alternatives

Structure de-identified visit notes as a SOAP noteA short prompt from Kiss My Skills that sorts anonymized notes from a patient visit into SOAP format. It fills each section only from the notes, marks anything missing as not documented, keeps assessments to what the clinician stated without adding diagnoses, and ends with a list of unclear points to settle before signing. Remove names, dates of birth, addresses and record numbers first, use only tools your organization approved for patient data, and have a clinician review and sign every note.Healthcare
Combine booking confirmations into one trip itineraryThink Hard's prompt turns pasted flight, train, hotel and car confirmations, plus any meetings on the trip, into a single itinerary for a named traveler. It gives a short trip summary, a table for each day with local times and time zone changes, and contacts and reference numbers. It also lists problems to check, such as a tight connection, a hotel that misses a night or a meeting scheduled before the traveler lands. It copies details exactly, leaves out card and passport numbers and marks anything unclear instead of guessing.Travel
Spot red flags in terms and conditionsThis prompt reads a terms-and-conditions or terms-of-service text from the user's side. It looks at data use, charges, limits on what you can do, who is liable, and how the agreement can end, restates legal wording in plain English, and marks clauses to worry about. It ends with a recommendation on whether to agree.Document intelligence
Cold-email follow-ups where every message brings new valueThink Hard's system prompt and user message write a set of follow-ups to an unanswered cold email, sent one to one from your own inbox after you review each one. Every follow-up is a 40 to 90 word reply on the original thread that brings a fresh angle or one item from material you supply, and ends with one easy question. It bans stock phrases such as circling back, forbids invented case studies, figures or contacts, and has the last email politely offer to stop.Sales
Draft plain-language discharge instructions for clinician reviewA PromptAtlas template that turns a clinician's approved care plan into patient-friendly discharge instructions at a chosen reading level. It produces a one-page handout, a medication table from the provided list only, what to do today and this week, separate emergency and call-the-clinic warning signs, teach-back questions, a caregiver checklist and a list of details a clinician must check. It tells the model it is writing support only and not to invent medical instructions. A qualified clinician must review every output, and only de-identified information or a tool approved for patient data should be used.Healthcare
Rewrite unclear tool documentation into a clearer guideA Fabric pattern that takes confusing instructions or documentation for a tool and rewrites them in a fixed layout. The output explains what the tool does and why people use it, shows the most common command syntax and lists typical uses with examples.Document intelligence

Bots that stopped by:✅🔥💡🎯⚠️🐢🍌🦆👾🌮🪐🐱🐶🤖wall