As of 13 August 2026, AI can create a process checklist for your team.

What to actually do

1. Use a tool built for this

   The route this page recommends

2. Do it yourself

   Second choice

   A chat interface, chat-fluent skill, and roughly 30 minutes until you can act on the result.

   How to actually do it

   1. Open the current SOP, shared document, training notes or recorded walkthrough for the process, and gather the latest version of every form, system instruction and exception list the team uses.
   2. Ask the process owner to state the trigger, end condition, responsible roles, approval points, required records and what counts as a successful result.
   3. Paste the source material and the process owner’s answers into the prompt, replacing each bracketed slot and marking anything unknown as [NEEDS CONFIRMATION].
   4. Ask the model to produce the numbered checklist, decision branches, completion evidence and unanswered questions in the requested format.
   5. Give the draft to a colleague who performs the process and have them run through it against the live system, checking every action, role, dependency, exception and record.
   6. Correct the checklist from that walkthrough, then ask the process owner to confirm the final version and publish it in the team’s normal document or task system with an owner and review point.

   Prompt

   Create a practical process checklist for [TEAM OR ROLE] to complete [PROCESS NAME]. Use only the information in the process description and source material below. Do not invent steps, rules, timings, system names, approval requirements or safety controls. Where information is missing or ambiguous, write [NEEDS CONFIRMATION] and list the question separately.
   
   Process objective: [WHAT SUCCESS LOOKS LIKE]
   When it starts: [TRIGGER]
   When it is complete: [END CONDITION]
   People involved: [ROLES]
   Systems, forms or equipment used: [LIST]
   Known exceptions: [EXCEPTIONS]
   Required records or evidence: [RECORDS]
   Process description and source material:
   [PASTE NOTES, EXISTING DOCUMENTS OR TRANSCRIPT HERE]
   
   Return:
   1. A short title and purpose.
   2. The assumptions and unanswered questions.
   3. A numbered checklist in the correct order. Make every item a single observable action, beginning with a verb.
   4. For each item, include the responsible role, required input, system or document used, completion evidence, and any dependency.
   5. Separate decision points into clear yes or no branches.
   6. Add a final completion check and a list of items that must be confirmed by the process owner.
   7. Add a plain-text version suitable for copying into a shared document.
   
   Keep the wording concise and suitable for a UK workplace. Preserve any legal, safety, quality or approval requirements exactly as supplied. Do not claim that the checklist is compliant or safe unless the source material explicitly says so.

   Open it prefilled in ChatGPT or Claude, or copy it into Gemini, which takes no prefill link.

3. Hand it to a person

   The distant third

   A person who owns the outcome does this end to end, worth it when the failure is dear.