What a clean monthly board pack looks like (sample, redacted)

A clean monthly board pack for a public-company digital-asset treasury is roughly twenty pages. It is the document the audit committee, the CFO, and the chair all read from in the same meeting. The version below is anonymised from a live engagement, with identifying numbers replaced and counterparties renamed. The structure transfers; the numbers do not.

What the pack contains

Cover page (1 page). Reporting period. One-line headline. Three bullets summarising the month: program performance, regime status, exceptions. The chair reads only this page if pressed for time, and is not misled by it.

Position summary (3 pages).Reserve balances, overlay positions, mark-to-market by leg, attributable P&L, Greeks at portfolio level. One row per leg; one summary row per program. No commentary on the page; the numbers carry it. Commentary lives in a separate appendix the committee can reach if it wants.

Counterparty status (2 pages).Each counterparty with current exposure, current collateral posted, current threshold use, any open disputes, any documented review notes. Highlighted in amber if any threshold is more than 75% utilised, in red if a review note is open, in green otherwise. The colour is not decoration; it drives the meeting's attention.

Financing status (2 pages). Outstanding debt, convertible windows, any structured-product issuance in flight, the regime- aware execution status. The page answers: what is open, what is closing, what would we do if we needed to move on it this week.

Scenario monitor (3 pages). The set of triggers in policy, the current value of each, the green/amber/red status of each, and the pre-authorised response next to it. Page three is the historical chart of trigger levels for the last twelve months, so the committee can see whether anything is creeping toward a threshold.

Activity log (4 pages).Every trade executed in the period, with multi-dealer quote dispersion captured at execution. Every roll. Every exception requested or approved. The page answers an auditor's first question.

Sign-off (1 page). CFO attestation, audit- committee chair acknowledgement, dated. No language not specifically required; no boilerplate.

Appendix (~4 pages).Methodology notes, reference tables, a glossary that defines the program's terminology so a new committee member can read the pack without an onboarding call. Pulled out of the body so the body stays scannable.

What it does not contain

Market commentary. Macro views. Dealer research. Forward-looking volatility forecasts. These are interesting and have a place, but they belong in a separate document the committee can choose to read. In the pack, they crowd out the operational picture and invite second-guessing of the program on terms the program is not built around.

Long narrative paragraphs. Anything the committee has to read twice to follow has been written badly. Numbers go in tables, status goes in colour, exceptions go in a list. Where prose is unavoidable, it is short.

Why this shape

The board pack is not a report card. It is the operating record of a program the board has authorised, presented in a way that lets the committee discharge its oversight duty in a defined window, every month. The structure is built around what the committee needs to confirm, not around what the desk wants to show. A pack that gets that ordering right takes less time to read and produces better decisions, in sequence and on schedule.