Agreeing the definitions before anyone builds a page
The single biggest cause of a board pack losing credibility is two pages disagreeing about revenue. Before we build anything, we run a short definition session with your CFO or controller and write down what each headline measure means: which accounts roll into revenue, whether margin is stated before or after allocated overhead, which entities consolidate, and what the fiscal calendar does at period boundaries. Those decisions become governed DAX measures (opens in new tab) in one semantic model rather than formulas hidden inside individual visuals, so the same definition serves the pack, the management report and any drill-down a director asks for in the room. Deeper variance and forecasting work for the finance team itself lives on our Power BI for finance page.
Locking the as-of date so the pack stops moving
A live dashboard and a board pack want opposite things. A dashboard should always be current; a pack must be frozen, because directors annotate a reading copy days before the meeting and will not forgive a figure that changed underneath them. We agree an as-of date with finance, snapshot the pack at that date, and stamp it on every page footer. When the pack is exported we take current values rather than default values so the filters and period selections in the reviewed version are exactly what lands in the PDF. A late journal posted after cut-off shows up in next cycle's pack with a note, not as a silent revision of a page someone already marked up.
Handling prior-period restatements honestly
Restatements are normal — a reclassification, a corrected accrual, an entity moving between segments. The failure mode is overwriting history so that this year's pack shows a prior-year comparative the board has never seen. We model the reporting period separately from the accounting period, which lets a page show as-reported and restated figures side by side, keeps last year's approved comparative intact, and carries a short restatement note on the affected page. Audit committees notice this; it is usually the first thing a new chair tests.
Board-ready export: PDF and PowerPoint that survive printing
Power BI can export a report to PDF (opens in new tab) or PowerPoint straight from the service, which is enough for many packs. When the board expects a printed document — consistent page size, page numbers, headers that repeat across a long table, a table of contents — we build the pack as a paginated report in Power BI Report Builder (opens in new tab) over the same model. Two limits are worth knowing up front: a standard Power BI report cannot export to PDF beyond 50 report pages, while paginated reports have no such cap, and uncertified custom visuals do not render in a PDF export — so we design board pages using core visuals rather than discovering the gap the night before distribution. Sensitivity labels and their encryption settings carry through to the exported file, which matters when the pack leaves your tenant.
Read-only access for directors who are not employees
Most boards include people who have no account in your tenant. The clean pattern is to invite them as guest users with Microsoft Entra B2B (opens in new tab), publish the pack as an app, and give each director viewer access to one audience — never a role in the build workspace. Row-level security (opens in new tab) then decides what each guest resolves to, so an investor director sees the consolidated view while an operating partner sees their division. For operating partners managing day-to-day portfolio company performance and value creation milestones, our private equity KPI dashboard builds that operating-layer model. Two practicalities we cover in the handover: guests need either their own Pro or PPU licence or a workspace on Fabric capacity, and directors invited through a personal email address get browser-only access, not the mobile apps. Our step-by-step Power BI row-level security setup guide shows how the roles are defined and tested.
What goes on each page, and where it comes from
A working reference for the spine of the pack — the recurring question each page exists to answer, the systems we usually pull it from, and who owns the narrative that sits beside it.
| Board pack page |
The question it answers |
Typical source systems |
Commentary owner |
| P&L and cash vs plan |
Are we on plan, and where did the variance come from? |
General ledger / ERP, budget and forecast files, bank feeds |
CFO or controller |
| Operating KPIs |
Is the operating engine improving or just the accounting? |
Operational systems, CRM, service desk, production data |
COO or function lead |
| Headcount |
Are we hiring to plan and what is it costing per FTE? |
HRIS and payroll exports, approved headcount plan |
Head of people |
| Pipeline and bookings |
Is there enough coverage for the next two quarters? |
CRM opportunity and bookings data, sales plan |
Chief revenue officer |
| Risks and covenants |
How much headroom is left, and what changed since last meeting? |
GL, credit agreement terms, risk register |
CFO and company secretary |
Live pages or a printed pack — you usually want both
Directors read differently. Some want the exported document and nothing else; others open the live pages during the meeting to answer a follow-up. The two formats have genuinely different strengths, so we build one model and two front doors rather than compromising on a single one.
| Consideration |
Live Power BI report pages |
Paginated report PDF pack |
| Best for |
Answering follow-ups in the meeting, drilling to the transaction |
Pre-reading, printing, minuting, archiving with the board papers |
| Page fidelity |
Reflows to the screen; page breaks are not guaranteed |
Fixed page size, margins, page numbers and repeating table headers |
| Page count |
PDF export is limited to 50 report pages |
No comparable page-count limit |
| Access required |
Guest account, licence or capacity, and RLS role assignment |
A file — readable by any director, offline |
| As-of behaviour |
Current unless deliberately snapshotted |
Frozen at the export, stamped on every page |
Who this is for
We build these packs for CFOs and controllers at companies with an active board or audit committee, for chiefs of staff and company secretaries who assemble the papers, and for founder-led businesses that have just taken on institutional investors and suddenly owe someone a quarterly pack. Sponsors rolling several companies into one comparable view should start instead with Power BI for private equity, and advisors running the same pack across a client portfolio will find the standardised approach on Power BI for fractional CFOs closer to what they need. If the more pressing need is the weekly grid your leadership team reads in its Level 10 meeting rather than the papers your directors receive, start with our EOS scorecard Power BI dashboard build instead — different cadence, different audience, and usually built from the same model. Credit unions whose directors and supervisory committee read a packet built around member growth, delinquency and the quarterly Call Report ratios should begin with Power BI dashboards for credit unions. School boards are the same problem with a different vocabulary — enrollment, attendance, assessment results and site spending rather than revenue and margin — and that build is covered on Power BI dashboards for school districts. A college or university board of trustees reads a third vocabulary again — the admissions funnel, retention and completion, net tuition revenue and the endowment draw — and that pack is built from the model described on Power BI dashboards for higher education.
What it costs and how the engagement works
There is no retainer and no project minimum. You buy a fixed-price block of senior-led Power BI hours upfront — Starter, 20 hours at $125/hour ($2,500); Growth, 40 hours at $115/hour ($4,600); Power, 80 hours at $100/hour ($8,000) — and draw them down task by task. Every request gets a written scope and an hours estimate before any work starts, hours are deducted only for work you have reviewed and approved, and unused hours never expire. Most individual pages land in three to five business days; a first full pack with definition sessions and a distribution dry run typically runs across two to three cycles as the board tells you what it actually wants. See how Flex hours work.