Record someone doing the real work and write the SOP from that recording, not from memory. Keep it short: what starts the process, the steps in order, who owns each step, what to do when something goes wrong, and which system holds the record. Give every SOP one owner who updates it when the work changes. Then add an AI assistant that answers your team's questions from the SOPs. Automate only the steps that run the same way every time.
Who this is for: operations managers and owners of professional services firms, such as accounting, insurance and consulting firms, when a key person is about to leave or the team keeps asking the same questions. The examples use an accounting firm onboarding a new client. The same steps work for any process your firm repeats.
How we know: we map how your business runs and build AI into it. Before FlowChainLabs, our founder, Alvin Chikaeze, did process and project work inside Southern Glazer's Wine & Spirits, PepsiCo, AT&T and Salesforce.
Why do SOPs sit unread?
Check yours for these four gaps.
- It describes the work as someone wishes it ran. Write it from a recording of the real work, not from memory.
- It is too long. A page of paragraphs is hard to follow while a client waits on the phone.
- It is hard to find. Put it where the work happens, so finding it is faster than asking down the hall.
- Nobody owns it. Give it one owner who changes it the same week the work changes.
If your team keeps asking the same questions, or a key person is about to leave, start there. We wrote more on that risk in when critical process knowledge lives in one person's head.
How do you write an SOP from the work as it is really done?
Start from a recording, not a blank page.
- Pick one process with a clear start and end. New client onboarding starts when the client signs the engagement letter. It ends when the first piece of work is on the calendar.
- Record your best person doing it on a real client. Record the screen and their voice. Ask them to say out loud what they click, what they check and why.
- Ask the what-if questions right after. What happens when the client sends the wrong documents? When they never log in to the portal? When they add a second business partway through?
- Turn the recording into steps. Have an AI assistant draft the first version from the transcript, then have a person who knows the work check every step against the recording.
- Test it on the next client. Have someone else onboard that client using only the draft. Every time they stop to ask a question, you found a gap. Fix it in the SOP, not in a side conversation.
The test: a newer team member onboards a client from the SOP alone. Their questions are about the client, not the process.
What goes in an SOP?
Six parts. If one is missing, the team fills the gap by asking someone.
| Part | What it answers | At an accounting firm onboarding a client |
|---|---|---|
| Trigger | What starts this? | The signed engagement letter comes back |
| Owner | Who is responsible from start to finish? | The onboarding lead, named by role, not by person |
| Steps | What happens, in what order? | Create the client record, send the welcome email and document list, open portal access, collect prior returns, assign the team, book the kickoff call |
| Exceptions | What do we do when it does not go to plan? | Documents still missing after the reminders, a new entity type, a client who starts midyear |
| System of record | Where does the truth live? | Your practice management software holds the client record and status. Your document portal holds the files |
| Done | How do we know it is finished? | The record is complete, the documents are in and the kickoff is booked |
Follow four writing rules.
- Start each step with a verb: create, send, check, assign.
- Name owners by role. People change jobs. Roles stay.
- Add a screenshot only where a step is easy to get wrong.
- Write for someone in their second week. Leave out what everyone already knows.
See how we approach this on our standard operating procedures page.
How do you keep an SOP current?
An SOP goes stale the day the work changes and the document does not. Build the update into the work.
- One owner per SOP. The owner is the person who updates it, not the person who wrote it first.
- Update on change. When your software, a rule or a handoff changes, the owner updates the SOP that same week.
- Turn repeat exceptions into steps. When the same exception comes up a second time, it belongs in the SOP.
- Show the date and owner at the top. Add a short note on what changed and why.
- Keep one copy. Archive old versions so nobody follows the wrong one.
- Review on a set schedule. Once a quarter, the owner walks through it with someone who does the work.
It is working when people stop keeping their own private notes.
Where does an AI assistant fit with your SOPs?
Set up an AI assistant to answer your team's questions from your SOPs. Someone types, "What do we send a new client who also needs payroll set up?" The assistant answers from the onboarding SOP and shows the step it used.
Set it up with four rules.
- It answers only from your approved SOPs and the documents you choose, not from the open internet.
- It shows its source. Every answer points to the SOP and the step, so the person can check it.
- It says when it does not know. If the SOPs do not cover a question, it says so and sends the question to the SOP owner.
- It respects access. People see only what they are already allowed to see. Client files stay where your firm's rules put them.
The questions it cannot answer are useful. Each one points to a gap in an SOP. The owner fills the gap, and the next person gets an answer.
To test it, collect ten real questions your team asked last month. Ask the assistant each one. Have the SOP owner mark every answer right, wrong or missing. Fix the SOPs before you fix the assistant. Our playbook to connect your company knowledge covers the setup.
Which steps should you automate, and which stay with a person?
Automate a step when the SOP describes it the same way every time and a mistake is easy to catch. Keep a person on a step that needs judgment, shapes the client relationship or carries risk.
| Onboarding step | Who does it | Why |
|---|---|---|
| Create the client record when the engagement letter is signed | Automation | Same every time |
| Send the welcome email and document request list | Automation | Same every time, with a list for each service |
| Remind the client about missing documents | Automation | Runs on a set schedule |
| Check what came in against the list | Automation, then a person reviews the gaps | Matching is repeatable. Deciding what a gap means is not |
| Review an unusual situation, like a new entity or a messy prior year | Person | Needs judgment |
| Assign the engagement team | Person | Depends on skills and workload |
| Run the kickoff call | Person | Sets the relationship |
| Handle a client who is confused or upset | Person | Needs a human answer |
Write the SOP before you automate. If the team does a step three different ways, automation repeats the confusion faster. Once the SOP is stable, the automated steps should match it line for line. The SOP should say which steps run on their own.
What can you do this week?
- Write down the onboarding questions your team asked in the last two weeks.
- Pick the process most of those questions point to.
- Record your best person doing it on the next real client.
- Draft the SOP with the six parts in the table above.
- Have someone else follow the draft on the client after that, and mark every place they stop.
- Name an owner and set the next review date.
- Mark each step: automate, keep with a person, or not sure yet.
If a key person is leaving soon, do step three first. You cannot make the recording after they go.
How does FlowChainLabs handle SOPs and AI?
We map how your business runs and build AI into it. We build it into the systems you already run, teach your team to use it and keep improving it. See how this looks for firms like yours on our professional services page.
Have a key person leaving, or a team that keeps asking the same questions? Schedule a strategy call. Bring the questions your team asks most and a recording of the process, if you have them.
