How to build a board report that separates fact from inference
A useful board report is a decision document, not a dashboard export. Reconcile a stable KPI set, show actual versus plan and prior period, explain material drivers, separate observed facts from management interpretation and forward-looking assumptions, state decisions and risks explicitly, and preserve definitions and source history in an appendix so the concise narrative remains auditable.
The essential checks
- Keep KPI definitions stable across meetings.
- Label fact, interpretation, forecast, and recommendation distinctly.
- Explain changes, not every metric.
- End each section with the decision or watch item.
Where errors enter the process
Board packs accumulate screenshots, inconsistent metric definitions, selective success stories, and unexplained forecast changes. Readers cannot tell which statements are measured, inferred, or aspirational.
Evidence worth tracing
- Historical KPIs change without restatement notes.
- Charts omit plan or prior comparison.
- Forecast assumptions are presented as results.
- The requested board decision is buried in an appendix.
From the field · Nonprofit finance and impact lead
Build a nonprofit board report without exposing donors or overstating impact
The board pack combines donations, restricted funds, program participation, and outcome surveys. Donor identities are sensitive, attribution is imperfect, and late expense postings can alter program cost conclusions.
Columns used in the example
period · fund · donation_amount · restriction · program · expense · participant_id · outcome_measure
Follow it with your own file
- Reconcile finance and program facts before drafting narrative.
- Label causal or impact interpretations separately from observed associations.
- Aggregate donor and participant details to the minimum decision-useful level.
- End sections with explicit risks, decisions, owners, and missing evidence.
Check: Every figure must trace to approved evidence, restricted funds must reconcile, small groups must be protected, and uncertainty must remain visible in the final pack.
A method you can follow
- Define decisions and stable scorecard: Start with board responsibilities and choose a limited set of financial, customer, operating, and risk indicators.
- Reconcile and annotate: Lock definitions, sources, periods, and restatements; compare actual, plan, prior, and forecast consistently.
- Write layered narrative: Separate result, driver evidence, management interpretation, uncertainty, and requested action.
- Publish with appendix: Place decisions and exceptions first; retain KPI dictionary, detailed tables, and lineage for audit.
Structure around decisions and exceptions
Boards need to allocate capital, assess risk, evaluate progress, and support or challenge management. Organize the pack around those duties rather than the application's navigation.
A stable scorecard provides continuity; exception narrative explains what changed and why it deserves attention now.
Label epistemic status
Observed: churn increased from 4.2% to 5.1%. Interpretation: onboarding friction contributed. Assumption: the planned fix will recover half the gap. Recommendation: fund the fix. These statements require different evidence.
Clear labels increase trust without making the report timid.
Sign-off questions
- Decisions stated
- KPIs reconciled
- Definitions stable
- Comparisons consistent
- Assumptions labeled
- Appendix traceable
Statement types in a board report
| Type | Example role | Evidence standard |
|---|---|---|
| Fact | Measured performance | Reconciled source |
| Interpretation | Why movement occurred | Driver evidence and alternatives |
| Forecast | Expected future result | Model and assumptions |
| Recommendation | Proposed action | Trade-off and owner |
Doing these steps in Prepyr
Upload a CSV working copy in Prepyr. Describe the result you need: Build a board report that visibly separates verified facts, interpretations, risks, and decisions. Check the columns selected, preview any proposed changes, and compare the output with the source before applying or exporting it.
Prepyr steps used here: Board report templates · KPI tables · Charts · PDF export
A board pack that supports governance and decisions while making it easy to distinguish verified performance from management judgment.
Questions readers usually ask next
How many KPIs should a board report contain?
Use a compact stable scorecard, often 8 to 15 headline measures, with diagnostics in the appendix.
Should bad news appear first?
Material decisions, misses, and risks should be prominent regardless of whether they are positive or negative.
How do I handle metric restatements?
Show the old and new definition, affected periods, impact, reason, and whether prior packs are restated.