Weekly scorecard template, with a worked example

What a weekly scorecard is (and isn't)

A weekly scorecard is a short table: one row per measurable, one column per week, a named owner and a goal for every row. It exists for one reason — so the team can spot what is off track early, while there is still time to do something about it. It is not a dashboard with forty charts, it is not your monthly financial pack, and it is not a place to show off every number your CRM can produce.

The discipline is what makes it work: the same numbers, reviewed the same way, every week. After a quarter you can read trends at a glance. After a year the scorecard is the most honest history of the business you have. In Enginely the scorecard opens the weekly meeting, keeps 13 periods of history with a trend sparkline per row, and turns any off-track number into an issue with one click.

Example scorecard for a 25-person company

Here is a realistic leadership-team scorecard for a small B2B company (made-up data). Red cells with ▼ missed their goal that week. Notice how few rows there are, that every row has exactly one owner, and that each goal is a number, not a direction.

Reading it takes less than a minute. Leads have missed goal two weeks running — that is a trend, not noise, so it goes on the issues list. Week 38 was a rough week for support (tickets, response time, on-time shipping all slipped together), which hints at one shared cause rather than three separate problems. Cash dipping under goal in week 39 is worth a question even though it is a single miss, because the trend has been down for four weeks.

How to choose your measurables

Most teams get the list wrong the first time, and that is fine — expect to revise it after four to six weeks. These rules get you close on the first try:

1. Start from the outcomes you care about, then go upstream. Revenue is the outcome; proposals sent and sales calls held are the activities that predict it. A good scorecard mixes a few results with more leading activity numbers, because activity numbers move this week, while results often lag by a month or more.
2. One owner per number. Not a department, not "Sales team" — one person who will explain a miss. Shared ownership means nobody owns it.
3. Weekly, and countable. If it cannot be counted every week without a two-hour spreadsheet exercise, it will not survive. Pick numbers that come straight from a system you already use (CRM, help desk, accounting, shipping).
4. 5 to 15 rows. Fewer than five and you are missing whole areas of the business; more than fifteen and nobody reads them. If a department wants more detail, it can keep its own scorecard for its own weekly meeting.
5. Cover every seat at the table. Each leadership-team member should own at least one number. If someone owns none, either their function is invisible or the list is lopsided.

Measurable ideas by function

• Sales: qualified meetings held, proposals sent, pipeline added ($), win rate (rolling 8 weeks).
• Marketing: new qualified leads, cost per lead, demo requests, website-to-lead conversion.
• Operations / delivery: on-time delivery %, backlog in days, defects or rework, utilization.
• Customer success / support: open tickets at week end, first-response time, churned accounts, NPS.
• Finance: cash in bank, receivables over 60 days, weekly collections, burn vs plan.
• People: open roles, days-to-hire, regretted departures (quarter to date).

How to set goals that mean something

Every row needs a goal the owner has agreed to, written as a threshold: "≥ 25", "≤ 4 hrs", "≥ 95%". Avoid ranges and avoid "up and to the right". A threshold makes the weekly review binary — on track or off track — which is what keeps the scorecard segment to five minutes.

Set goals from the plan, not from hope. If your quarterly revenue target needs $50k a week, the goal is $50k, even if you have only hit it twice this year; the gap is exactly what the team should be talking about. Revisit goals at the start of each quarter, not mid-week after a miss. For numbers where lower is better (tickets, response times, receivables), flip the comparison and say so explicitly in the goal so nobody has to think about it.

How to review the scorecard in a weekly meeting

The scorecard segment of a weekly leadership meeting should take about five minutes. The rule that makes that possible: report, don't discuss.

1. The facilitator reads down the rows, or each owner calls out their number with one word: "on" or "off".
2. For any off-track row, the owner says "drop it down" — it goes to the issues list. Nobody explains, debates, or problem-solves yet.
3. The team moves on. All the talking happens later, in the issue-solving block, where it can be prioritized against everything else (see the IDS issue-solving guide).

The most common failure is letting a miss trigger a ten-minute story. By the time the team reaches row six the meeting is behind, and the issues that actually matter get rushed. Parking misses on the issues list protects the whole agenda (see the weekly meeting agenda template for the full 90-minute format).

Common scorecard mistakes

• Too many rows. Thirty numbers means nobody reads any of them. Cut to what the leadership team would genuinely act on.
• Only lagging numbers. Revenue and profit tell you what already happened. Add the activity numbers that predict them.
• Goals that move. Changing a goal the week it is missed hides the problem. Change goals quarterly, deliberately.
• Monthly numbers on a weekly scorecard. If a number only updates monthly, it will show blank or stale three weeks out of four. Track it elsewhere, or find a weekly proxy.
• Nobody owns the data entry. If the facilitator is chasing numbers during the meeting, the owner model is broken.
• Discussing during review. Covered above, and still the number-one reason scorecard segments run long.

Spreadsheet vs. software

A spreadsheet is a perfectly good place to start, which is why the free toolkit below includes one (a scorecard tab plus priorities and to-dos tabs). Teams usually outgrow it when they want history and trends without copying columns every week, a clean way to push an off-track number into the issues list, and one place where the whole meeting lives.

That is what Enginely does: goals and owners per row, 13 periods of history with a sparkline, green/red status at a glance, one click to turn a miss into an issue, and the rest of the meeting (quarterly priorities, to-dos, issue solving, ratings) on the same screen. It is free for teams of up to 10 people and $49/month flat for up to 25 — no per-seat fees.

Frequently asked questions

How many measurables should a weekly scorecard have?

Between 5 and 15 for a leadership team. Fewer than five usually leaves whole areas of the business invisible; more than fifteen and the team stops reading them. Departments can keep their own scorecards for their own meetings.

What is the difference between a scorecard and a dashboard?

A dashboard shows many numbers for exploration. A weekly scorecard is a short, fixed list of numbers, each with one owner and one goal, reviewed the same way every week so the team can spot what is off track and act on it.

Should scorecard numbers be leading or lagging indicators?

Both, weighted toward leading. Results like revenue confirm what happened; activity numbers like proposals sent or sales calls held predict what will happen and can be acted on this week.

How long should the scorecard review take in a meeting?

About five minutes. Each owner says whether their number is on or off track; anything off track is dropped to the issues list without discussion and solved later in the meeting.

How often should we change scorecard goals?

Quarterly, deliberately, when you plan the quarter. Changing a goal the week it is missed hides the problem the scorecard is meant to surface.

Is there a free scorecard template?

Yes. The free Enginely toolkit includes a scorecard tracker for Excel or Google Sheets (with priorities and to-dos tabs), a printable agenda, and a facilitator slide deck. Enter your email on this page and it is sent to you.

Is this an official EOS® scorecard?

No. Enginely is an independent product and is not affiliated with or endorsed by EOS Worldwide, LLC. This guide describes the weekly-scorecard practice for teams running that style of meeting.