Judgify

Features
Solutions
Pricing
Log In
Try For FreeBook a Demo
Log In
Try For FreeBook a Demo
5 to 8 minute read

Playbooks by Role

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.

The same shape, many names

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.
On Judgify specifically: entrants get their own dashboard showing exactly where their entry stands, so you're not stuck guessing during the wait.

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.
3. True or false: a single organization can only run one type of recognition or evaluation program at a time.
4. Which of these is NOT one of the five core design questions from this section?
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.

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 dont get a confirmation after submitting?
A
2.Most programs give every entrant detailed feedback on why they didnt win.?
Before naming any specific product, it helps to know what this category of software actually does in general. Every submission and evaluation platform, regardless of brand, is built around the same core set of jobs. Once you can name these jobs, evaluating any specific platform becomes a matter of checking how well it does each one, rather than being swayed by whichever feature list sounds most impressive.
In plain terms: A submission and evaluation platform exists to move a program through its full lifecycle online: collecting entries, managing who reviews them and how, optionally opening some part of the decision to public voting, handling any related payments, and producing a clear result with reporting to back it up.

The core jobs, in lifecycle order

  • Collecting entries : A configurable form that entrants fill out, replacing email attachments.
  • Managing entrants and communication : Automated confirmations, reminders as deadlines approach, and a way for entrants to check their own status without emailing an organizer to ask.
  • Handling payments, where relevant : For paid programs, processing entry fees online, tracking who has paid, and often applying discounts or early-bird pricing.
  • Assigning and managing judges : Getting the right entries in front of the right reviewers and tracking who has completed their reviews.
  • Scoring and evaluation : The actual mechanism judges use to assess entries, typically a rubric or scorecard with defined criteria.
  • Public voting, where a program uses it : A separate, often simpler, mechanism for open audience participation.
  • Reporting and results : Turning individual scores into a final ranking or decision, with enough of an audit trail that an organizer can explain how a result was reached.
  • Security and access control : Making sure each type of user only sees and can do what they’re supposed to.

Why this list matters before looking at any specific product

Nearly every platform in this category will claim to do all eight of these jobs. The real differences between products show up in how well and how flexibly each job is done, not in whether it exists at all. A useful habit when evaluating any platform: for each of the eight jobs above, ask how it would actually work for your specific program, rather than accepting that a checkbox on a features page has been ticked.

Recap

  • Every submission and evaluation platform is built around the same eight core jobs.
  • Almost every product in the category will claim to cover all eight.
  • The meaningful differences are in the depth and flexibility of each job, not in whether it’s offered at all.
  • Evaluate any platform by asking how each job would work for your specific program, not by scanning a feature checklist.

Quick check

Regardless of what a program is called, the design questions behind it are mostly the same:
1. Which of these is NOT one of the eight core jobs described in this section?
2. According to this section, where do platforms in this category mostly differ from each other?
3.Public voting and expert judging are typically kept as separate mechanisms.
4. What is the recommended way to evaluate a platform, according to this section?
The first five sections deliberately stayed general. This one doesn't. Here's who Judgify actually is, in plain terms, before the next section walks through what the platform does in more detail.
In plain terms: Judgify is a cloud-based platform for managing awards, competitions, grants, scholarships, and similar submission-and-evaluation programs, used by organizations to collect entries, manage judging, and announce results without relying on spreadsheets and email.

The basics

Judgify has been operating for 12 years, and has supported more than 8,000 programs for over 200 organizations across more than 60 countries. It's built to serve the full range of program types covered in Section 1, awards, competitions, grants, scholarships, abstracts, hackathons, and more, on a single platform rather than requiring different tools for each.

How the plans are structured

Judgify offers four plans: Basic, Pro, Pro Unlimited, and Enterprise.
  • Basic : is a free entry-level tier, intended as a starting point for organizers who are new to the platform or running a small, simple program.
  • Pro : sits in the middle, adding capacity and features suited to a growing program.
  • Pro : Unlimited is billed annually and supports up to 10 events per year, despite the name, it is not literally unlimited on event count, which is worth knowing upfront rather than discovering later.
  • Enterprise : is billed per event and is aimed at larger organizations running high-stakes or high-compliance programs, with access to capabilities like single sign-on and compliance certificates that aren’t available on the lower tiers.
The right starting tier depends far less on organization size than on how many programs you plan to run in a year and how much compliance and control your specific program needs.

Why this list matters before looking at any specific product

Nearly every platform in this category will claim to do all eight of these jobs. The real differences between products show up in how well and how flexibly each job is done, not in whether it exists at all. A useful habit when evaluating any platform: for each of the eight jobs above, ask how it would actually work for your specific program, rather than accepting that a checkbox on a features page has been ticked.

Recap

  • Judgify is a cloud-based platform for managing awards, competitions, grants, scholarships, and similar programs.
  • 12 years operating, 8,000-plus programs, 200-plus organizations, 60-plus countries.
  • Four plans: Basic (free), Pro, Pro Unlimited (annual, up to 10 events/year), Enterprise (billed per event).
  • Pro Unlimited is not literally unlimited on event count.
  • Plan choice depends more on program volume and compliance needs than organization size.

Quick check

Regardless of what a program is called, the design questions behind it are mostly the same:
1. How long has Judgify been operating?
2. What is true about the Pro Unlimited plan?
3.Enterprise is the only plan billed per event rather than annually or as a flat subscription.
4. What should mainly drive which plan an organizer chooses?
Section 5 laid out the eight jobs any submission and evaluation platform needs to do. This section walks through that same list again, this time naming specifically what Judgify offers at each stage.
In plain terms: covers the full lifecycle from entry collection through final reporting, with particular strength in role-specific access, multi-language and multi-currency support, and judging flexibility like blind and double-blind review.
  • Entry collection and branding : Judgify’s entry forms can be built and branded to match a program’s own look, and the platform supports content across a wide range of languages, useful for programs running in multiple countries or regions.
  • Payments and promotions : For paid programs, Judgify handles entry fee processing directly, with a processing rate in the 1 to 3.5 percent range depending on setup, and supports a wide range of currencies. Payment processing is not available on the free Basic tier.
  • Judging and public voting : Role-specific dashboards mean judges, organizers, and entrants each see an interface built for what they actually need to do. Judgify natively supports blind and double-blind review, entrant identity can be hidden from judges by design, not as a manual workaround. Eligibility screening is handled as a separate step from judging itself. Where a program wants it, public voting runs as a distinct mechanism from expert judging.
  • Scoring and reporting : Scoresheets can be downloaded as Excel files, and the platform supports one-click relaunching of a program from one season to the next, useful for annual programs that don’t want to rebuild their setup from scratch every year.
  • Security and compliance : Judgify holds ISO 27001 and PCI DSS certifications and is built on AWS infrastructure with a 99.9 percent uptime target. Single sign-on and access to compliance certificates are available on the Enterprise plan.
  • Support : Support response times are tiered by plan: roughly 24 hours on the free tier, 6 to 8 hours on Pro, and 2 to 4 hours on Enterprise.

How the plans are structured

Judgify offers four plans: Basic, Pro, Pro Unlimited, and Enterprise.
  • Basic : is a free entry-level tier, intended as a starting point for organizers who are new to the platform or running a small, simple program.
  • Pro : sits in the middle, adding capacity and features suited to a growing program.
  • Pro : Unlimited is billed annually and supports up to 10 events per year, despite the name, it is not literally unlimited on event count, which is worth knowing upfront rather than discovering later.
  • Enterprise : is billed per event and is aimed at larger organizations running high-stakes or high-compliance programs, with access to capabilities like single sign-on and compliance certificates that aren’t available on the lower tiers.
The right starting tier depends far less on organization size than on how many programs you plan to run in a year and how much compliance and control your specific program needs.

Why this list matters before looking at any specific product

Nearly every platform in this category will claim to do all eight of these jobs. The real differences between products show up in how well and how flexibly each job is done, not in whether it exists at all. A useful habit when evaluating any platform: for each of the eight jobs above, ask how it would actually work for your specific program, rather than accepting that a checkbox on a features page has been ticked.

Recap

  • Full lifecycle coverage: branded multi-language forms, payments (not on Basic), role-specific judging with native blind/double-blind review, separate eligibility screening, optional public voting, Excel exports, one-click relaunch, and ISO 27001/PCI DSS security.
  • SSO and compliance certificates are Enterprise-only.
  • Support response time scales with plan tier.

Quick check

Regardless of what a program is called, the design questions behind it are mostly the same:
1. Which judging capability does Judgify support natively?
2. What is true about payment processing on Judgify?
3.Single sign-on and compliance certificate access are available on every Judgify plan
4. What does "one-click program relaunch" refer to?
This closing section of Book 1 is deliberately practical: a walk-through of what the first month on a new platform typically looks like, and the mistakes organizers most commonly make during that window, so you can avoid them the first time rather than the second.
In plain terms: The first 30 days on any new platform are about setup, not judging: getting your program's structure right, inviting the right people with the right roles, and testing the entrant experience before you ever open submissions to the public.

A typical first-month sequence

  • Week 1: Structure your program. Define your categories, build your entry form, set your key dates. Decide whether you need blind or double-blind judging now, since it’s easier to set up correctly from the start than retrofit later.
  • Week 2: Invite your team. Add organizers and coordinators with the right permissions, start recruiting and inviting judges, and think through conflicts of interest before assignments are made.
  • Week 3: Test everything as an entrant would. Submit a test entry yourself, all the way through, before opening the program publicly. Check confirmation emails, form clarity, and anything that might confuse a first-time visitor.
  • Week 4: Open submissions and monitor. Launch the call for entries and keep an eye on your dashboard for early signals, so you can adjust while there’s still time.

Common first-time mistakes

  • Not testing the entrant flow before launch : The single most common mistake. A confusing form or a broken confirmation email costs far more in lost entries than the ten minutes it takes to test.
  • Setting judge deadlines too close to the results announcement : Judges need real buffer time; a tight window leads to rushed scoring or missed deadlines.
  • Uneven category assignment : Some categories quietly attract far more entries than others, overloading some judges while others sit idle.
  • Deciding on blind judging after entries have already come in : Far easier to build in from the start than apply retroactively.

Where to go from here

Book 1 has covered the general orientation. The rest of the Academy goes deeper: Book 2 covers each role individually, Book 3 covers each of the 11 program types, Book 4 covers industry-specific considerations, and Book 5 goes deep on judging and evaluation craft.

Recap

  • The first 30 days should focus on structure and testing, not judging itself.
  • Typical sequence: structure, invite your team, test as an entrant would, launch and monitor.
  • The most common mistake is skipping the entrant-flow test before launch.
  • Decide on blind judging before entries start coming in, not after.

Quick check

Regardless of what a program is called, the design questions behind it are mostly the same:
1. What is described as the single most common first-time mistake?
2. When should a program decide whether to use blind judging?
3.Judges should be given as little buffer time as possible to keep the program moving quickly.
4. What does Week 3 in the typical sequence focus on?