Capability template for operations and process improvement
SOP exception capture
Turn what your most experienced person does with the awkward cases into an exception register for one procedure. Once the owner approves it, every colleague handles those cases the way your best person does.
The outcome
Every step of the procedure carries the decisions, stop conditions and escalation paths your best people already use, each traced to a real case. A new hire handles the awkward case in their first week. An AI assistant preparing the work flags it and names whom to ask. The whole team works at the level of its best person, and that is how you 10X what it can do.
The people who do the work are the source of every rule. Where colleagues disagree, the owner settles it once.
Who starts the work, and when
The procedure’s owner starts it: an operations lead, a controller, a firm administrator or a people lead. Start before a procedure goes to AI or a new hire, after the same mistake happens twice, or before the one person who knows the exceptions changes role.
What they supply
- The written procedure, or a transcribed walkthrough where there is none.
- Three to five recent real cases, including one that went sideways, with client details removed.
- Thirty minutes with the person who does the work.
What comes out
You get an exception register for the procedure. For each step it records the missing decisions, the stop conditions, who is asked, the rule the expert follows and the evidence (which case, which words). Open questions where colleagues disagree come last, for the owner to settle. Nothing changes in the procedure until the owner approves.
A good register uses the expert’s words, cites a case for every rule and leaves each disagreement for the owner.
An invented example
Illustrative example with invented data. An invented regional building-supplies distributor: the procedure, then one step of its register and the open questions.
New-customer account setup
Sales operations · Version 2
- Receive the signed account application from the account executive.
- Check the business details against the application.
- Send the application to the credit controller for terms.
- Collect the tax exemption certificate where one applies.
- Create the account in the order system.
- Send the welcome pack and first-order instructions.
Owner: Operations lead
Exception register · New-customer account setup · Step 4, collect the tax exemption certificate
- Missing decisions: What to do when the certificate is expired, issued to another entity or promised to follow.
- Stop conditions: The certificate name differs from the account’s legal name. The certificate has expired.
- Who is asked: The finance lead.
- Expert’s rule: Set the account up as taxable until a valid certificate in the account’s legal name is on file. Never mark an account exempt on a promise.
- Evidence: Account 5518: marked exempt on a note; the certificate arrived in the parent company’s name. Coordinator: “I set them up taxable and switch them when the certificate is in.”
Open questions for the operations lead
- Question 1: With no trade reference, one coordinator holds the account; another opens it on cash-on-delivery terms. Which is the rule? Evidence: Accounts 5509 and 5530.
- Question 2: Who releases a first order before setup is complete? The account executive and the credit controller each name themselves.
Status: draft for the operations lead’s approval. The procedure has not been changed.
Where it fits
- Operations and process improvement, where procedures are owned.
- Quality management: a stop condition is a check built into the step.
- Finance and accounting, where approvals, tolerances and cutoffs hold the exceptions.
- Law firms, for intake, billing and file procedures.
- Professional services, where senior staff carry the judgment.
- Logistics and trade, where shipments rarely arrive as the procedure assumes.
- Manufacturing, for receiving, returns and supplier procedures.
- Growth & scaling, when hiring outpaces coaching.
- Acquisitions & integration, when two teams run one procedure two ways.
- Established businesses, where long-serving staff hold unwritten rules.
What has to change for your company
Name the owner who settles disagreements. Decide which cases can be shared and what client detail comes out first. Set your own thresholds, and agree where the approved register lives and who approves later changes. The register then becomes the job aid and the instructions an AI assistant works from, on ChatGPT, Claude, Copilot or Gemini. Your organization keeps control of how the work gets done.
What has been checked
Fully Powered AI wrote this capability template. It was editorially reviewed on 9 November 2026. It has not yet been tested in a client environment. It has not yet been tested as a packaged version in ChatGPT, Claude, Copilot or Gemini.
Testing in your environment means running it on one of your procedures and cases, then checking the register with your expert: every rule cited, every disagreement left open, nothing changed without approval. Pilot acceptance-test preparation sets those cases up, and what we test before we call an AI workflow ready describes the record we keep.
The full capability template
Everything above is the outline. The complete capability template is the working version: the roles, the inputs, the procedure, the exceptions and stop conditions, the output format, the reviewer checklist, the acceptance tests, the instructions for an AI assistant and what to customize for your company. It comes with a download and the link to its folder in Fully Powered’s public repository.
Free with an account. Sign in by email: no password and no card.
Next step
Bring a real piece of this work to a call. We’ll walk through what it takes to fit this capability to your rules, prove it on your work and put it in the hands of the roles that own it.