Most scholarship committees agree that reviewers should score the student, not the name. Getting there is the hard part. At many programs, blind review means one or two staff members blacking out names, schools, hometowns, and parents' employers page by page in the middle of the deadline crunch, then keeping track of whose application is whose until results are final. Other programs skip it entirely and hope a committee that knows many of the applicants stays neutral.
In this on-demand session, Reviewr shows scholarship programs how to build blind review into the application itself, so it works without a marker and a long weekend. It works through two sets of moves: building it into the form by collecting identifying details in their own hidden fields, telling students what to leave out of essays and uploads, and giving reviewers the facts instead of the transcript; and keeping scoring fair with the same weighted rubric for every application and a check on harsh and easy reviewers. The session is built for scholarship programs, but the same moves apply to grants, awards, competitions, and any other application-based program. It closes with a live demo of the judging experience inside Reviewr and a Q&A on letters of reference, fixing names that slip through, and programs where every applicant attends the same school.
The session opens with research on blind review: in one experiment, 245 reviewers were randomly assigned to see authors' names or not, and in another, 657 submissions to an academic conference were scored both ways. Hiding names narrowed the gap between students and senior applicants and between less prestigious and more prestigious schools, and the blind scores predicted later success just as well. In other words, hiding names changed who got ahead without hurting accuracy.
Most committees, though, still rely on one of two approaches:
Even careful hand redaction leaks, because blind review by hand is only as blind as the last page checked. An essay that cheers "Go Wildcats" gives away the school. A reference letter on school letterhead or sent from a school email does the same. Transcripts print the school name at the top of every page. And a last name or a story the committee recognizes from town gives away the applicant entirely.
The session illustrates the cost with an example: two days before the committee meeting, staff finish redacting 120 applications by hand. During the meeting, a reviewer recognizes a volleyball story in one essay, and now every score on that application is in question, whether the student wins or not. The hours spent redacting didn't buy what they were supposed to. Blind review by hand costs in three ways:
Blind review gets decided when the application is built, not when applications arrive. Where names are collected, how pages are organized, and what students are told to leave out of their essays are all choices made while the form is being designed. Many programs plan in the fall and build their forms ahead of a January launch, right in the middle of the holiday season. Once applications start arriving, it's too late to change the form.
The session frames the fix through Review Integrity, five questions every scholarship, grant, or award program should be able to answer with confidence, 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. Collect identifying details in their own fields, and hide them (Reviewer Calibration). Ask for name, school, hometown, and other identifying details as separate form fields, ideally grouped on a single applicant profile page. In Reviewr, a visibility condition hides that whole page from reviewers in one step. Admins and applicants still see everything; in the judge view, the hidden fields don't appear at all, as though they were never on the form. No one has to decide what to black out across four pages.
2. Tell students what to leave out of essays and uploads (Intake Proportionality). Stories are often what decides a scholarship, so keep the essays. Add clear instructions at every essay prompt and upload: no name, no school, no hometown, and refer to yourself as "the applicant." Students still get to show who they are, and staff have one less thing to catch later.
3. Give reviewers the facts, not the transcript, and review by ID (Reviewer Calibration). Ask for GPA, class rank, and credits as form fields instead of relying on a transcript upload. Those numbers are usually easier for students to provide than a full transcript, and there's nothing to redact and re-upload. Programs that need transcripts for verification can still collect them as attachments hidden from reviewers. Reviewers see an applicant ID on every application they score, never a name.
4. Score every application on the same weighted rubric (Rubric Clarity). Once the rubric holds only the questions that matter, weight them to match the program's priorities. A scholarship that values community involvement most might weight it at 30% and GPA at 10%, so GPA still counts without driving the decision. Many programs already weight criteria but do the math by hand in another tool; in Reviewr, admins assign point values and weights while building the scorecard, and the calculation is automatic and tied to the application.
5. Account for harsh and easy reviewers (Reviewer Calibration). Reviewr's normalization report sets a baseline for each reviewer from the average score they gave across their assigned submissions. Scores above that baseline read as above average (1.1, 1.2) and scores below it read as below average (0.9, 0.8), so the results show which applicants scored well across reviewers rather than which ones drew an easy grader.
A five-question self-check before your application opens. Are names, schools, and hometowns collected in their own fields? Are those fields hidden from reviewers without anyone redacting by hand? Do essay prompts and uploads tell students what to leave out? Is every application scored on the same weighted rubric, shared in advance? Do you check reviewers' scores against each other before results are final?
Common questions. Reviewr doesn't black out names inside essays, but it can hide entire form fields, and clear instructions keep identifying details out of essays and uploads. Reviewr is SOC 2 Type 2 compliant and supports single sign-on, so student data stays secure. Programs running only a few scholarships benefit most, since small community committees are even more likely to know the applicants. Setup typically takes about 30 days, but the timeline is up to you, and Reviewr can be fully self-serve.
Questions from the live session.
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 small business stays open, so Reviewr was built to give applicants the best shot at funding and help admins choose the best recipients every time. Reviewr 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.