The short version:

1. Morning: check in, grab breakfast, catch the talks.
2. 12:15 PM: find your team if you don't have one.
3. 1:00 to 5:00 PM: build.
4. 5:15 PM onwards: demos, then judging and results.

Exact times live on the agenda, which shows what's on now and what's next.

• Solo or in a group of up to 2 people.
• Coming solo is completely fine. Join the Find your team slot and we'll help you match with people building something similar.
• One person submits for the whole team, so decide who early.

Build something that works, even if it's small. A focused demo that does one thing well beats a big idea that only exists on slides.

There are four tracks for now: Voice, People, Experiences and Social Impact. They're working titles and still TBC. The Buildathon overview has a line on each.

• Code you submit should be written during the build session. Planning, sketching and setting up your tools beforehand is fine.
• Open-source libraries, APIs and templates are fine. Say what you used.
• AI coding tools are welcome. You should still be able to explain how your project works.
• Be kind to the people around you. The code of conduct applies all day.

Anything unclear? Ask at the help desk before you sink hours into it.

Depending on your pass, you may get credits for tools you can use while building. Open the Credits page to see yours.

• Credits can be claimed after you check in at the venue.
• Each offer explains how it works: some give you a code, some send an email, some are a link.
• Which tools are included is TBC.

Use the Submit page in this app. You'll need:

• A project name, even a working title
• A link to your code (a public repo is easiest for judges)
• A demo link or a short video
• A few lines on what you built and who it's for

There are two deadlines, and it's the same entry both times:

1. v0 by 5:00 PM on the day. Whatever you have working by then. You need it in to demo.
2. Final by 11:59 PM on Fri 27 Nov. Five more days to polish it at home. Update the same entry, no need to start over.

Edit as often as you like. Whatever is saved before each deadline is what counts.

Each team gets a few minutes on stage (exact time TBC). Some tips:

• Show the thing working first. Context second.
• Have a backup video ready in case the wifi has a bad moment.
• Keep one tab open, not twelve.

Judges score each project from 1 to 5 on a short rubric. How the v0 and the final add up is still being worked out, so treat everything here as TBC. The criteria below are a draft.

Judges see your project and team, not your personal contact details.

Be respectful, be inclusive, and look out for each other. Harassment of any kind isn't okay. If something feels off, tell a volunteer or the help desk and we'll take it from there, quietly.

The full TPF code of conduct is on the UnConference site (opens in a new tab).

• Stuck on code? Mentor office hours run during the build session (TBC).
• Anything else? The help desk near registration is staffed all day.
• Lost? The venue page has rooms, wifi and directions.