How to Document a Process With AI (Turn What You Do Into an SOP)

The fastest way to document a process is to stop trying to write it. Do the task once while narrating what you are doing, paste the messy transcript into an assistant, and ask it to turn your words into numbered steps. Ten minutes of talking becomes a usable procedure, and the parts you skipped show up as gaps you can fill. The blank page is what kills process documentation, and this method removes it.

Why does process documentation never get written?

Because the person who knows the process is the worst person to write it. When you have done something two hundred times, the steps have collapsed into muscle memory: you no longer see the small decisions, the exception you always handle, or the button you click without thinking. Writing it down means slowing yourself to the speed of a beginner, which feels tedious, so it gets postponed until someone leaves and the knowledge goes with them. Knowledge management writers such as ProcedureFlow describe this as the quiet cost of turnover: the process still runs, right up until the one person who understood it is on holiday.

AI does not fix the motivation problem. It fixes the blank page, which turns out to be most of it.

How do I capture a process without writing anything?

Narrate the task out loud while you do it, then hand over the transcript. Open a voice memo or your meeting tool's transcription, do the task at normal speed, and say what you are doing as you go: 'now I open the finance folder, I copy last month's file, I rename it with today's date.' Do not tidy your speech. Then paste the transcript and prompt: 'Turn this into a numbered procedure. Each step should be one action with the tool or file named. Flag anything ambiguous as a question for me to answer.' If you would rather talk to the assistant directly, voice mode works just as well and skips the file step entirely.

What does a good procedure actually contain?

Purpose, trigger, steps, exceptions, and an owner. Guides such as Mintlify's walkthrough of writing an SOP and Trainual's guide to standard operating procedures agree on roughly this shape. Purpose is one line on why the task exists. Trigger says when it starts, which is the field people forget most often: 'every Monday at 9' or 'when a customer emails about a refund'. Steps are single actions. Exceptions cover the two or three things that commonly go wrong. Owner is a named person who keeps the document true. Ask the assistant to fill each of those sections from your transcript and to leave the ones it cannot answer blank rather than inventing them.

How do I catch the steps I forgot?

Ask the assistant to read it as a beginner and list what it cannot do. Prompt: 'You are a new colleague on your first week. Walk through this procedure literally. At every point where you would not know what to do, where you lack access, or where a step assumes knowledge, stop and ask a question.' You will typically get eight to fifteen questions, and most of them are the gaps: which folder exactly, what if the file is already there, who approves it, what does done look like. Answer them and the procedure roughly doubles in usefulness. This is the same trick behind good project plans made with AI: make the model play the person who does not already know.

How do I know the procedure works?

Give it to someone who has never done the task and stay quiet. Watch them try. Every question they ask is a missing step, so write it in rather than answering out loud. This is the whole test, and it takes fifteen minutes. A procedure that has never been used by a second person is a draft, not a document. It is also the cheapest onboarding you will ever build; new joiners can work through it in their first week, which pairs well with the approach in your first 30 days at a new job with AI.

What should I document first, and what should I skip?

Start with what only you know and what happens often. Rank your recurring tasks by two questions: how bad is it if I am unavailable, and how often does someone ask me how to do this. Document the top three. Skip anything that changes every month, anything one person does once a year, and anything a screenshot would explain faster than a paragraph. If a task turns out to be entirely mechanical while you are writing it down, that is a signal to automate it instead of documenting it.

How do I keep it from going stale?

Put a date and an owner at the top, and update it the moment the process changes. A wrong procedure is worse than none, because people follow it. The cheap habit is to fix the document in the same sitting where the process changed, not later. Once a quarter, paste the procedure back into the assistant with a note of what changed and ask for an updated version; five minutes of maintenance keeps it trustworthy. And write plainly, because the audience is a stressed colleague covering for you, not an auditor.

Documentation is not for the person who knows the job. It is for the Tuesday when they are not there.

Pick the one task nobody else can do this week. Talk through it once, let AI shape the transcript into steps, then hand it to a colleague and watch where they stop.