Bring your campus together
Start a hub at your university; host Campus Builds and connect the builders and researchers around you.
Swipe
Campus Reps / Resources
Your hub,
start to finish.
Start a hub, run an approved Campus Build and keep your community growing.
The role
Be the campus connection.
Bring your campus together
Open more doors
Share hack opportunities, challenge previews, and research prizes with students and faculty.
Know your people
Know your campus, care about your peers, and take initiative; any year or discipline can apply.
Start with the application
Prepare your name, email, institution, course, and statement of purpose; interview, onboard, then start representing Build54.
Apply on build54.com
Grow through the role
Build leadership experience, meet partners and mentors, and earn recognition; every Campus Build budget needs its own approval.
Your hub
Start small. Keep showing up.
Find people who care
Find people who care
Invite classmates and student societies across disciplines; ask who wants to help.
Swipe
Give people a reason
Host an info session or study group; ask what people want to learn, then plan around it.
Leave with a next step
Agree on a project to try, who will follow up, and how everyone can reconnect.
Share the event work
Name Campus Build owners for safety, check-in, and projects; volunteers must accept their roles and complete a briefing.
Meet the wider community
Meet volunteers and Campus Reps; eligible members can choose to share their story through their live profile.
Meet the communityFirst Campus Build
Run your first Campus Build.
Know the format
Know the format
Run a free, one-day, in-person sprint as an approved Rep; format changes need written Build54 approval.
Read the operating agreementSwipe
Running it online?
A virtual Campus Build needs written approval of the online format; the virtual guide covers the room, online check-in, and safety.
Read the virtual guide
Request before you announce
Apply at least 14 days ahead with your venue, institution contact, team, and plan; wait for approval before committing.
Request a Campus Build
Make the room ready
Upload written venue permission; check capacity, access, water, exits, power, and internet, with a tested fallback.
Pass the readiness check
Complete the dashboard check 48 hours before opening; confirm incident reporting and resolve material safety or permissions failures.
Check people in individually
Check in each registered person present; record meals separately; no bulk check-ins, proxies, or attendee-list sharing.
Make the brief clear
Explain the challenge, conduct, submission deadline, and demo format at kickoff; check progress; never give private deadline extensions.
Help teams submit complete work
Check demos, videos, accessible code, and READMEs covering contributions and reused or AI-assisted work; check completeness, not winners.
Promotion
Promote it the right way.
Approval comes before publicity
Approval comes before publicity
Wait for event approval, then promote only confirmed, approved details.
Swipe
Use the current templates
Use current Build54 files and specifications; keep safe areas; never redraw the logo or invent a co-brand.
Get the media templates
Submit before you post
Submit portrait and story files at least ten days ahead; get Build54 approval for final files and captions before posting.
Make the message accessible
Use readable contrast, video captions, and useful alt text; publish only media you have rights to use.
Respect the camera opt-out
Show a media notice and photo opt-out; avoid private screens; get specific permission for identifiable interviews and testimonials.
Money
Know what the money covers.
One combined allowance
One combined allowance
Cover meals, water, and reasonable essentials such as data and power from one allowance per verified participant.
Swipe
Check your approved cap
Check your event’s approved local-currency allowance and participant limit; the country rate card is your starting point.
See country allowances
Get independent vendor quotes
Upload three independent meal quotes at least seven days ahead; disclose related-party vendors; wait for budget approval.
Payment goes to the vendor
Build54 prefers direct vendor payment, with no Rep cash advance; Rep reimbursement needs prior written approval and payment proof.
Verified costs set the claim
Claim only eligible documented costs, capped by verified participants and your approved allowance; keep invoices and evidence.
Plan for excluded costs
Plan separately for venue, transport, printing, media, equipment, prizes, organiser costs, extra meals, and over-ordering.
Partners & prizes
Keep partners and prizes clear.
Propose a partner first
Propose a partner first
Propose partners in the platform; never sign or accept money for Build54; announce relationships only after approval.
Swipe
Use only approved partner assets
Use approved partner files for the approved event; submit co-branded files and captions for approval; stop when permission ends.
Protect people and fair judging
Never give partners attendee lists, judging influence, or guaranteed winners; extra project access requires the owner’s separate written agreement.
Record prizes before promoting
Get Build54 approval for the provider, award, value, eligibility, allocation, conditions, and delivery before promoting a prize.
Winners receive prizes directly
Build54 or the approved partner delivers directly to verified winners; never handle or deduct from prizes; no release or processing fees.
Builders keep their work
Builders keep ownership; commercial rights need a separate agreement; declining it does not affect an earned result or prize.
Read partners, prizes and IPAfter the event
Close out your Campus Build.
Close out in the dashboard
Close out in the dashboard
Submit your closeout records in the dashboard within 24 hours.
Open your live dashboardSwipe
Deliver the event story
Upload an event-wide view, highlights, two participant interviews, and one volunteer interview; follow the media chapter’s requirements and consent rules.
Record the people who served
Record volunteer attendance within 48 hours; reconcile equipment, hand over unresolved work, and remove temporary access.
Certificates follow verified participation
Confirm qualifying participation before certificates are issued; Volunteer certificates need recorded present service; members find certificates in their account.
View your certificates
Stay available for review
Keep evidence until review closes; resolve gaps so Build54 can accept results and record approved payments.
Bring the learning back
Share what worked with your hub; use participant feedback to choose what to explore next.
Resources
Your Rep toolkit.
Campus Build guide chapters
- Operating agreement
- Apply to host
- Venue and delivery team
- Registration and participant data
- Media and publicity
- Partners, prizes, and IP
- Volunteer management
- 48-hour readiness check
- Run the event
- Check-in and meal service
- Projects and submissions
- Remote judging and talent signals
- Meals and reimbursement
- Safety, conduct, and incidents
- Close out the event
- Integrity, enforcement, and appeals