Grantee onboarding as framework alignment — one structured call that binds the theory of change, data dictionary, and cadence before the first cycle.
Everything a funder will ever report — outcomes, portfolio comparisons, board answers — is decided in the weeks after the award, when each grantee's theory of change either becomes a bound, measurable framework on the record or stays a PDF nobody opens again. One structured call per grantee does it. This page shows the design.
The work between the award letter and the first reporting cycle: confirming what the grant will change, how the change will be measured, what the grantee will submit and when. Done well, it is framework alignment — the grant agreement becomes a measurable commitment on the grantee's record. Skipped, every later report becomes a negotiation about definitions.
Turning each grantee's own theory of change into fields the portfolio can compare. The grantee keeps its goals and outcomes in its own language; each maps to the funder's data dictionary — shared definitions, units, evidence requirements. Thirty grantees stay comparable without being flattened. Funds call the same step investee onboarding.
Consistency is the whole trick. When every onboarding call follows the same agenda, every transcript yields the same fields — and the portfolio framework assembles itself from thirty consistent conversations.
Who is served and how underserved they are; the program model and its mechanism; partners and context. This grounds the Who and What of everything measured later.
What the grant should change, the activities and outputs that lead there, and the outcomes the grantee will stand behind — in the grantee's own words first, mapped to the dictionary second.
What the grantee already measures and with which instruments; data capacity and gaps; the reporting calendar and contacts. This is where burden gets capped by design.
The transcribed call is read for goals, partners, activities, outputs, and outcomes — each extracted with the source passage, drafted into the grantee's framework for confirmation.
"From each transcript, extract goals, partners, activities, outputs, and outcomes; map them to the portfolio framework."
Set once, used by every cycle that follows. The framework agreed here is what every quarterly submission is read against — drift detection, missing-data checks, and the portfolio roll-up all depend on it. Get onboarding right and the rest of the grant is collection; the full lifecycle sits in our grant management software guide.
Onboarding is where reporting burden is decided. The rule: new collection is added only where an outcome genuinely has no existing evidence source — and the grant shape decides what "existing" means.
Binds to the program's own intake forms, attendance, and assessments. The dictionary maps fields; nothing new is invented unless an outcome has no instrument.
Binds to organizational artifacts — annual outcomes, financials, board reports. The framework reads what the organization already publishes, at the cadence it publishes.
Binds to a capability rubric baselined on the call — the one genuinely new instrument worth adding, because capacity change is the outcome being purchased.
First reports arrive in thirty formats measuring thirty definitions. The program officer reconciles by hand; grantees feel re-asked and over-asked; the portfolio report averages inconsistencies. Every cycle relitigates what should have been agreed once.
Submissions land against agreed fields; missing data goes back via unique link; drift from the confirmed theory of change flags a conversation mid-cycle. The portfolio rolls up because it was aligned at the start.
The most common failure is partial onboarding — a kickoff call that covers logistics (payments, contacts, deadlines) but never touches measurement. The relationship starts warm and the data starts broken. The nine-question agenda exists so the measurement conversation cannot be skipped politely.
The work between the award letter and the first reporting cycle: confirming what the grant will change, how that change will be measured, what the grantee will submit and when, and who the contacts are. Done well, it is framework alignment — the grant agreement becomes a measurable commitment on the grantee's record. Skipped, every later report becomes a negotiation about definitions.
Turning each grantee's own theory of change into fields the portfolio can compare. The grantee keeps its goals, activities, outputs, and outcomes in its own language; each maps to the funder's data dictionary — shared definitions, units, and evidence requirements. The result: thirty grantees stay comparable without any of them being flattened into a generic template. Funds call the same step investee onboarding.
One structured call — typically 60 to 90 minutes — that follows the same agenda for every grantee: the problem and population, the program model, goals and partners, activities and outputs, intended outcomes and how the grantee already measures them, capacity and data practices, and the reporting cadence. Transcribed, the call becomes that grantee's draft framework; the program officer and grantee confirm it, and it binds to the record.
Same agenda, same extraction, same dictionary. Every call asks the same systematic questions; each transcript is read for goals, partners, activities, outputs, and outcomes; each extraction maps to the shared portfolio framework. The consistency is what makes the portfolio roll-up trustworthy later — and it costs one call per grantee, not a consulting engagement.
By capping the ask to what the grantee already produces. Onboarding surfaces what the organization measures today — its forms, its case notes, its existing reports — and the framework binds to those artifacts wherever possible. New collection is added only where an outcome genuinely has no evidence source. The burden conversation happens once, by design, instead of at every reporting deadline.
The first report arrives in the grantee's format, measuring the grantee's definitions, and the program officer discovers the grant agreement and the grantee's data don't describe the same program. Multiply by thirty grantees and the portfolio report becomes an averaging of inconsistencies. Most reporting pain attributed to grantees is actually an onboarding gap — the framework was never aligned, so every cycle relitigates it.
Grant Intelligence includes the onboarding scenario in full — the agenda, the extraction, the portfolio alignment across 30 grantees — and how the bound framework drives every cycle of Sopact's grant management software. Bring a real grant agreement to a demo and leave with its framework drafted.
