Scoring Your Committee Can Defend

Rubric scores, ranking, head-to-head, live pitch or public vote, chosen per round. Rubrics carry weights and descriptors so a panel scores alike.Each round chooses how it is judged: rubric scores against weighted criteria, a ranking of each evaluator's entries, head-to-head pairs that IdeaScore balances, live pitch scoring on the day, or a public vote. Rubrics carry a weight for every criterion and descriptors for a low and a high score, so a whole panel reads a seven the same way.

• Head-to-head is fair once every entry has been compared five times
• Rank by dragging, with arrow buttons or from the keyboard
• Public vote, available once your organisation turns it on
• The mode is fixed once rankings, comparisons or votes exist

The plan is ready when you open it: who would score what, and why, with every declared conflict kept apart. Check, apply, and undo in one step.Conflict-aware assignment shows its plan as soon as you open it: who would score what, and why, each team joined to its evaluators by expertise or the lightest load, and every declared conflict kept apart. Pick by hand in a list or a grid, auto-assign by expertise, or Balance to move unscored teams from the busiest evaluators to those with room. Check shows exactly what will be saved, and one Undo removes it.

• A locked cell for each declared conflict, with who declared it and why
• Submitted scores never move
• Open declarations, each with a one-click reassign

Evaluators open decks with names, contact details and photos taken out of the file. Preview a real slide first; staff and teams keep the original.Switch on deck masking and evaluators open a copy of every deck with the names of the people in your programme, their contact details and every photograph taken out of the file itself, not covered over. Preview a real slide first, for every round or just one. Staff and the team always see the original, a deck masking cannot be sure of waits for your decision, and a page in a script IdeaScore can't check for names is held back from blind reviewers.

• Text removed, so it cannot be copied or searched for
• Decks with words inside pictures held back until you choose
• Pages in a script IdeaScore can't check held back from blind reviewers
• Every change recorded in the audit log

A finish date from each judge's own pace, who is holding it up, and Remind or Reassign on the card. Reminder Effect shows whether reminders work.Review Forecast works from each judge's own pace over the last seven days, not the panel's average, so a judge who is behind shows as the slow tail. It names who is holding scoring up, with Remind and Reassign on the card. Reminder Effect sets reviews scored within 48 hours of a first reminder against those never reminded, and names the best time to send.

• Appears after three days of scoring, so it is never a guess
• Past the deadline, the line turns amber and says Finishes late
• Reminder Effect shows counts only, never an evaluator's name

Up Next shows what to score first and the next deadline. Scores are kept safe on a weak connection, and contact details stay hidden by default.Evaluators land on Up Next: the next teams to score across every programme, overdue first, with the next deadline in their own time zone. Scoring has descriptors beside every criterion, drafts that are saved on the device first when the connection is weak, and J and K to move between teams. Team contact details and rankings stay hidden unless you choose otherwise.

• Declare a conflict from the list or the scoring page
• A submitted score is read-only until Edit my score
• Flag a criterion for the committee to discuss