Build a useful board pack with a clear outline, a worked decision brief and a review process that connects portfolio results to their supporting evidence.
Foundation board reporting is the preparation of information trustees need to oversee the foundation, review progress and make decisions. A useful board pack connects strategy, grant commitments, finances, results and risks. It explains what changed, what needs attention and what the board is being asked to do.
The pack is sometimes called a board docket. Whatever the name, it should help a trustee distinguish an update from a decision. An attractive dashboard is useful only if its figures, limitations and implications are understandable.
This guide focuses on grantmaking foundations and the partner evidence behind their board reports. It offers a practical outline, an illustrative decision brief and a repeatable preparation process. Adapt the financial, governance and meeting requirements to your foundation rather than treating this outline as a compliance checklist.
Before requesting another slide from each department, agree the agenda with the people responsible for the meeting. Ask which items need a decision, which need discussion and which are for monitoring. These are different reading tasks.
For a decision item, state the request early. Present the options, relevant evidence, uncertainties and staff recommendation. For a monitoring item, show the agreed benchmark and meaningful change. For a discussion, frame the question without pretending that the evidence already settles it.
BoardSource’s meeting guidance recommends reserving meeting time for critical issues and decisions, with advance materials that let members prepare. Its recommendation to move routine updates to a consent agenda is not a reason to hide difficult results. Follow the board’s agreed process for items requiring discussion.
Use a consistent order so trustees can find the same information from one meeting to the next. The following is a starting structure, not a requirement to include every section at every meeting. Put detail in an appendix when it supports a question without improving the main narrative.
On a narrow screen, scroll the table horizontally to read all columns.
| Section | What to include | Reader’s question |
|---|---|---|
| Executive summary | Material changes, decisions requested and unresolved concerns. | What needs my attention? |
| Strategy and portfolio progress | Progress against agreed objectives, coverage and significant differences between programs. | Are we moving in the intended direction? |
| Grant portfolio | Commitments, disbursements, due reports, amendments and decisions within the board’s remit. | What have we committed to, and what changed? |
| Financial review | Finance-approved statements, budget variances and explanations relevant to oversight. | What does our financial position mean for the plan? |
| Results and learning | Selected measures, partner explanations, limitations and lessons for future work. | What do we know about progress, and how well do we know it? |
| Risks and exceptions | Material issues, evidence gaps, response owner and next review date. | Where is action or further inquiry needed? |
| Decision briefs | Request, options, evidence, trade-offs and recommendation. | What exactly are we deciding? |
| Action log and appendix | Previous decisions, outstanding actions and supporting sources. | What happened after the last meeting? |
Keep commitments, payments and expenditure distinct. A grant approved by the foundation, cash disbursed to a partner and expenditure reported by that partner describe different events. A single unlabeled “funds deployed” total can obscure that difference.
Finance should confirm the financial definitions and reconcile relevant figures with its authoritative records. The narrative impact summary supplements that work. It does not replace financial statements or the board’s financial oversight. BoardSource recommends that financial statements receive separate consideration rather than being placed on the consent agenda.
A number needs a measure, population, period and source. A narrative needs enough context to distinguish a documented observation from an interpretation. Store these details during reporting, rather than asking one staff member to reconstruct them just before the meeting.
Keep source references and approved corrections throughout. New evidence should update the working record without silently changing a previously issued board pack.
For example, “employment improved” is incomplete without the cohort, follow-up timing and definition of employment. A total drawn from six reporting partners should not look like a result for all ten funded partners. A strong outcome story can explain experience, but does not establish how common that experience was.
Use a shared dictionary for common measures and retain partner-specific measures where needed. Different programs do not become comparable merely because their reports use the same heading. The portfolio data management guide explains record relationships, definitions and corrections in more detail.
Illustrative example. A foundation has ten active grants in a training portfolio. Eight partners submit their quarter-two reports by the preparation cutoff; two are still outstanding. Six of the eight reporting partners use a compatible definition of completion and report 240 completions against their combined target of 300.
That is 80% of the target for those six partners. It is not an 80% success rate for the entire portfolio, and it does not measure sustained employment. The remaining two submitted reports count enrollment, so their figures should not be added to completions.
Progress: six partners report 240 completions against a combined target of 300. Coverage: six of ten active grants contribute to this comparable result; two reports use a different measure and two are missing. Interpretation: progress is below plan for the included partners; portfolio-wide performance remains incomplete.
Suppose a partner requests a three-month extension. Its update describes a delayed venue opening, and dated correspondence supports that explanation. Staff should connect this evidence to the relevant grant rather than treating a portfolio average as evidence for that individual decision.
The board still needs to exercise judgment. Better reporting makes that judgment more informed; it does not turn an extension into an automatic approval. After the meeting, record what was decided and any conditions so the next report can close the loop.
Use a short exception register for issues that affect interpretation or need action. State the issue in plain language, its possible effect, the owner and the next step. Avoid using an unexplained red indicator as a substitute for that information.
Keep three distinctions visible: a result below target, a missing report and an unresolved data conflict. They may require different responses. Missing evidence is not proof of poor delivery; equally, a submitted report is not proof that its claims are correct.
When a narrative reports 125 participants and its attachment lists 118, retain both figures and ask the source owner to explain the discrepancy. Do not let an automated summary select whichever number makes the story smoother. Use a provisional label or withhold the affected aggregate until the handling is agreed.
Show changes in definitions alongside trend charts. If the foundation changes from counting all placements to counting placements sustained for three months, explain the break in comparability. Do not draw a continuous performance conclusion across different measures without a justified method.
Set the timetable around the meeting and the foundation’s own notice and review requirements. There is no universal number of days that makes every board pack ready. Work backward from distribution, leaving time for clarification, financial review and approval.
A live dashboard and an issued board pack can coexist. Label the live view’s refresh date, and retain a dated snapshot of what trustees received. If a material correction arrives later, document the amendment rather than silently replacing the earlier record.
Keep sensitive partner or individual material out of broadly distributed appendices unless access is justified. A trustee’s access to a summary does not automatically require access to every interview transcript or personal record supporting it.
Configured AI can help identify themes in partner updates, extract candidate figures, flag apparent contradictions and prepare a first draft around a board question. Those uses are more dependable when sources, reporting periods and agreed definitions remain attached to the result.
Ask the reviewer to inspect the supporting evidence, not just the fluency of the paragraph. Check arithmetic, coverage, changed meanings and whether an interpretation goes beyond the source. An AI-generated risk flag is a reason to review, not a verified finding or a decision about a partner.
The practical opportunity for Sopact is recurring collection and analysis of evidence that otherwise arrives in separate surveys, uploaded documents and partner conversations. Test the configured workflow against your own board question and source material. Confirm supported formats, integrations and access controls during implementation.
The video is a broader introduction to impact measurement and management with AI. It complements the evidence discussion; the board-pack outline, preparation steps and approval responsibilities are explained in this article.
A board portal may distribute meeting materials; a grants system may maintain agreements and approvals; finance software maintains financial records. Identify which problem you need to solve before buying another dashboard. The hard part may be collecting and interpreting partner evidence across those systems.
Test a representative board item with a late report, a corrected value and a narrative that disagrees with an attachment. Evaluate the complete workflow:
Include setup, migration, partner support, integrations, review time and ongoing maintenance in the total implementation cost. A low subscription price is not the whole cost, but neither does a higher price guarantee better evidence. Test whether the proposed process reduces repeated assembly without hiding necessary review.
Use the portfolio monitoring software guide for a fuller evaluation, and Sopact’s portfolio solution to explore its collection and reporting approach.
Kuramo Foundation’s published story describes translating its internal gender-lens framework into a working data and dashboard approach before launch. The relevant lesson is to connect the framework to collection and review. The story is not evidence of a specific board-pack implementation or an independently audited outcome.
For your next meeting, choose one important question and trace the answer through a few grants. Agree what the board needs to see, what belongs in supporting evidence and what is still unknown. Use that small cycle to improve the dictionary, responsibilities and review process before extending it across the portfolio.
A board pack serves internal oversight and decisions. A public impact report serves a wider audience; a funder report answers the agreed reporting requirements; a statutory filing has its own applicable rules. Reuse checked evidence where appropriate, but do not assume these documents are interchangeable.
Continue with the Portfolio Intelligence course. For audience-facing reporting, use the impact report writing guide and report examples and dashboards.
Include the decisions requested, strategy and portfolio progress, grant commitments, financial review, results, risks, outstanding actions and supporting evidence. Adapt the outline to the board’s responsibilities and meeting agenda.
A board docket is the packet of agenda items and supporting material prepared for a board meeting. The term is often used interchangeably with board pack or board packet.
Prepare material for the board’s agreed meeting and oversight schedule. Set collection cutoffs and review time around that schedule and applicable requirements rather than assuming one universal monthly or quarterly rule.
Long enough to support the decisions and oversight required, with a concise main narrative and accessible supporting detail. There is no single page count that fits every foundation or meeting.
State how many reports are included and which measures are affected. Keep missing evidence distinct from zero results or poor performance, and assign follow-up without hiding the coverage gap.
AI can help extract information, organize evidence and draft summaries in a configured workflow. People still need to verify sources, arithmetic, interpretation, permissions and the final recommendation.
Not by itself. Trustees also need context, limitations and clear decision requests. Keep a dated record of the material issued to the board even when a dashboard continues to update.
No. The board report supports internal oversight and decisions. An annual impact report communicates to a wider audience. They can reuse checked evidence, but their purpose, detail and access requirements differ.
