Most awards programs are stuck on a seesaw.
Push for more nominations and the review committee drowns. Protect the committee and participation flatlines. Either way, someone loses — usually the volunteers, and eventually the nominees who deserved a fair look.
But participation and volunteer capacity were never actually a trade-off. They're two outputs of the same thing: how the workflow is designed.
This article walks through a full awards workflow from start to finish, using the University of Tennessee Alumni Association's program as the working example. It's drawn from a live session we ran with association and nonprofit awards teams, and it covers the seven decisions that determine whether your program grows or stalls.
You can apply most of this with or without award management software. The point isn't the tooling — it's the design.
#1
Decision: Award category design
The common approach: A handful of prestige awards most members can't qualify for
The modern approach: Categories built so every member segment has a home
#2
Decision: Nomination structure
The common approach: One-dimensional — nominator does everything, or self-nomination only
The modern approach: Parallel nominator and nominee workflows
#3
Decision: Reviewer workload
The common approach: Whatever the pile happens to be
The modern approach: A ratio you set, based on real fatigue thresholds
#4
Decision: Committee structure
The common approach: One committee reads every nomination in every category
The modern approach: Groups scoped by category and sized from the ratio
#5
Decision: Evaluation
The common approach: No formal scoring, or a 30-question weighted rubric
The modern approach: Low-barrier quantitative scoring that tabulates itself
#6
Decision: AI
The common approach: Not used, or used to make decisions
The modern approach: Used to orient reviewers faster — never to score or select
#7
Decision: Results
The common approach: Raw averages across reviewers who score differently
The modern approach: Normalized against each reviewer's own tendency
Every association we talk to says the same thing: we want more nominations. Almost every one of them starts by trying to market their way there.
The problem usually isn't the marketing. It's that most of their membership isn't eligible for anything.
Look at a typical awards lineup. There's a lifetime achievement award. Maybe a hall of fame. Both are prestigious, both are meaningful — and both are realistically available to a tiny fraction of the membership. If only five percent of your members have a plausible path to any award you offer, declining participation isn't a mystery. It's arithmetic.
So before you touch a nomination form or write a single promotional email, ask a harder question: does every segment of our membership have somewhere to go?
Some categories that tend to fill the gaps:
There's a compounding benefit here that's easy to miss. Recognizing a member early creates a documented engagement touchpoint that follows them for the rest of their membership. A 40 Under 40 honoree at 32 is a plausible board candidate at 45. The award category is the on-ramp.
Practically, this means your awards program management setup needs to handle multiple categories cleanly — each with its own eligibility criteria and its own required fields, so a nomination lands in the right place with the right information attached rather than being manually re-sorted after the fact.
This is the single biggest change most programs can make, and it's the one that moves participation.
Most nomination structures are one-dimensional. Either the nominator does everything on behalf of the nominee, or the program accepts self-nominations. Both have real problems.
When the nominator does everything: you're asking a volunteer to write someone else's biography. They don't have the résumé. They don't know the exact titles or dates. They're guessing at accomplishments. So one of two things happens — they submit something thin, or they abandon the nomination entirely. A highly qualified candidate goes unnominated because the form was too much work for the person who wanted to nominate them. That isn't fair to the nominee.
When you accept self-nominations alongside peer nominations: you can't compare them. A self-nominee will almost always submit stronger material, because nobody knows more about a person than that person. You end up ranking two fundamentally different kinds of submission against each other and calling it a competition.
There's also a practical reality that undercuts the usual objection. The most common reason programs keep the nominator-does-everything model is to preserve the surprise. But in practice, nominators frequently go to the nominee anyway to get the information they need. The surprise is already gone — you've just made the process harder without preserving the thing you were protecting.
The University of Tennessee runs both models side by side, which makes it a useful example.
Their Volunteer 40 Under 40 uses parallel workflows:
Their Rocky Top award keeps the traditional model, where the nominator completes everything and the nominee is never involved. Both are legitimate. The point is that the choice should be deliberate, not inherited.
That last point deserves more attention than it usually gets. Once nominations and applications are separate stages, you can see exactly where people stall: nominations started but not submitted, nominees notified but not yet applied, applications in progress but incomplete. Each of those is an automated reminder waiting to happen — and reminders sent to the right segment at the right stage recover submissions that would otherwise be lost.
If your nomination management software can't show you that funnel in real time, you're marketing blind.
One useful variation: some organizations don't auto-notify nominees. Their staff vets incoming nominations first, then invites a filtered set to apply. This costs you a step but gives you control over who enters the pipeline.
Here's where most programs run into trouble. You've just made it dramatically easier to nominate someone. Volume goes up. Now what?
We analyzed well over a million submissions processed on our platform to answer two questions, and the answers should shape how you structure review.
That's roughly where a volunteer reviewer's capacity ends.
The important finding isn't when fatigue sets in — it's what happens after. Once a reviewer pushes past about 40 submissions, submissions 40 through 60 get scored on a materially different scale than submissions 1 through 30. The reviewer either starts rushing and compressing their scores, or they begin comparing later entries against the accumulated context of everything they've already read — an advantage the first thirty never had.
That's not a reviewer problem. It's a workload design problem, and the nominees pay for it.
Two mitigations:
Fewer than three reviews per nomination doesn't produce enough data to make an informed decision. More than five hits diminishing returns fast — a nomination reviewed twenty times lands at essentially the same average it had at five.
Nominations × reviews-per-nomination ÷ reviewers = the load each volunteer carries.
Set your coverage at five reviews per nomination, hold every reviewer under 40, and the equation tells you how many reviewers you actually need to recruit. Workload stops being something you discover in week three and becomes a number you set in advance.
Run your own numbers before your next cycle. A lot of programs find they don't need every reviewer to read everything — they've just never questioned the assumption.
Once you know how many reviewers you need, the question becomes which reviewers see what. There are three structures worth knowing, and they combine well.
Category-based groups. Instead of one committee reading everything, build a group per award category. Nominations route into their category bucket automatically, and each committee only ever sees its own. In UT's setup, one group handles the Distinguished category while another handles Achievement — and neither reviewer ever opens a nomination outside their scope.
This has a recruiting benefit that's easy to underestimate. "Review twelve nominations in your field" is a far easier ask than "join the awards committee." It's also the ask that gets a yes from busy members, which means your reviewer pool grows — which improves the ratio.
Phased review. Round one is a broad screen: thumbs up or thumbs down, is this worth advancing? Reviewers can handle more than forty submissions when the task is that light. The full scoring rubric only comes out in round two, against a much smaller field. Many programs then bring the whole committee together for a final cross-category round.
Automated assignment with caps. Set your rules — every nomination reviewed exactly five times, no reviewer assigned more than 35 — and let the system distribute assignments randomly and evenly across the committee. No spreadsheet, no reviewer drawing the short straw.
Most mature programs use some combination: categorize, phase, then auto-assign within each phase.
Awards programs tend to fail evaluation in one of two opposite directions.
Too loose: no formal scoring at all. The committee gets together, talks through the nominations, and picks favorites. It feels collaborative, but the outcome depends heavily on who spoke first and who spoke loudest — and there's no record to point to when someone asks how the decision was made.
Too heavy: a thirty-question weighted rubric where reviewers agonize over whether a nomination is a 16 or a 17. The committee gets bogged down in the mechanics of scoring instead of the substance of the nomination, and at volume those meaningless one-point distinctions genuinely move the averages.
A workable review process needs four things:
A split-screen review layout — nomination packet on one side, scorecard on the other — sounds like a minor convenience. Run the numbers. Save two to four minutes per review, across twenty reviewers looking at a hundred submissions each, and you've saved your volunteers well over a hundred hours. That time comes directly out of the fatigue budget.
Blind review belongs here too. If you want evaluation on merit rather than name recognition, redact names and identifying details before reviewers ever see a nomination. This was one of the original problems that led us to build Reviewr — watching a review process drift toward a popularity contest because personal information that could have been redacted wasn't.
Instead of asking reviewers to score on a 1–15 or 1–20 scale, use a short qualitative scale with clear anchors — Below Expectation through Outstanding.
Three reasons this works better:
The output is a live leaderboard: every nomination, who reviewed it, individual scores, totals, and averages — available before the deliberation meeting rather than assembled during it.
Two AI applications genuinely help awards programs. Neither one scores or selects.
Smart summaries. AI reads everything a nominee submitted — nomination form, application, file uploads — and produces a one-page review brief. For most programs, that brief carries enough substance for a first-pass screen. Reviewers who advance a nomination then open the complete packet for full evaluation. The full submission is always one click away; the summary never replaces it.
Scorecard alignment. This one is less obvious and arguably more useful. Say a rubric criterion is "clarity of proposal." The evidence a reviewer needs might be spread across two form fields and three file uploads. Rather than making the reviewer hunt through everything, remember what they found, and map it back to the criterion, AI locates the relevant submitted content and surfaces it alongside that criterion.
Note what this is not: it's not summarizing, interpreting, or evaluating. It's restructuring content the nominee already submitted so it lines up with how you're scoring. The words are the nominee's own.
Reviewers toggle between the AI-assisted view and the full submission at any time.
The guardrail is absolute. AI assists; humans decide. It never scores a nomination and it never selects a winner. Its only job is making your volunteers' limited time go further — which, for a program with high volume and a small staff, can be the difference between a defensible process and a rushed one.
This is the stage most programs skip, and it's the one that quietly determines outcomes.
Once you're distributing nominations across reviewers — which is what the fatigue math requires — not every nominee is evaluated by the same people. That creates a problem nobody sees on the leaderboard.
Reviewers score on different personal scales. Suppose one reviewer averages 10 and another averages 30. On paper that looks like a twenty-point gap, and any nominee assigned to the first reviewer appears to be at a twenty-point disadvantage.
But a 10 from the first reviewer and a 30 from the second are the same score. They're each that reviewer's own baseline. The gap is an artifact of scoring tendency, not a judgment about the nominees.
A normalization report fixes this. It calculates each committee member's individual average, then evaluates every nomination against that reviewer's own tendency rather than against the group. Scored above your baseline? That's a strong review. Below it? That's a weak one — regardless of the raw number.
The system then produces a normalized leaderboard. Run your top ten against a traditional average and against a normalized one, and the lists will differ. That difference is the set of nominees who were being advantaged or disadvantaged by which reviewer they happened to draw.
There's a second benefit worth noting. Because normalization surfaces each reviewer's pattern, unusual scoring behavior becomes visible. If a committee member has a close relationship with a nominee or a clear favorite, it stands out against their own baseline in a way it never would in a group average.
If your program distributes nominations across reviewers rather than having everyone review everything, normalization isn't optional. It's what makes the results defensible.
And defensibility is retention. Nominees who lose to a transparent process stay engaged. Nominees who suspect the draw decided it don't come back — and neither do the people who nominated them.
Read the seven decisions in order and the logic is cumulative:
Category design determines who can participate. Dual nomination workflows determine how many actually do. The fatigue ratio determines how much review capacity that volume requires. Committee structure determines who supplies it. Low-barrier evaluation determines how fast they get through it. AI extends their time. Normalization makes the outcome fair.
Change one in isolation and you'll feel the seesaw again. Change them in sequence and participation and volunteer capacity move in the same direction — because they were always the same system.
What is award management software? Award management software handles the full lifecycle of a recognition or awards program: collecting nominations and applications, screening eligibility, assigning nominations to review committees, capturing scores against a rubric, and producing ranked results for selection. It replaces the combination of forms, email, shared drives, and spreadsheets most programs run on.
How many nominations should each reviewer evaluate? Roughly 30–40 per sitting. Beyond that, scoring consistency degrades measurably — later submissions get evaluated on a different scale than earlier ones.
How many times should each nomination be reviewed? Three to five. Fewer than three doesn't give you enough data to decide; more than five produces almost no change in the resulting average.
Should we allow self-nominations? Not mixed in with peer nominations under the same form — the quality gap makes them impossible to compare fairly. Either run a dual nominator-and-nominee workflow so every entry has substantive content from the nominee, or route self-nominations to a complete application while keeping peer nominations minimal.
Does AI decide who wins? No. In a well-designed program, AI summarizes and organizes submitted content so reviewers can work faster. Scoring and selection stay entirely with your committee.
What is score normalization in awards judging? Normalization adjusts for the fact that reviewers score on different personal scales. Rather than comparing raw scores across reviewers, it evaluates each nomination against the scoring tendency of the specific reviewers who saw it — so a nominee's outcome reflects their nomination rather than which reviewer they were assigned.
Reviewr is purpose-built software for application-based programs — recognition and member awards, scholarships, grants, board nominations, volunteer committee applications, calls for speakers, fellowships, and competitions. Anything that requires collecting submissions and running them through a formal review, scoring, and selection process.
We've been building for this since 2011, we're SOC 2 Type II certified, and we've processed more than a million applications across thousands of organizations.
The name isn't an accident. Our team came out of serving on review committees for programs like these — the paper binders, then the email-and-spreadsheet era. We felt the volunteer fatigue firsthand, and more importantly we watched what it did to applicants: scoring that drifted, materials that got lost, identifying information that should have been redacted and wasn't.
That's why the platform exists, and it's why the numbers in this article come from our own data rather than a general-purpose research report.
The all-in-one platform for managing scholarships, grants and awards programs.
