Using Juryza

An event moves through phases derived from its dates — never a stored flag — so deadlines and the timeline can never disagree. Each phase unlocks different actions.

Upcoming

Before submissions open. The event page is live; nothing can be submitted yet.

Submissions

Teams form, projects are created and edited, and submitted before the deadline.

Judging

The panel scores assigned projects against the weighted rubric.

Community voting

An optional public vote runs in its own window; it can overlap judging.

Results

Once the organizer publishes, the leaderboard, awards and certificates appear.

Ship a project and put it in front of the judges.

1. 1

   Create an account and register

   Sign up, then open the event and register. Creating or joining a team registers you automatically.
2. 2

   Form or join a team

   Start a team and share its invite link, or join one with a link. One team per person per event; teams lock at the submission deadline so rosters cannot be reshuffled once judging starts.
3. 3

   Build your project page

   Add a title, tagline, write-up, repo, live URL, demo video and tech tags. The write-up is rich text stored safely as structured content.
4. 4

   Submit before the deadline

   Submitting is enforced by the server against the clock — a late submission is refused no matter what the browser says. You can keep editing until the deadline.
5. 5

   Follow results

   After the organizer publishes, your placement, any awards and your certificate appear on the event and on your public profile.

Judges only ever see the projects assigned to them — cross-judge reads are refused by the backend, not just hidden in the UI.

1. 1

   Accept the panel invitation

   The organizer invites you by email; the link is bound to that address, so a forwarded link will not work for another account.
2. 2

   Open your queue

   Your assignments appear in Judging. If you are limited to certain tracks, you only receive projects from those tracks, and never a project from a team you belong to.
3. 3

   Score against the rubric

   Give an integer 1–5 for every criterion. Partial scores are refused; the weighted aggregate and the cross-judge normalization are computed on read, so re-weighting never leaves stale numbers behind.
4. 4

   Or judge pairwise

   Some events use pairwise judging: pick the better of two projects and a Bradley–Terry model ranks them. This needs no calibration and is a good cross-check on rubric scores.

Set up the event, run judging, and publish results.

1. 1

   Create the event

   Set the name, dates, tracks, prizes and the weighted rubric. Draft events are visible only to you until you publish.
2. 2

   Build the judging panel

   Invite judges by email and optionally limit each to tracks. Then generate assignments — balanced (every project gets the same number of reviews) or batch (contiguous chunks per judge), with a dry-run preview.
3. 3

   Configure community voting

   Optionally open a public vote. Choose the access mode and strength — see the voting-integrity guide for how to keep it clean.
4. 4

   Watch the integrity dashboard

   Voters by kind, voters sharing a network, burst minutes, and a full audit log are all visible and exportable while the event runs.
5. 5

   Publish results

   Publishing is refused while voting is open, so a live vote can never see standings. On publish, the leaderboard, awards and signed certificates go live.