Convert a policy or procedure document into a checklist

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.