At some point, every hospital foundation gets asked the same hard question, in one form or another: what actually changed because we funded it? A board member wants to know before approving next year's budget. A major donor wants to know before renewing their gift. Hospital leadership wants to know before backing the next capital request. And too often, the honest answer is that no one quite knows — not because the funding didn't work, but because the intended impact was never captured clearly enough to compare against what actually happened.
In our recent webinar, The Hospital Foundation's Hardest Question: What Changed Because We Funded It?, Reviewr walked through connecting what a program intended to do, what actually happened, and what it means for the next funding decision — so that question finally has a real answer. If you missed it live, here's what we covered, and you can catch the full session on demand below.
Most foundations can describe what they hoped would happen. Few can prove what actually did.
Applications capture what a program hopes to do, but rarely in a way that can be measured later — so once funding goes out, the story turns into memory and hallway conversation. By the time someone asks what changed, a foundation is left reconstructing impact from memory instead of a record. The alternative is a record where intended impact, actual outcomes, and the next funding decision all stay connected in one place — so what changed because you funded it has a real answer instead of a guess.
1. Capture the Full Picture Before You Fund It: We covered structuring the application itself around intended impact, populations served, community needs, and project goals, so every funding decision starts with a clear, comparable record of what success was supposed to look like. Intended impact, target population, and community need become structured fields — not a paragraph buried in a narrative response — and every application captures project goals in the same comparable format, cycle after cycle. Importantly, this doesn't mean overhauling your form from scratch: Reviewr is built to make small, ongoing improvements manageable in the spare time admins actually have, keeping the foundation's original event and building off it rather than starting over each year. A clear definition of success exists before a single dollar goes out, and the same structured fields carry forward into scoring, reporting, and next year's comparison.
2. Track What Actually Happened After You Fund It: We showed how supplemental forms collect updates, outcomes, documents, and results after funding goes out, so a foundation isn't chasing grantees for information months after the fact. Supplemental forms tie directly to the recipient's original application and account, so they simply log back in, see what's required, and submit — no separate portal, no guesswork. Automated email reminders keep that follow-up on the recipient's radar without a single manual email from your team, and some foundations use it to tie the second half of a disbursement to that completed report, giving them real leverage to get it back.
3. Evaluate Consistently, Every Time: We walked through how weighted criteria, scorecards, assignments, and structured workflows keep every funding decision defensible, whether it's a small community health grant or a major capital request. Weighted criteria reflect what the foundation actually values, applied the same way every cycle, and scorecard questions line up directly with the application so a judge always has something clear to reference. Reviewer assignments are balanced automatically to avoid the reviewer fatigue that comes from an uneven number of submissions per judge — replacing an ad hoc gut check with a documented standard, so every funding decision can be explained and defended later, not just remembered.
4. Turn Funding Into Reports Your Board Can Actually Use: We covered how reports organize funding, outcomes, populations served, and program activity into a picture that can be handed to a board or leadership team, instead of reconstructed by hand every time someone asks. Funding, outcomes, populations served, and program activity live in one report instead of five separate files — generated automatically as the program runs, so a board member's question gets a current answer instead of a promise to compile one. Because those reports pull directly from the event with no manual entry, they're what we called "backable, defendable information" — numbers a board or leadership team can trust weren't reconstructed from best guesses.
5. Let Last Year's Data Sharpen This Year's Decisions: We demonstrated comparing historical application, award, and outcome data to see what's actually worked, so each funding cycle builds on real evidence instead of starting from scratch. Historical outcome data shows which kinds of programs actually moved the needle, not just which ones got funded, and award and application history from prior cycles informs this cycle's criteria and priorities. Updating a form from year to year is as simple as cutting, copying, or adding a question — and if a change doesn't work out the way you hoped, you can always revert back to a prior year's version, since nothing is lost when you evolve the program.
After walking through the five fixes, the session moved into a live look at Reviewr itself, covering the applicant, judge, and admin experience:
Old way: Intended impact, populations served, and community need captured informally, if at all, and rarely in a way anyone could measure later. Post-funding updates arriving as emails and hallway conversations, if they arrive at all. Funding decisions made on whatever standard feels right that cycle, with no defendable reasoning behind them. Outcomes, populations served, and program activity scattered across files with no single report to pull. Each funding cycle starting over, with no real record of what worked the last time.
New way: Intended impact, populations served, community need, and project goals captured directly in a structured application. Supplemental forms gathering post-funding updates, outcomes, and results automatically, tied to the original award. Weighted criteria and scorecards built to fit the program, keeping evaluations consistent and defensible. Reports that organize funding and outcomes automatically, ready to hand to a board or leadership team at any point in the cycle. Historical applications, awards, and outcome data sharpening every new funding decision instead of starting from a blank page.
Getting this right isn't only about satisfying one board meeting — it's about every funding decision this year, and the ones that follow.
Built Around Every Funding Decision. A small community health grant and a major capital request both start with the same structured record of intended impact — not a guess reconstructed only for the ones someone happens to ask about.
Connected From Intent to Outcome. An application, its outcomes, its reports, and next year's decisions all stay part of one continuous record.
Or, as we summed it up in the session: a record built before you fund, plus an outcome captured after, equals an answer you already have.
This isn't about proving a guess. It's about having the answer already. From the intended impact captured before you fund, to the outcome captured after, to the report ready whenever it's asked for, "what changed because we funded it" stops being a guess and becomes a real, defensible answer.
The all-in-one platform for managing scholarships, grants and awards programs.
