Every growing consultancy or agency has a few processes that “only Sarah knows”.
It might be how a particular client report is compiled, which checks happen before an invoice goes out, how a new client is onboarded, or where the awkward exceptions are in a monthly admin routine. While the business is small, that knowledge can survive informally. People ask across the room, search old emails, or copy what happened last time.
Then someone goes on holiday, is off sick, changes role or leaves. Suddenly, the business discovers that an important process was never really documented.
An example workflow: an internal process documentation gap-finder
This is an example automation workflow, not a real client case study.
Imagine a consultancy that has grown from five people to twenty. It has a shared drive containing some standard operating procedure documents, a project management tool with recurring tasks, and plenty of internal emails or Slack threads where people have explained “how we do this” in fragments.
A process documentation gap-finder does not try to replace proper management. It scans a defined set of sources and produces an audit. The assistant might review:
- a folder of existing SOP documents and their last-modified dates;
- a list of recurring internal task types from the project management system;
- optional recent internal messages where process steps are discussed;
- a simple list of high-risk business areas, such as onboarding, invoicing, reporting and compliance checks.
The output is a ranked gap report. It shows which recurring tasks appear to have no written SOP, which SOPs have not been updated in over a year, and which missing documents should be prioritised first. For the top one or two gaps, the assistant can also create a draft outline or skeleton for a team member to complete.
For example, the report might flag that “new retainer client onboarding” appears in project tasks every month, but there is no matching SOP in the shared drive. It might also find that the “monthly management report” SOP exists but was last updated eighteen months ago, despite several process changes being discussed in internal messages since then.
Why this is a business resilience issue
Process documentation can sound dull until the moment it is needed. The real issue is not tidy folders. It is business continuity.
If the person who understands a process is unavailable, can someone else complete it safely? If a new hire joins next month, will they learn from a clear process or from half-remembered explanations? If a client asks why something was done a certain way, can the firm point to an agreed method?
A gap-finder helps leaders see the weak points before they become urgent. It is especially useful when preparing for growth, onboarding new staff, handing over responsibilities, or reducing dependence on one experienced person.
Keep the assistant in audit mode
This is a low-risk workflow if it is kept as an audit and drafting assistant.
The assistant should not publish official internal guidance by itself. A manager or operations lead should review the gap report and any proposed SOP outline before it is treated as approved. The people who actually perform the task should validate the steps, exceptions and edge cases.
Access also needs to be sensible. If the audit includes internal emails or chat threads, the assistant should only read sources that are already visible to the person running the audit. There is no need to give broad access to private messages just to find process gaps. In many firms, the first version can work from a shared drive and a manually exported list of recurring tasks.
What the output might look like
A useful report does not need to be long. It could include three sections:
- Missing SOPs: recurring tasks with no matching written process.
- Stale SOPs: documents not updated for more than twelve months, or likely contradicted by newer activity.
- Priority recommendations: the top gaps to close first, based on frequency, risk and dependency on one person.
For the highest-priority missing SOP, the assistant might draft a simple skeleton: purpose, owner, inputs, steps, exceptions, checks and review date. That gives the team a starting point without pretending the document is finished.
A practical first step
List the ten recurring internal tasks your business relies on every month. Then check whether each one has a written, findable, recently reviewed process. If more than a couple are missing, you have a documentation risk worth addressing.
If your business depends on knowledge held in a few people’s heads, AI can help you audit the gaps and create sensible first drafts. I help consultancies and professional SMEs design practical, human-approved AI workflows like this. If you want to explore your own version, book a short call.
