# On track or off track? How to report Rocks in your Level 10 Meeting

How to report Rocks as on track or off track in your Level 10 Meeting, use milestones to keep the call honest, and catch slipping Rocks by week six.

URL: https://www.success.co/blog/eos-rocks-on-track-off-track  
Published: 2026-11-20

Does this scenario sound familiar? It's week nine of the quarter. The Rock review in your Level 10 Meeting™ takes five minutes, as it has every week, and every Rock is marked "On track." Nothing to worry about, right? Then, at the Quarterly, three of those Rocks come back "Not Done." The goal for the quarter is an 80% Rock completion rate (not 100%), but it's easy enough to feel blindsided when a Rock that seemed on track the entire quarter actually wasn't. After all, that's the entire purpose of the Rock review: to gauge the work being done and to remove blockers to that work. So what happened?

Done and Not Done are the two irrefutable statuses of a Rock. "On track" and "off track," the two statuses you report every week, are often where the problem lies. It's easy to say "on track" if work has started, or if the deadline seems far away. And because we are human, saying "off track" can feel like failure, even when it's an honest assessment.

The fix? A shared definition of each word, milestones that make the call easy to check, and a clear habit for what happens when someone says "off track."

This guide covers how the Rock review works in the L10™, what on track and off track really mean, how milestones keep the call honest and what to do with an off-track Rock. It is part of the [Success.co EOS Implementation Wiki](https://www.success.co/blog/the-success-co-eos-implementation-wiki).

## What are EOS Rocks?

Every quarter, a leadership team chooses a few things that matter more than everything else. These are its Rocks™: usually three to seven for the company, and one to three for each leader. Each one grows out of the 1-Year Plan in the V/TO™, and each one has a single owner and a clear finish line. Ninety days later, a Rock is either done or not done, and there is a real satisfaction in that kind of clarity.

Daily work never needs a reminder. It knocks on the door by itself: a customer calls, a deadline arrives, a number on the Scorecard turns red. Rocks are quieter. They are the work that builds the company you described in your Vision, and quiet work is easy to set down when the week fills up. That is why each Rock gets one word in every Level 10 Meeting. Said out loud each week, that word keeps the Rock in view and gives the team a chance to help long before the quarter runs out.

## How does the Rock review work in a Level 10 Meeting?

The Level 10 Meeting is the weekly leadership meeting in EOS®. It follows the same agenda every week, and the Rock review is one short section of it, right after the Scorecard. If you need the full agenda first, start with [how to run a Level 10 Meeting that actually works](https://www.success.co/blog/how-to-run-a-level-10-meeting-l-10-that-actually-works).

During the Rock review, the person running the meeting reads each Rock, and its owner answers with one of two words: on track or off track. That's the whole report. No updates, no stories, no "well, mostly." The section should take about five minutes for the whole leadership team.

The brevity is the point. Any Rock that needs a conversation gets dropped to the Issues List and solved later in the meeting, during IDS. Keeping the two apart protects the agenda and keeps the review honest.

## What does "on track" actually mean?

> I am confident this Rock will be done by the end of the quarter, as written.

That is what "on track" means. Simple, right? And yet it's easy to equate "on track" with "I worked on it this week," "nothing has gone wrong yet" or "I have plenty of time to do it."

The problem with those definitions is that they are more subjective than measurable. Work done doesn't always mean the right work, and it says nothing about how much is left. The same goes for the idea that there is plenty of time. We all know what happens when work is left to the last minute: blockers appear, problems surface at the eleventh hour, and the Rock either goes undone or gets finished in a way that no longer matches its written definition of done.

Here is what that looks like in practice. An operations leader owns the Rock "Quality checklist implemented and in use on 100% of client deliveries." A weak report would be "On track, mostly. A couple of teams haven't started using it." A strong one is simply "On track," because the plan is visibly working: the checklist was drafted in week two, piloted with one team in week four and rolled out to every team in week six.

## What does "off track" mean?

> I am not confident this Rock will be done by the end of the quarter, as written.

Here's the really important thing to remember about "off track": it does not mean failure.

It means something stands between the Rock and the finish line, and the team should know about it now rather than in twelve weeks.

The Rock review exists for accountability. It happens in the leadership L10 not to shame anyone, but because the team is there to help solve problems, and it can only do that if the problems are visible. An off-track Rock is really an early warning. A Rock called off track in week five still has seven weeks of runway. One called off track for the first time in week eleven has almost none.

It's also important to reward early "off track" calls. How the leadership team reacts the first time someone says "off track" sets the tone for the rest of the year. If the response is to help, people will assess their work honestly. If the response is a lecture, the next owner will say "on track" until the Quarterly.

## Why milestones matter

Imagine you're driving across the country. You know your starting point and your destination. But the route in between? Just as you'd never start a long trip without a map, you shouldn't start a Rock without milestones. Milestones inside the Rock turn a subjective feeling of confidence into dated checkpoints against which the work can be honestly assessed.

With the right milestones in place, the question in the L10 stops being "do you feel good about this?" and becomes "did the milestone that was due this week happen?"

Here is how that changes the call.

### 1. Break the Rock into dated checkpoints at the Quarterly

When the Rock is set, the owner lists the steps that must be finished for it to be done, and puts a date on each one. But a few dates aren't enough on their own. If the first milestone is due in week ten, you have no real signal until week ten. Front-load the milestones and spread them across the quarter, so there is at least one checkpoint every few weeks. If you are still writing the Rocks themselves, our guide on [how to set EOS Rocks that your team actually completes](https://www.success.co/blog/how-to-set-eos-rocks-that-your-team-actually-completes-not-just-writes-down) covers the criteria.

### 2. Tie the status to the next milestone

Each week, the owner looks at the milestones before the meeting. If the milestones due so far are done and the next one looks achievable, the Rock is on track. If a milestone has slipped past its date, the Rock is very likely off track, unless the owner can explain in one sentence why the finish line is still safe. Milestones inform the call. The owner still answers the bigger question: will this be done by the end of the quarter?

Take a sales Rock: "12 qualified demos booked per month by end of quarter, up from 7." A weak report sounds like "On track. We had a good week and the team is really pushing." A strong one is "Off track," because the week-four milestone, "new outbound sequence live," hasn't happened yet. The owner drops it to the Issues List, and IDS finds that the sequence is waiting on approved copy. The call is backed by something the whole team can see.

## What should happen when a Rock goes off track?

The rule is simple: an off-track Rock goes to the Issues List.

There is no judging and no explanation. The owner says "off track," and the facilitator or the owner adds it to the list for IDS later in the same meeting. This separation matters because solving an issue is different from reporting it. Trying to solve an off-track Rock during the review means Rocks get discussed in the order they appear, not by priority. Moving it to IDS means it sits alongside related issues, which can often be solved together.

During IDS, the team does what it does with any issue:

- **Identify** the real reason the Rock is slipping. Is it a missing decision, a resource problem, a dependency on another team, or a Rock that was too big from the start?
- **Discuss** it briefly, with everyone saying what they think once.
- **Solve** it with a clear action, usually a To-Do with an owner and a date. Sometimes the solution is help from another leader. Sometimes it is accepting that the Rock will not be done and deciding what that means.

Remember that 80% Rock completion rate? That's the target, which means accepting that a Rock will not be done is allowed. EOS is strict about not renegotiating Rocks mid-quarter, but it is not about pretending. Knowing in week seven beats finding out at the Quarterly.

A finance example shows how early that call can come. The Rock is "Monthly close completed within 5 business days, three months running," and last month took seven days. The weak report is "On track. Last month was seven days, but we will catch up." The strong one is "Off track," because the Rock needs three months in a row and one has already been missed. The team takes it to IDS and decides whether it is still possible and what to change.

For more on keeping that list healthy, see [how to clean up a long EOS Issues List](https://www.success.co/blog/how-to-clean-up-a-long-eos-issues-list).

## How Success.co supports the weekly Rock review

The weekly status only works if everyone sees the same list at the same time. In Success.co, Rocks are built into the L10 agenda, and every Rock carries a live On Track / Off Track status, so the review happens inside the meeting rather than in a separate document. [Rock milestones](https://www.success.co/blog/rock-milestones) sit inside each Rock, so owners can see at a glance which checkpoints are on track, overdue or completed before they make the call.

For Second Life Mac, that shared view changed the Integrator's week. Brian Spears used to go team by team to find out which Rocks were off track. Now [he sees every team's Rocks and To-Dos in under five seconds](https://www.success.co/customer-stories/second-life-mac), a job that used to fall to his assistant, so when one team falls behind he can ask the right questions straight away.

When a Rock is off track, dropping it to the Issues List keeps it in the same meeting, ready for IDS. And if a Rock is too vague to report on honestly, [Ask AI in Success.co](https://www.success.co/blog/ask-ai-eos-software) can help sharpen it into something specific and measurable. You can read more about [Rock tracking in Success.co](https://www.success.co/platform/rocks).

## Make the weekly word count

The Rock review is the shortest section of the Level 10 Meeting, and one of the most important. Agree on what on track and off track mean, back every call with milestones, and send every off-track Rock straight to IDS. Do that every week, and the Quarterly stops holding surprises.

**See it in your own L10**

Start free, or open the instant live demo to see Rocks, milestones and the L10 agenda working together.

[Start free](https://www.success.co/signup)

[Try the live demo](https://www.success.co/demo)

## FAQs about reporting Rocks

### How long should the Rock review take in a Level 10 Meeting?

About five minutes for the whole leadership team. Each owner gives a one-word status for each Rock, and anything that needs discussion goes to the Issues List for IDS later in the meeting.

### Can a Rock go from off track back to on track?

Yes. If IDS solves the issue and the owner is confident again that the Rock will be done by the end of the quarter, the next week's status can be on track. The status is a weekly judgment, not a permanent label.

### What if a Rock is clearly not going to be finished this quarter?

Say so as early as possible and take it to IDS. The team can decide what to do: add help, accept that it will be marked not done at the Quarterly, or carry the remaining work into next quarter's Rocks. What matters is that nobody finds out at the Quarterly.

### Do Rocks need milestones?

Not strictly, but milestones make the weekly call far more reliable. They turn "I feel good about it" into "the checkpoint due this week is done," which is much harder to get wrong.
