5 to 8 minute read

Playbooks by Role

Part I: Entrants

This section walks through what happens from the moment you find a program to the moment you hear the result. Nothing here is Judgify-specific; it's the same journey no matter which platform a program uses.
In plain terms: As an entrant, you'll move through five stages: finding the program, submitting your entry, waiting through judging, hearing the result, and (sometimes) a public announcement or ceremony.
Despite the different names, most of these programs share the same underlying shape: someone submits something, someone else reviews it against criteria, and a decision gets made. Once you see that shape, the different labels start to look like variations on a theme rather than separate categories:
  • Finding the program. You come across a call for entries through the organization’s website, an email, or word of mouth. This is where you’ll first see the rules, deadlines, and categories.
  • Submitting your entry. You fill out a form and upload whatever the program asks for, a project, a write-up, a video, or an application. If there’s a fee, you pay it here.
  • Waiting through judging. This is usually the quietest part. Your entry gets reviewed against the program’s criteria. You may hear nothing for weeks. That’s normal.
  • Hearing the result. You’re told whether you were shortlisted, won, or didn’t advance. How much detail you get varies a lot by program.
  • Public announcement, if there is one. Some programs end here quietly. Others hold a ceremony or publish a winners’ page.

Recap

  • Five stages: find, submit, wait, hear the result, sometimes a public announcement.
  • A long quiet period during judging is normal, not a sign something went wrong.
  • How much detail you get about the result depends on the program, not on you.

Quick check

Regardless of what a program is called, the design questions behind it are mostly the same:
1.Which stage usually involves the longest wait with no updates?
2.Every program ends with a public ceremony.
This section walks through what happens from the moment you find a program to the moment you hear the result. Nothing here is Judgify-specific; it's the same journey no matter which platform a program uses.
In plain terms: A strong submission does two things well: it follows the rules exactly, and it answers the judging criteria directly instead of making judges guess how it fits.
  • Follow the rules first. Word counts, file formats, category fit. A brilliant entry over the word limit often gets marked down before a judge even reads the content.
  • Answer the criteria, not just the prompt. If the program lists what it’s judging on (originality, impact, execution), address each one directly. Don’t assume a judge will connect the dots for you.
  • Be specific, not impressive-sounding. Judges read a lot of entries. Concrete details (“reduced processing time by 40%”) stand out more than vague claims (“significantly improved efficiency”).
  • Proofread, then have someone else proofread. Typos and confusing sentences cost more attention than they should.
Most real programs blend two or three of these. A scholarship program is clearly about identifying talent, but it's also a visibility and engagement play for the foundation funding it. A corporate awards program is community-building on the surface, but the winners often become case studies used for external marketing later.

Why the reason matters for everything downstream

Once you know which of these four an organization is actually optimizing for, a lot of design questions answer themselves. A program built for visibility usually wants a public gallery of entries and a splashy announcement. A program built for funding decisions usually wants confidentiality and a much stricter judging process. A program built for engagement can tolerate looser judging criteria, since the goal is participation, not precision. A program built to defend a standard cannot.
Getting this wrong is a common early mistake: organizations borrow the judging structure of a prestige awards program (multiple expert rounds, strict confidentiality) for something that was really meant to be a fun, high-participation engagement exercise, and end up with a slow, over-engineered process that discourages the very participation they wanted.

Recap

  • Follow the rules exactly before worrying about the writing.
  • Address each judging criterion directly.
  • Specific beats impressive-sounding.
  • Always get a second pair of eyes before submitting.

Quick check

Regardless of what a program is called, the design questions behind it are mostly the same:
1.What should you check first, before polishing your writing?
2. Vague, confident language scores better than specific details
In plain terms: A fee, a deadline, and an eligibility rule all exist for the same reason: to keep the program fair and manageable for everyone entering.
  • Fees. Some programs charge an entry fee, usually to cover judging and admin costs. Free and paid programs aren’t a sign of quality either way.
  • Deadlines. Almost always firm. A missed deadline, even by minutes, usually means the entry isn’t accepted, since letting one exception in is unfair to everyone who submitted on time.
  • Eligibility. Rules like location, category fit, or timing (for example, only work from the last 12 months) get checked before judging starts. If you don’t meet them, your entry won’t reach a judge at all, regardless of quality.

Recap

  • Fees fund the process, not a quality signal either way.
  • Deadlines are firm. Submit early.
  • Eligibility is checked before judging. Read it carefully first.

Quick check

Regardless of what a program is called, the design questions behind it are mostly the same:
1.Why are deadlines usually enforced strictly, even by a few minutes?
2.A free program is generally lower quality than a paid one
After you submit, your entry usually moves through a status: received, under review, shortlisted or not, and finally a result. Not every program shows you all of these steps.
  • Received : You’ll normally get a confirmation, often by email. If you don’t get one, check your entry actually went through before assuming it’s fine.
  • Under review : Your entry is with a judge or panel. There’s rarely anything to do here but wait.
  • Shortlisted : (if the program has this stage). You’ve passed an initial round but haven’t won yet. Being shortlisted is a real result worth noting, not a consolation prize.
  • Final result : Win, place, or not this time. Some programs explain why, most don’t, since giving detailed feedback to every entrant takes time most programs don’t have.

On Judgify specifically: your status (received, under review, shortlisted) is visible directly on your own dashboard, rather than something you have to email and ask about.

Recap

  • Confirmation should arrive after submitting. Follow up if it doesn’t.
  • “Shortlisted” is a genuine milestone, not just a near-miss.
  • Detailed feedback isn’t guaranteed. It’s the exception, not the rule.

Quick check

Regardless of what a program is called, the design questions behind it are mostly the same:
1.What should you do if you do not get a confirmation after submitting?
2.Most programs give every entrant detailed feedback on why they did not win.
  • Can I edit my entry after submitting? Usually not once the deadline passes. Some programs allow edits before the deadline, check the specific program’s rules.
  • Can I submit the same entry to two categories? Rarely, unless the rules explicitly allow it. Most programs expect one entry per category.
  • What if I miss the deadline by a few minutes? In almost all cases, it won’t be accepted. Submit well before the deadline, not at the last minute.
  • Do I have to pay to enter? Depends on the program. Check the rules before you start filling out the form.
  • Why didn’t I win, and can I get feedback? You can ask, but don’t expect a detailed answer. Most programs don’t have the capacity to explain every decision.

Recap

  • Editing after the deadline: usually no.
  • Same entry, two categories: usually no, unless stated.
  • Late by minutes: still late.
  • Fees and feedback: both depend entirely on the specific program.

Quick check

Regardless of what a program is called, the design questions behind it are mostly the same:
1.Can you usually edit your entry after the deadline passes?
2.Submitting the same entry to two categories is normally fine.

Part II: Organizers

In plain terms: A program timeline has four blocks: set-up, submissions, judging, and results. Each needs its own real buffer, not a squeezed-together schedule.
Despite the different names, most of these programs share the same underlying shape: someone submits something, someone else reviews it against criteria, and a decision gets made. Once you see that shape, the different labels start to look like variations on a theme rather than separate categories:
  • Set-up. Categories, entry form, key dates, and judge recruitment. Do this before announcing anything publicly.
  • Submissions. The window entrants have to submit. Long enough to get quality entries, not so long that momentum dies.
  • Judging. Give judges real time. A rushed judging window leads to rushed, inconsistent scoring.
  • Results. Build in time to review results before announcing them publicly. Mistakes caught here are far cheaper than mistakes caught after an announcement.

On Judgify specifically, if this is an annual program, one-click relaunch carries your setup into next season instead of making you rebuild categories and forms from scratch.

Recap

  • Four blocks: set-up, submissions, judging, results.
  • Judging needs real buffer time, not leftover time.
  • Review results before you announce them.

Quick check

Regardless of what a program is called, the design questions behind it are mostly the same:
1.What happens when the judging window is too rushed?
2.Results should be reviewed before they are announced publicly
  • In plain terms: Categories should be defined by what makes entries genuinely comparable, not by how many labels sound appealing on a website.
  • Fewer, clearer categories beat many overlapping ones. Too many categories split entries thin and confuse entrants about where to submit.
  • Watch for uneven distribution. One category can quietly attract far more entries than another. Check this partway through the submission window, not after it closes.
  • Decide category rules before launch, not after entries arrive. Changing categories mid-program is confusing and can feel unfair to early entrants.

Recap

  • Fewer, clearer categories work better than many narrow ones.
  • Check entry distribution across categories while there’s still time to adjust.
  • Lock category rules before launch.

Quick check

Regardless of what a program is called, the design questions behind it are mostly the same:
1.What is a risk of having too many narrow categories?
2.It is fine to change category rules after entries start coming in
In plain terms: A good judging panel has enough people to cover the entry volume, real expertise in what's being judged, and no unresolved conflicts of interest.
  • How many judges you need depends on volume, not tradition. More entries or more categories mean more judges or a longer judging window; there’s no fixed universal number.
  • Look for expertise over prestige. A well-known name who doesn’t understand the field is less useful than a lesser-known expert who does.
  • Screen for conflicts of interest early. Ask judges directly if they have ties to any likely entrants before assignments are made, not after.
  • Onboard judges quickly. A short briefing on criteria and process saves far more time later than it costs upfront.

On Judgify specifically, each judge works from their own dashboard showing only their assigned entries, so there’s no manual file-sharing to track who has what.

Recap

  • Judge count should scale with entry volume, not a fixed number.
  • Expertise matters more than name recognition.
  • Ask about conflicts of interest before assigning entries.
  • A short onboarding briefing pays for itself.

Quick check

Regardless of what a program is called, the design questions behind it are mostly the same:
1.What should mainly determine how many judges you recruit?
2.Conflicts of interest should be checked after judges are assigned entries
In plain terms: Fairness comes from structure, not good intentions. Blind review, clear rubrics, and consistent rules do more for fairness than trusting judges to simply be fair-minded.
  • Consider blind or double-blind review. Hiding entrant identity from judges reduces the chance of unconscious bias. Decide this before entries start coming in, since it’s much harder to apply retroactively.
  • Use a rubric, not a gut feeling. A shared rubric keeps scoring consistent across different judges, not just fair-sounding in theory.
  • Separate eligibility screening from judging. Filter out entries that don’t meet the rules before they ever reach a judge, so judges spend their time only on entries that could actually win.
  • Decide how ties get resolved in advance. Deciding this after a tie happens looks arbitrary, even if it isn’t.

On Judgify specifically, blind and double-blind reviews are built into the platform, so hiding entrant identity from judges is a setting, not a manual workaround. Eligibility screening also runs as its own separate step before judging opens.

This section covers the basics. Book 5, Judging & Evaluation Craft goes much deeper into bias, rubric design, and calibration.

Recap

  • Blind review reduces bias and should be decided before entries arrive.
  • A shared rubric keeps scoring consistent.
  • Screen eligibility separately from judging.
  • Set a tie-break rule in advance, not in the moment.

Quick check

Regardless of what a program is called, the design questions behind it are mostly the same:
1.Why decide on blind judging before entries arrive?
2.Deciding how to break a tie after one happens looks arbitrary even if it is not.
In plain terms: Running a paid or sponsored program adds operational work on top of judging: collecting fees, keeping sponsors informed, and getting the word out to attract entries.
  • Entry fees need clear tracking. Know who’s paid, who hasn’t, and what happens to an entry if payment doesn’t go through.
  • Sponsors want visibility into the process, not just the result. Regular, simple updates keep a sponsor relationship healthy long after this year’s program ends.
  • Promotion works best started early. A call for entries announced with plenty of runway consistently draws more, and better, submissions than a rushed one.

On Judgify specifically: entry fee processing runs at 1 to 3.5 percent depending on setup, and supports multiple currencies for international programs. Payments aren’t available on the free Basic tier.

Recap

  • Track payment status clearly, including what happens on non-payment.
  • Keep sponsors updated throughout, not just at the end.
  • Start promoting the call for entries early.

Quick check

Regardless of what a program is called, the design questions behind it are mostly the same:
1.What tends to happen when a call for entries is promoted with plenty of lead time?
2.Sponsors are usually satisfied with an update only at the very end of the program
In plain terms: Fairness comes from structure, not good intentions. Blind review, clear rubrics, and consistent rules do more for fairness than trusting judges to simply be fair-minded.
  • What if a category gets zero eligible entries? It’s usually better to cancel or fold that category than force a winner from ineligible entries.
  • What if a judge doesn’t finish scoring in time? Have a backup plan before it happens, either a reserve judge or a short, clearly communicated extension.
  • Can I run a program with only one judge? You can, but it removes any cross-check on bias or error. Two or more is safer whenever it’s feasible.
  • What if a chosen winner declines the award? Most programs move to the next-highest-scored entry, if the rules allow for that in advance.

Recap

  • Empty category: don’t force a winner.
  • Slow judge: have a backup plan ready beforehand.
  • One judge: possible, but riskier than two or more.
  • Declined award: decide the fallback rule in advance, not in the moment.

Quick check

Regardless of what a program is called, the design questions behind it are mostly the same:
1.What is the recommended response to a category with zero eligible entries?
2.Running a program with only one judge removes any cross-check on bias or error

Part III: Judges

In plain terms: Being a judge means applying the same criteria consistently, staying within your assigned entries, and keeping what you see confidential.
  • Score consistently, not just honestly. Two entries of similar quality should get similar scores, even if you review them days apart.
  • Stay within what you’re assigned. Don’t review or comment on entries outside your assignment, even out of curiosity.
  • Keep it confidential. Scores, discussions, and results stay between judges and organizers until there’s an official announcement.

Recap

  • Consistency matters as much as honesty.
  • Only review what you’re assigned.
  • Confidentiality applies until the official announcement.

Quick check

Regardless of what a program is called, the design questions behind it are mostly the same:
1.What matters as much as being honest when scoring?
2.It is fine to informally discuss scores with entrants before results are announced
In plain terms: A rubric breaks judging into specific criteria so your score reflects the same standard every other judge is using, not just your personal impression.
  • Read every criterion before you start scoring. Skimming the rubric leads to scoring on gut feeling instead of the actual standard.
  • Score each criterion on its own, then let the total add up. Don’t decide the overall score first and reverse-engineer the individual numbers to match.
  • If a rubric feels unclear, ask before scoring, not after. Guessing at what a criterion means leads to inconsistency across judges.

Recap

  • Read the full rubric before scoring anything.
  • Score criterion by criterion, not overall-first.
  • Ask about unclear criteria before you start, not after.

Quick check

Regardless of what a program is called, the design questions behind it are mostly the same:
1.What is the risk of deciding an overall score first and working backward?
2.If a rubric criterion is unclear, it is best to just guess and stay consistent with yourself
In plain terms: A conflict of interest is any personal, professional, or financial connection to an entrant that could affect your judgment, and it should be declared, not judged privately by you as manageable.
  • Declare it even if you think you can be fair. The appearance of a conflict matters almost as much as an actual one.
  • Recusal is normal, not a failure. Stepping back from one entry doesn’t affect your role on the rest of the panel.
  • Confidentiality includes casual conversations. Mentioning scores or leanings outside official channels, even informally, breaks confidentiality.

On Judgify specifically: judges only ever see the entries assigned to them, so recusing from one entry doesn’t require anyone to manually reshuffle files, it’s just a reassignment.

This section covers the basics. Book 5, Judging & Evaluation Craft, goes deeper into how conflicts of interest and bias actually get managed in practice.

Recap

  • Declare conflicts even if you believe you can stay impartial.
  • Recusing from one entry is normal and expected.
  • Confidentiality covers informal conversations too, not just official reports.

Quick check

Regardless of what a program is called, the design questions behind it are mostly the same:
1.Should a judge declare a conflict of interest even if they believe they can stay impartial?
2.Recusing yourself from one entry means you are removed from the whole panel
In plain terms: Disagreeing with other judges is normal and expected. The goal is a fair discussion of the evidence, not consensus for its own sake.
  • Ground disagreement in the rubric. “I scored this lower because criterion three wasn’t addressed” is more useful than “I just didn’t like it.”
  • Feedback to entrants should be specific and kind. Vague criticism doesn’t help anyone improve, and unnecessarily harsh feedback discourages future entrants.
  • It’s fine not to reach full agreement. Most programs have a process for resolving disagreement, whether that’s an average, a discussion, or a lead judge’s call. Trust the process rather than pushing for unanimous agreement.

Recap

  • Base disagreement on the rubric, not personal preference.
  • Feedback should be specific and constructive.
  • Full agreement isn’t required. Trust the program’s resolution process.

Quick check

Regardless of what a program is called, the design questions behind it are mostly the same:
1.What makes a disagreement between judges more productive?
2.Judges are expected to always reach full agreement before a result is finalized.
In plain terms: Running a paid or sponsored program adds operational work on top of judging: collecting fees, keeping sponsors informed, and getting the word out to attract entries.
  • Can I abstain from scoring a specific entry? Yes, especially if you lack the expertise or have a possible conflict. It’s better than scoring something you shouldn’t.
  • Can I change a score after submitting it? Usually only within a window the program defines, and often only with a stated reason. Check the program’s specific policy.
  • What if I know an entrant personally? Declare it. In smaller fields or communities, some familiarity is common, disclosure is what matters, not the fact that you know them.
  • Is it okay to discuss scores with other judges before submitting? Depends on the program’s process. Some want independent scoring first, others build in discussion. Follow whatever that specific program has set up.

Recap

  • Abstaining is acceptable and often the right call.
  • Changing a score: usually possible only within a defined window.
  • Knowing an entrant: declare it, don’t hide it.
  • Discussing scores beforehand depends entirely on the program’s process.

Quick check

Regardless of what a program is called, the design questions behind it are mostly the same:
1.Is abstaining from scoring an entry generally acceptable?
2.Knowing an entrant personally always disqualifies you from judging entirely

Part IV: Public Voters

In plain terms: Public voting is open participation from anyone; judging is assessment by an appointed panel using set criteria. Programs may use one, the other, or both, and they don't always carry equal weight in the final result.
  • Voting is participation, judging is expertise. A vote reflects popularity or appeal; a judge’s score reflects assessment against specific criteria.
  • They’re not always weighted equally. Some programs let public voting decide the whole result. Others use it as just one factor alongside expert judging.

On Judgify specifically, public voting runs as its own separate mechanism from judge scoring, so the two don’t get mixed together by accident.

Recap

  • Voting is open participation; judging is expert assessment against criteria.
  • The two aren’t always weighted the same in the final result. Check the specific program.

Quick check

Regardless of what a program is called, the design questions behind it are mostly the same:
1.What does public voting mainly reflect?
2.Public voting always decides 100% of the result.
In plain terms: Voting is usually quick: browse entries, cast a vote, sometimes confirm your identity to prevent fraud.
  • You may need to log in or verify your email. This exists to stop the same person voting many times, not to make voting difficult.
  • Voting periods are time-limited. Once it closes, votes usually can’t be added or changed.

Recap

  • Login or email verification prevents repeat voting, it’s not a barrier for its own sake.
  • Voting periods close on a fixed date, after which votes are final.

Quick check

Regardless of what a program is called, the design questions behind it are mostly the same:
1.Why do some programs require email or login to vote?
2.Votes can usually be changed at any time, even after the voting period ends.
  • Can I vote for more than one entry? Often yes, check the specific program’s rules, some limit you to one vote per category.
  • Can I change my vote after casting it? Usually not once submitted, though this varies by program.
  • Does public voting decide everything, or just part of the result? Depends entirely on the program. Some use voting as the sole decision, others blend it with judge scores.

Recap

  • Multiple votes: often allowed, but check the rules.
  • Changing a vote: usually not possible once cast.
  • How much voting counts: always check the specific program, it varies.

Quick check

Regardless of what a program is called, the design questions behind it are mostly the same:
1.Can votes usually be changed after being cast?
2.How much public voting counts toward the final result is the same for every program.