The New AI Employee
How-to

A standard operating procedure template anyone can follow

A standard operating procedure template with five simple parts: purpose, start, steps, checks and filing. Write it from your real emails and files.

The New AI Employee6 min read
A single-page procedure form with numbered steps and checkbox icons on a clipboard, beside a folder of emails.
Short answer

A standard operating procedure template has five parts: why the job exists, what starts it, the steps and who does them, the checks, and where the result is filed. Write it from how the work really happens, using your emails and files, not from memory.

What is an SOP, and why write one?

An SOP is a short page that says how one regular job gets done. A standard operating procedure template keeps every page in the same shape.

Say the baker who places the flour order is off sick. The person covering has no idea which supplier, which day or how much. With a page, they just follow it. Without one, they ring around and hope.

SOPs earn their keep in three moments. Someone new joins. The usual person is away. Or something goes wrong and you need to see which step got missed.

Most SOPs fail for the same reasons. They're written from memory, they describe the perfect day instead of the real one, and they're too long to read with the work open on the other screen. One job per page fixes the last problem. The template fixes the others.

An SOP is one piece of process documentation, which is just the habit of writing down how your business runs. Business process mapping draws the big picture: which jobs exist and who hands what to whom. An SOP zooms into one box on that map.

What goes into the five-part template?

Every SOP needs five parts: purpose, start, steps, checks and filing. Anything more is a bonus.

It works for almost any office job. Keep each part short. If one part grows longer than the rest of the page, you probably have two jobs and need two SOPs.

Use the same shape every time. Once someone has read one SOP, they know where to look in all the others. Add a line at the top with the name, the owner and the date it was last checked. That date tells a reader whether to trust the page.

PartWhat it answersExample for supplier bills
PurposeWhy does this job exist?Every supplier bill is entered and filed so it can be paid on time
StartWhat sets the job off?A bill lands in the accounts mailbox or the scans folder
StepsWhat happens, in order, and who does it?Open, check the supplier, enter the bill, attach the PDF, file it
ChecksWhat must be verified, and who approves?Totals add up, no repeated invoice number, the finance lead approves
FilingWhere do the result and proof go?PDF in the supplier's folder, bill left as a draft

How do you write steps people actually follow?

Good steps are numbered, start with a verb, say who does them and fit on one screen.

Write an instruction, not a description. Say: "Check the supplier name against the supplier list." Don't say: "The supplier is usually checked." You can do the first one. You can only argue about the second.

Name the person on any step that changes hands. Most mistakes happen at handovers, when each person thinks the other did it.

Here's how a small team might handle supplier bills. Notice what's missing: no lesson on the accounting system, no speech about why bills matter. That belongs in training. Each line is one action someone can tick off.

  1. Accounts assistant: open each new bill in the accounts mailbox at the start of the morning.
  2. Accounts assistant: check the supplier is on the supplier list. If not, hand the bill to the finance lead and stop.
  3. Accounts assistant: check the invoice number hasn't been entered before for that supplier.
  4. Accounts assistant: enter the bill as a draft in the accounting system and attach the PDF.
  5. Accounts assistant: save the PDF in the supplier's folder, named by date and invoice number.
  6. Finance lead: review the drafts and approve the correct ones.
Interactive

Does your SOP have what it needs?

Open a procedure you already have, or the one you're writing now. Tick each line that's true of it.

Where do checks and approvals belong?

Put a check wherever a mistake would cost real money or trust, and leave the rest alone.

Too many checks and people tick boxes without looking. Pick the moments that matter: a payment, a new supplier, an email to a customer, a figure going into a tax return.

Say a plumber's office sends quotes. The check is simple: the total adds up and the customer's address matches the job. One person looks, in ten seconds. That's a good check.

Write each check so anyone can verify it fast. Also write down what the SOP doesn't cover, so nobody stretches it to cases it was never made for.

  • What to do when a case doesn't fit the steps, and who decides.
  • Which documents always need a second pair of eyes, such as refunds.
  • Which changes need the owner's yes, such as a new supplier or new bank details.
  • Where to note that the check was done.

Can you write an SOP from real emails and files?

Yes, and it's the most accurate way: the emails, attachments and folders show what people really do.

Ask anyone to describe their job and you get the version they think they do. The mailbox shows the real one: which suppliers write in, which customers chase, which report goes out at month end.

This matters most when someone leaves. A handover note written in the last rushed week lists the obvious jobs and misses the yearly renewal and the favor done for one particular customer. You find those gaps after the person has gone.

That's where an AI employee helps, and it's one we run today. When a key person is leaving, our handover robot reads their mailbox history and attachments, read-only. It writes down what the role really did, what's still open, the deadlines, and a handover plan before the last day.

That write-up is raw material, not an SOP yet. Someone picks the repeating jobs and puts each into the five-part template. This is also how you build a proper employee handover document that people trust.

How do you keep SOPs up to date?

An SOP stays useful when one person owns it, reviews it on a fixed rhythm and updates it the day the job changes.

Pages go stale quietly. A supplier moves to a portal, a folder gets renamed, and the page still describes last year. The fix is dull but works: one owner per page, a review date at the top, and a habit of editing on the day things change.

When you review, don't just reread. Watch someone do the job with the page open, or compare it with the last few real cases in the mailbox. If you change the template itself, update the other pages at their next review, not all at once.

Keep every SOP in one place your team already uses, like a shared folder. A page nobody can find might as well not exist.

One last thing. An SOP describes the job; it doesn't do it. If a job follows the same steps many times a month and ends in a document or an entry, it may suit an AI employee. We'd start with your approval, and the SOP becomes its job description.

Questions

What are the five parts of an SOP?

Purpose, what starts the job, numbered steps with who does each, the checks, and where the result is filed. A line at the top gives the owner and the last review date.

How long should an SOP be?

Short enough to follow with the work open on the other screen, usually one page. If it runs much longer, it's probably two jobs.

What's the difference between an SOP and a process map?

A process map shows the big picture: which jobs exist and who hands what to whom. An SOP takes one job from that map and says exactly how it's done.

What goes in an employee handover document?

The repeating jobs the person did, what's still open, coming deadlines, who they deal with and where the files are. Writing it from their emails and folders catches what memory forgets.

Who should write an SOP?

The person who does the job, checked by whoever will cover it or approve it. Using real emails and files keeps it honest.

Tell us your workflow. We will build it around you.

Write to hello@thenewaiemployee.com about the job that eats most of your team's hours each month. We'll tell you plainly whether an AI employee can take it on.

Talk to us Related service: Process mapping and handover

Keep reading

Write to us

Tell us which hours you want back.

Three lines are enough: what you do, what takes your time, how many hours a week it costs. Write to hello@thenewaiemployee.com.

Offices in Sheridan (Wyoming), Panama City, London, Bucharest and Milan.