Your Employees Want the Benefit. Your Program Is Getting in the Way.

Of the employees who qualified for your scholarship, award, or giving program last year, how many actually applied? And of those who started an application, how many finished? A program that sees 500 people start and only 250 submit has lost half its applicants somewhere along the way. That's rarely a sign employees don't want the benefit. It's usually a sign the program itself is in the way.

In this on-demand session, Reviewr walks corporate giving teams through how to make employee scholarships, awards, and giving programs easy to use, fair to every employee, and simple to run. The five-move approach starts with eligibility on the very first page, moves through the application, the scorecard, and a private review, and ends with a record of every decision. It applies to any organization running scholarships, grants, or awards, and it closes with a live demo of the applicant experience inside Reviewr.

Eligible Is Not the Same as Applying

Being eligible doesn't mean someone will apply. Research cited in the session found that 79% of college undergraduates have skipped a scholarship they were eligible for because it didn't feel worth the effort. Employee programs face the same wall, plus a few barriers of their own. The session names five places a program gets in employees' way:

• Do I even qualify? Eligibility isn't clear on the program page or at the start of the form, so employees can't tell before putting in the effort.
• It's a lot. The application asks more questions instead of the right questions, and anyone who finishes tells coworkers how long it took.
• Who sees this? An employee in financial need may not want a colleague reading about it, so they don't apply at all.
• How do they decide? Without clear criteria for every judge, decisions come down to how a reviewer feels that day.
• Did it go through? No confirmation and no visibility into status leaves applicants guessing and admins answering emails by hand.

Those barriers carry real costs. The benefit reaches fewer people than intended, and a frustrating experience can cost a program 10 to 20 applications every cycle, more for larger programs. The program picks up a "it's who you know" reputation, where employees assume the reviewer will pick a friend's kid and don't bother applying. And decisions become hard to defend: when an employee asks why they weren't chosen and there's no good answer, that costs the program them and the five other people they tell.

The session frames the fix through Review Integrity, a five-dimension framework of questions every review process should be able to answer, in the order a real program runs: Intake Proportionality (does what's asked scale to what's at stake?), Rubric Clarity (are criteria written, weighted, and visible before anyone applies?), Reviewer Calibration (are reviewers trained, conflicts enforced, and score spread measured?), Decision Traceability (can any decision be reconstructed and defended?), and Loop Closure (do declined applicants get real feedback, and does it shape the next cycle?). Each dimension moves up a four-stage ladder, from Ad hoc to Documented to Calibrated to Instrumented. This session goes deep on Intake Proportionality, Rubric Clarity, and Decision Traceability.

What We Covered

1. Move eligibility up front. Put the eligibility requirements on the first page applicants see, whether that's a microsite, a website, or the first page of the form, and follow them right away with the questions that determine eligibility. Employees who qualify move straight down the right path. Employees who don't are told immediately, on a page explaining why, instead of finishing a form they were never eligible for. That saves applicants frustration and saves admins, for whom the program is often a side responsibility handled after hours or over lunch, from sifting through ineligible submissions or answering "do I qualify?" emails.

2. Size the ask to the award. A recognition award shouldn't ask the same questions as a scholarship, and a one-time scholarship shouldn't ask the same questions as a four-year one. In Reviewr, separate programs like an award, a scholarship, and a grant can run as separate events that still live in one place for the admin. A program with several scholarships can run as one event with different pathways, so each applicant answers only what applies to them. Employees keep one account from year to year and across programs, which makes it easy for organizations running giving programs several times a year.

3. Publish how winners are chosen. Show applicants what they'll be evaluated on, on the microsite and before they apply, so they know where to focus. Judges need the same visibility so everyone shares the program's goals and values. The scorecard should only include questions that should influence the outcome, and not every question should carry the same weight. In the session's example, academic record, the top priority, carried 30% of the score, while financial need mattered but carried 15%. Reviewr's weighting tool applies those weights in a couple of clicks, so no one has to do the math by hand.

4. Make it safe to apply when coworkers review. Reviewr can redact names, addresses, and other identifying information from judges while admins keep the full application. When employees know a coworker or a friend's parent won't see who they are, they're more willing to apply and to put forward their strongest, most honest application.

5. Keep the record and keep employees informed. Reports are available at any point: while testing before any real submissions, halfway through a cycle, or at the end, and they can be re-downloaded a year later from the same event. Every submission stays tied to its evaluation, comments, and notes, so any decision can be revisited and defended. The same reports show which questions drew strong responses and which were poorly answered or could be cut, so next year's program gets better.

The session closed the slides with a self-check across Intake Proportionality, Rubric Clarity, and Decision Traceability. If the program grew by 100 applicants, could you handle it alone? If you were gone for a month with no notice, could someone else take over? Do judges know exactly what the program's goals are? And could you find why a recipient was chosen in under five minutes, with an answer you could defend?

What the Live Demo Showed

• Secure accounts. Applicants, judges, and admins each create an account in Reviewr, which is SOC 2 compliant, so employee information stays secure.
• Saved progress and autofill. Progress saves page by page, with a save-and-log-out button on every page, and account details fill into the form automatically. Applicants who can't finish in one sitting log back in and pick up where they left off, which is where the biggest gains from started to completed submissions come from. Judges get the same ability during evaluations.
• Automated communication. Incomplete-submission reminders, submission confirmation emails with a results timeline, and a status view when applicants log in replace manual follow-up.
• Question types that validate. Phone, email, and other question types only accept valid entries and produce clean, easy-to-read reports.
• Eligibility and matching. Eligibility questions route qualified applicants to the programs they can apply for and stop ineligible applicants with a clear message, so each person answers only the questions that apply to them.
• Letter of recommendation invites. Instead of applicants uploading letters themselves, references receive an email invite when the application is submitted, open the form without creating a password, and submit directly, so the letter comes from the person requested.

The Recap: Old Way vs. New Way

• Eligibility: Instead of employees guessing whether they qualify and finding out after a full application, eligibility is clear on the first page and the form tells them in the first minute.
• Application: Instead of one long form for every award, each scholarship, grant, and award asks only what matters for it, with one account across programs and years.
• Criteria: Instead of judges deciding based on how they feel that day, applicants and judges see the same weighted criteria, and totals are calculated automatically.
• Privacy: Instead of employees holding back because a coworker will read their application, identifying details are redacted from judges while admins keep the full record.
• Communication: Instead of manual "did you get it?" emails, reminders, confirmations, and status updates go out automatically.
• Decisions: Instead of searching an inbox for why someone won, every evaluation, comment, and report is tied to the submission and ready to defend, and reports shape next year's program.

About Reviewr

Reviewr is an application management platform founded in 2011 by a team that had been through application processes that didn't work for anyone involved: not the admins, not the judges, and not the applicants. It has since run thousands of programs, including scholarships, grants, awards, competitions, and calls for entries, for organizations including community foundations, associations, banks, credit unions, K-12 foundations, and YMCAs. Applications, judging, communication, and reporting all live in one place, and every account gets a dedicated one-on-one Reviewr team member for support.

‍