Rules of
the build.

Teams

• Teams have 1 to 3 people. You can build solo or with up to two teammates.
• Every team member must be a registered attendee in grades 9–12.
• You can be on one team only. Need teammates? Join the morning team-forming session.

Build it at the event

Every project must be started from scratch and built during hacking hours, 9:30 AM to 5:30 PM.

• Before the event, you may brainstorm ideas, learn new tools, install software, and buy parts.
• During the event, you may use open-source libraries, frameworks, APIs, public tutorials, and off-the-shelf components.
• Not allowed: code, designs, or hardware assembly made before 9:30 AM, or submitting someone else’s project as your own.

Organizers may ask to see your commit history or build progress.

AI tools

AI tools are fully allowed and encouraged. Our sponsors are providing AI credits, and we’ll share how to claim them at the event. You’re responsible for everything you submit, so be ready to explain how your project works.

Submitting

Submit your project by 5:30 PM. We’ll share how to submit at the event. Late submissions won’t be judged.

Judging and prizes

To be eligible for a prize, your team must:

• Submit by the 5:30 PM deadline
• Present to judges during judging, 6:00–6:50 PM, with at least one team member there
• Follow these rules and the code of conduct

Projects are scored on technical execution, creativity, impact, and presentation, 25% each. Each team can win at most one award. The 5 finalists compete for 1st through 5th place grand prizes and aren’t eligible for other awards. Grand prize winners pass their track award to the next eligible team. Judging decisions are final.

Your project

You own what you build. Oregon Unlocked may share your project’s name, description, and demo photos to promote UnlockedHacks.

Changes and decisions

Organizers may update these rules before or during the event, and they decide how the rules apply. Breaking a rule can lead to disqualification. Organizers’ decisions are final.