Can this judge review the category?
Match category or subject expertise to the entry before distributing work.
Give the coordinator one place to see who can review, which entry is assigned, what is overdue and which conflict requires reassignment.
The example has three judges, assigned and overdue scorecards, a declared conflict and a recused review that does not count toward the final decision.
Free for up to five users. No credit card required.
Adapt fields, workflows, and dashboards without code. Explore 1,000+ app templates and use cases
The gallery shows sample data from the working App. Form links open a new blank entry; install a copy with sample data to inspect existing records and adapt the workflow.
A name in a spreadsheet is not enough to establish a usable assignment.
Match category or subject expertise to the entry before distributing work.
Use current availability and maximum assignments rather than last season's assumptions.
Capture known relationships and require the judge's conflict declaration on the scorecard.
Keep the current agreement state with the judge profile.
The coordinator needs an exception queue, not just a total assigned count.
The judge has the entry but has not started the review.
At least part of the scorecard is underway, but it cannot enter comparison yet.
The due date has passed; follow up or reassign before the program stalls.
A declared conflict removes the judge from that entry and the review does not count.
Use workload status to direct the coordinator to the next step.
| Condition | Coordinator action | Counts as accepted? |
|---|---|---|
| Assigned | Confirm the judge can start | No |
| In progress | Monitor until all criteria and reasons are complete | No |
| Overdue | Follow up or reassign | No |
| Conflict declared / recused | Assign a different judge | No |
| Accepted scorecard | Include in review coverage and comparison | Yes |
The sample workload includes a Repair Together review marked recused after a conflict declaration. Another assigned review is still in progress, so neither can count as an accepted scorecard yet.
Keep the judge, entry and conflict declaration on the review record. Do not quietly delete the assignment or turn the unfinished score into a zero.
The coordinator checks category expertise, availability, current assignment count and the deadline before giving the entry to another judge.
The final decision must wait until the category has enough complete, accepted and conflict-free reviews. A reassignment alone does not satisfy the review requirement.
A conflict is a managed exception, not an embarrassing note to delete.
The scorecard stays unscored and records the declaration.
It remains in history but is excluded from accepted review coverage.
Use expertise, availability and current workload to choose the replacement.
The final result cannot be authorized until enough accepted conflict-free reviews exist.
The coordinator needs current availability, due dates and conflict declarations in the same place as the assigned reviews.
An overdue or recused review has a clear next action instead of disappearing in a spreadsheet.Use judge profiles and a workload view rather than spreading entries evenly by name alone.
A conflicted review remains visible but does not count toward accepted coverage.
Review routing and deadlines can be changed by the program team without rebuilding the tracker.
Workload visibility and record-level access are related but separate configuration decisions.
A coordinator needs to balance judges across categories, dates and conflict exceptions.
Check what separate judge and coordinator accounts can see before sharing live entries.
Use a scorecard for criterion ratings and a separate final decision for result authorization.
Track judge expertise, category fit, availability, capacity, confidentiality, assigned entries, due dates, conflict declarations, review status and accepted completion.
Require a declaration, preserve the reason, mark the review recused and reassign the entry. Do not count a conflicted scorecard toward required review coverage.
There is no universal number. Set a capacity that reflects entry complexity, review depth, deadline and the judge's current availability, then show actual assignments against it.
Configure member-based record permissions for judges, then check the actual access with separate judge and coordinator accounts before opening judging. A coordinator's view alone cannot prove what a judge can see.
Open the workload dashboard, inspect the conflict example and install the App to adapt capacities, deadlines and review routing.
Use the judge tracker