JUDGE ASSIGNMENT TRACKER

Judge assignment tracker for workload, conflicts and deadlines

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.

3sample judge profiles
4review workload states
1conflict and recusal path
BEFORE ASSIGNING

Check fit, capacity and impartiality together

A name in a spreadsheet is not enough to establish a usable assignment.

01

Can this judge review the category?

Match category or subject expertise to the entry before distributing work.

02

Are they available before the deadline?

Use current availability and maximum assignments rather than last season's assumptions.

03

Is there a relationship to declare?

Capture known relationships and require the judge's conflict declaration on the scorecard.

04

Has confidentiality been accepted?

Keep the current agreement state with the judge profile.

DURING JUDGING

Follow the work that has not finished

The coordinator needs an exception queue, not just a total assigned count.

01

Assigned

The judge has the entry but has not started the review.

02

In progress

At least part of the scorecard is underway, but it cannot enter comparison yet.

03

Overdue

The due date has passed; follow up or reassign before the program stalls.

04

Recused

A declared conflict removes the judge from that entry and the review does not count.

ASSIGNMENT QUEUE

Prioritize the condition that needs action

Use workload status to direct the coordinator to the next step.

ConditionCoordinator actionCounts as accepted?
AssignedConfirm the judge can startNo
In progressMonitor until all criteria and reasons are completeNo
OverdueFollow up or reassignNo
Conflict declared / recusedAssign a different judgeNo
Accepted scorecardInclude in review coverage and comparisonYes
A CONFLICT IN PRACTICE

One recusal changes the coverage plan

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.

01

Preserve the recusal

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.

02

Choose a replacement

The coordinator checks category expertise, availability, current assignment count and the deadline before giving the entry to another judge.

03

Recheck result coverage

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.

WHEN A CONFLICT APPEARS

Reassign without erasing the reason

A conflict is a managed exception, not an embarrassing note to delete.

01

Judge declares the conflict

The scorecard stays unscored and records the declaration.

02

Review is marked recused

It remains in history but is excluded from accepted review coverage.

03

Coordinator assigns another judge

Use expertise, availability and current workload to choose the replacement.

04

Decision checks coverage

The final result cannot be authorized until enough accepted conflict-free reviews exist.

WHY TEAMS BUILD THIS IN JODOO

Spot overload and conflicts before judging stalls

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.

Assign against capacity

Use judge profiles and a workload view rather than spreading entries evenly by name alone.

Preserve recusals

A conflicted review remains visible but does not count toward accepted coverage.

Move work deliberately

Review routing and deadlines can be changed by the program team without rebuilding the tracker.

WHERE THIS APPROACH FITS

Track assignments; verify access before judging starts

Workload visibility and record-level access are related but separate configuration decisions.

Good fit

A coordinator needs to balance judges across categories, dates and conflict exceptions.

Test with real roles

Check what separate judge and coordinator accounts can see before sharing live entries.

Next step

Use a scorecard for criterion ratings and a separate final decision for result authorization.

COMMON QUESTIONS

Questions about judge assignment tracker

What should a judge assignment tracker include?

Track judge expertise, category fit, availability, capacity, confidentiality, assigned entries, due dates, conflict declarations, review status and accepted completion.

How should judge conflicts be handled?

Require a declaration, preserve the reason, mark the review recused and reassign the entry. Do not count a conflicted scorecard toward required review coverage.

How many entries should each judge receive?

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.

How can I limit judges to assigned entries?

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.

TRY THE WORKING EXAMPLE

Make every assignment actionable and accountable

Open the workload dashboard, inspect the conflict example and install the App to adapt capacities, deadlines and review routing.

Use the judge tracker