Skip to content
Programme governance

Voice AI board pack: the one-page template for the steering committee

  • VP / COO
  • CX directors
By Lewis CrookPublished
Bottom line up front

If the executive sponsor cannot read the entire report in three minutes, the report fails. One page, five lines, written prose, no dashboard exports.

The five-line template

Each line is one paragraph, two to four sentences. No charts, no tables, no exported tiles. The discipline of writing it produces sharper thinking than any dashboard ever will.

  1. Primary metric vs target. Single number this quarter, single number target. One sentence on any miss, named cause, named owner.
  2. Top three failure modes shipped against this quarter. Each one named, the change shipped, the measured impact.
  3. Top three failure modes carried from last quarter. Each one named, the reason it remains open, the date by which it closes.
  4. What shipped, what is shipping. One paragraph each. Concrete artifacts, not categories.
  5. Forward risk. The single risk most likely to compromise the next quarter, with the mitigation already in motion.

The four questions sponsors actually ask

Every steering committee asks the same four questions in some form. The pack should answer each before the question is asked.

  • Are we on track against the business case? — primary metric line
  • What are we doing about the thing that broke last month? — carried failure-mode line
  • What is the next big risk? — forward-risk line
  • What happens if we pull funding? — implied in the carried failure-mode line; make it explicit in the appendix

What not to include

  • Dashboard exports — the sponsor will not scroll
  • Vendor-supplied slides — the sponsor cannot judge them
  • Quarter-on-quarter charts before the second quarter — there is no trend yet
  • The full failure-mode catalogue — top three carried, top three shipped, nothing more
  • Long-form vendor evaluation language — that lives in the procurement record, not the operating board pack

The appendix — what belongs there

Behind the one page sits a structured appendix the sponsor can open if they want to. Three things, in order.

  • Methodology note — how every number on the front page is calculated, dated to the current quarter
  • Risk register — full risk list with owner, mitigation, and date; the front page lifts only the top one
  • Kill-criteria status — each of the five gates, current status, trend versus last quarter
Do this on Monday

Write the next board pack to this template today. If a section feels uncomfortable to write, that is the section the steering committee needs to read.

Key takeaways
  • One page, five lines, written prose — no dashboard exports.
  • Primary metric, top three shipped, top three carried, what shipped / what is shipping, forward risk.
  • Always pair containment with re-contact; never report one without the other.
  • Appendix carries the methodology note, full risk register, and kill-criteria status.
  • Operations lead writes the pack; vendor contributes, does not author.

Frequently asked questions

Why five lines and not more?
Because the constraint forces prioritisation. A ten-line pack lets the team include the comfortable lines; the five-line pack forces the uncomfortable ones to the front.
Who writes the board pack?
The operations lead, not the vendor. The pack is the customer's narrative about the programme, not the vendor's report on it.
What is the most common board-pack mistake?
Reporting containment without re-contact. Containment alone reads as good news; the moment re-contact is added, the picture is honest. Steering committees notice when the second number is missing.

Terms used in this guide

  • Voice AIVoice AI is software that answers the phone, understands what the caller wants, and takes action — not just a smarter IVR.
  • Containment rateContainment rate is the percentage of calls the automation finished on its own.
Last reviewed: 2026-06-15. This guide is updated when production patterns shift; see the corrections page to flag anything that no longer matches reality.
About the author
Lewis Crook
Practitioner writer on enterprise voice AI

Lewis Crook — 20 years in enterprise technology, from FTSE 100 voice deployments to over a million AI-handled minutes a month across Asia-Pacific. Buyer, builder, and now working with CX leaders on enterprise voice AI. Writes The Voice AI Brief. Connect on LinkedIn. More about Lewis.

Newsletter
Liked this? Get the next edition.

Plus the Voice AI Readiness Diagnostic in the welcome email.

Welcome email includes the Voice AI Readiness Diagnostic. No second list, no extra form.