What the tool does

The assigner takes a pasted project list and judge list, applies the rules you set, and builds panels that respect every declared conflict, availability window and judge maximum. When a seat cannot be filled without breaking one, it leaves the seat empty and says why. It then prints route sheets, judge lists and a conflict audit. Project codes, judge names and student initials stay in your browser.

Where the figures come from

A worked example in a guide is this site's own solver run over an invented sample fair of 36 projects and 12 judges; every name in it is fictional. Conventional practice, such as how many judges a project usually gets or how fairs handle conflicts, comes from 3 published sources: Category Judging Guide (Synopsys Silicon Valley Science and Technology Championship), Judging at Your Fair (Society for Science), and Judging Plan (Major League Hacking). Each guide that leans on one names and links it at the foot of the page, and the tool comparison dates every price it quotes. No rubric, scoring scale or governing body's rules are reproduced.

One test keeps the examples honest: src/lib/guideExamples.test.tsx renders the guide pages and checks that their text contains the figures the solver actually produces for the sample fair. It runs under npm test.

Who is behind it

There is no company or office here: Judgegrid has a single independent developer and no staff. That developer also makes Icesheet for dividing practice ice, Endbook for archery club records, Hymnwise for parish hymn planning and Curatorbook for small-museum registers. No person's name sits on a guide; each one goes out as Judgegrid, and the author field in its page markup points to the Judgegrid organization. No fair director's post or teaching career is claimed. A guide bears the date of its most recent wording change.

What it cannot decide

Whether your fair is fair. The rules are the ones you type and the conflicts are the ones your judges declare; a panel is only as sound as both, and it knows nothing about a conflict nobody reported. It has no connection to any fair, affiliated network or governing body, ships no scoring rubric, scores nothing and submits nothing.

Start with how conflicts become rules or how many judges a project needs, or see every guide. Questions: [email protected]. Where a fair is stored is in the privacy policy; the terms say what is never warranted.