The Business Review Preparation Checklist I Run Before Anything Reaches My CEO's Calendar

The Checklist Nobody Taught Me

Ninety minutes before a Monday leadership review last quarter, I opened a slide that said a customer account was "on track" and, out of habit more than suspicion, clicked through to the actual support queue behind it. The ticket that slide was built on had been reopened two hours earlier. Nobody had touched the slide since. Nobody was going to before the meeting started. If I hadn't clicked through, I would have told my CEO an account was healthy that, as of that morning, was actively on fire.

That's not a formatting problem. It's a verification problem, and almost nothing written about "business review checklists" is built to catch it — most of it is written for account managers prepping a customer-facing EBR, where the worst outcome is an ugly slide. In an internal leadership review, the worst outcome is telling your CEO something false to his face.

A business review preparation checklist for an internal leadership review needs to check four things: every number against its live source, not the version pulled three days ago; every open risk with a named owner; every prior decision's follow-up status actually confirmed; and one person explicitly accountable for a same-day "is this still true" pass. Most checklists people find online cover none of these, because they were never built for this room.

Check 1: Is the Number Still True Right Now — Not Three Days Ago

Most prep cycles treat data-gathering as something you finish on Thursday and format for the rest of the week. The problem is that Thursday's number and Monday's number are not the same number, and nobody budgets time to notice the difference.

A 2025 survey of 550-plus data and analytics professionals by Precisely and Drexel University's LeBow College of Business found that 67% don't completely trust their own data for decision-making — up from 55% the year before. That's people who work in data every day, looking at systems they own. If they're not confident the number is still true, the operator building a deck from a Thursday export has even less business being confident.

I've watched a customer's churn-risk score go from an 82 on Thursday to a 41 by Monday, because an integration test failed over the weekend and nobody thought to flag it outside the product team's own channel. Same account, same slide, completely different conversation depending on which day you pulled the number. This is exactly the gap Rhythms' Reviews is built to close — instead of a deck assembled from whatever export existed when someone had time to build it, the numbers get pulled from the connected system at the moment the review actually opens, not the moment someone remembered to check.

Check 2: Does Every Open Risk Have a Name Attached to It

A risk without an owner isn't a risk. It's a line item everyone has silently agreed someone else is handling.

I once watched an integration delay show up in three consecutive weekly reviews as "in progress" before anyone realized it had no actual owner — just a team it had been generally assigned to. By the time someone asked "whose is this," it had cost three weeks nobody could get back. The fix is a rule: if a risk doesn't have one specific person's name next to it, it doesn't go on the slide as "being managed." It goes on as "unowned" — a different, far more useful sentence for a CEO to read.

Check 3: Did Every Decision from the Last Review Actually Get a Status

Decisions made in a leadership review have a strange half-life. They feel resolved in the room, and then they vanish until three months later when someone asks, half-joking, half not, "did we ever actually do that?"

I keep a running list now — not a shared doc everyone forgets to update, but a specific check I run before every review: for each decision made last time, what changed as a direct result of it. If the answer is "nothing yet, and here's why," that's a fine answer. If the answer is a blank stare, that's the thing worth catching before the meeting, not during it. This is the exact overhead Playbooks was built to absorb — the recurring cadence that carries last review's decisions into this one automatically, instead of relying on someone's memory of a conversation from six weeks ago.

The Four Smaller Checks That Catch Everything Else

The big three cover the failure modes that actually sink a review. These four catch the ones that just make it worse — and one of them, honestly, might be the most important check on this whole list.

Does the deck assume context the room doesn't have. A new board observer sat in on a leadership review I ran last spring, and half my slides referenced internal shorthand — "the Q3 pull-forward," "the renewal cliff" — that meant nothing to her. I hadn't built it for someone joining cold. Now I read every slide once as a stranger would, before I read it as the person who built it.

Is there one named person doing the final pass — not "the team." "The team will double-check it" is functionally the same sentence as "no one will," because everyone on the team assumes someone else already did. The fix is boring and it works: one specific name, an hour before the meeting, whose only job in that hour is opening the actual source systems — not the deck — and confirming nothing has changed since the last pull.

Have you actually opened the source system, or just trusted last week's export. A pipeline number I'd built from a Thursday Salesforce pull was off by roughly $180,000 by Monday morning, because a deal had quietly slipped a stage over the weekend. This is exactly where Radar earns its keep — it surfaces a stage change like that the day it happens, not the morning of the review when it's too late to do anything but explain it.

Is "I don't have confirmed data on this yet" somewhere in your prep. I resisted this one longest. I used to think being thorough meant having an answer for everything. It took me longer than I'd like to admit to realize that having an answer for everything is usually a sign you've stopped checking, not a sign you've checked enough. Telling my CEO "I don't have confirmed renewal numbers on two accounts yet, I'll have them by 2pm" has never once cost me credibility. Guessing, and being wrong in front of the leadership team, has cost me plenty.

What I'd Tell Myself Before That Monday Review

If I could go back to the version of me building that "on track" slide, I wouldn't tell her to work faster or check more sources. I'd tell her that the sentence "I don't have confirmed data on this yet" is not an admission of failure — it's the single most useful sentence available to someone prepping a leadership review, and most people are too embarrassed to say it out loud.

A leadership team doesn't lose trust in a review cadence gradually. It loses trust the first time someone catches a number that was wrong, and it remembers that moment for a lot longer than it remembers the eleven reviews that went fine. The checklist above exists to make sure that moment doesn't happen on your slide. But if it's ever a choice between guessing and saying "not yet, and here's when I'll know" — say the second thing. It's the check that makes every other check on this list actually hold.

Try for free at rhythms.ai.

Frequently Asked Questions

What should be on a business review checklist before it goes to leadership?

At minimum: every number cross-checked against its live source rather than the version pulled three days ago, every open risk flagged with a named owner, every prior decision's follow-up status confirmed, and one person explicitly accountable for the final "is this still true" pass — not assumed to be everyone's job, which in practice means it's no one's.

How do I make sure the numbers in my business review are still accurate the morning of?

Build in a same-day refresh step, not just a source check three days out. The riskiest gap isn't old data — it's data that was true when the deck was built and quietly changed afterward: a support ticket reopened, a deal slipping stage, a metric crossing a threshold overnight.

What's the difference between prepping a customer-facing EBR and an internal leadership review?

An EBR is built to reassure a customer. An internal leadership review is built so your CEO can make a real decision in the room. The stakes are different — a stale number in an EBR is embarrassing. A stale number in a leadership review can send your CEO into a board conversation with something false.

How far in advance should I start preparing a business review?

Start structural prep three to five days out — gathering inputs, drafting the narrative — but treat the final 24 hours as a verification pass only, not a building pass. If you're still building content the morning of, the checklist failed earlier in the week, not that morning.

Who should own the business review checklist — the Chief of Staff or the function leads?

The person who owns the review should own the final verification pass, but each function lead should own their own section's accuracy. Centralizing verification without decentralizing ownership just recreates the same bottleneck with extra steps.