The complete journey through a HyperSprint: creating your account, finding your sprint, forming a team, and shipping your deliverables before the deadline. Follow it start to finish, or jump to the step you're on.
1. Create your account
Press Sign up in the header. Enter your email and a password (8+ characters), or use Continue with Google / GitHub — OAuth accounts arrive already verified, so you skip the next step entirely.
Fig. 1 — The sign-up card: email + password, Google and GitHub below.
Full detail in the account guide →
2. Verify & onboard
Email sign-ups get a verification link (valid 60 minutes — check spam, or press Resend email). After verifying, the 90-second onboarding asks for three things: a display name, 1–2 skills, and your signature under the BGI Commons Constitution. Pick your skills honestly — they power team matching later.
Fig. 2 — Onboarding: three steps, about 90 seconds.
3. Pick a HyperSprint
Open HyperSprints and choose the active sprint (look for the Registration open badge). The sprint page has everything in one place: timeline, tracks, prizes, rules and FAQ. Read the tracks before forming a team — every team registers into exactly one.
Fig. 3 — The sprint page; the stepper shows where the sprint currently is.
4. Join or create a team
From the sprint page, press Team to reach the team directory. Two paths from here:
Join an open team. Browse or filter by track and the skills teams are looking for, then press Request to join and write a line about what you can take on. The captain reviews it — you'll get a notification either way.
Create your own. Press Create a team: pick a name, track, team size (1 = solo), the skills you're looking for, and optionally invite teammates by email straight from the modal. You become the captain and can transfer that later.
Fig. 4 — One team per sprint: join requests and invites both respect it.
5. Work in the team workspace
Your team page is the workspace: roster, open join requests (captain), invite link, and team settings — avatar, description, size, visibility, looking-for skills. Need more hands? Find teammates browses people looking for a team, and you can invite anyone from their profile page.
Fig. 5 — The captain approves requests and manages settings; members see the roster.
6. Submit your deliverables
Before the submission deadline (on the sprint page), the captain opens the team's Submissions tab and presses Submit deliverables. Add links to everything judges should see — repo, docs, demo — with a label and an optional comment each, plus your pitch video if the sprint requires one. You can edit and resubmit any time until the deadline; the team status flips to Deliverables Submitted.
Fig. 6 — Submissions are public; chat and files stay private to the team.
7. After the sprint
When the sprint ends the team goes read-only: roster and submission stay viewable, files stay downloadable for 30 days. Judging happens per track; results and rewards land on your dashboard and in notifications. Awarded teams appear with their placement — and everything you built stays linked from your profile for the next sprint.
Fig. 7 — The archived team view after the sprint closes.