Automation · 7 min read

From SOP to agent: how a written process becomes something Copilot Studio can run

James Wilkinson

By James Wilkinson 12 September 2026 Updated 30 October 2026

Everyone says document your processes first. Nobody says what the document must contain. The engagement letter procedure, before and after it is mapped.

TL;DR
  • The SOP as it usually exists is seven numbered steps on a shared drive and the rest in someone's head. The honest answer to most of the questions we ask in Map is it depends who is doing it that week, and that is the reason it cannot be automated yet.
  • Five questions turn a procedure into something buildable: what varies, what is copied from elsewhere, who decides and on what, where it waits and what goes wrong. The answers become form fields, lookups, approval steps, triggers and exception paths.
  • Every step in the running version is one of three kinds: a flow does it, an agent drafts it or a person decides it. Labelling each step is most of the map.
  • What changed: the form became the SOP, the approvals became visible, the exceptions got a path and the partner's time moved from amending to approving. The approval is the control.
  • The useful preparation is not rewriting the SOP. It is listing the last five times the process went wrong, how long each of the last ten approvals waited and everything that gets copied from somewhere else.

Everyone says document your processes first. Almost nobody says what the document has to contain, which is why so many firms arrive with a neat procedure and leave the first conversation realising it describes about half of what actually happens. This post shows the transformation on one process, the engagement letter, from the page on the shared drive to the version Copilot Studio can run. The thing to take away is that the exceptions and the approvals are the specification, and they are the parts nobody has written down.

The before version below is a typical firm’s, written to be recognisable rather than taken from anywhere. The after version reflects what we have built. Where a step is the next phase rather than live, it says so.

The procedure as it usually exists

Here is the engagement letter SOP, more or less as it sits in most practices’ procedures folder.

  1. Partner agrees services and fee basis with the client.
  2. Partner emails business support with the details.
  3. Business support opens the template, fills in the client details, selects the service paragraphs and adjusts the fees.
  4. Draft sent to the partner for review.
  5. Partner amends or approves.
  6. Letter sent to the client for signature.
  7. Signed copy filed. Client record updated with the services. Onboarding checklist started.

Seven steps, one page, and it is not wrong. It is just not the process. Sit with the people who do it and ask what happens when there are two signatories. When the client is a group of companies. When the client is not yet a client and has no record to update. When the partner is away. When KYC has not cleared. When the client signs, but with a change in the margin. Who decides the fee when the standard rate does not apply. Where the letter waits at each step, and for how long, and who notices when it has waited too long.

The honest answer to most of those is “it depends who is doing it that week”. That answer is not a criticism of the firm. It is the reason the process cannot be automated yet. A flow needs to know what to do with two signatories every time, not the way whoever is in that week does it.

The five questions Map asks

Map, the first two weeks of a Firmwide install, is not a technical audit. It is time spent with the people doing the work, mapping the workflow as it actually runs, and five questions do most of the reshaping.

What varies between one run and the next? Client, services, fee basis, signatories, group structure. Those become form fields, and the form becomes the way the process starts.

What is copied from somewhere else? Client address, company number, partner name, last year’s scope. Those become lookups, pulled from the system that holds them rather than retyped.

Who decides, and what do they decide on? The partner decides the terms. Business support checks the details. KYC clears the client. Those become approval steps with defined inputs, so each approver sees what they need to decide and nothing else.

Where does it wait, and why? In the partner’s inbox. In the client’s inbox. In a folder waiting for KYC. Those become triggers and notifications, or they get removed altogether when the waiting turns out to serve no purpose.

What goes wrong, and what does someone do when it does? The two-signatory case, the group, the non-client, the signed-with-changes letter. Those become the exception paths and, for anything that does not fit a path, the review queue.

The output of Map is the answers, and what the answers become: the workflow map with every step labelled, which the Foundation and Agents and skills steps build from. The price was fixed earlier, on the Plan on a Page that follows a Readiness Check. The FiveForward Framework page shows where each step sits in the five.

The same procedure after Map

Here is the engagement letter again, with each step labelled by who or what does it. Three kinds of step: a flow does it, an agent drafts it or a person decides it.

  1. Form (person). The partner or business support completes one form: client, services, fee basis, signatories, group companies if any, KYC status. The form asks the questions in order, every time.
  2. Lookup (flow). Client details are pulled from the practice system. If the client does not exist yet, the non-client path creates the record first.
  3. Draft (agent, or a template merge where the wording is fixed). The engagement letter is generated from the firm’s own template with the selected service paragraphs and fee wording. In the next phase, the same request also produces the risk assessment and the fact find.
  4. Approval chain (flow with people in it). Business support check, partner approval, KYC clearance. Each is a Teams approval with the draft attached. Nothing proceeds until all three have said yes, and each approval is timestamped.
  5. Send and sign (flow plus person). The letter goes for signature. The signed date is captured when it comes back.
  6. Record update (flow, gated). Services are written to the client record only once the signed date is populated. This detail is real and worth a sentence: the record reflects what the client signed, not what was proposed.
  7. File (flow). The PDF is filed to the document management system and the document reference stored back on the client record. The status is visible throughout, so “where is the letter” has an answer without asking anyone.

Evidence status, plainly. The form, the background generation, the review before sending and the change from 30 to 60 minutes of assembly to a few minutes of form filling are delivered, at a practice we work with, and the form-and-flow version is written up in our engagement letter automation example. The three-document output, the approval chain with KYC, the non-client path, the signed-date gate and the PDF and document reference on the record are the next phase, in progress. They are described above as the shape that phase takes, not as live.

On the labels. Steps 2, 4, 5, 6 and 7 are flows because they should behave identically every time, and the line between that and an agent step is the subject of Copilot Studio vs Power Automate. Step 3 is where wording varies, which is what a drafting agent is for. The newer Workflows Designer in Copilot Studio lets both kinds of step sit on one canvas, which makes a map like this easier to build as drawn. The post pipeline in one letter, two minutes is the same three labels applied to incoming correspondence.

What changed

Four things, none of them the technology.

The form became the SOP. There is no longer a page in a shared drive that may or may not be followed. The form asks the questions, in order, every time, and a run that skips a question cannot start. The procedure is enforced by the fact that it is the only way in.

The approvals became visible. “Waiting for the partner” was invisible before. Now it is a status with a timestamp, and the person who set the process running can see where it is without asking. This alone changes behaviour, because a letter that has waited three days is visible to everyone rather than to nobody.

The exceptions got a path. Group companies, multiple signatories and non-clients used to be handled by whoever knew how. Now each has a defined branch. Anything outside the branches stops and asks a person, which is the same rule the post pipeline runs on: when unsure, route to a person rather than guess.

The time moved. Thirty to sixty minutes of assembling became a few minutes of form filling and a review. The partner’s time did not go down much. It moved from amending a draft to approving one, and the approval is the control point, not a formality. That is the honest description of what automation does to a partner’s role: it changes the shape of the work rather than removing it.

What this means for your own SOP

If your firm wants a process ready for Map, the useful preparation is not rewriting the procedure. The polished version is the least informative document you have. What is worth an hour is listing the exceptions and the approvals honestly, and three prompts get most of it out.

Write down the last five times this process went wrong, and what someone did about it. Write down who approved the last ten runs and how long each one waited at each step. Write down everything that gets copied from somewhere else, and where from.

That list is the specification. It is worth more than the procedure, and it is what the first Map conversation would spend its time trying to reconstruct. The engagement letter is one of five admin jobs an agent can take off a practice, and the same three prompts work for every one of them.

From the map to the running version

The route is the same for every firm. A free Copilot Readiness Check tells you where Copilot can and cannot see your data, the two jobs to automate first and a rough install price, and the Plan on a Page fixes it. The Firmwide install then builds it over six to eight weeks: Map, the foundation that makes Copilot safe and useful, then an agent and a skills pack per department, with an engagement letter agent like this one chosen from the six accountancy agents or built bespoke. The first department is £6,950 and each extra department £2,500, excluding VAT. The handover shows the people who run the process how to use it on their own cases, by the people who built it.

Whichever size of install, the running version needs an owner from the day it goes live, because the form, the approvals and the connectors all move. What happens after the agent is built is about who that is.

Related reading

More on Automation

Automation Copilot Studio workflows designer: first look and what the billing question means A first look at Microsoft's Workflows Designer in Copilot Studio. What's new, what's missing and why the licensing question matters for Power Automate users. Automation Automation maintenance for Microsoft 365: why workflows need ongoing support Automation maintenance is what keeps Microsoft 365 workflows saving time. Owners, monitoring, documentation and change reviews stop quiet failures. Automation Copilot Studio's new engine: what the GitHub Copilot harness changes and what it costs Copilot Studio's default is now the GitHub Copilot harness, the engine behind Copilot Cowork. What changes, what the credits cover and the checks before you build. How we work The FiveForward Framework Five steps from a free Copilot Readiness Check to agents kept running: Check, Plan, Build, Handover, Run. The install Firmwide A fixed-price install, typically six to eight weeks: Copilot made safe and useful in your Microsoft 365, an agent and a skills pack for every department, handed over with training. Then Run keeps it working. Automation Strategy Copilot Studio vs Power Automate: when each is the right answer A practical guide to choosing between Copilot Studio agents and Power Automate flows for Microsoft 365 work, with examples for UK professional services firms. Industry Copilot Five admin jobs an agent can take off a 30-person accountancy firm Post, engagement letters, WIP reporting and meeting write-ups: five admin jobs we have built or scoped agents for, what stays with a person and what each costs. Copilot Agents What happens after the agent is built? Why every agent needs an owner An agent is a running service, not a finished project. What changes after go-live, the five-point minimum a firm with no IT team can run and who owns it. Copilot Agents One letter, two minutes: inside a post room agent A VAT penalty notice arrives at 09:02. By 09:04 it is filed, logged and visible in Teams. What happened in between, and what pipeline, agent and flow mean. Client acceptance Engagement letter automation Letters of engagement and representation generated from a form in the firm's CRM into controlled Word templates, so the partner reviews rather than drafts. It is the core of the client onboarding agent.

Common questions

Questions about preparing a process for an agent build

What does an SOP need to contain before it can become an agent?
The exceptions and the approvals. A procedure that lists the happy path in seven steps is a starting point, but the specification is what happens when there are two signatories, when the client is a group, when the partner is away and when KYC has not cleared. If those answers are it depends who is doing it, the process is not ready, and the Map step of a Firmwide install exists to get the answers out of people's heads and onto the map.
What is the difference between the Readiness Check and the Map step?
The Copilot Readiness Check is 30 minutes, free and online. It tells you where Copilot can and cannot see your data, the two jobs to automate first and a rough install price, and the Plan on a Page follows with the price fixed. Map is the first two weeks of the install itself, time spent with the people doing the work and mapping each workflow as it actually runs, with every step labelled flow, agent or human. The Readiness Check decides what to build. Map works out exactly how.
Is the engagement letter process an agent or a flow?
Mostly flows, with a drafting step in the middle and people at the approval points. The lookup, the approval routing, the filing and the record update are flows because they should behave identically every time. The drafting is where wording varies, and that is an agent step or a template merge depending on how much varies. The rule is that agents talk and flows do.
Which parts of the engagement letter build described here are live?
The form, the background generation, the review before sending and the change from 30 to 60 minutes of assembly to a few minutes of form filling are delivered at a practice we work with. The three-document output, the approval chain with KYC, the non-client path, the signed-date gate and the PDF and document reference on the record are the next phase, in progress, and are described here as the shape that phase takes.
Does the partner's role shrink when the process is automated?
It changes rather than shrinks. Before, the partner amended a draft that business support had assembled. After, the partner approves a draft generated from the form, with the draft attached to a Teams approval. The time spent does not fall much. What changes is that the approval is now the control point, visible and timestamped, rather than an email that may or may not have been read.
Can our own team do the mapping instead of FiveForward?
The three prompts at the end of this post are the part your team can do before anyone from FiveForward arrives, and the Map step goes faster when they have. The mapping itself is done with your team in the first two weeks of a Firmwide install, on your own processes rather than an example, and the handover at the end shows each department how the finished agents and skills run on its own data. There is no separate self-build route.