Chief of Staff Operating Cadence Template
Four documents and three sheets, including a Decision Flow Map that assigns each recurring topic to exactly one of four standing forums.
Free download · No account needed
Cadence Health Check
One request crossed three forums. Nobody decided it.
Halberd Instruments, Q2 2026: a two-person Customer Success headcount request, tracked across all three standing forums held between offsites.
| Forum | Appearances | Decision |
|---|---|---|
| Weekly Leadership Sync | 4 | None |
| Monthly Business Review | 2 | None |
| Quarterly Progress Review | 1 | None |
| 7 instances, 3 forums, 0 decisions, still open when the quarter closed. | ||
After the Decision Flow Map chartered headcount requests to the Monthly Business Review alone, the next same-shaped request reached one forum, once, and was decided in that meeting: 7 instances down to 1, an 85.7% cut.
Chief of staff guides agree on the shape of an operating rhythm: a weekly sync for tactical calls, a monthly review for resourcing, a quarterly session for strategy, each meeting type assigned a broad decision class. The closest of them even warns that decisions stall when no single meeting owns them. None goes further than a decision class per meeting type to a per-topic map. None checks a real quarter's agendas against that map afterward, to catch a topic that quietly gained a standing slot at more than one forum.
Halberd Instruments, a fictional instrumentation manufacturer, ran its first such check retrospectively against its second quarter of 2026: 17 standing meetings, 24 distinct topics reaching the eight-person leadership team. Nineteen topics stayed inside a single forum. Five crossed into a second before anyone decided them. One, a two-person Customer Success headcount request, crossed into all three: four Weekly Sync appearances, two Monthly Business Review appearances, one Quarterly Progress Review appearance. Seven instances total, still undecided at quarter close, one flagged repeat away from a fourth-forum appearance at the leadership team's own August offsite.
Chartering headcount requests to the Monthly Business Review alone, and nowhere else, changed that immediately. A same-shaped request the following quarter reached that one forum once and was decided in that same meeting. One instance instead of seven is an 85.7 percent cut, and the topic's owner knew exactly where to raise it instead of guessing. Bain's own research on decision ownership makes the same case one level up: "there should only be one decider for each decision". This pack applies that same rule to which meeting decides, not just to who does.
What is in the pack
Cadence Design
Names why the stack has the tiers it has, not just what they are: a diagnosis of what a two-tier or four-tier stack would each leave uncovered, run once against the leadership team's real meeting history rather than assumed.
Meeting Charters
One page per forum in a fixed five-section shape: purpose, decision authority, attendees, cadence, and explicitly out of scope, naming which other forum a topic outside this one's authority should go to instead.
Escalation Path
The one named, ruled reason a topic moves forums: two consecutive stalled cycles at its own chartered forum, never urgency and never whoever raises it loudest at a different meeting's agenda.
Operating Rhythm Diagram
Every forum and every escalation arrow drawn out in one shape, with two real topics traced through it: one that followed the arrows to a decision, and one that never touched an arrow at all.
Meeting Register
Every standing-forum occurrence, logged the same day: date, attendees against the charter's named list, and a topic count, the same forums an executive calendar audit prices by the hour instead of by decision.
Decision Flow Map
Every recurring decision category assigned to exactly one forum, with a concrete trigger and a named escalation target, so a topic's owner knows where it belongs before raising it anywhere.
Cadence Health Check
Audits real meeting topics against the map every quarter and flags any topic that crossed forums without escalating, the step a leadership team's own decision register has no way to run on its own. Worth running on a quarterly cadence given executives already spend nearly 23 hours a week in meetings.
How it works
- 1
Send your current meeting stack
Whatever standing meetings the leadership team already runs between offsites: who attends each one, how often, and roughly how long they run. No stack yet is fine; the design starts from a blank charter.
- 2
Get a charter for every forum
One page per forum: purpose, decision authority, attendees, cadence, and what's explicitly out of scope, so a topic outside one forum's authority has a named place to go instead of nowhere.
- 3
Get the Decision Flow Map
Every recurring decision category assigned to exactly one forum, with a two-cycle escalation trigger named for the one legitimate reason a topic should ever move from its chartered home.
- 4
Run the Cadence Health Check each quarter
Real meeting topics checked against the map, flagging any topic that crossed forums without escalating, before it reaches a third forum or a fourth one at the next offsite.
Frequently asked questions
How is this different from a chief of staff cadence guide?
Most guides assign a broad decision class per meeting type: weekly for tactical calls, monthly for resourcing, quarterly for strategy. This pack maps specific recurring categories one-to-one to a single forum and audits real agendas against that map afterward, which is how it catches a topic quietly holding a slot at more than one forum at once.
How is this different from a leadership decision log?
A decision log records what a working team's own weekly meeting decided, plus a dissent field and a reopen rate. This pack decides which of the four standing forums should even be discussing a topic in the first place, before any decision reaches a log at all.
How is this different from board minutes?
Board minutes are the formal record of the board of directors, a separate body with its own legal recordkeeping requirements. This pack runs the leadership team's own internal cadence between board cycles and offsites, where nothing gets minuted for a regulator or a court.
What exactly counts as a stalled cycle?
A topic discussed at its own chartered forum on two consecutive occurrences with no decision recorded, regardless of how long either discussion ran. Urgency, seniority, or a stakeholder asking for more visibility do not trigger escalation; only the two-cycle count does, so the rule never depends on who is impatient that week.
What if a topic doesn't fit any existing forum?
That is a real gap, not a reason to force the topic into the nearest existing box. The Cadence Health Check surfaces it directly: a category with no chartered owner shows up as a topic bouncing between forums with no escalation ever firing, which is the signal to add a forum, not to guess one.
What format are the downloaded files, and is it free?
Four Word documents and three CSV sheets in one zip, free and with no account required. The documents open in Word, Pages or Google Docs, the sheets in Excel, Numbers or Google Sheets. Edit with AI installs the same pack as a private Space and builds the map against your own meeting stack.
How is this different from an executive communication plan?
This pack decides which of the four standing forums a topic belongs to and audits whether it stayed there. An executive communication pack picks up after a forum has already decided something big enough to reach the board, all employees and customers, and keeps those three versions from drifting apart before or after they ship.
Find out which topics are already crossing forums
Send the standing meetings your leadership team already runs between offsites, plus a few weeks or months of past agendas if you have them. The Cadence Health Check runs against that history first, before anything new gets drafted.
Map my cadence