How to Run an AI Systems Audit for Your Organisation in 5 Working Days

A practical five-day process for mapping AI information gaps — no consultant required, no jargon, and a clear Architecture Brief you can act on by Friday.

AI systems audit complexity vs clarity scales diagram

You don’t need to pay £9,000 a month to find out where your AI strategy is failing. This AI systems audit guide gives you a map — and this is how you build one in five working days.

The most valuable thing I deliver to a client in our first week isn’t a 50-page strategy deck.

In essence, it’s a map.

A simple, brutal diagram showing every single place in their business where an expensive digital system stops — and a human being has to manually type information into another one.

You don’t need to pay me £9,000 a month to build this map. You just need five days, a structured process, and the willingness to ask questions your IT department has been quietly avoiding.

Before you start, three questions will anchor the entire process. One: where does information leave one system and get entered manually into another? Two: what decisions are being made on stale, disconnected, or incomplete data? Three: which workflows require a human to be present simply to move information between tools?

Every activity across the five days maps back to one of these three. Keep them visible throughout the process — print them out if it helps.

The full commercial context for why these three questions underpin a fractional AI consulting service is in the pillar article for this series: The Fractional AI Architect — I’m the Person Companies Call When Their AI Strategy Turns Into a £2M Bonfire.

DAY 1 — Inventory Everything in Your AI Systems Audit

You are not solving problems today. Instead, you are creating an accurate picture of what exists.

What to do:

  • List every digital tool the organisation uses — including shadow tools and free-tier accounts not on the approved list.
  • For each tool connection, ask one question: is this transfer automatic, or does a human do it?
  • Mark every manual transfer as a gap. Not a potential gap. An actual gap where information is delayed, mistyped, duplicated, or lost.
  • Pay particular attention to gaps that happen on a schedule — the Monday morning report assembled from three systems, the end-of-month reconciliation built by hand. These are your highest-priority targets.
  • Output: A handoff map. Every automatic connection in green. Every manual transfer in amber. The amber nodes are your audit.

DAY 2 — Map the Handoffs

Furthermore, day two takes the inventory and adds consequence. You’re not just noting that a handoff exists — you’re establishing what breaks when it goes wrong.

As a result, this is where the smartest people in your organisation become your biggest risk. For example, the employees who have learned to work around broken architecture are often the last to flag it — because they’ve built the workaround themselves, and it works, until it doesn’t.

DAY 3 — Audit the Decisions

Importantly, most AI implementation projects fail not because the technology doesn’t work, but because decisions get made on the wrong data at the wrong time. Day three maps which decisions in the organisation rely on information that passes through manual handoffs before it arrives.

What to do:

  • List the five most important recurring decisions your organisation makes.
  • For each one: trace the information backward. Where did the data come from? How many manual touches did it pass through before it reached the decision-maker?
  • Every manual touch is a latency cost and an error risk.

The three-question stress test is useful here: Is this transfer automatic, or does a human do it? What decisions rely on this data? What breaks when the data is late or wrong?

DAY 4 — Score the Gaps

By day four, therefore, you have a map and a decision impact list. Now score each gap on two dimensions.

What to do:

  • How often does this gap occur? (Daily, weekly, monthly)
  • What is the consequence when it goes wrong? (Revenue risk, compliance risk, decision failure)
  • High frequency + high consequence = fix this first. Low frequency + low consequence = park it.
  • Do this exercise with the people who actually do the work — not just the managers who commissioned the audit. The people doing the work know exactly how bad each gap is.
  • Output: A prioritised gap list with a clear build order.

DAY 5 — Write the Brief

Ultimately, the output of an AI systems audit is not a PowerPoint. It’s a brief.

  • Document three to five gaps with their frequency and cost consequence.
  • Describe the architecture that closes each gap — what should connect to what, triggered by what, with what exceptions.
  • Sequence the build: quick wins first (high impact, low complexity), longer-term changes second, deferred items third.

In other words, this brief is what any implementation specialist, automation developer, or fractional AI architect needs to begin work. It turns vague organisational anxiety about the AI setup into a manageable engineering project with clear deliverables and measurable outcomes.

AI Systems Audit Results: What Comes Next

A five-day AI systems audit produces a map and a brief. What you do with them depends on your organisation’s complexity. Some will find two or three Zapier automations close 80% of the gaps. Others will need a more substantial engagement.

For the full 4-week implementation process — including the 20-question diagnostic framework and scored prioritisation matrix — the companion post walks through the complete methodology.

If you’re also wondering whether the fear around AI replacing roles is the right lens — rather than the cost of not integrating it properly — The Real Cost of AI Tool Sprawl: What £400K Buys You (And What It Doesn’t) gives the financial case for doing this work properly.


Tools for Non-Technical Leaders

Put This Audit Into Practice

The resources below are built for the kind of work this article describes.

AI Audit Template (Gumroad) | AI Audit Template (Ko-Fi)
The complete 20-question diagnostic framework, scored prioritisation matrix, and Architecture Brief template. Available as a downloadable Google Sheets file.

Decision-Making Implementation Pack — Nine frameworks for high-stakes decisions, built for the kind of clarity problem this article describes.

MBA Alternative Reading Kit (FREE) — The mental models MBA programmes charge six figures to teach, in one free 57-page guide.

Ko-Fi Practitioner Membership — Get the AI Audit Template and other tools free, plus direct access.


Before you go: What’s the one manual transfer in your organisation that would embarrass you most if someone mapped it publicly? That’s your Day 2 starting point. Drop it in the comments — the more specific, the more useful.