How to run a fit-to-judge competition
Fit-to-judge is a competition format where an entry has to be built to match a specific judge's stated requirements, like a size or a dietary need, rather than judged after it already exists. The judge publishes what they need anonymously, the entrant builds an entry to match, and neither side learns who the other is. Nobody else offers this as a built-in format; most judging platforms only handle entries that already exist before judging starts.
Once the entry is built, nothing about scoring changes. It moves through intake and anonymization like any other entry and is scored against the same rubric the rest of its category uses. Fit-to-judge only changes how the entry came to be, not how it is evaluated.
Continuous Cup is competition-management software for organizers who need to collect entries, coordinate judging, calculate scores, and publish trustworthy results from one platform. Fit-to-judge is a setting on the competition, not a separate product: turn it on for the categories that need it and the rest of the platform, entries, anonymization, scoring, results, works the same as it does everywhere else. See pricing or start free.
What kinds of categories need fit-to-judge
The common thread is a requirement that exists only because of who is judging, not because of the competition's general rules. A few examples:
- Homebrew or cider, built to a bottle or growler size. A judge names the container size or format they want to receive, and entrants brew or package a batch to match.
- Baking, built around a dietary need. A judge specifies a restriction, such as gluten-free or nut-free, and entrants bake to that constraint instead of a general recipe.
- Guild and maker categories, built to a fit. A judge provides measurements or a size, and entrants make a piece, garment, or item to match.
Not every category in a competition needs this. Most organizers turn it on for one or two categories where a made-to-order entry makes sense, and leave the rest of the competition judged the ordinary way.
How the fit-to-judge flow works
1. Turn it on during setup
Fit-to-judge is a decision you make while setting up the competition, not something you add once judging is underway. Judges need their requirements published before entrants start building, and entrants need real time to build to spec before intake closes, so the setting locks once the competition leaves setup.
2. Judges publish their requirements anonymously
Once judges are recruited, each one shares what they need, a size, a fit, a dietary need, and it is relayed to entrants by an anonymous code, never by the judge's name. A judge writing their own requirements down is also a natural moment to be specific: a vague requirement produces entries that technically qualify but do not really fit what the judge needed.
3. Entrants build to match
Entrants see the published requirements, not who wrote them, and build or make their entry to match before the normal entry deadline. This step is the one genuinely new part of fit-to-judge; everything before and after it is the same process as any other category.
4. The entry moves through the same intake and anonymization as any other entry
Once built, a fit-to-judge entry is not treated any differently from an entry that existed from the start. It gets logged at intake, assigned an anonymous code, and reaches judges the same way every other entry does. For the general mechanics of keeping an entry anonymous from intake through scoring, see anonymized judging software and, for physical entries specifically, tasting competition software.
5. Judges score it like any other entry
The judge who wrote the original requirement is not guaranteed to be the one scoring the resulting entry, and either way, scoring uses the same rubric and scoring form as the rest of the category. The fit-to-judge step is over by the time judging starts.
6. Results publish the same way
A fit-to-judge category is a category like any other on the results page: ranked results, the scoring method, and certificates for winners. See how to run a judged competition for the full publishing step.
Where doing this by hand breaks anonymity
The manual version of fit-to-judge is usually an email or a shared sign-up sheet: a judge's requirements typed into a message with their name in the header, or a document where entrants sign up next to the judge they are building for. Both leak the exact thing fit-to-judge is supposed to protect, and they leak it at the one moment nobody is thinking to check, before judging has even started. Matching entrants to judges by hand for a field of any real size adds a second problem on top: it is easy to mismatch a requirement, and there is no anonymous code to catch the error, only whoever is doing the matching remembering correctly.
The fix is the same structural one anonymized judging uses everywhere else: the requirement and the match should live in a system that relays them by code, not in a document a person has to remember to redact.
A worked example: a homebrew club's "brew to spec" category
A homebrew club wants a category where entrants brew to a judge's exact request instead of a general style. Each judge on that category specifies a batch or bottle size and any dietary flag, for example a gluten-reduced request. Those requirements are published to entrants under anonymous codes, never the judge's name. Entrants brew and package a batch to match one published requirement and submit it by the entry deadline. At intake, the finished bottle is anonymized exactly like every other entry in the competition: logged, coded, and staged for judging. Judging then proceeds on the club's normal style rubric, the same one every other homebrew category uses. Nobody involved, not the judge and not the entrant, ever learns who was on the other side of the match.
How Continuous Cup handles fit-to-judge
Fit-to-judge is a setting on the competition, available during setup and locked once judging is underway. Judges publish sizes, fits, or dietary needs, and the requirement reaches entrants by anonymous code, never by name. Once an entrant's entry is built, it is anonymized and scored exactly like every other entry, since fit-to-judge is a layer on top of Continuous Cup's ordinary anonymized-judging flow, not a separate one.
If you have not settled on a rubric or an anonymization level yet, start with how to run a judged competition for the full process, or anonymized judging software for how identity stays out of scoring end to end.
Frequently asked questions
What does fit-to-judge mean?
Fit-to-judge is a competition format where an entry has to be built to match a judge's stated requirements, such as a size or a dietary need, instead of being judged after it already exists. The judge publishes what they need anonymously, the entrant builds an entry to match, and neither side learns who the other is. Once the entry exists, it is scored the same way any other entry is.
How is a fit-to-judge category different from a normal anonymized category?
Anonymization hides identity during scoring; fit-to-judge adds a step before scoring where the entry itself is made to order for one specific judge. Every fit-to-judge category is also anonymized, since the entry still moves through intake and judging under a code, but not every anonymized category is fit-to-judge. Most categories judge an entry that already exists; a fit-to-judge category judges an entry built for the occasion.
What kinds of competitions use fit-to-judge?
Anywhere an entry has to be built for a specific person rather than a general style: a homebrew or cider category built to a bottle or growler size a judge names, a baking category built around a dietary restriction a judge specifies, or a guild or maker category built to fit measurements a judge provides. The common thread is a requirement that only exists because of who is judging, not because of the competition's general rules.
Does fit-to-judge change how judges score the finished entry?
No. Judges score the finished entry against the same rubric as every other entry in the category. Fit-to-judge only changes how the entry came to be built; the criteria, the scale, and the scoring form are unchanged.
Can fit-to-judge be turned on after the competition starts?
No, and this is deliberate. Fit-to-judge is a setup-time decision because judges need to publish their requirements before entrants start building, and entrants need time to build to spec before intake. Once a competition leaves setup, the fit-to-judge setting locks.
Does fit-to-judge ever reveal who the judge or entrant is?
It should not, and the design goal is that the matching step itself never becomes the leak. A judge's requirements are relayed by an anonymous code, never their name, and an entrant's finished entry moves through the same anonymization as any other entry once it is built. The two people involved never learn one another's identity from the process.