Credit unions give back in real ways: member scholarships, scholarships for employees' children, community grants, donation requests, and local sponsorships. But when the board asks what this year's giving actually did, the answer often lives in an inbox, a spreadsheet, and one staff member's memory. The story is there. The record behind it usually isn't.
In this on-demand session, Reviewr walks credit unions through five practical moves for running scholarships, donation requests, and sponsorships so every award comes with a record your board, CFO, and community can follow: one front door for every request, a protected committee, one weighted scorecard on the record, a clear picture of what happened after the award, and reports that tell the story with the record behind it.
The session opens with a simple test. For any scholarship, grant, or sponsorship you've run in the past year or two, can you show who applied, how it was decided, and what happened after? Do you know which applicants were members, which weren't, and which were children of employees? Could you walk someone through how the recipient was chosen? And did anything happen once the award went out?
For many credit unions, the honest answer is "partly." Community giving usually runs on one person with another job. Requests come in by email or at the front desk. The committee is made up of employees or board members who often know the families. Scores, notes, and decisions sit in a spreadsheet, if they're written down at all, and thank-yous and updates either arrive or don't, scattered across inboxes and spam folders.
The session frames all of this through Review Integrity, a five-dimension standard for running a fair, defensible review process, from what you ask applicants to how each cycle informs the next: Intake Proportionality, Rubric Clarity, Reviewer Calibration, Decision Traceability, and Loop Closure. It goes deepest on two of them: Reviewer Calibration and Decision Traceability.
1. The questions you're already hearing. Boards and leadership ask, "What did this year's giving actually do?" and "How was this one decided?" A nonprofit or student who wasn't selected asks, "Why them and not us?" And in a member-based program, someone eventually asks, "Did the committee know the winner?" Without a clear record, each of these turns into a scramble to piece together an answer.
2. What a story without proof costs. A story without proof is hard to fund and hard to defend. The first cost is the budget line: community giving competes for dollars with products that can show a number, so you need to know things like how many scholarship applicants became members and how many recipients encouraged others to apply. The second is reputation: every applicant, winner or not, walks away with an impression of how the process treated them, and a frustrating experience can cost you a member and travel by word of mouth. The third is the person running it: if the program lives in one person's head, it stalls the moment that person is out, and whoever steps in is left guessing, hunting for files, and digging through an inbox.
3. Move 1: Give every request one front door (Intake Proportionality). Move every scholarship, grant, donation request, and sponsorship application off PDFs, email, and the front desk and onto one link and one microsite, so everyone follows the same process. Screen first: ask eligibility questions at the start of the form so no one spends time on an application they can't win, and no one on staff has to sift them out later. For member scholarships or employee-child scholarships, add a member verification step, such as a member ID, so you know every applicant is eligible before review begins. Before any of that, confirm that what you ask matches what's at stake and the goals your board set for the year.
4. Move 2: Protect the committee that knows the families (Reviewer Calibration). When board members and employees review applications from their own community, hide the names. Reviewr can hide personally identifying information from judges with a click, which adds a layer of trust for applicants. Route reviewers thoughtfully, too, for example by having board members from one branch review another branch's applications. Then account for tough and easy graders with a normalization report, which treats each judge's own average as a baseline of 1.0. If one reviewer averages 7 out of 10 and another averages 9, an 8 from the first reads as above average while a 9 from the second reads as just average, so you can see which applicants score highest consistently, regardless of who reviewed them.
5. Move 3: Score every request the same way, on the record (Decision Traceability). A surprising number of programs have no scorecard at all. Use one scorecard for every reviewer looking at the same scholarship or program, with context on each criterion so reviewers know your goals and where to spend their time. Weight what matters most: if GPA should drive 30% of the decision and community involvement 10%, set those weights so the final decision reflects the priorities your board agreed on. In Reviewr, you add each question, set its points and weight, and the weighted total is calculated automatically. Give reviewers everything side by side in one tab, so they aren't downloading files or juggling windows. And keep applicants informed automatically, with incomplete-submission reminders, a thank-you page and confirmation email on submit, and a portal that shows the status of their application.
6. Move 4: Collect what happened after the award (Decision Traceability). Add an acceptance step so recipients confirm the award before funds go out, and add a supplemental form for impact reports, receipts, and thank-yous. That gives you the proof of what each award made possible, and the material to promote next year's program and draw more applicants.
7. Move 5: Tell the story with the record behind it (Loop Closure). Download your reports at the end of each cycle so the record stays in your files for years to come, and use them to see which questions worked, which created barriers, and how to make the form better. Then copy the program forward, with every question, configuration, and automation carried over, so you can improve what didn't work without rebuilding from scratch. The two patterns to avoid are never changing the program at all and starting over every year.
Reviewr is an application management platform founded in 2011 by a team who had lived through application processes that didn't work for anyone involved, from applicants to admins to judges. Today it runs scholarships, grants, awards, sponsorships, and calls for entries for credit unions, banks, community foundations, associations, and more. Applications, judging, and reporting all live in one place, and every account gets a dedicated one-on-one Reviewr team member for support.