The AI readiness audit: what it covers and how to run one
An AI readiness audit examines how a team currently works and where AI could take part, before anyone commits budget to tooling. The word audit makes it sound heavier than it is. For a small team it is an afternoon of honest questions about your own week, and you can run it yourself.
Audit or assessment?
In practice the two words get used interchangeably, and most providers pick whichever their buyers respond to. Where a real difference exists, it is one of posture. An assessment scores where you are so you can decide what to do next. An audit checks what is actually happening against what people believe is happening, and the finding is usually the distance between the two.
That distinction matters more than the label. If leadership thinks the post-event report takes two hours and the person who writes it says six, the audit has already paid for itself, whatever you call it.
What an audit covers
- Where the hours actually go — not the org chart version, the real one. Ask people to account for a normal week and the surprises show up immediately.
- What is documented — which workflows survive the person who runs them, and which would stall if that person were away for two weeks.
- What tools are already in use — including the ones nobody told you about. Shadow usage is a readiness signal, not a violation.
- Where data lives — reachable in a system, or scattered across inboxes and someone's desktop.
- What rules exist — whether anyone has written down what is safe to paste into an AI tool. Usually nobody has. See an AI policy template.
Running one on yourself
List the recurring work
Every task the team does more than once per event or per month. Aim for fifteen to twenty-five lines. Anything you do once a year can wait.
Ask each person for their own hours
Get the estimate from the person who does the task, not from their manager. Collect it in writing so nobody adjusts in the room.
Ask the leader separately
Get leadership's estimate for the same tasks without showing them the team's answers. Compare afterwards. The tasks with the widest difference are where attention is most misplaced.
Mark what is written down
For each task, does a document exist that someone else could follow? Yes or no. Do not give partial credit for a document that is out of date.
Score and rank
Apply the 0-10 scoring in the framework, then sort. The ranking is the output; the individual numbers matter less than the order.
The scoring bands are in the 0-10 readiness framework, and the question set is in the 17 assessment questions.
The finding that shows up almost every time
The blocker is rarely the technology. It is that the highest-value workflows are undocumented, so there is nothing to hand over. A team can have every AI licence on the market and still get nowhere, because you cannot automate a process that only exists as a habit in one person's head.
Which makes the first action after most audits unglamorous: write down one workflow properly. That is also why audits are worth doing before buying tools rather than after. The tooling decision is easy once you know which three tasks you are actually trying to change.
What to do with the result
Pick one workflow and change it this month. Measure the before and after honestly, using the method in how to measure AI ROI. Then use that single number to earn the room for the next one. The rollout sequence is in AI adoption for event teams.
Frequently asked questions
- What is an AI readiness audit?
- An AI readiness audit examines how a team currently works, where its hours actually go, what is documented, and where data lives, so you can see where AI could take part before committing budget. Its distinguishing feature is checking what is happening against what people believe is happening.
- What is the difference between an AI readiness audit and an assessment?
- The terms are used interchangeably by most providers. Where a real difference exists, an assessment scores where you are so you can plan, while an audit checks belief against reality, and the distance between the two is usually the finding.
- Can a small team run an AI readiness audit itself?
- Yes, in an afternoon. List the recurring work, get hour estimates from the people who do each task and separately from leadership, mark what is documented, then score and rank. The ranking is the output.
- What does an AI readiness audit usually find?
- That the blocker is documentation rather than technology. The highest-value workflows tend to be undocumented, which means there is nothing to hand over, no matter how many AI licences the team has.
Want an outside read on it?
The Team AI Readiness Audit runs the same scoring across your whole team and returns a ranked list, an hours estimate, and a first build.
See the audit