One of the most expensive sentences a leadership team can say during a Scorecard review is, “Next week will be better.”
Across more than 400 session days, I’ve heard versions of it when a Measurable has been off track, but the team doesn’t want to enter the Issue. They acknowledge the number, move on with the meeting, and hope the result changes.
Seven days later, the same number is still off track.
That isn’t a data problem. It’s a discipline problem.
The EOS Scorecard™ gives your leadership team a weekly pulse on the business. It sits in the Data Component™ of the EOS Model® and tracks 5–15 activity-based numbers called Measurables. When those numbers are focused, owned, and reviewed consistently, the team can see trouble early enough to do something about it.
Putting numbers into a spreadsheet isn’t the goal. The goal is better visibility, clearer accountability, and faster issue-solving.
Key Takeaways
- Create weekly visibility: Use the EOS Scorecard to determine whether the company is on or off track before monthly or quarterly results arrive.
- Focus the data: Track 5-15 activity-based Measurables, each with one owner and a clear weekly goal.
- Solve what is off track: Move off-track numbers to the Short-Term Issues List and use IDS® during the Level 10 Meeting™.
- Start with leading indicators: Measure the weekly activities that drive revenue, profit, and Core Process health.
- Build the discipline: Use Ninety to keep Scorecards visible, current, and connected to Issues and weekly meetings.
What Is the EOS Scorecard?
The EOS Scorecard is a weekly report designed to measure business performance and promote team accountability. It contains 5-15 activity-based numbers, called Measurables.
This powerful tool is also powerfully simple. It has four key columns: the number, the person who owns or drives it, the weekly goal, and 13 weeks of results.
We love to see the patterns or trends because they bring visibility and an opportunity to fix what’s not working. If the number is off track, we “drop it down” to the Short-Term Issues List and use IDS® (Identify, Discuss, Solve™) when we get to that section of our Level 10 Meeting™. Teams that get this discipline love that we're focused on advancing or fixing what’s off rather than just endlessly talking about it.
What Should an EOS Scorecard Tell You Each Week?
A strong EOS Scorecard answers one practical question: Are we doing the work required to achieve our goals?
The tool is simple. Each Measurable includes:
- The number being measured
- The person who owns or drives it
- The weekly goal
- Thirteen weeks of actual results
That 13-week view matters because one result can be noise. A pattern tells a story.
The Scorecard should help the leadership team see whether weekly activity is moving the company toward the revenue, profit, and other goals established in the Vision/Traction Organizer®.
This is why a Scorecard isn’t the same as a financial report. Revenue and profit still matter, but they’re mostly lagging indicators. By the time they change, much of the underlying work has already happened.
The Scorecard should reach further upstream. It should measure the activity that produces those results.
For example:
- Qualified leads created
- Sales meetings held
- Proposals delivered
- Units completed
- Customer Issues resolved
- Open positions filled
- Errors or rework
- Accounts receivable over 60 days
- Compliance with a Core Process
These numbers give the team an opportunity to act before a missed target becomes a missed quarter.
How Do You Build an Effective EOS Scorecard?
A useful Scorecard is built through practice. It rarely comes out of the first meeting perfect, and that’s okay. Start with the best numbers available, use them, learn from them, and improve the tool over time.
1. Start with the Accountability Chart™
Before deciding what to measure, get clear about who owns what.
Your Accountability Chart™ defines the seats and roles required to achieve the company’s vision. The Scorecard should show whether the people in those seats are completing the activity connected to their responsibilities.
A practical starting point is to ask each leadership team member:
Which one to three weekly numbers tell us whether your function is doing the right work?
A five-person leadership team will usually produce 5–15 Measurables. That is enough to create visibility without turning the Scorecard into a data warehouse.
Less is more until it isn’t. Most teams begin with too much.
2. Choose activity-based leading indicators
Revenue tells you what happened. Activity helps you influence what happens next.
Start with the steps inside your sales funnel, customer journey, or operating workflow. Identify the activities that have to occur consistently for the desired outcome to follow.
A sales team might track:
- New qualified opportunities
- Discovery meetings completed
- Proposals sent
- Opportunities advanced
- Closed business
An operations team might track:
- Units produced
- On-time deliveries
- Labor utilization
- Defects
- Customer complaints
The right Measurables should help the team predict, not simply report.
3. Connect Measurables to your Core Processes
Every business depends on a handful of Core Processes, including hiring, marketing, sales, operations, customer service, and finance.
The Scorecard should show whether those processes are healthy.
A hiring process might track qualified applicants, interviews completed, offers accepted, and time to fill a seat. A customer service process might track response time, open Issues, resolution time, and customer satisfaction.
When a Core Process starts to break down, the numbers should reveal it before customers, team members, or margins take the full hit.
4. Give every Measurable one owner and one goal
Shared accountability usually becomes no accountability.
Each Measurable needs one clear owner. That person may not enter the number personally, but they are accountable for producing and explaining the result.
Every Measurable also needs a weekly goal. Without a goal, the team has information but no agreement about what good looks like.
The full Scorecard should have a champion as well, often the Integrator™. The champion makes sure the numbers are updated and ready before the weekly meeting.
5. Build for your business before chasing benchmarks
Leadership teams often ask for industry-specific Scorecard templates. Benchmarks can be useful later, but they aren’t the best place to begin.
The answers are usually already in the room.
Your team knows the work. Your Core Processes already exist, even when they aren’t documented well. Your sales funnel already contains steps. Start by measuring the activities your business needs to perform consistently.
Use the Scorecard for several weeks. Look for patterns. Then refine it based on what the team learns.
6. Use IDS® to improve the Scorecard itself
Sometimes the Issue is the result. Sometimes the Issue is the Measurable.
A number may be too hard to collect, too far downstream, owned by the wrong person, or disconnected from a decision the team can make. Those are Issues worth solving.
Use IDS® to ask:
- Is this the right number?
- Does it help us predict?
- Can the owner influence it?
- Is the weekly goal appropriate?
- Does this Measurable tell us something useful?
- Are we willing to act when it is off track?
A Scorecard should evolve as the company, team, and processes mature. It shouldn’t change every week, but it shouldn’t become a static report nobody uses either.
How Should the Scorecard Work in a Level 10 Meeting™?
The Scorecard portion of a Level 10 Meeting is a five-minute review. That timing creates an important discipline. The team isn’t there to explain every number or solve every problem during the Scorecard section. Each owner reports whether their Measurable is on track or off track. When a number is off track, drop it down to the Short-Term Issues List. Then keep moving.
The team will address it during IDS®, the 60-minute portion of the meeting dedicated to solving the most important Issues. This protects the agenda while making sure the underlying problem receives the attention it deserves.
An off-track number isn’t a failure. It is a signal.
The failure happens when the team sees the signal, ignores it, and expects next week to be different. Strong teams don’t punish people for bringing forward accurate data. They use the data to create healthy accountability and make better decisions.
When Should You Add Department Scorecards?
Start with the company or Senior Leadership Team Scorecard. Build the weekly habit. Strengthen the Measurables. Make sure leaders update their numbers, report honestly, and use off-track results to identify Issues. Then cascade the discipline into departments.
Each department can build a focused Scorecard with 5–15 Measurables, depending on the team's size and complexity. Those numbers should connect the department’s weekly activity to the company’s larger goals.
The purpose isn’t to create more reporting. It is to help every team understand what it owns, what success looks like, and whether it is doing the work required to win the week.
How Does Ninety Support Scorecard Discipline?
The software can make the discipline easier. It can’t replace the leadership work.
With the Ninety platform, team members can update their Measurables from anywhere, review current performance, and see trends across the 13-week view.
When a Measurable is off track, the team can turn it into an Issue and have it waiting in the IDS section of the next Level 10 Meeting. That connection matters because the number doesn’t disappear into a spreadsheet or get lost between meetings.
Ninety also keeps the Scorecard connected to the broader system:
- Accountability Chart
- V/TO®
- Issues
- Rocks
- Level 10 Meetings
- Department teams
That shared visibility supports the EOS disciplines of Shared by All and Followed by All. It helps teams Focus, Align, and Thrive by keeping the plan, the numbers, and the weekly execution in one place.
What Should Your Team Do Next?
Begin with a simple working session.
Ask each leadership team member to bring one to three weekly activities they believe indicate the success of their role. Narrow the combined list to the 5-15 numbers that provide the best pulse on the business.
For every Measurable:
- Assign one owner.
- Set a weekly goal.
- Enter the prior weeks of data when available.
- Review it during every Level 10 Meeting.
- Drop off-track numbers to the Issues List.
- Use IDS® to solve the root cause.
Your first Scorecard won’t be perfect. That isn’t the standard. The standard is whether the team uses it consistently, learns from what it reveals, and makes better decisions as a result.
You can begin building your Scorecard with the EOS Toolbox™. Entering the numbers is the easy part. The real work is reviewing them every week, telling the truth about what is off track, and solving the Issues that stand between the team and its goals. If you want a single source of truth to document your Scorecard, and make it visible to all, build it in Ninety.
