GuidesCampus Build Guide

Campus Build guide / In person

How to host a Campus Build.

Plan an approved, in-person Campus Build, from your host application to event closeout.

Start with the operating agreement
A campus organiser with a clipboard waving people in

Campus Build handbook

One chapter at a time.

Running it online? The virtual guide

Host a Campus Build

16 chapters

Host a Campus Build

Swipe

Operating agreement

A free, one-day campus hackathon, approved and funded by Build54 one event at a time.

Open chapter

Apply to host

Apply at least 14 days ahead with a real venue, a named contact, and a team of three.

Open chapter

Venue & team

Get written venue permission, test the basics, and name an owner for every part of the day.

Open chapter

Registration & data

Register everyone through Build54, collect only what is needed, and keep attendee lists private.

Open chapter

Media & publicity

Announce only after approval, use current Build54 templates, and get consent before filming.

Open chapter

Partners, prizes & IP

Partners need Build54 approval; prizes go straight to winners, and builders keep their IP.

Open chapter

Manage volunteers

Assign volunteers by email, role, and shift; brief them on site and record attendance within 48 hours.

Open chapter

Ready to open?

Confirm readiness 48 hours before opening; do not proceed with unresolved safety or venue problems.

Open chapter

Run the event

Brief the team, explain the rules, build, serve meals after check-in, lock submissions, demo, and close.

Open chapter

Check-in & meals

Keep separate records for a registered person arriving and receiving a meal.

Open chapter

Project submissions

Teams of 2–5 submit a working demo, video, repository, and README naming contributions.

Open chapter

Remote judging

Build54 judges videos and repositories remotely, with two independent reviews per project scored out of 100.

Open chapter

Meal allowances

One combined meal-and-essentials allowance per verified participant, up to the approved cap, paid to the vendor.

Open chapter

Safety & conduct

Name an incident lead, publish a private reporting method, and act to stop harm first.

Open chapter

Close out

Within 24 hours, submit counts, evidence, project lists, incidents, receipts, and a short outcomes note.

Open chapter

Integrity & appeals

Build54 audits events and acts on evidence; appeal within five business days with new, verifiable evidence.

Open chapter

Jump to a chapter.