Many associations run a full portfolio of awards: an Emerging Leader award, a lifetime achievement award, scholarships, grants, and competitions, each built at a different time by a different person. Over the years, that turns into 15 awards with 15 separate setups: different forms, different scorecards, different judging routines, and records spread across inboxes, folders, and spreadsheets. It works as long as the one person who knows how it all fits together is at their desk. When that person is out mid-cycle, or moves to a new role, the program waits, or someone starts digging through old emails.
In this on-demand session, Reviewr shows associations how to let every award keep its own look, questions, and committee while one process and one record sit behind all of them. It covers where separate setups break down, why the fall is when to fix it, and how to build a portfolio that anyone on the team can run and explain. The session is built for associations, but the same approach applies to community foundations, small teams, and anyone running several scholarships, grants, awards, or competitions at once. It closes with a live demo of the admin experience and a Q&A on nominee notifications.
The session opened with a poll: if the person who runs your awards were out for a month mid-cycle, what would happen? Would everything wait until they came back? Would someone have to dig through their inbox and folders? Would each award be handled differently, making it harder to pick up? Or could anyone on the team step in, because it's all in one place?
For most associations, that question lands close to home. As presented in November 2026, more than half of associations describe themselves as understaffed, and many award programs are run by one or two people. Award portfolios rarely shrink to match, and they shouldn't: awards are one of the most visible benefits members get. The relief has to come from the process instead, through automation and a setup that more than one person can work in.
That's hard to do with 15 awards and 15 setups. Many of those awards share the same timeline and ask the same base questions, and often many of the same in-depth ones, with only a few award-specific questions. When that's the case, they can run as one event: applicants answer a set of matching questions and are routed to the award they're applying for, while reports, questions, scorecards, and results stay in one place, still divided by category so each award stays organized and separate.
The session named four places where separate setups show up, and what fixes each:
What you set up this fall is what you'll have to explain next year. September and October are when most associations meet with their board, leadership, and budget staff to approve the budget, decide which awards to offer, and review what worked last year. By mid-November, those decisions are mostly made, and November and December are when they become a working process: setting up each award, building applications, updating scoring, and getting judges into the system. Nominations typically open around January 1. With the holiday season starting, the days in the office to make those changes go quickly, which is why the setup needs to be easy enough that the time goes to the work that matters: better application forms, better scorecards, and a low-barrier experience for applicants.
The session frames the work through Review Integrity, five questions every awards, scholarship, or grant program should be able to answer with confidence, whatever platform it runs on, 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. One portal, and every award keeps its own look (Intake Proportionality). Awards run as one event share one microsite and one link; awards run separately each get their own. Programs can also skip the microsite and link straight to the login page. Either way, the portal can carry the association's colors and logo, so applicants know they're applying for their association's award. Applicants can save and log out at any point, and completed pages save as they move through the form, even if they leave by accident. That one feature makes applicants much more likely to come back and submit.
2. Ask each nominee only what their award needs (Intake Proportionality). For associations offering several awards through one submission form, conditional logic sends each applicant down the path for the award they chose. They see and answer only the questions that apply to them, while everything stays organized in one place for the admin.
3. Check membership and eligibility once, the same way everywhere (Intake Proportionality). The first page of the application holds the eligibility questions. Eligible applicants continue, and ineligible ones are told so and asked to leave the form. Membership works the same way: applicants confirm they're members or enter a member ID, and non-members can't continue. The system handles the check, so the admin doesn't have to verify each entry by hand.
4. Every entry goes to the right committee, with its own scorecard (Rubric Clarity, Reviewer Calibration). Whether awards run in one event or several, each award should have its own scorecard, so judges compare apples to apples, with questions that match what's actually in that award's form. Entries are routed by award category, and each committee sees only its category and the entries assigned to it.
5. Every application, score, and decision for every award in one place (Decision Traceability). Applicants create their submission and profile, judges complete their assignments, and the evaluation form, score, and judges' comments are tied directly to that one application. When a board, donors, or leadership ask how a decision was made, the answer and every deciding factor are in one place.
6. Start next year's awards from this year's (Loop Closure). Instead of rebuilding each award every year, the whole event copies over: every automation, configuration, email, question, and scorecard. The admin updates dates, deadlines, and emails, and spends the rest of the time improving the questions and scorecard based on last year's results.
The same question, two ways. "How was this year's Emerging Leader chosen?" With 15 setups: the staffer who ran it is on leave, the scores are in a spreadsheet somewhere, the judges' notes went by email, and the answer is "Let me get back to you." With one record: anyone on the team can open the award, every judge's scores are on record, comments sit with every score, and the answer is "Here's how she was scored."
A five-question self-check for your award portfolio. Can your members find every award in one place? Does your smallest award ask for less than your biggest? Do judges use the same scoring view for every award? Could someone else explain how any winner was chosen? Could a new award start from one you've already built?
Common questions. Do all of your awards have to match? No. Every form, award, page, and question can be customized, and a dedicated Reviewr team member can advise on what has worked for other programs. Does it connect to your AMS? Not with a live sync, but membership can be verified on the form, SSO is available, and all results can be exported. Can judges be volunteers? Yes, as they are in almost every awards program. Judges see only their assigned entries and the scorecard. How long does setup take? Typically about 30 days, and because Reviewr is self-serve, programs can go live sooner or take more time as their timeline allows.
An attendee whose association already runs its awards in Reviewr asked how to notify people that they've been nominated and let them review and correct their information, since nominators often know only part of a nominee's record. The answer was the nominator-nominee process: the main form handles both self-nominations and nominations of someone else, and is kept short. When a nominator submits, the nominee is invited by email to a supplemental nominee application, where they fill in the bulk of the information themselves, such as a current resume and accomplishments. That invitation is also how nominees learn they've been nominated. Programs that don't want nominees to complete a full application can use the same step to collect just the contact details or information they need.
Reviewr is an application management platform founded in 2011 by a team that had been part of application programs that weren't intuitive or easy for admins, applicants, or judges. Scholarships, grants, and awards can decide whether someone continues their education, keeps a business open, or moves forward in their career, so Reviewr was built to give applicants their best opportunity to show why they deserve an award and to help administrators choose the best-suited recipient. Over the last 15 years, it has grown to run 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.