Weekly Scorecard: How to Turn Your Numbers Into Decisions

Picture a sailboat crossing open water before GPS. Before leaving port, the navigator draws a line on the chart from the harbor to landfall. Every day at noon she takes a sight of the sun, marks where the boat actually is, and compares the mark with the line. Two degrees off course on Tuesday costs a small turn of the wheel. Found on Saturday, the same two degrees costs a day of sailing.

Most startups check their numbers the way a careless crew checks the chart: at month's end, or when something feels wrong. By then a slow week of demos has become a thin quarter, and the fix has to be bigger.

A weekly scorecard is the noon sight. It works when two things hold. Every number has one person who answers for it, and the review ends in decisions rather than a recap.

What goes on a weekly scorecard

A noon sight only helps because it lands next to a line drawn in advance. A scorecard row works the same way, and each row carries five parts:

• Metric: one number, defined tightly enough that two people would calculate it the same way, as a measurement plan does for each marketing channel.
• Owner: one person's name, never a team. Pick whoever can move the number day to day, which often isn't the most senior person.
• Target: where the number should be this week, set before the week starts.
• Bands: the thresholds, written as numbers, that turn a reading yellow or red.
• Trend: this week beside last week, so the room sees direction as well as level.

Keep the list short. A startup's scorecard usually needs five to ten rows. Weight them toward leading numbers like demos booked and pipeline created, which move weeks before revenue does. A number that only climbs, like total sign-ups since launch, earns no row. Vanity metrics covers how to spot one.

Leadership's own short list lives on the executive dashboard. The scorecard gives those numbers, and the team numbers beneath them, an owner and a meeting.

The weekly scorecard template

Those five parts fit on one page, with the meeting's agenda and its follow-ups below them.

WEEK OF: [date]
REVIEW: [day and time], 30 minutes, run by [name]

ROWS (five to ten, leading numbers first)
Metric: [name, with its exact definition]
  Owner: [one person]
  Source: [the one system the number comes from]
  Decision it changes: [what you'd do differently if it moved]
  Target this week: [number]
  Yellow below: [number]    Red below: [number]
  This week: [ ]    Last week: [ ]    Status: [green / yellow / red]
  Note from owner (yellow or red only): [cause] / [next step by Wednesday]

[Repeat for each row]

AGENDA
0:00  Name every yellow and red row. Skip the green ones.
0:05  Each off-track owner: cause and next step, 2 to 3 minutes each
0:20  Leading numbers: any early warning before it reaches revenue
0:25  Rows that recovered since last week
0:27  Confirm follow-ups

FOLLOW-UPS
Task: [what]    Owner: [one person]    Due: [date]

RED TWO WEEKS RUNNING
Metric: [name]    Founder session on: [date]    Revised plan: [ ]

Fill it in once, before the first meeting:

• Decision first: write the decision each row changes. A row with no decision behind it comes off.
• Bands per metric: a workable starting point is yellow below 95% of target and red below 80%. Widen the bands for a number that swings week to week, like daily sign-ups.
• One source: each number comes from one system, pulled automatically if you can, so the meeting never argues about whose spreadsheet is right. RevOps settles which system owns each fact.

Running the weekly review

A filled-in scorecard still changes nothing until a meeting acts on it. Hold the review on the same day each week, and cap it at 30 minutes. Three rules keep the template's agenda on time:

1. Spend the time on yellow and red rows, and let green ones pass in silence.
2. Ask each owner for a cause and a next step, then move on.
3. End with every follow-up written as a task with one owner and a date.

The owner answers for explaining the problem and bringing a plan by Wednesday, whoever ends up doing the fix. Deep problem-solving moves to a separate session with the people it needs, so the review stays short enough that nobody skips it.

When a number stays red: if a row is still red at the second review in a row, take it out of the weekly meeting and into a session with the founder, with a revised plan and a date. A third straight week of the same red reading teaches the team that red means nothing.

Common scorecard mistakes

Most scorecards that stop working fail in one of four ways:

• Status readout: the meeting walks through every green row and runs out of time before the red ones.
• Team owners: a row owned by the sales team belongs to nobody, so it drifts until it's a crisis.
• Stale names: someone changes roles and their name stays on the row, which looks covered when it isn't. Update the owner the week the role changes.
• Silent bands: a yellow band nobody has hit in a quarter is too wide, and a red band that fires every week trains people to ignore it. Recheck the bands each quarter.

Starting your first scorecard

A navigator doesn't wait for a perfect chart before taking the first sight. Pick five numbers this week, put one name beside each, and hold the first review next Monday. Your bands will be wrong at first, and the first few reviews will show you where.

If nobody at your company has the time to own that meeting, your numbers need a leader before they need a tool. At Everee I built the team's Salesforce reports and funnel dashboard, and in my fractional CMO engagements I track the metrics we agree on while we work together. The free diagnostic on that page ends with a written roadmap either way.

Take the sight every week, and the corrections stay small.