A Rocks tracking template is the tool you use to set, assign, and monitor your company’s most important 90-day priorities, called Rocks in a Business Operating System. The point is to keep those priorities visible and owned so they get finished before the quarter ends, instead of quietly slipping. This guide shows you how to write good Rocks and why a live tracker in Ninety.io beats the spreadsheet almost every team starts with.
What is a Rock?
A Rock is a priority that must be completed within a 90-day window. The name comes from the old jar analogy: if you put the big rocks in first, the sand and water fill in around them, but if you pour the sand in first, the rocks never fit. Rocks are the big things your team commits to before the daily grind eats the quarter.
The math is simple. A typical team member carries one to three individual Rocks per quarter, and the company as a whole focuses on three to seven company-level Rocks. More than that and you are not prioritizing, you are just making a to-do list with a deadline. Good Rocks usually target one of four areas: execution, organizational structure, results and reporting, or company culture.
How to write a Rock that actually gets done
A vague Rock is a Rock you will argue about at the end of the quarter. The fix is to write every Rock as a SMART goal, so completion is a fact, not an opinion.
Specific
Clear and well-defined. “Implement HubSpot CRM” is a Rock. “Improve sales systems” is a wish.
Measurable
There is a hard line for done. “Onboard 5 sales reps and import 500 leads” tells you exactly when to color the Rock green.
Achievable
Realistic given the team’s actual resources and bandwidth this quarter, not the quarter you wish you had.
Relevant
It ladders up to your 1-Year and 3-Year plans. If a Rock does not move a bigger number, ask why it is a Rock at all.
Time-bound
It has a firm deadline, almost always the end of the quarter. A Rock without a date is a project that drifts.
Why spreadsheets fall short as a Rocks tracking template
Most teams start tracking Rocks in Excel or Google Sheets because it is fast to set up. It works for a week or two, then three predictable problems show up.
Out of sight, out of mind
A spreadsheet is a static file buried in a shared drive. Leaders open it right before a meeting, update the cells, and never look at it again during the week when the actual work happens.
Disconnected milestones
A 90-day Rock is really a stack of weekly steps. In a spreadsheet there is no clean way to link a Rock to the individual to-dos and weekly milestones that get it done, so progress is a guess until someone checks.
No built-in accountability
When a goal slips, a spreadsheet does nothing. It does not flag the owner, change color, or push the problem onto the agenda. The Rock just sits there marked “in progress” until the quarter runs out.
How Ninety.io works as your Rocks tracking template
Ninety.io fixes the spreadsheet problem by putting your 90-day goals inside the same environment where your team already works every day. Static targets become live workflows, and four features do most of that work.
Visual progress tracking
Every Rock is color-coded, green for on track and red for off track, and it shows up on each owner’s workspace. That single color turns the weekly meeting into peer-to-peer accountability. A wall of red Rocks is a conversation nobody can avoid.
Linked milestones
You break a 90-day Rock into weekly milestones inside the platform. Miss a milestone and the Rock’s status can flip to red on its own, so bottlenecks surface early in the quarter instead of in the final week when it is too late to recover.
IDS and the weekly meeting
When a Rock goes off track, one click pushes it onto the Issues List for your weekly L10 meeting. Instead of quietly ignoring a stalled priority, the leadership team is forced to identify, discuss, and solve the roadblock together, which is exactly what the meeting is for.
Accountability alignment
Rocks are nested under seats on your Accountability Chart, tying each priority to a specific role rather than a floating name. Ownership is unambiguous, and “whose Rock is this?” stops being a question.
What good and bad Rocks look like
The gap between a Rock that gets finished and one that limps to 60 percent is usually the wording. Here are two before-and-after pairs you can use to pressure-test your own list.
Take marketing. A bad Rock reads “Improve marketing copy.” There is no way to know when it is done or what “improved” even means. The SMART version is “Rewrite homepage copy, launch an A/B test in Optimizely, and achieve a 15% conversion increase by Sept 30.” Now the scope, the tool, and the target metric are all on the table, and completion is obvious.
Take operations. A bad Rock reads “Optimize client onboarding.” That is not a quarter, it is a multi-quarter initiative, and treating it as one Rock guarantees it stays half-done. The SMART version narrows it: “Document the new client onboarding process in Trainual and achieve a 95% satisfaction score on first-month client surveys.” One quarter, clear deliverable, measurable result.
Common mistakes
The most common failure is having too many Rocks. When a person carries six or seven priorities, none of them are priorities, and the whole list finishes the quarter yellow. Cap individuals at three and the company at seven, and defend that cap.
The second is writing Rocks you cannot measure. If you and the owner could reasonably disagree about whether a Rock is done, it is written wrong. Rework it until “done” is a number or a shipped deliverable, not a feeling.
The third is setting Rocks in the quarterly planning session and then never looking at them until the next one. A Rock reviewed once every 90 days is a Rock you are not managing. The whole reason to keep them in Ninety.io rather than a spreadsheet is that they show up in the weekly rhythm, so use that rhythm: check status every week and push the red ones to the Issues List.
Get your Rocks out of the spreadsheet
Scaling companies win on execution velocity, and that means keeping your highest priorities in front of the team, not buried in a drive. At Force Scaling, we help leadership teams move from static goal sheets to a live operating system where Rocks are visible, owned, and finished on time. Claim your 30-day free trial and set up your Rocks dashboard on our Ninety Partner Page.
Frequently Asked Questions
How many Rocks should a person have per quarter?
One to three individual Rocks per person is the standard. The company as a whole should focus on three to seven company-level Rocks. More than that and you are not prioritizing, you are just listing tasks.
What makes a Rock different from a regular task or to-do?
A Rock is a major 90-day priority, while a to-do is a short action step, usually completed in a week or less. Rocks are the big outcomes; to-dos are the weekly steps that get you there and are often linked underneath a Rock.
Can I track Rocks in a spreadsheet instead of software?
You can, but spreadsheets go stale fast. They live in a shared drive, are not linked to weekly milestones, and never flag a goal that slips. A live tool like Ninety.io keeps Rocks visible and pushes off-track ones into your weekly meeting automatically.
What happens when a Rock goes off track in Ninety.io?
The Rock is color-coded red on every owner’s workspace, and with one click it can be pushed onto the Issues List for your weekly L10 meeting. That forces the leadership team to identify and solve the roadblock rather than let the priority quietly slip.
