Fair judging is designed before the first review is assigned

Most judging problems are process problems. If reviewers get unclear criteria, uneven workloads, late assignments, or no place to declare conflicts, the final decision meeting becomes harder than it needs to be. Most of those problems are easier to solve in the nomination process design than they are once judging is underway.

A fair process does not require legal complexity. It requires clarity: who is eligible, what reviewers should evaluate, how conflicts are handled, how scores are documented (a shared rubric helps), and how finalists are selected.

Step-by-step judging process

  1. 1

    Define eligibility before judging

    Use eligibility questions and category rules so clearly ineligible submissions do not move into the reviewer pool.

  2. 2

    Create the rubric before assigning reviewers

    Set criteria, weights, score scales, and reviewer guidance while no scores exist, then lock structural changes once reviews begin.

  3. 3

    Assign reviewers with workload balance

    Decide how many reviewers each submission needs and spread assignments so every entry gets attention.

  4. 4

    Ask reviewers to declare conflicts

    Make it easy for reviewers to flag employment, family, board, vendor, client, or close personal relationships.

  5. 5

    Monitor progress before the deadline

    Use reminders and progress views to catch overdue assignments while there is still time to recover.

  6. 6

    Compare finalists with context

    Look beyond the average score. Review medians, score spread, notes, conflicts, and incomplete reviews before making final decisions.

What to document

Assignments

Which reviewer was assigned to which submission, and whether the assignment was completed, pending, or conflicted.

Scores

The score for each criterion, not just one final number. This makes differences easier to discuss.

Reviewer notes

Brief notes explaining what influenced the score and whether the entry should be part of finalist discussion.

Status changes

When an entry moved from submitted to finalist, winner, declined, or another internal status.

Award judging questions

How many reviewers should score each submission?

Many programs use three reviewers per submission because it gives a better signal than one score while keeping workload manageable. Larger or high-stakes programs may use more.

Should reviewers see each other's scores?

Usually not during initial review. Independent scoring helps prevent early reviewers from anchoring the rest of the panel.

When does multi-round judging make sense?

Use multi-round judging when the first round narrows a large pool and the finalist round needs a deeper or different discussion.

How should ties be handled?

Decide before judging starts. Common approaches: a committee chair or senior reviewer makes the call; a runoff vote among reviewers using a shorter rubric; or weighting one criterion as the tiebreaker, usually the one most central to the award's intent. Document the rule and apply it consistently.

What happens if a reviewer drops out mid-cycle?

Have a fallback plan before assignments go out. The cleanest options are reassigning the dropped reviewer's queue to another reviewer with similar background, or accepting fewer reviewers on those entries if your minimum review count still holds. Log the change so the audit trail explains any score-count differences.

Next step

Put this process into a working awards workspace.

ChamberPages Awards Manager connects public forms, categories, reviewer assignments, scoring, reminders, finalist review, and committee packets so the process stays organized from intake to decision.

Talk through your judging process