Clear answers for hackathon teams.

Teams must have 3 to 5 participants. Every participant must be individually registered on the GDG portal before the hackathon starts, and one participant can be a member of only one team.

Each participant registers individually on the official GDG Tashkent hackathon page before the event. After the hackathon starts and teams form, the team lead registers the team once at ai.gdgtashkent.uz.

The team lead submits the team registration form, confirms access to the team dashboard, and submits final materials. Organizers and checkpoint volunteers record checkpoints in the admin dashboard.

Yes. Join the Day 1 team formation, track selection, and idea refinement block. Teams finalize members, select one track, and prepare for Checkpoint 1 before lunch and early afternoon checks.

Only with organizer approval. Track changes may affect loyalty point eligibility and judging room allocation.

Yes. The venue closes after the Day 1 19:00 block and after the Day 2 18:00 awards block unless organizers announce otherwise, but teams may continue remotely. Official on-site support, mentor access, and organizer assistance are not guaranteed after venue closure.

Yes, if the resources are open-source or public and properly disclosed. The project itself must be built during the hackathon, and the final repository must clearly show the team's work.

Teams do not self-submit checkpoints. Organizers or assigned checkpoint volunteers visit teams, verify presence and progress, ask required questions, and mark results in the admin dashboard.

Report the issue to organizers immediately and before the relevant deadline. Organizer or platform-caused issues may be treated as exceptions only if they are logged before the deadline.

The team lead can submit final materials only after organizers mark Checkpoints 1, 2, and 3 as passed. The submission must include a Google Slides link, a public GitHub/GitLab repository link, project summary, and required confirmations for template use, viewer access, public repository access, README presence, and public/sponsor review use. Demo URL, access notes, organizer notes, and loyalty evidence are optional when relevant.

Yes. Final submissions must include a Google Slides presentation link only, and the slides must use the official presentation template. PDF, Canva, PowerPoint, image, or other presentation formats are not accepted.

The team may be disqualified. Teams must verify Google Slides sharing, repository visibility, demo links, README completeness, and official template use before the May 24, 14:00 deadline.

Yes. Final submitted Google Slides and GitHub/GitLab repositories are expected to remain public and accessible after the hackathon. Organizers and sponsors may view, reference, demonstrate, share, and use submitted public materials for hackathon-related review, recap, promotion, and follow-up. Do not submit confidential information, secrets, private datasets, or materials you do not have the right to publish.

Final presentations run from 14:30 to 17:00 in 3 rooms in parallel by track. Each team has 4 minutes total: 3 minutes for pitch and demo, then 1 minute for judge Q&A. Time limits are strictly enforced.

Judges score teams out of 100 points: Innovation & Creativity 30, Problem-Solution Fit 20, Presentation & Completeness 20, and Technical Execution & Code Evaluation 30. Eligible loyalty points are added after the judging score.

Organizers compare Ideathon records with the hackathon team's selected track, core idea, and majority same-member conditions. Loyalty points do not stack, and organizers make the final eligibility decision based on records and submitted evidence.

No. Organizers, mentors, judges, and official event staff cannot participate as team members.