π GEM Resource Hub Β· π Library Β· π About RocketLevel Β· π Playbooks Β· πΊοΈ What's Your Market Worth? Β· π Book a Call
<aside> π
Make your own copy. This page is the template. Make your own copy in Google Sheets and fill it in with your real initiatives. The dropdowns and column counts are built in. Or print this page or save it as a PDF and work by hand.
</aside>
A resource from RocketLevel for restoration company owners and the people who help run the business, backed by decades of experience in the trade. About a 6-minute read.
Plenty of owners run their week off a list, a notebook, a phone, and their memory. The problem with a list is that it only has two states: done and not done. Everything that is not done sits in the same undifferentiated pile, the urgent next to the someday, the thing you committed to next to the thing you already decided to drop. Work disappears into that pile. A sprint board fixes this by giving every initiative a column, an owner, and an honest read on effort and value, so nothing hides and the cuts you make are visible on the board instead of lost in your head.
A sprint board is one place that holds every initiative the business is choosing to spend attention on, sorted by when it ships, not by when you happened to think of it. Each item lives in exactly one column, carries a named owner, and gets an honest effort and value read. That structure does three things a list cannot. Timing becomes a decision instead of an accident, because an item is either this week, soon, later, or triggered. Ownership is explicit, so there is no shadow work that everyone assumes someone else is doing. And the cuts stay visible: parking something or killing it is a move you make on the board, in the open, instead of something that quietly falls off the bottom of a list.
The board is small on purpose. It does not need project management software to start. A whiteboard, a shared doc, or a printed copy of this page all work, as long as someone walks it every week.
Every initiative sits in exactly one of six columns. The column says when, not what. The NOW, NEXT and LATER horizons borrow from the Now-Next-Later roadmap created by ProdPad co-founder Janna Bastow, and the short, fixed-length sprint comes from Scrum, run here on a one-week cycle; the trigger, parked and killed columns are added here for how a restoration shop actually works.
NOW is this week. The two to four things actually in motion right now. Keep this column short.
NEXT is the two-to-four-week horizon. Committed work queued behind NOW, ready to pull forward when something ships.
LATER is the 30-to-90-day horizon. Real initiatives you intend to do, scoped but not yet started, waiting on time or resources.
TRIGGER-BASED is work that ships when an event or threshold hits, not on a date. A storm-response calling push, a hiring move that fires when a branch crosses a revenue line, a vertical you open when the current one saturates. You pre-build it and wait for the trigger.
PARKED is off the active board but not dead. You name the condition that would bring it back, so parking is a decision with a revisit rule rather than a shrug.
KILLED is off the board and not coming back. Leave it named on the board so nobody keeps working on it.
Columns that overlap turn the weekly review into an argument about labels. Four rules keep every item in exactly one place.