Operating Cadence Design Template
Three documents and three sheets that cost every recurring meeting in real salary hours, then cut or merge the ones sharing another meeting's job.
Free download · No account needed
Meeting Cost Estimate
Callahan Ridge Software, 52 employees, six recurring meetings
| Old cadence | $254,520 / year, priced at real attendee rates |
| Distinct-job test found | 2 meetings sharing one job, 5 attendees with no open work |
| New cadence | $181,980 / year — $72,540 saved, 28.5% |
What changed
| Meeting | Change | Savings |
|---|---|---|
| Product Review + Ops Sync | Merged into one Roadmap Sync | $10,740 |
| Daily Standup | 10 to 5 attendees, 15 to 10 min | $26,600 |
| Monday All-Hands | 30 to 20 min | $35,200 |
| Leadership Sync | Unchanged — passed the job test | $0 |
No meeting was cut to zero. Every saving traces to a specific overlap or attendee finding, never to a cost ranking alone.
Every meeting cost calculator on page one does the same arithmetic well: attendees times an hourly rate times duration times frequency, sometimes with a loaded-rate multiplier for benefits and overhead. One widely-used Excel meeting-cost template even offers a per-attendee tiered-rate method for accuracy. What every version produces is a ranked list, one meeting per row, sorted by annual cost. That ranking answers which meeting is expensive. It never answers the question that actually saves money: whether two rows on that same list are quietly doing the same job.
The audit frameworks built on top of the calculator inherit the same blind spot. A representative version scores every recurring meeting against three filters: does it have a decision owner, does it produce a written outcome, and would an async update work instead. Each filter judges one meeting against itself. None of them asks whether Tuesday's roadmap review and Thursday's operational sync, each individually passing every filter, are the same conversation happening twice with half the attendees swapped out.
Callahan Ridge Software's six recurring meetings each passed a per-meeting value check and still cost $254,520 a year. Comparing every meeting's stated purpose against every other meeting's, not against a generic filter, found two problems no isolated filter would catch. Product Review and Ops Sync did the identical job for overlapping attendees, and five of ten daily-standup attendees had no open work the standup covered. Merging one pair and trimming the other, plus a shorter all-hands, cut the annual figure to $181,980: a $72,540 saving with no meeting cut to zero.
What's in the pack
Meeting Register
Every recurring meeting with its stated purpose tested against every other meeting's, not scored in isolation, so a shared job shows up even when each meeting looks justified on its own.
Why the distinct-job test beats a cost ranking
A cost ranking tells you which meeting is expensive. It never tells you that two differently-named meetings on that same ranking are doing the identical job for overlapping attendees.
Attendee Map
Who's actually required per meeting, by seniority tier, checked against real open work rather than who accumulated a standing invite somewhere along the way.
Meeting Cost Estimate
Annual cost computed from real tiered attendee rates, before and after the redesign, so a change is a dollar figure a leader can act on rather than a scheduling opinion.
Cadence Design
The final redesigned stack with what changed for each meeting and why. If a meeting exists mainly to patch around a broken step, mapping the process itself fixes the cause instead of scheduling around it.
Agenda per Meeting
One template per surviving meeting, each stating its one distinct job as the first line, so an agenda item that doesn't serve that job has somewhere else to go instead.
Escalation Note
Where a new need goes instead of becoming a new standing meeting. A genuine live incident still goes to the faster escalation ladder built for exactly that, never to this note.
How to use it
- 1
Open in River, or download it
Install the pack and hand River your calendar and attendee lists, or download all three documents and three sheets blank and run the test yourself.
- 2
Send the calendar and attendee tiers
Every recurring meeting's name, duration, frequency, and attendee list or headcount by seniority tier, plus a rough fully-loaded rate per tier.
- 3
Let the distinct-job test run across all of them
Every meeting's stated purpose gets checked against every other meeting's at once, and every attendee gets checked against a stated reason to be there.
- 4
Publish the redesigned cadence and agendas
The surviving stack becomes the Cadence Design, each meeting gets its one-job agenda, and the Escalation Note routes whatever comes up next.
Frequently asked questions
Is this free, and what do I get?
Free, no signup needed for the download: three documents and three spreadsheets. The AI half is optional. Send River your calendar and attendee lists and it costs every meeting and runs the distinct-job test for you. More in the template library.
How is this different from a meeting cost calculator?
Because the calculators get the arithmetic right and stop there. They rank meetings by cost, one row at a time. Nobody's cost ranking catches that two differently-named meetings, each individually justified, are doing the identical job for overlapping attendees, which is where this pack's savings actually came from.
How does the pack decide two meetings should merge?
By checking every meeting's stated purpose against every other meeting's at once, not against a generic checklist. Two meetings whose purpose overlaps enough that one could absorb the other's job are a merge candidate, whatever their individual cost or attendance looks like in isolation.
What if a meeting's purpose is fine but it still costs too much?
It usually means an attendee problem, not a purpose problem. In the worked example, the daily standup's job was sound; five of ten attendees simply had no open work it applied to. The fix was shrinking the invite list, not cutting the meeting.
What happens to a new need that doesn't fit any meeting?
It goes through the Escalation Note, not straight onto the calendar. The note checks whether an existing meeting's job already covers it, whether it's really a one-time conversation, and only allows a new standing slot if the need will keep recurring on a predictable schedule.
How does this relate to a RACI or a decision rights policy?
For a decision that genuinely needs a name on who decides or a test of whether an escalation is worth keeping, those are the right tools. This pack answers a narrower question: given the decisions already being made, does the meeting making them need to exist in its current form.
What does Edit with AI actually do?
Creates a free account, installs this exact pack as a private space, and primes the agent to ask for your calendar and attendee rates. Nothing gets costed until you send something, and the blank pack is always there to download instead.
Price your meeting stack before you cut it
Take the documents and sheets blank, or install this pack in River and send it your calendar, attendee lists and rough tiered rates.
Edit with AI