An AI Audit Checklist for Executives Who Haven't Run One Before
A pre-flight checklist for commissioning an AI audit — what to prepare, who to invite, and the questions to answer before day one.
Commissioning your first AI audit is like commissioning your first physical exam. You'll do fine, but there are a few things you can prepare beforehand that make the exam useful instead of just a checkbox. This post is a short pre-flight checklist for executives running the audit process for the first time.
Before you sign the engagement
Confirm you have decision authority
An audit is only worth commissioning if someone has the authority to act on the output. If your board or CEO needs to approve the plan afterward, that's fine — as long as the audit is scoped to produce the document they'll approve.
If the audit will just get shopped around internally with no clear owner, delay it until the owner exists. Otherwise the plan lands on desks and dies quietly.
Set the deadline before scoping
The audit should end by a specific date, ideally driven by an internal event (board meeting, budget cycle, planning offsite). Working backward from that date creates the discipline that a fixed-scope engagement runs on.
If you can't name the date, ask yourself what the audit's plan is going to feed. If the answer is fuzzy, the audit will drift.
Agree the deliverables format upfront
Not "we'll figure it out." A specific list. Ours is: a one-page reality check, process maps with costs, a two-page competitive gap analysis, a prioritised action list (Google Sheet, not PDF), and a 3-5 page action plan.
Whatever the format, agree it before day one. Audits that renegotiate deliverables halfway through are auditing themselves, not your business.
The four to five people to involve
An audit needs a small, deliberately chosen core team from the client side:
- The decision maker — CEO, owner, or the executive with budget authority
- The operations lead — usually COO, head of ops, or head of a specific business unit
- The IT/tech representative — CTO, head of engineering, or systems lead
- The finance representative — CFO, controller, or finance business partner
- One power user — someone actually doing one of the workflows under review
More than five and the conversations get careful. Fewer than four and you lose one of the perspectives that keeps the plan honest. This is a case where the specific shape of the group matters more than any individual's title.
The artifacts to have ready
You don't need much before day one, but a few things speed the first two days significantly:
- An org chart at team level (not every individual, but the functions)
- Rough headcount and cost per major function
- The top three to five workflows leadership already suspects need AI
- Any existing AI tools in use, and how they're going
- A list of the three biggest operational pain points, in leadership's words
- Any prior strategy documents about AI, even half-finished ones
None of these need to be polished. Rough versions save more time than they cost.
The questions to answer honestly before day one
What outcome would make this audit worth the fee?
The answer should be specific. "A plan the board approves." "A prioritised list of three workflows to build in Q1." "A defensible number for our AI budget request." If the answer is vague, the audit will be too.
What's blocking us from making this decision internally?
Not blaming, just naming. Is it disagreement between departments? Missing information? Fear of the wrong bet? The audit team can address each of these differently, but only if the question is named.
What would a "no, don't automate this yet" answer mean for us?
Half the honest outcomes of an audit are "not yet" or "not this workflow." If you're only prepared to accept "go build" as an answer, you're not really commissioning a diagnostic — you're commissioning a rubber stamp. Confirm you'll accept a "no" if it comes.
What's our timeline for phase one after the audit?
The 30-day sprint that follows the audit needs to exist on your calendar. If it doesn't, the plan will land and stall. Book the phase-one kickoff before the audit starts, contingent on the plan being ready.
Communication during the audit
A well-run audit needs a light-touch communication cadence with the client team. What we recommend:
- A kickoff on day one (60-90 minutes)
- A quick check-in at end of week one (30 minutes)
- A working session on the prioritised list (day 11-12)
- The final delivery meeting on day 14
Between those, expect Slack access and asynchronous updates. If the audit needs weekly formal meetings, it's scoped like a retainer, which is a different engagement type.
What to prepare inside your team
Brief the workflow owners
The people whose workflows will be mapped need to know the audit is happening, why, and that shadowing isn't performance review. Frame it explicitly as "help us understand how this actually works, not how it should work."
Grant read access to relevant systems
Read-only access to your CRM, helpdesk, project management, and any AI tools in use. Set this up in the first two days — it's usually the boring bottleneck that costs the audit team a full day if it lingers.
Book the leadership team's time upfront
The leadership check-ins during the audit need to be on calendars before day one. Otherwise scheduling eats a week and the audit gets compressed.
Warn the CFO the plan will need a decision
Not a heads-up on the fee — a heads-up on the follow-on budget request. If the plan produces a $30K first-phase budget request, the CFO should know that's coming before it lands.
What to do while the audit is running
Mostly, wait. The temptation for executives is to steer the audit as it runs. Resist it. The value of an outside diagnostic is exactly that it isn't steered by internal politics.
What you should do:
- Answer honest questions promptly when the audit team asks
- Show up to the checkpoints prepared, not multitasking
- Reserve your reactions until the final deliverable — don't debate the plan mid-stream
What to do after the audit
Read the plan on day 14, decide within a week
The value of the audit decays if the decision is deferred. Read the plan on delivery day. Question it. Ask for clarifications. Decide within a week of receiving it. Any longer and momentum is gone.
Announce the plan internally
Not the whole document — a short summary of the top three priorities and the phase-one commitment. This makes the plan real and creates accountability inside the organisation.
Book phase-one kickoff on the calendar
Day 15, or as close to it as feasible. Every week between the audit ending and phase one starting is a week the plan gets diluted.
Use the 30-day Slack access
Most audits include a support tail after delivery. Use it. Pressure-test the phase-one scope, ask the questions that only come up once you start executing, and confirm the assumptions the plan was built on still hold.
Common mistakes in commissioning an audit
Making the audit team recommend the tools they'd sell
If the audit team also sells the implementation, incentive alignment matters. Insist that the audit's recommendations would be defensible even if the client took the plan to a different vendor. If the audit team can't say that, you're getting a sales document, not a diagnostic.
Skipping the qualification call
A good audit team runs a qualification conversation before scoping. If they take the engagement without asking whether you're ready, they're taking the wrong engagement. Insist on the conversation — even if you're eager to start.
Over-scoping the audit
Trying to cover every function, every workflow, every possibility. Two weeks isn't enough for that, and stretching to four doesn't make it enough either. Focus on three to five workflows that carry most of the ROI.
Under-scoping the follow-through
Commissioning the audit and then leaving no budget or capacity for phase one. The plan without a first build is a document. The audit only pays for itself when phase one ships.
Frequently asked questions
How much internal time does an AI audit actually require?
Roughly 10-15 hours total across the two weeks, spread over four to five people. The outside team does the process mapping, competitive analysis, and drafting. Your team's time is spent on interviews, checkpoints, and reviewing outputs.
Can we run an audit without executive sponsorship?
Not usefully. An audit without a decision-maker at the table produces a plan nobody has authority to act on. If executive sponsorship isn't available, the useful first step is smaller — a workflow inventory, or a single-process assessment — until sponsorship exists.
How do we know the audit will actually be honest?
Look for two signals in the scoping call: does the team push back on your framing when it deserves pushback, and are they willing to name outcomes that don't require ongoing engagement with them? A team that says "you might not need us for phase two" is the team you want auditing you.
What if we can't commit five people for two weeks?
Then the audit takes longer or produces a narrower plan. Both are honest outcomes. Compressing the team commitment doesn't compress the exercise — it just moves where the compromise shows up.
Where this fits
This checklist is the pre-flight for an AI Audit. If you're still deciding whether to commission one, our posts on signs your company is ready for an AI roadmap and AI audit vs consulting retainer are the earlier steps.
Working with us
Our AI Audit is scoped exactly for the shape of company this checklist assumes: 20-500 employees, one clear decision-maker, and a preference for a fixed-price diagnostic over a retainer. Two weeks, five deliverables, and a plan you can act on in phase one.
FAQ
Frequently asked questions
How do I prepare for an AI audit?+
Confirm you have decision authority, set a hard deadline, agree on deliverables in writing, assemble four to five internal participants (decision-maker, ops, IT, finance, one power user), and pre-gather rough artifacts like org chart, headcount, top workflows, and existing AI tools.
How much time will an AI audit require from our internal team?+
Around 10 to 15 hours total across two weeks, spread over four or five people. The outside team handles the process mapping, competitive analysis, scoring, and drafting. Your team's time is spent on interviews, checkpoints, and reviewing deliverables.
What happens if we don't act on the audit's plan?+
The audit's value decays fast. Most audits pay back only when phase one ships within 30 days of delivery. Commissioning an audit without booking follow-through time is a common expensive mistake.
How do we tell if an audit team is honest versus a sales pitch?+
In the scoping call, look for pushback when your framing deserves it, and willingness to name outcomes that don't require ongoing engagement with them. A team that says 'you might not need us for phase two' is auditing you, not selling to you.
Building something similar?
Let's talk in 30 minutes.