Write It Down Once: An AI Routine for Your Standard Office Processes

The most important document in a small office is usually the one nobody ever wrote down: how things are actually done. Who opens the mail, how a new client is taken on, how the monthly billing runs, where the backups live, what happens on the first of the month. It all lives in one head — yours.

That works fine, until it does not. The day you are ill, or finally on holiday, or you bring in a helper and have to explain the same task for the tenth time. Then the office quietly depends on a single person who cannot be in two places at once.

Why "just ask me" stops working

Every small practice starts this way, and there is nothing wrong with it. But over the years the same costs start to show:

• A single point of failure. If only you know how the billing or the client intake runs, nothing moves while you are away.
• Training takes forever. Explaining a task live, each time slightly differently, is slow for both sides.
• Inconsistency. What you explain on Monday may differ from what you explain on Thursday.
• Holidays feel risky. You do not really switch off, because half of your attention stays at the office.

A calm routine to write it down

You do not need to document everything at once. You need one short routine, repeated once a week, until the most important processes are on paper.

Step 1 — Collect what you actually do

For one week, keep a simple list. Every time you finish a recurring task — sending the quarterly VAT, onboarding a new client, preparing a file — write down one line: what it is and roughly how long it takes. At the end of the week you have the raw material for your process notes.

Step 2 — Let the AI turn each task into steps

Take one task and give the AI everything you know about it, in plain words. Ask for a first draft of a step-by-step instruction:

Here is how I take on a new client: I receive the enquiry by email, check the conflict list, send a short reply with a link to book a call, then prepare an intake note before the meeting. Turn this into a clear step-by-step instruction for someone who has never done it. Use short numbered steps, plain language, and mark anything that is a legal or confidentiality requirement as "must". Leave out any fluff.

Step 3 — Add the details only you know

The AI drafts the skeleton, but the soul of a process note is the small things only you know: where the template lives, which login to use, who to call when something is unclear, and the one exception to the rule. Add these as notes after each step.

Step 4 — Test it on a fresh pair of eyes

Give the draft to someone who does not know the task — a colleague, a family member, or simply yourself after a week away. Wherever they stop and ask, the note has a gap. Fill it in.

What belongs in a good process note

A useful process note is short and answers five questions. If it does, you can hand it to anyone with confidence:

• The trigger. What starts the task — a client email, the first of the month, an invoice arriving?
• The steps. In the order they happen, each one small enough to follow.
• The tools. Which folder, template, software or login is involved.
• The exception. What to do when the standard path does not fit.
• The finish line. What "done" looks like, so the task does not drift on.

Here is a second prompt, for when you already have a draft and want it checked:

Here is my process note for sending payment reminders. Check it for gaps: is any step unclear, is anything missing that a newcomer would not know, and are there any assumptions I have not written down? Ask me the questions one by one, and I will answer, then update the note.

What AI cannot do for you

The AI can draft and tidy, but it does not know your office. It will not notice that the backup runs on the old laptop in the cupboard, or that the notary prefers a call to an email. The knowledge is yours; the AI just helps you get it out of your head and into a form others can follow. And as always: keep client names, patient details and confidential figures out of public models. Write the process in general terms, or use a local model.

The outcome

After a few weeks you have a small folder of process notes — the way your office actually runs, written down once and easy to update. The first time you take a holiday without checking your email, or hand a task to someone else and watch it get done without you, you will feel the difference. The office stops living in your head and starts living on paper, where it can be shared, improved and trusted. That is the quiet kind of progress that pays off for years.