How to write an SOP with AI (without it reading like a robot wrote it)

Every business and every independent professional runs on routines: how a new client is onboarded, how invoices go out at month end, how a report is put together, how a new hire gets access to everything. Most of these routines live in one person's head.

That is fine until the person is away, busy or gone. A standard operating procedure (SOP) is simply that routine written down so someone else, or future you, can follow it. This guide shows how to get SOPs written without losing an afternoon to each one.

Why SOPs go unwritten

Nobody disagrees that SOPs are useful. They go unwritten for three reasons:

1. Writing them is tedious. Turning something you do on autopilot into numbered steps is slow, careful work.
2. They go out of date. A process changes, the document does not, and people stop trusting it.
3. They are written for the writer. "Update the sheet" makes sense to you. A newcomer needs to know which sheet, where, and what "updated" looks like.

AI helps most with the first problem and makes the other two easier to manage.

What a good SOP contains

Before asking an assistant to write one, know what good looks like:

• A clear title and purpose. "Month-end invoicing: getting every client invoice out by the 2nd."
• When it applies and who does it. The trigger, such as the last working day of the month, and the role responsible.
• What you need before you start. Access, files and information.
• Numbered steps, one action each. "Open the client list. Filter by 'active'. For each client..."
• What done looks like. How the person knows the job is finished and correct.
• Common mistakes. The two or three things that go wrong, and how to spot them.

How to describe a process so the AI gets it right

The quality of the SOP depends on the quality of your description. You do not need to write well; you need to be complete. Talk it through as if you were explaining it to a new colleague on their first day:

• Say what triggers the process and what the end result is.
• Walk through what you actually do, in order, including the small checks you do without thinking.
• Name the tools and places involved (the accounting system, the shared folder, the client spreadsheet).
• Mention what usually goes wrong.

Dictating it out loud often works better than typing, because you naturally include the detail you would skip when writing.

Review it like a newcomer would

An AI draft is a first draft. Before you share it:

1. Follow it literally, step by step, without filling in gaps from memory. Wherever you hesitate, add a step.
2. Check every name. Tools, folders and people should be exactly right.
3. Cut what is not needed. An SOP that is shorter and correct beats one that is long and padded.
4. Date it and name an owner, so people know whether it is current and who to ask.

Keep it alive

Set a simple rule: whenever the process changes, the person who changed it updates the SOP that week. Because an AI assistant can rewrite a section from a one-line description of the change, keeping it current takes minutes rather than an afternoon.

How Casitka helps

In Casitka you can ask your companion in chat to create an SOP and describe the process in your own words, for example "Create an SOP for our month-end invoicing:" followed by what you do. You can type it, or dictate it with the Casitka desktop app. It turns your description into a structured, step-by-step procedure and saves it as a draft in your knowledge base, where you can edit it, keep it current and come back to it. Where your description leaves something out, such as who is responsible, the draft marks it "To confirm" rather than inventing an answer.

Whether you are writing down how your business runs or documenting your own repeatable work as a consultant or analyst, the approach is the same. To try it, see the plans or read how it works.