The Weekly Executive Scorecard Every Leadership Team Should Track
The five domains — revenue, cash, customer health, delivery, and people — that belong on a weekly executive KPI dashboard, and the design rules that keep it actionable.
Executive Summary
Most leadership teams track too many numbers and act on almost none of them. A weekly executive scorecard exists to solve a narrower problem: which five to eight metrics, reviewed every single week, tell a leadership team whether the business is healthy right now, not thirty days from now when the monthly close finally surfaces the same story. This article defines that scorecard across five domains — revenue, cash, customer health, delivery, and people — and lays out the design rules that keep a weekly dashboard useful instead of decorative.
This piece does not cover how to run the meeting where the scorecard gets discussed, how cadence should be sequenced across weekly, monthly, and quarterly reviews, or how leadership teams should make decisions once a red metric appears. Those are addressed in How High-Performing CEOs Structure Their Weekly Leadership Meetings, The Leadership Operating Rhythm: The Leadership Operating System, and Executive Decision Frameworks: How Great Leadership Teams Make Better Decisions. This article's scope is narrower and specific: which numbers belong on the scorecard, and why.
Introduction
A monthly financial close tells a leadership team what happened four weeks ago. By the time a churn spike or a cash shortfall shows up in a board deck, the decisions that could have prevented it were available weeks earlier — buried in data nobody was required to look at on a fixed schedule. The weekly executive scorecard closes that lag. It is not a replacement for financial reporting; it is a smaller, faster instrument built for one purpose: surfacing deviation early enough that it is still cheap to correct.
Executive dashboard research consistently converges on the same design principle: a CEO-level view should answer one question in under sixty seconds — is the business on track — while a deeper operational view exists one layer down for anyone who needs to diagnose why. CEO dashboard research recommends daily tracking of the top three numbers (revenue, pipeline, cash) with a full weekly review of the complete set, and monthly review of trend lines — a cadence structure this article adopts as the default.
What Belongs on a Weekly Scorecard — and What Doesn't
The single most common failure in executive dashboard design is not omission; it is inclusion. Teams add a metric because it is measurable, not because it is actionable at a weekly grain. The design test that filters this correctly: for every metric on the scorecard, someone in the room must be able to answer "if this number moves 20 percent in the wrong direction this week, who do I call, and what do I ask them to do?" If no one can answer that, the metric belongs in a monthly deep-dive, not the weekly view.
This test eliminates most vanity metrics automatically. Total signups, gross pageviews, and headcount alone rarely pass it — they describe scale, not health, and no single leader owns a corrective action tied directly to them moving. The metrics that survive the test cluster into five domains, each of which should have exactly one clear owner in the room.
The Five Domains of the Weekly Scorecard
1. Revenue
Revenue on a weekly scorecard is not last month's recognized revenue restated more often — it is the leading indicators that predict whether the month closes on target. The most reliable weekly revenue set separates four numbers that get dangerously conflated in less rigorous dashboards: bookings, billings, recognized revenue, and cash collected. Conflating these produces a dashboard that quietly lies, because a strong bookings week can mask a collections problem that will not surface for another thirty days.
* Revenue run-rate vs. target — month-to-date actual against a daily-projected pace, not a static monthly number checked once.
* Pipeline coverage ratio — qualified pipeline relative to the remaining target, with 3x–4x coverage treated as the healthy floor in most B2B models.
* Win rate and sales cycle drift — a moving week-over-week comparison, since a single week's win rate is noisy but a multi-week drift is a genuine signal.
2. Cash
Cash is the domain where weekly tracking matters most and monthly tracking is most dangerous, because a cash problem can move from manageable to existential faster than a monthly close cycle can catch it. CFO dashboard research groups the core cash metrics into liquidity and capital efficiency, with liquidity checked at the highest frequency of any category on the scorecard.
* Cash position and runway — current balance and months of runway at the trailing burn rate, the single number most CEOs check first.
* Net burn (trailing average) — smoothed over several weeks so a single large invoice doesn't distort the read.
* Days sales outstanding — how long cash takes to actually arrive after a sale closes, since a revenue number without a collections number is incomplete.
3. Customer Health
Customer health metrics answer a different question than revenue metrics: not how much is coming in, but how much of what already exists is at risk of leaving. Net revenue retention and logo churn are the two numbers most B2B leadership teams underweight relative to their long-term importance — a pattern explored in depth in our related piece on why SaaS Metrics That Matter: Why Churn Rate Is the New Fundraising Metric for growth-stage companies. On a weekly scorecard, the goal is not full churn analysis but an early-warning read: accounts trending toward risk before the cancellation email arrives.
* Net revenue retention trend — a rolling view, since NRR moves slowly enough that week-over-week noise matters less than the direction of the trend.
* At-risk account count — accounts flagged by usage decline, support escalation, or renewal proximity, reviewed as a raw count with named accounts, not an aggregate percentage.
* Support escalation volume — a leading indicator for churn risk that moves faster than churn itself.
4. Delivery
Delivery metrics measure whether the organization is executing on what it committed to — product roadmap, client deliverables, or internal operating priorities, depending on the business. This domain is the one most likely to be entirely absent from finance-oriented dashboards, which is precisely why it needs a deliberate slot on the weekly scorecard rather than being left to a separate project-management tool nobody at the leadership level actually reviews.
* On-time delivery rate — the percentage of committed milestones hitting their date, tracked as a rolling percentage rather than a single week's snapshot.
* Blocker count and age — the number of active blockers and how long the oldest one has been open, a direct proxy for whether the How High-Performing CEOs Structure Their Weekly Leadership Meetings is actually resolving what it surfaces.
* Quality or defect rate — whatever the closest proxy is for output quality in the specific business, since delivery speed without a quality check simply relocates the risk downstream.
5. People
People metrics are the domain most executive teams review least often and need to review more, because organizational health degrades quietly and compounds. Gallup's 2026 State of the Global Workplace found that global employee engagement fell to just 20 percent in 2025, its lowest level since 2020, with disengagement estimated to cost the world economy roughly $10 trillion in lost productivity — and notably, manager-level engagement has fallen faster than individual-contributor engagement, meaning the leadership layer itself is often the earliest signal of organizational strain. See Gallup's State of the Global Workplace 2026.
* Voluntary attrition (trailing) — tracked weekly as a trailing rate, since a single resignation is noise but a rising trailing rate is signal.
* Open critical roles and time-to-fill — roles that block delivery or revenue if left unfilled, tracked by age, not just count.
* Manager engagement pulse — a short, standing pulse check specifically on the management layer, given how disproportionately manager disengagement predicts wider organizational decline.
The Framework: Building the Scorecard Grid
A weekly executive scorecard should fit on a single screen. Research on executive dashboard design consistently converges on six to ten total metrics as the practical ceiling — beyond that, the dashboard stops being scannable and becomes another report nobody actually reads before the meeting. The recommended structure below allocates one to two metrics per domain, with color-coded status (on track, at risk, off track) and a one-line owner assignment for anything flagged at risk.
* Row 1 — Revenue: run-rate vs. target, pipeline coverage.
* Row 2 — Cash: runway, net burn.
* Row 3 — Customer Health: NRR trend, at-risk account count.
* Row 4 — Delivery: on-time rate, oldest open blocker.
* Row 5 — People: trailing attrition, open critical roles.
Each row should carry a named owner — the single leader accountable for that domain, not the whole leadership team collectively. This mirrors the decision-rights principle covered in depth in Executive Decision Frameworks: How Great Leadership Teams Make Better Decisions: a metric without a named owner is not actually being managed, it is simply being observed.
Where the Scorecard Fits in the Operating System
The weekly scorecard is an input into the operating rhythm, not a replacement for it. It supplies the data that makes the How High-Performing CEOs Structure Their Weekly Leadership Meetings's blocker-surfacing segment substantive rather than anecdotal, and it feeds the broader cadence structure described in The Leadership Operating Rhythm: The Leadership Operating System. As organizations scale, the volume of data available to track grows faster than any single dashboard can absorb — a dynamic examined in Why Growth Breaks Companies: Operational Complexity — which is exactly why domain-based discipline matters more, not less, as headcount and product lines expand.
Increasingly, the aggregation work behind a weekly scorecard — pulling numbers from a CRM, a finance system, and a project tracker into a single view — is itself being automated by agentic tools rather than assembled manually by a finance or operations team every Friday. That shift is covered separately in our Executive AI Stack; the scorecard's design principles in this article hold regardless of whether a human or an agent compiles the underlying numbers. Executive AI Stack
Key Takeaways
* A weekly scorecard should answer one question in under sixty seconds: is the business on track, and does anything need attention this week.
* Six to ten metrics is the practical ceiling; every additional metric past that reduces, rather than increases, how much the room actually uses the dashboard.
* The five domains that consistently earn a weekly slot are revenue, cash, customer health, delivery, and people — each with exactly one named owner.
* Every metric needs an owner and a lever: if a number moves sharply and no one can name who to call, it does not belong on the weekly view.
* People metrics, especially manager-level engagement, are the domain most commonly under-tracked relative to how early they signal organizational strain.
Conclusion
A weekly executive scorecard is not a bigger dashboard; it is a smaller, more disciplined one, built specifically to catch deviation while it is still cheap to correct. The leadership teams that get the most value from theirs are not the ones tracking the most metrics — they are the ones who have been ruthless about which five to eight numbers actually predict trouble, and who has the authority to act the moment one of them turns red. Paired with a well-run weekly leadership meeting and a clear decision-making framework, the scorecard completes the operating system: it tells the room what to look at, the meeting tells the room what to do about it.