Weekly Business Review Template
Four documents and five sheets that count how many weeks running each issue has been raised without anybody deciding anything.
Free download · No account needed
How the Recurrence Counter Works
Twenty-six consecutive weekly reviews at Aldercroft Systems, a fictional mid-market software company. 2 March to 24 August 2026, sixty minutes, nine attendees.
Every issue carries one extra number: consecutive weeks raised without a decision recorded against it. An issue reaching four leaves the room.
| Weeks raised | Issues | Decided in the room | Minutes consumed |
|---|---|---|---|
| 1 | 11 | 11 | 42 |
| 2 | 8 | 8 | 70 |
| 3 | 2 | 2 | 25 |
| 4 | 5 | 0 | 83 |
| 5 | 2 | 0 | 44 |
| 6 | 2 | 0 | 48 |
| 8 | 1 | 0 | 40 |
| 11 | 1 | 0 | 68 |
Nobody tuned the threshold to produce that break. Every issue the room could decide, it decided inside three weeks. Of the eleven that reached a fourth consecutive week, not one was ever decided in the review. The worst was sandbox provisioning latency at eleven weeks and 68 minutes, because the fix needed an $84,000 spend nobody in the room could approve. The executive committee approved it in nine minutes.
Every weekly business review template hands you the same two things: an agenda with timings on it and a metric table with a red, amber and green column. Neither addresses the thing that actually goes wrong in these meetings, which is that the same topic comes back week after week and nobody can say how many weeks it has been. The room knows. What it does not have is the number, and the number is what turns a complaint into an escalation with a case attached.
So this pack adds one column. Every issue carries a count of consecutive weeks raised without a decision recorded against it, and an issue reaching four leaves the room. At Aldercroft Systems, over twenty-six consecutive reviews, that threshold separated the issues cleanly. Twenty-one were decided in the room and every one closed inside three weeks. Eleven reached a fourth week and not one of them was ever decided there at all.
Written for whoever chairs the thing and has started to suspect it is theatre. Four attempts is not a patience problem, it is a signal that the decision needs a budget, an authority or a person the meeting does not contain. The metrics on the pack want defining first in a metric register, the version a leader reads is an executive one-pager, and if the numbers themselves are suspect that is a data quality monitoring problem rather than a review problem.
What you get
Recurring Issue Log
One row per issue with consecutive weeks raised, total weeks raised, minutes consumed, person-hours at your attendee count, and the sentence naming what the room was missing when it escalated. Both week counts are there because a consecutive counter resets on a missed week, which is the one way this can be gamed.
Meeting Time Log
One row per review splitting the hour into issue minutes, minutes on a fourth attempt or later, minutes reading the pack aloud, and admin. It is the only place the review's own drift shows up. A decide segment at zero for four running weeks means this has become a status meeting.
Metric Pack
The week's numbers against last week, with a threshold and one named owner per metric and the commentary as submitted. Four of fourteen metrics breached in the worked week, so four commentary requests went out. The metric with no reply says so on the row rather than sitting blank.
Decision Register
What was decided, by whom, where, and how many minutes it took. Splitting in-room decisions from post-escalation ones is what produces the comparison the threshold rests on: 42 minutes to decide seven issues that had consumed 206 minutes in the review first.
Action Tracker
Owner, due date, close date, days late, and what changed as a result. That last column is the only evidence the review produces anything, and counting the closed actions with it left empty is a monthly check worth running.
Review Agenda
Sixty minutes with a measured budget rather than an aspirational one, including five minutes of silent reading, exceptions only, and a two-minute escalation slot that is read aloud and never discussed.
How the Recurrence Counter Works
Why four, what the escalation sentence has to name, and the six categories Aldercroft's eleven fell into. Spend above the room's limit, a person who does not attend, a board reservation, a third party, a queue, and two owners with no tiebreak.
Commentary Prompt
The four questions each owner answers, with worked good and bad examples. Restating the number, direction without a level, causes that cannot be wrong, and a cause with no owner are all shown as what to reject.
How it works
- 1
Assemble the pack from the exports
Thursday, so there is a Friday. River fills the metric pack, computes each status against its threshold mechanically, and names anything that failed to refresh instead of shipping a hole.
- 2
Request commentary on the exceptions only
One request per breached metric to that metric's owner. Four questions, answerable from a phone, and the row says so when nothing comes back by the deadline.
- 3
Run the review, then log the minutes
Immediately after, while they are still accurate. Every issue gets a decision or an incremented counter, and nothing else counts as an outcome.
- 4
Escalate anything that hits four
The case comes straight from the log. You write one sentence naming what the room was missing, and the issue leaves rather than getting another slot.
Frequently asked questions
Is this free, and what format are the downloaded files?
Free, and no account is needed for the download. Documents arrive as .docx and sheets as .csv, so they open in Word, Pages, Google Docs, Excel, Numbers or Sheets without a conversion step. Edit with AI is the other button: it installs the same pack as a private space and backfills the issue log from whatever meeting history you have.
Why four weeks rather than three or five?
Because three attempts is enough evidence, and because it happened to split Aldercroft's issues exactly without being tuned. Three is defensible for a fast-moving weekly operation. Set it, write it down, and leave it for a quarter: a threshold that moves the first time it is inconvenient is not a threshold.
Does escalating an issue actually resolve anything?
Not by itself, and the pack says so. Seven of the eleven had a recorded decision by 24 August. Four went into a billing roadmap, a board paper, a retainer request and a dependency, which are legitimate places to be and none of them a decision. That is why the escalation list keeps its own age counter.
Is there precedent for a review that reaches outside itself?
The federal performance framework requires it. A quarterly progress review has to coordinate with relevant personnel within and outside the agency who contribute to the goal, and to categorise goals by risk of not being achieved. Reaching outside the reviewing body is in the statute rather than left to whoever notices.
Why does every metric need a threshold to enter the pack?
Without one it can never breach, so it never generates commentary and never gets examined. It just gets read aloud forever. The SEC expects a company presenting a key metric to disclose the reasons why the metric provides useful information; a threshold and an owner are the internal version of that demand.
Will this fix a review that shows the wrong metrics?
No. The pack forces an owner, a threshold and a stated decision per metric, which took Aldercroft's pack from twenty-two metrics to fourteen. It cannot tell you the remaining four revenue metrics are three too many. Deciding which reports deserve to exist is a report inventory audit, and what gets built at all a dashboard spec.
Find out what your recurring issues have cost
Send the exports the review runs on and whatever meeting history exists. River backfills the issue log, counts the consecutive weeks, and prices the ones nobody in the room could decide.
Edit with AI