Every named fund starts with a donor's purpose: one high school, one field of study, one town. A fund set up to last 50 years can look very different 10 years in. The school may have consolidated, the field and its jobs may have changed, or fewer young families may live in the town. When a fund's purpose and a community's needs drift apart, students miss out on funding, donor relationships strain, and the answer to "What did the fund accomplish?" gets rebuilt by hand.
In this on-demand session, Reviewr shows community foundations how to keep every named fund true to its donor's purpose while still reaching the people who need it today. It works through two sets of moves: building clear criteria by turning each fund agreement into eligibility questions and a scorecard, matching each student to every fund they fit, giving each fund its own committee, and starting a conversation when a fund still doesn't fit; and keeping a clear record that shows donors and the board how every award honored the fund. The session is built for community, education, and hospital foundations, but the same moves apply to any organization running donor-funded scholarships, grants, or awards. It closes with a live demo of the applicant experience and an extended look at the admin side of Reviewr.
Donors come to a foundation with a reason for giving, and that reason has to survive every handoff. The donor sets the purpose. The committee interprets it, often adjusting the program every few years to fit the cycle. The applicant has to fit it this year. And the committee itself turns over, so the people carrying the donor's intent forward change from year to year.
The session names two ways a fund drifts from its purpose:
The goal is the middle: respecting the donor's wishes and original criteria without broadening the fund so far that it applies to everyone.
When nobody can see the drift, it costs three groups:
Most scholarship, grant, and award programs spend September and October meeting with their boards about goals, values, and desired outcomes, and what needs to change from last year. Late October into early November is when those changes go into the application questions, criteria, and scorecard. What a foundation sets up now is what students see when windows open on January 1, and committees make their decisions in early spring. Since most people running these programs do it on top of another job, after hours or over lunch, the weeks before the holidays are the time to put a better process in place.
The session frames the work through Review Integrity, five questions every review process should be able to answer, in the order a real program runs:
Each dimension moves up a four-stage ladder, from Ad hoc to Documented to Calibrated to Instrumented.
1. Turn the fund agreement into criteria (Intake Proportionality).What the fund agreement says becomes eligibility questions and a scorecard. Eligibility screening runs automatically: eligible applicants move through the form, and ineligible applicants are stopped and flagged before they complete an application they never qualified for. That saves admins the sorting and saves applicants the frustration, which makes them more likely to come back if they're eligible next year.
2. One application, matched to every fund a student fits.A student applies once, and the form saves as they go. Questions about school, field of study, town, and need double as matching questions, so the answers decide which funds a student is considered for. A student who fits a narrow fund doesn't have to know it exists to be matched to it, and each applicant sees only what applies to them.
3. Each fund gets its own committee and its own scorecard (Rubric Clarity and Reviewer Calibration).Many programs still send application packets to judges and ask them to pick a winner with no scorecard at all. Every fund should have a scorecard, and funds with different goals should be scored differently. A grant for an established business and a grant for a small business getting back on its feet shouldn't ask the same questions or use the same rubric. Assigning reviewers to the funds that match their expertise keeps them comparing like with like, and it makes their work easier rather than spreading them thin.
4. Hide identifying information from reviewers.Admins keep the full profile, while reviewers see only what affects the score. It's less for reviewers to sift through, and it removes the bias that comes with knowing an applicant, which is common in community foundations even when everyone intends to be fair.
5. When a fund still doesn't fit, start a conversation (Loop Closure).Applicant numbers that drop year after year are a red flag. Look at the last cycle and how many students qualified for each fund. If qualification is the problem, reach out to the donor about what matters most to them and how the criteria could reach more qualified applicants. Bring the change to the board, build it into the form, and measure the next cycle: how many more applications came in, and whether there's still more to adjust.
6. Separate what the donor shapes from what the committee owns (Decision Traceability).The donor shapes the fund's purpose, the criteria before students apply, and what they hear after the award. The committee owns scoring every eligible student on the same weighted scorecard, the decision, and the reason for it. A donor who wants a bigger role can join the committee and score applicants with identifying information hidden.
7. Show how every award honored the fund.The application, matched funds, reviewers, scores, comments, and award stay together. Each student's history across past cycles stays on one profile, so a student who applies every year doesn't recreate an account and can see past applications, and the foundation can see how each applicant has changed over time.
8. Close the loop with donors and the board.Automated supplemental forms collect acceptance forms, impact forms, proof of enrollment, and thank-you notes from recipients, with automatic reminders and little added work for admins. Donors can hear who received their fund and read the student's thank-you note. For the board, standard and custom reports, including recipient profiles, show what each fund accomplished and make each decision easier to defend.
The same question, two ways.A donor's family asks how their scholarship was awarded. Without a record, the fund agreement is in a cabinet, last year's committee has turned over, nobody knows who else applied, and the answer is "Let me look into it." With a record, every eligible student was matched, all were scored on the fund's criteria, the reason is in a comment, and the answer is "Here's how we decided."
A five-question self-check for your named funds.Is every fund's purpose turned into eligibility questions? Is every student considered for every fund they fit? Does every committee score on weights set before students apply? Could you show a donor's family how any student received their award? Could you name the funds that struggled to find applicants?
Common questions.Foundations with dozens of funds can run them in one application, with each fund keeping its own committee and scorecard. Funds that share a timeline and applicant profile questions can live in one program, with conditional logic sending each applicant only to the funds they match. Reviewr doesn't pay scholarships, so foundations keep their current payment process. Reviewr is SOC 2 Type 2 compliant and supports single sign-on. Setup typically takes about 30 days, but the timeline is flexible, and programs can go live in as little as a week.
Reviewr is an application management platform founded about 15 years ago by a team that had been part of application processes that didn't work well for applicants, judges, or admins. Scholarships can decide whether someone continues their education, and grants can decide whether a small business stays open, so Reviewr was built to give every applicant the best chance to put their best foot forward. It runs thousands of programs every year, keeps releasing new features and enhancements, and gives every account a dedicated one-on-one Reviewr team member for support.