The week the pack is allowed to move
A cadence charter is the custom page most pack owners ask for after the first painful sitting. It is not a software workflow. It is freeze language, refresh windows, and a short list of doors that remain after lock — written so a corridor request can be answered with a sentence instead of a feeling.
Cross-functional reporting needs this because each function keeps a private clock. Finance closes accruals. Operations wants yesterday’s outage. People wants a hire that signed at 17:10. Without a charter, the executive KPI dashboard becomes two packs: the one you emailed and the one that arrived in the room.
What the charter actually contains
A clock, a timezone, and the pack owner’s name. Restatements after that clock require a dated exception note on the canvas.
Which measures refresh nightly, which wait for a payroll or close, and which therefore cannot live on the first page.
The two or three restatements the sitting is allowed to hear. Everything else waits for the next cycle.
What was published, kept for comparison. A local tracking copy may sit on the owner’s machine; it is not a second unofficial pack.
Book the charter, or the canvas
If your freeze already holds and the first page still cannot be read on a train, you need board-pack KPI dashboards. If the page is readable and the corridor still wins, start with reporting cadence design. Desk details are on contact.