
Progress Report Checklist Before a Leadership Review: 7 Items That Surface Real Gaps
TL;DR
- •A progress report before leadership review must show Plan vs Fact vs Gap by workstream.
- •Include only what changed since last update — no activity logs.
- •Flag blockers with owner-level impact, not task-level noise.
- •How to structure a progress report before a leadership review**
- •What to include in the checklist**
- •[ ] Each workstream shows one clear Plan vs Fact comparison (no vague “ongoing” or “in progress”).
- •[ ] Gaps are quantified in time, cost, or decision delay (e.g., “2-day delay in vendor sign-off pushes launch to Friday”).
- •[ ] Blocker ownership is clear — who is unblocking it, and by when?
- •[ ] No jargon or acronyms without expansion (e.g., “QBR” must be spelled out first use).
- •[ ] Only include changes since the last report — no repeating old updates.
- •[ ] If there is no gap, say so explicitly: “No gap — on track for Friday review.”
- •[ ] The report takes less than 60 seconds to read — if longer, cut details.
When a founder of a 60-person ops team told me they spent 45 minutes in a leadership review just trying to understand why a project was late, I realized most progress reports are noise — not signal.
Micro-case (what changes after 7–14 days)
A founder of a 40-person logistics team started using this checklist before weekly ops reviews. Within 10 days, they noticed two patterns: first, the sales team kept reporting ‘client outreach done’ while the gap showed zero contracts moved to negotiation; second, the support team’s ‘ticket volume down’ fact hid a 30% increase in escalations. By making the gap visible, the founder stopped accepting surface-level updates and began asking, ‘What decision is this gap blocking?’ — leading to a realignment of sales incentives and a support process fix, all without adding meetings.
Note on this case: This example is illustrative — based on typical patterns we observe with companies of 30–500 employees, not a single named client. Specific numbers are rounded approximations of common ranges, not guarantees.
FAQ
How is this different from a regular status update? A regular status update often lists tasks attended or meetings held. This checklist forces a comparison between intent and outcome — the gap is where decisions live.
What if we have no gaps to report? Say so. ‘No gap — on track’ is a valid and powerful signal. It builds trust that reports are honest, not performative.
Should we include risks or only facts? Include only verified facts and resulting gaps. Risks belong in a separate blocker or risk register — mixing them dilutes the Plan → Fact → Gap clarity.
Can this work for async teams? Yes. The checklist is designed to be read in under 60 seconds — ideal for async consumption via Slack, email, or a shared doc.
How often should we update this? Before every leadership review — whether weekly, biweekly, or monthly. The cadence should match the decision rhythm, not the other way around.
Use this checklist before your next leadership review to stop guessing and start seeing. If you want a system that surfaces the Plan → Fact → Gap automatically — every day, across the company — see how the 7-day diagnostic works.
Frequently Asked Questions
Read with AI
Open this article in your assistant — it will summarize it and help apply it to your company.
Show the prompt
Read the article https://aiadvisoryboard.me/blog/progress-report-checklist-before-leadership-review.md and summarize the key points. Then ask me about my company (industry, team size, what takes the most time) and explain which ideas from the article apply to us and where to start.
The pillar guide for "Progress Without Time Tracking" linking every article in this cluster.

Implements AI agents in companies and teaches founders and their teams to work with them — through courses and corporate programs.
This article was prepared with AI assistance, based on Yaroslav Maxymovych's methodology and materials. Spotted an inaccuracy — let us know via the form below.
A template is good. A system where the report writes itself is better
A 10-minute daily ritual for every employee: plan + fact + blockers. Implemented in 1 day. Teams that write down their plans hit their goals 42% more often.
New case studies on AI adoption — in your inbox
Once a week: practical breakdowns of what companies automate with AI and what actually comes out of it.
No spam. Unsubscribe anytime.
Related Articles

Role-Based Daily Report Checklist: Function by Function
A role-based daily report checklist gives founders the signal they need — not more noise. See what to include for each function to surface real work, not activity theater.
Read more
The CEO/COO Handoff Using AI — Visibility Without Micromanagement
Scaling requires the CEO to step back from operations without losing sight of the truth. Learn how to use AI to build a high-trust visibility layer that allows for a seamless CEO/COO handoff while…
Read more
Microsoft 300,000-Employee Copilot Rollout: 3-Week Collapse Lessons
Microsoft's attempt to roll out Copilot to 300,000 employees saw usage drop off in just three weeks. This article analyzes why a tools-first strategy fails and how SMB founders can build a…
Read more