Step by step
Do this first.
Projects & judging
Review
Projects & judging
Swipe
Checked-in teams only
Every team member is registered, checked in, and attached to the team on the platform.
Demo, video, repository
Teams submit a working demo, a 2–3 minute video, a repository, and a README.
Say who did what
The README says who did what and discloses prior, third-party, and AI-assisted work.
Start at kickoff
Standard-track projects start at kickoff. Bring ideas, not finished code.
Judged remotely
b54 judges remotely from the video and repository, with two independent reviews per project.
Integrity still applies
Copied work or fabricated contributions can be disqualified. b54 audits events and acts on evidence.
Close out the event
Next chapterRead the full chapter
Projects, judging, and integrity work the same way online. The full rules are in the Campus Build Guide chapters linked below.
• Every team member must be registered, checked in, and attached to the team. • The platform requires a project name, a problem-and-solution description, a repository or b54-accessible code, and a 2–3 minute demo video before submission. • The repository includes a README with setup notes, technologies used, each member’s contribution, and disclosure of pre-existing, third-party, and AI-assisted work. • Standard-track projects start at kickoff. • b54 judges remotely from the video and repository, with two independent reviews per project. • Undisclosed prior work, copied work, or fabricated contributions may be disqualified. b54 audits events and acts on evidence.