Every Integrator eventually has to answer the same question for their own company, and most end up clicking through every team’s space to do it.
EOS reporting answers one question: is EOS working? A useful report tracks six signals for every team — whether L10s happen weekly, meeting ratings, Rock health, Scorecard measurables on target, To-Dos done on time, and how fast Issues get solved. Read together, those signals show which teams run EOS well and which need support.
Shaz knows those numbers because he can see them in one place. “I love the reports — the ability to see a timeline and see who did what,” he told us. “The activity log, the analysis of what’s open, who’s got the most to do, what’s completed.” That same idea is behind Strety’s new Reports, and it’s where this post ends up. First, the signals themselves.
What EOS health metrics should you track? Six metrics cover most of what an Integrator needs to know about EOS health: whether L10s are held every week, how teams rate those meetings, the share of Rocks on track, the share of Scorecard measurables hitting their goal, the share of To-Dos done by their due date, and how quickly Issues get solved. Each one maps to a core EOS discipline, so a weak number points you to a specific habit to coach.
L10s held and meeting rating At the end of every Level 10 Meeting , each attendee rates it from 1 to 10. The rating tells you how the meeting felt to the people in the room. Pair it with the share of weeks the team met at all, and you have the earliest warning sign in EOS, because a team that stops holding its L10 stops reviewing everything else along with it.
We see this pattern often. The skipped L10s come first, and the Rocks and To-Dos slip a few weeks later, which is why this is the first number we’d check for any team.
Rock health Rock health is the share of Rocks that are on track or complete. EOS Implementers regularly describe 80% to 100% Rock completion as achievable for teams that set Rocks well and check in weekly.
Two supporting numbers make the headline more useful. Milestone completion tells you whether the work is moving before the quarter’s last month, and stale check-ins — Rocks with no update in 14 days — tell you which ones nobody is looking at.
Scorecard on target The Scorecard holds each team’s weekly numbers, and the useful roll-up is the share of measurables hitting their goal. A measurable that sits below target for several weeks in a row usually points to an Issue the team hasn’t put on the list yet, which is exactly what the Scorecard review at the top of the L10 is there to catch.
To-Do completion on time To-Dos in EOS are seven-day commitments made in the L10 . The number worth tracking is the share done on or before their due date, since most task lists count a To-Do finished three weeks late as simply “done.” On-time completion is what shows whether a team keeps its word week to week, and EOS aims for 90% done every week .
Issue-solving pace Issues health is about pace. Track how many Issues each team solves per L10, the average number of days from raised to solved, and the oldest Issue still open. A long list with a low solve rate usually means the team is discussing without deciding, which is a good cue to revisit how the team runs IDS .
Why EOS reporting should cover every team EOS reporting that stops at the leadership team misses where most execution happens. Department teams hold their own L10s, own their own Rocks, and carry most of the company’s To-Dos, so company-wide EOS health depends on how the system lands in the accountability layer.
Mark Lukehart, COO of Parachute Technology , watched this happen as Parachute went from six executives on their system to more than seventy people:
“The ease of use of Strety has allowed us to push it across not only the executive level, but also into the department and individual levels.”
Once EOS reaches that far, the Integrator’s question changes. It becomes “which of these twelve teams needs me this month?” and, one level down, “who is carrying too much of the weight?” Answering both takes a view of every team side by side, plus a way to see everything assigned to one person across every space. We cover the weekly habits that make that possible in our post on the five tools behind EOS accountability .
How often should you review EOS health? EOS health works best on three rhythms. Each team reviews its own numbers weekly in the L10, the Integrator scans every team every week or two, and the leadership team reviews company-wide health at the Quarterly, often with their EOS Implementer.
The weekly team review already happens if the L10 is running well, since the Scorecard, Rock review and To-Do list are built into the agenda. The Integrator’s scan is the layer most companies are missing. Fifteen minutes on a Monday morning, before the day’s L10s, is enough to spot a team that skipped its meeting or a Rock that has gone two weeks without a check-in.
The quarterly review is where the Traction Report earns its place. It gives your Implementer a clean snapshot of the quarter in a format they already know, and our Traction Report guide walks through how to pull one.
Common EOS reporting mistakes Most teams run into at least one of these once EOS spreads beyond the leadership team.
Building the report the night before the Quarterly. When the numbers live in each team’s space, somebody ends up exporting and pasting them into a spreadsheet. That spreadsheet is out of date the moment it’s finished, and it only gets built when a meeting forces it.
Reading one number alone. A team can show 90% of Rocks on track while half its To-Dos land late. The Rock number looks healthy because nobody has updated a status, and the To-Do number is the one telling you what’s happening. Read the signals as a set.
Finding out at the Quarterly. A team that stopped holding L10s in week three can lose most of a quarter before anyone notices. Weekly visibility turns that into a nudge in week four.
Using the report to grade people. The numbers work best as a coaching tool. An Integrator who opens a conversation with “your To-Do rate dropped, what’s getting in the way?” gets a very different answer than one who opens with a ranking. Dana Johnson, Integrator at Point North Networks , puts the payoff simply:
“If I do have some correction to make for somebody, they should know it’s coming. By having the transparent metric, we can reduce surprises even more.”
How Strety Reports works Strety Reports is a reporting view built into Strety that shows EOS health for the whole company and for each team, using the live data teams already enter during their L10s. Integrators start from a company-wide Overview, then click into any team, Rock, or person to see the details behind a number.
The project started with a short brief from Brian Dosal, our CEO and Integrator, listing the handful of high-level metrics he’d want to see as an Integrator. The metrics that followed came from what customers and EOS Implementers told us they check to know whether EOS is taking hold.
Here’s how it tends to get used. On a Monday morning, an Integrator opens the Overview and sees the quarter’s overall health in five numbers: meeting rating, Rocks on track, Scorecard measurables on target, Issues solved and To-Dos done on time, with the EOS targets marked on the bars. Trend charts underneath show how meeting ratings, Rock status and the flow of Issues moved week by week.
Further down, Cadence by team lists every team with a week-by-week strip of L10s held, alongside its rating, Scorecard, Rocks and To-Dos, so a team that has missed five of the last thirteen weeks stands out right away. Filtering the Overview to that one team shows its health on its own, and clicking into a number opens the Rocks, To-Dos or meetings behind it, so the Integrator walks into that team’s L10 knowing what to ask about.
From there, a tab for each tool goes deeper. The Rocks tab filters by team and quarter and includes a Rocks-by-Team view that matches the Traction Report format. The To-Dos tab surfaces the oldest open items, and the Issues tab shows solve pace by L10. Projects works as a status report, grouping work into overdue, coming up, open ended and finished, and a “Powers a Rock” filter shows which projects move which Rocks. Assignments pulls everything on one person’s plate into a single view.
Julia Folk, the Integrator at Brilliant Group , describes the job Reports is built for:
“I just did a report for my Visionary on where we’re at this quarter — these are the Rocks that are on track, these are off track, this is why, this is the plan. I pulled it all from Strety, and it took no time at all.”
EOS Implementers can see the same view . Once a client adds their Implementer as a coach on the Strety account, the Implementer can check how the company is running EOS between sessions instead of waiting for the next Quarterly to find out.
Nothing needs to be built or refreshed, because Reports reads from the same data your teams update every week, and it’s included on every Strety plan . The Strety Reports complete guide covers every tab and metric definition.
Reporting for one team or a hundred A single leadership team gets a clear read on its own EOS health from week one, which is useful for companies just starting EOS, since the early habits are the ones that stick. An organization with dozens of teams sees every one of them side by side in Cadence by team, and can filter the Overview to any single team for a closer look.
That range matters because EOS rarely stays with the leadership team for long. The companies we work with usually start with six or seven people in one L10 and add department teams within a year or two. A reporting setup that works for both ends means the Integrator keeps the same habits as the company grows, and the numbers stay comparable from the first quarter onward.
Frequently asked questions What is EOS reporting? EOS reporting is how a company tracks whether EOS is working across its teams. It covers L10 consistency and ratings, Rock health, Scorecard results, To-Do completion and Issue-solving pace.
What metrics show whether EOS is working? The six core signals are L10s held, meeting rating, Rock health, Scorecard measurables on target, To-Dos completed on time and Issues solved. Read together, they show which teams are running EOS well.
What is a good Rock completion rate in EOS? EOS Implementers generally treat 80% or higher as the target, and many teams reach 80% to 100% once they set Rocks well and check in weekly.
How do you track whether every team is holding its L10? Track the share of weeks each team completed an L10 during the quarter. Strety Reports shows this for every team side by side in the Cadence by team section of the Overview.
What’s the difference between Strety Reports and the Traction Report? Strety Reports is a live, company-wide view of EOS health that Integrators use week to week. The Traction Report is a quarterly snapshot designed for sharing with your EOS Implementer.
How often should an Integrator review EOS health? Every week or two for a quick scan across teams, with a full company review at each Quarterly.
Can an EOS Implementer see a client’s Strety Reports? Yes. Once a client adds their Implementer as a coach on the Strety account, the Implementer can view Reports between sessions.
Do I need to build dashboards to use Strety Reports? No setup is needed. Reports is included on every Strety plan and updates from the live data teams already enter, so there’s nothing to build or refresh.
Where to start this week Pick one team outside the leadership team and look at two numbers from the last six weeks: how many weeks they held their L10, and what share of their To-Dos landed on time. Those two numbers will tell you more about how EOS is landing in that team than any status update will, and they give you a specific, friendly question to bring to your next conversation with its leader.
If you’re already on Strety, open Reports and start from the Overview. If you’re not with us yet, you can try Strety free for 30 days and see your own EOS health from the first week, or start with the complete guide to Strety .
