Why Did Your Credit Union Fund That?

Sooner or later, someone asks why your credit union funded one request and not another. At many credit unions, the honest answer is hard to give: requests arrived by email, at the branch counter, and on someone's desk; a committee that knows the applicants talked it over; and the scores, notes, and final call ended up in a spreadsheet only one person can open.

In this on-demand session, Reviewr shows credit unions how to run community giving, including grants, scholarships, sponsorships, and donation requests, so every decision comes with a clear record and fair scoring behind it. It works through two sets of moves: building a clear record by taking every request through one link, screening out what you don't fund, routing requests to the right reviewers, keeping every giving season in one record, and answering the CFO's question with post-award reporting; and keeping scoring fair by hiding names from a committee that knows the applicants, scoring every request against the same weighted rubric, and accounting for tough and easy reviewers. The session is built for credit unions, but the same moves apply to any foundation, association, or organization running application-based programs. It closes with a live demo of the applicant experience inside Reviewr.

How Community Giving Usually Runs

The session describes four patterns that show up at many credit unions:

• Requests arrive everywhere. Email, the branch counter, a desk, the mail. They come from every direction and are hard to keep organized.
• One person with another job. Whoever runs the program usually works in marketing, community development, or the foundation, and fits giving in after work, over lunch, and wherever there's time.
• A committee that knows the applicants. Employees and board members often know the families and organizations applying. Even with the best intentions, that familiarity creates bias in the scoring.
• Decisions end in a spreadsheet. Scores, notes, and the final call sit in a file under one person's account, which is hard for anyone else to read and harder to defend.

Then the same question arrives from five people. A declined nonprofit wants to know why someone else was chosen. A parent wants to know why their student didn't win. Board members ask how the decision was made, auditors ask to see the process, and the chief financial officer asks what the giving returns. Each is a fair question, and each is inevitable. The hard part is having the answer in one place.

Without a clear record, that costs the program in three ways:

• Goodwill becomes something you have to defend. At a credit union, the declined nonprofit and the student who didn't win are members and neighbors. Not everyone can win, but a defensible process shows them exactly why they weren't chosen, with no gray area about whether it was fair.
• Uneven scores stay hidden. One tough reviewer or one pushed-through request rarely shows up in a spreadsheet.
• The budget gets questioned. A list of checks written doesn't show what the giving returned, and without follow-up information, the CFO is left asking what the credit union is getting out of it.

Why Now

A giving budget is set once a year, and whatever process is in place carries over with it. By this point in the year, most credit unions have built their budgets, held their planning meetings, and received board approval. Programs aiming to go live on January 1 are now finalizing their submission forms. If the process isn't updated now, next year's money is spent through whatever process carried over by default.

The Standard: Review Integrity

The session frames the fix through Review Integrity, five questions every giving process should be able to answer, in the order a real program runs:

• Intake Proportionality: Does what you ask scale to what's at stake? Many credit unions run several scholarships and grants at different funding levels. Larger awards warrant more in-depth questions, and every question should earn its place by informing the decision.
• Rubric Clarity: Are criteria written, weighted, and visible? The scorecard should be built alongside the application so the two go hand in hand, aligned with each program's goals and desired outcomes. Once every question is confirmed to matter, each is weighted: some carry enough weight to make or break a decision, and others inform the total without deciding it.
• Reviewer Calibration: Is every request scored the same way by people without a conflict? Reviewers need at least a short version of the board's goals and desired outcomes so everyone scores with the same end in mind, and identifying information can be redacted.
• Decision Traceability: Can any decision be reconstructed and defended with more than "that's what the committee decided"? That means scores tied to the application, the scorecard's weights, reviewers' comments, and the reports to back them up.
• Loop Closure: Does each year build on the last? Instead of rebuilding from scratch, keep what worked, remove the questions that created barriers, and lean into the ones that drew the strongest responses.

Each dimension moves up a four-stage ladder, from Ad hoc to Documented to Calibrated to Instrumented.

What We Covered

1. Take every request through one link (Intake Proportionality). Run every grant, scholarship, and request in one place. Many credit union programs see the same applicants year after year, and a familiar process keeps them coming back: they log in to an account they already have, receive automated updates on where they stand, and know what the post-award follow-up looks like.

2. Screen out what you don't fund, and verify membership. Put eligibility and criteria questions at the start of the form. Eligible applicants continue, and ineligible applicants are stopped before they spend time on a request you can't fund, so no one on staff has to sort them out later. For member-only grants and scholarships, add a membership step before eligibility, with a member ID, so membership is on file from the start.

3. Route each request to the right reviewers (Reviewer Calibration). Some reviewers are best suited to scholarships, others to grants, and others to a specific community focus area. Put reviewers in the right groups and auto-group submissions so each request reaches the people best equipped to score it. Assignment can also be automated, whether by assigning all submissions in a group or by random assignment.

4. Keep every giving season in one record (Decision Traceability). The request, eligibility answers, reviewers, scores, comments, and final decision all stay together, year after year. There's no pulling everything into a spreadsheet or a new PDF, and when a decision needs defending or a past year's application needs pulling up, it's already there.

5. Answer the CFO's question: what did the giving do? (Loop Closure) Automated supplemental forms collect acceptance, impact reports, receipts, and enrollment proof directly from recipients. That gives the board and CFO real answers submitted by the people the program funded. Impact reports can also be shared publicly, showing members and the community what the funds accomplished, which brings more people into the membership and the program.

6. Hide the names when your committee knows the applicants (Reviewer Calibration). When board members or employees score applications from members they know, redact identifying information. Staff keep the full profile, while the committee sees only what's required for scoring. That reduces bias and makes the decision easier to defend.

7. Score every request against the same weighted rubric (Rubric Clarity). Every event judged in Reviewr has a scorecard, so every reviewer scores with the same questions and the same weights. That rubric can be shown to the committee, or to a parent, as the record of how an applicant was scored. Reviewers work with the submission on the left and the scorecard on the right, so answers are easy to find.

8. Account for tough and easy reviewers. Every committee has tough graders and easy graders. Reviewr's normalization report treats each reviewer's own average as a baseline of 1.0. If one reviewer's average is 6 and another's is 8 across the same submissions, a 7 from the first reads as above average while a 7 from the second reads as below. Applicants are compared on the same footing, regardless of who scored them.

The same question, two ways. "Why did you sponsor them and not us?" Without a record, the request came in by email to a branch, two people discussed it in a hallway, nobody remembers the other requests, and the answer is "the committee liked the other one." With a record, both requests came through the same link, both were scored on the same rubric, the reason is in a comment, and the answer is "Here's how we decided."

A five-question self-check. Does every request come in through the same place? Do reviewers score against the same weighted rubric, or is there a rubric at all? Can you hide names from a committee that knows the applicants? Could you show why any gift this year was approved? Could you show your CFO what last year's giving accomplished?

Common questions. Reviewr is SOC 2 Type 2 compliant, supports single sign-on, and your data is yours to export. Reviewr doesn't send payments, so credit unions keep using their current payment process. Even a credit union running only a few scholarships benefits from running everything one consistent way. Setup averages about 30 days, but the timeline is up to you, and programs that need to launch quickly can go live in about a week.

What the Live Demo Showed

• Accounts with saved progress. Every applicant creates an account, which supports Reviewr's SOC 2 compliance and saves progress automatically as applicants move through each page.
• A clean profile page. Name, address, email, and phone use dedicated question types, so applicants get a clear format, admins get a clean report, and invalid email addresses, phone numbers, and addresses are flagged before applicants can continue.
• The eligibility and matching tool. A short series of questions determines whether an applicant is eligible. Ineligible applicants can't continue, and eligible applicants see exactly which scholarships they qualify for, then choose a path with only the questions that apply to them.
• Flexible questions and files. Essay and short-answer prompts show what a scholarship form can look like, and more than 130 file types are supported, so applicants don't have to convert files.
• References that submit directly. Applicants enter each recommender's name and email. On submission, the recommender gets an invite, uploads the letter directly, and the system sends the reminders, with every letter connected to the original application.

The Recap: Old Way vs. New Way

• Intake: Instead of requests arriving by email, at the branch counter, and on someone's desk, every request comes through one link, with a familiar process for repeat applicants.
• Eligibility: Instead of sorting requests by hand, eligibility and membership are checked at the start of the form.
• Reviewers: Instead of whoever is available, each request is routed to the reviewers best suited to score it.
• Bias: Instead of a committee scoring people it knows, identifying information is hidden and every reviewer uses the same weighted rubric.
• Score fairness: Instead of tough and easy graders going unnoticed, a normalization report puts every applicant on the same footing.
• Decisions: Instead of "the committee liked the other one," every score, comment, and reason is tied to the request and kept year after year.
• Results: Instead of a list of checks, acceptance forms, impact reports, receipts, and enrollment proof show the board and CFO what the giving accomplished.

About Reviewr

Reviewr is an application management platform founded in 2011 by a team that had been part of application processes that didn't work well for applicants, judges, or admins. Scholarships, grants, and awards can decide whether someone goes to college or whether a business stays open, so Reviewr was built to create a confident, defensible process where everyone can put their best foot forward. It works with many credit unions, keeps releasing new features and enhancements, and gives every account a dedicated one-on-one Reviewr team member for support.

‍