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.