What belongs in a foundation board pack, the three questions trustees ask, and how the docket, annual report, and filings regenerate from one record set.
Foundation board reporting is the periodic report a foundation gives its trustees: what the portfolio funded, what changed, and what it means for strategy. Sopact calls the record behind it the Grantee Thread — one funded record per grantee, under a persistent Contact ID, that keeps collecting after the money moves — so a board deck is a query over the grantee records rather than a manual assembly each quarter.
Program and strategy leads describe the same scramble before every board meeting: pull the grantee reports, re-read the narratives, re-type the numbers, and build a deck that a trustee will question line by line. Award-centric systems closed the grantee record at disbursement, so the outcomes the board wants live in PDFs, and the deck is rebuilt from scratch each cycle with no trail back to the evidence.
Key takeaways
Board reporting looks like a design task — charts, headlines, a narrative — but the real work is reading: gathering every grantee report, reconciling each against what it was funded to do, and turning narratives into portfolio figures a trustee can trust. When that reading happens once a quarter under deadline, the deck is only as reliable as the hours available, and a trustee’s follow-up question sends someone back into the PDFs.
Sopact keeps this on the Grantee Thread: one funded record per grantee, read against its logframe on arrival, and kept, so portfolio figures for the board are a query with the evidence attached. The portfolio itself is on grant software for foundations; the head category is grant management software.
Foundations build board reports from the outputs of their grants systems — Fluxx, SmartSimple, Foundant, Blackbaud Grantmaking (GIFTS Online) — usually exported into a spreadsheet and then a slide deck, sometimes through Power BI. These systems report on the transaction and the disbursement reliably; the outcome story that a board actually debates is assembled downstream from documents, by hand, with no link back to the grantee sentence behind each figure.
The one test that separates the approaches: ask the system to produce the portfolio outcomes for this board meeting, per program and rolled up, with the exact sentence from each grantee report behind every number, and let a trustee drill into any figure. A reporting export gives you rows to arrange; Sopact answers from the Grantee Thread, because each grantee report was read on arrival and kept.
The move that changes board reporting is reading each grantee report against its logframe as it arrives, so the portfolio figures the board sees are always current and always traceable, and building the deck is selecting from a live record rather than assembling from PDFs. Sopact extracts outcomes from the grantee reports a foundation already collects, so the deck carries evidence and a trustee can drill from a headline number to the grantee’s own words.
The result is a board report that holds up under questioning: portfolio outcomes per program and rolled up, each tracing to its source, and a consistent story across cycles because the record persists. Sopact keeps this on the Grantee Thread and reads on arrival, so a strategy lead confirms figures against the grantee reports rather than rebuilding the narrative every quarter.
An export-and-assemble approach rebuilds the board deck from PDFs each cycle; the Grantee Thread keeps every grantee report read and kept, so portfolio figures are a query with the evidence attached. The difference is whether a trustee’s question is answered from the record or from a scramble.
| The question | Assemble the deck | Grantee Thread |
|---|---|---|
| Produce portfolio outcome figures? | Exported and re-typed | Yes: a query over the records |
| Trace a board number to evidence? | Not without opening PDFs | Yes: grantee sentence quoted |
| Let a trustee drill into a figure? | No: back to the documents | Yes: down to the source report |
| Consistent story across cycles? | Rebuilt each quarter | One persistent record per grantee |
See the portfolio itself on grant software for foundations, or the impact-first capital angle on program-related investments.
A grantee going off-plan is worth catching in month three of a grant, not in the closeout report after the money is spent. The value of reading a grantee report is highest while the grant is still open, when a stalled outcome or a missed milestone can still be supported. That is the premise of the Loop, Sopact’s method for continuous intelligence: collect clean at the source, analyze the moment a grantee report arrives, improve while the grant can still be changed.
The Loop is also what makes an outcome defensible: every reported number traces back to the sentence in the grantee report and the logframe indicator it answers, the standard detailed in Loop traceability, so a portfolio roll-up or a board figure rests on the grantee’s own words rather than a re-typed spreadsheet cell.
One method, three moves that never stop
Then the next reporting cycle runs a little sharper. Read the method: the Loop methodology →
The fastest way to see the gap is to run it on your own portfolio. Export this cycle’s grantee reports with their IDs, then paste the prompts below into Sopact Sense’s Assistant, or reason through them with your program team. The arrow above each links the Academy walkthrough with the expected output and tips.
Academy walkthrough → Extract outcomes from a grantee report
Here is a grantee's narrative and financial report for this period: [ATTACH]. Read it against the logframe we funded, pull each outcome and output with the exact sentence from the report quoted as evidence, separate what they spent from what changed, and flag any indicator the report does not answer, so I get outcomes from the document I already have rather than sending another questionnaire.
Academy walkthrough → Compute grantee variance
Here is a grantee's committed targets and their latest report: [ATTACH]. For every indicator, show the target, the reported actual, and the variance, quote the sentence that supports the reported number, and flag any indicator off-plan by more than our threshold, so a grantee drifting shows up now while the grant is still open and we can help.
Academy walkthrough → Roll up a grant portfolio
Here are this quarter's grantee reports across the portfolio on their persistent IDs: [ATTACH]. Roll up each shared outcome across every grantee, show the per-grant number and the portfolio total, flag which grantees are driving the result and which are lagging, and quote one line of evidence per grantee, so the board view is a query over the records rather than a spreadsheet re-typed by hand.
Academy walkthrough → Onboard a grant or RFP program
Here is our program description and last cycle's reporting template: [ATTACH]. Draft the intake questions, the logframe indicators and their targets, and the reporting schedule, so every grantee this cycle lands on one persistent record and keeps collecting outcome data after the award instead of being chased at the deadline.
Each walkthrough is short and practical: what to do, the prompt to run, the output to expect, and the tips that keep it reliable.
Watch: reading grantee reports against the logframe on arrival and keeping every grantee on one persistent record.
It is the periodic report a foundation gives its trustees on what the portfolio funded and what changed. Sopact adds the Grantee Thread — one funded record per grantee that keeps collecting after the award — so a board deck is a query over the grantee records rather than a manual assembly.
Because award-centric grants systems close the grantee record at disbursement, so the outcomes trustees ask about live in PDFs. Sopact is record-centric: the Grantee Thread keeps every grantee report read and kept, so portfolio figures for the board are a query.
Every figure traces to the grantee report and the sentence behind it, so a trustee’s question is answered from the record. Sopact keeps that evidence on the Grantee Thread, so a headline number drills down to the grantee’s own words.
No. Sopact runs alongside them as an AND. The grants system collects reports and the BI tool visualizes; Sopact reads each grantee report against its logframe on arrival and keeps the portfolio figures on the Grantee Thread for the board.
Yes. Because every number is a query over the grantee records with evidence attached, a trustee can drill from a portfolio headline to the source grantee report. Sopact keeps that traceability on the Grantee Thread.
Yes. Sopact reads the grantee reports you already collect and rolls up outcomes per program and in total, quoting the sentence behind each. The evidence stays on the Grantee Thread, which reduces grantee reporting burden.
No. Sopact’s Assistant drafts portfolio figures and outcomes from the grantee reports with the evidence quoted; a strategy lead confirms or overrides them, human-in-the-loop. The Grantee Thread records what was read and from which report.
It keeps every grantee report on one persistent record, so each board cycle reads the same records forward rather than rebuilding from documents. The record persists, which is what makes a consistent, defensible board story possible on the Grantee Thread.
Next: see the portfolio on grant software for foundations, or the head category on grant management software.
