Most of the hours spent running a scholarship program have nothing to do with awarding a single scholarship. In this recorded session, Reviewr's Holly walks through exactly where those hours go — not in the few weeks it takes to actually run the program, but in everything that happens around it, year-round: rebuilding the application from scratch, answering the same applicant questions one at a time, reconciling reviewer scores that never had a shared standard to begin with, chasing status updates and outcomes after the fact, and pulling together leadership reports from spreadsheets that were never built to talk to each other.
The session opens with a bit of background on why Reviewr exists in the first place: it was founded by people who had personally sat on the applicant, judge, and admin sides of application-based programs, and saw the same disconnect from every angle — a process that wasn't built to work well for anyone involved. That's the lens the rest of the session runs through: not just adding features, but removing the invisible work a scholarship program accumulates every year without anyone noticing.
None of that invisible work shows up on a budget line. A scholarship cycle itself might run a month, sometimes less — but the work leading up to it, the ideas jotted down over months, the follow-up after it closes, adds up to nearly the whole year. It just quietly adds hours to a program that was supposed to take a few weeks to run, and because no one else sees that work, it rarely gets accounted for when it's time to evaluate what the program actually costs. The session makes the case directly: if a program is currently run on a free Word document, Google Doc, or Google Form, the sticker price may be zero, but the hours an admin spends compensating for what that tool can't do are not free — they're time pulled away from everything else on that person's plate, and they're the real cost most programs never measure.
This session breaks that down stage by stage, and walks through what changes when the process is built to prevent the waste instead of just absorbing it:
The session includes a direct recap of what's actually changing, stage by stage: instead of rebuilding an application from scratch every cycle (or never updating it at all), programs copy last year's workflow forward and improve on it. Instead of applicants emailing basic questions one at a time, chat and saved progress answer them with no email required. Instead of reviewer scores that "feel right in the moment" with no real backing, structured scorecards speed up review without adding judge fatigue. Instead of manually notifying every applicant and chasing outcomes for months, status updates and outcome collection run automatically, with no chasing required. And instead of pulling data from five disconnected spreadsheets, everything is already in one place and ready in minutes.
The key takeaway threaded through the whole session: every hour a program saves is an hour that comes back to the team running it, which is why the return on investment for a scholarship program run through Reviewr tends to run well past what most admins budget for going in. And saved time is only half the story — every improvement that makes the process better for applicants, admins, and judges reinforces the next: a good applicant experience and a good judging experience both feed into a program that grows its numbers year over year, and more applicants, more community awareness, and more funding all move together. Lower cost and lower time spent translate directly into higher participation, not a tradeoff between the two.
The session closes with a live walkthrough of the Reviewr platform itself — the applicant experience from account creation through submission, including the built-in eligibility and scholarship-matching tool for programs running multiple scholarships in a single cycle, so applicants only see and answer the questions relevant to what they actually qualify for. It covers how reference collection and ranking works (references are invited directly into the system rather than relying on an uploaded letter, and a program can weight a reference's ranking rather than relying on writing quality alone, since a stronger writer isn't necessarily a stronger recipient), and a full look at the judging portal, including blind review with personally identifying information redacted on request, range-based scorecards built around emotional-response language instead of raw numbers, and how judges see exactly what's assigned to them, what's scored, and what's left — all without juggling multiple tabs or files.