Run a judged competition people take seriously, from entry to certificate

Published July 14, 2026 · Updated July 14, 2026 · By the Continuous Cup team

A judged competition platform is software that runs an entire judged event, entries, judge assignment, blind scoring, and published results, from one system instead of several disconnected tools. That is the direct answer to "platform for running judged competitions": instead of a form builder for sign-ups, a spreadsheet for scoring, and a mail merge for certificates, everything runs against the same record, so nothing gets out of sync between stages.

Stitched-together tools work fine for the first few entries. Then a form field does not match a spreadsheet column, a judge scrolls past an entrant's name they were never supposed to see, a formula gets dragged one row short and quietly drops an entry, and someone mail-merges winner certificates before the tiebreak is actually settled. None of that is a judge's fault or an organizer's carelessness. It is what happens when a competition's data has to move between four separate tools by hand. Continuous Cup exists to remove those handoffs.

Setup: categories and the rubric live in the same system that will score them

Every judged competition starts with two decisions: what are the categories or divisions, and what does a winning entry actually look like. On a stitched-together stack, the rubric usually lives in a document that gets emailed to judges and then copied by hand into a scoring sheet. If an organizer tweaks a criterion's weight after judges have already started, the emailed rubric and the live scoresheet drift apart, and nobody notices until the results look wrong.

On Continuous Cup, you build divisions, categories, and a weighted rubric once, in the same system that will run entries, judge assignment, and scoring later. Judges score against the live rubric, not a snapshot of it from a week ago. If you have not built a rubric before, how to create a judging rubric covers how to weight criteria so the final numbers actually mean something.

Entry collection: one public page instead of a form tool plus a manual import

Entries come in through a public competition page at a shareable link, with custom entry-form fields, divisions, and optional entry caps built in, so you are not maintaining a separate form and then importing responses into a spreadsheet by hand. If entries carry a fee, card payment runs through Stripe on the same page. For events with physical drop-off, QR codes handle check-in, and a single-day walk-up mode lets entrants register and check in on-site, which matters for cuppings or tastings where entries arrive the morning of the event, not weeks ahead.

Because entries land in the same record that judging and scoring will use, there is no export-import step where a row can be mistyped or a column can shift. The entry an entrant submits is the entry a judge sees.

Judge recruitment: applications, invitations, and assignment without a roster spreadsheet

Recruiting a panel usually means a separate application form, an email thread to send invitations, and a spreadsheet tracking who confirmed and what they are allowed to judge. Continuous Cup keeps that in the platform: judge application forms with custom questions, email invitations, and automatic assignment that distributes entries across the panel with configurable overlap and rounds, so you set how many judges see each entry instead of dividing a roster by hand. Judges score from whatever device they have, phone, tablet, or laptop, which matters on the day when a judge is standing at a table, not sitting at a laptop.

Blind judging: entries carry a code, never a name

Blind judging is where stitched-together tools tend to fail quietly. A spreadsheet column can be hidden but not truly removed, and a judge who opens the wrong tab sees an entrant's name anyway. On Continuous Cup, entries get anonymous codes the moment they are submitted, and judges never see entrant names at any point in the scoring flow. For entries that need to be made to fit a judge, such as a homebrew batch size or a dietary restriction, a fit-to-judge flow shares the requirement with the entrant without revealing whose requirement it is. See blind judging software for how the anonymization holds up under audit, not just at first glance.

Scoring and normalization: the math a spreadsheet formula usually gets wrong

Once scores come in, aggregation is where most spreadsheet-built competitions quietly go wrong: a formula range that does not update when a late entry is added, an average that lets one outlier judge decide a category. Continuous Cup supports raw averages, robust z-score normalization, rank-based scoring, and Many-Facet Rasch Measurement, which models each judge's severity so a consistently harsh or lenient judge does not distort the standings. You can trim the highest and lowest score per entry, and set tiebreakers, including head-to-head mini tables and Buchholz pairings for leagues. Results tally live as judging finishes, so you are not waiting on someone to run a final formula pass. For the reasoning behind picking one aggregation method over another, see how to score a competition fairly; if you are coming from a spreadsheet-based process today, the spreadsheet alternative covers the migration directly.

Publishing results people can actually check

A results page assembled by hand, a PDF someone formatted the night before, invites doubt: entrants ask how a score was reached, and there is no good answer beyond "trust us." Continuous Cup publishes a results page anyone can check, backed by automatic judge-bias checks that flag any judge whose scoring drifts from the rest of the panel, using robust statistics that a single unusual score cannot throw off. A defensibility report and a public judging-transparency page show step by step how scores were combined, so the answer to "how was this decided" is a page, not a conversation. Multi-round competitions can advance entries between rounds on the same record, and public or people's-choice voting can run alongside judged scoring when an event wants both.

Records that outlive the event

A competition does not end when judging does. Winners need certificates, some need verifiable credentials they can point to later, and entrants and sponsors alike want the reassurance that results were reached fairly, not just announced. Because Continuous Cup keeps entries, judge assignments, scores, and the transparency page in one system, that record stays intact and checkable after the event, instead of living in a spreadsheet someone eventually deletes or a mail-merge template nobody can find again. Email notifications, with consent and unsubscribe handling built in, keep entrants and judges informed without a separate mailing list to manage.

One platform, two families of competitions

Continuous Cup covers judged cup competitions, coffee cuppings, homebrew, BBQ, baking, chili, and other tasting or maker contests scored by a panel against weighted criteria, and scored events, timed-race leaderboards, heats and finals, knockout brackets, and season leagues with round-robin fixtures, points tables, and Swiss pairings. If your event centers on judged scoring specifically, competition judging software and tasting competition software go deeper on those setups; how to run a judged competition is the fuller organizer guide this page draws from. Either way, the point is the same: one platform carries the thread from the first entry to the published result, so you run the event, not the spreadsheet.