Dates
May 23-24
Two-day competitive hackathon.
Hackathon
The official May 23-24 hackathon flow.
Teams form, lock one EdTech track, complete organizer-led checkpoints, submit official final materials by 14:00 sharp, and present working AI EdTech MVPs.
Overview
A build-first weekend with clear control points
The event maximizes build time while keeping fairness through team registration, organizer-led checkpoints, final submission discipline, and a transparent judging flow.
Venue
New Uzbekistan University
Day 1 closes at 19:00; Day 2 closes after the 18:00 awards block unless organizers announce otherwise.
Format
Build-first
Short mandatory briefings, mentor support, and dashboard checkpoints instead of long Day 1 workshops.
Tracks
3 EdTech tracks
Corporate Education, Public and Higher Education, and General Education.
Tracks
Choose exactly one EdTech track
Track selection locks at Checkpoint 1 unless organizers explicitly approve a change. Each team submits exactly one project.
Corporate Education
Companies, HR teams, L&D teams, employee onboarding, internal training, and compliance learning.
Public and Higher Education
Universities, public institutions, faculty, administrators, students, and researchers.
General Education
Schools, private learning centers, parents, teachers, young learners, and independent learners.
Checkpoints
Organizers verify progress at the venue
Checkpoint submissions are not self-submitted by teams. Organizers or assigned checkpoint volunteers visit teams, ask required questions, verify presence, and record results in the admin dashboard.
Day 1, 13:30-14:15
Checkpoint 1: Team and Idea Lock
Verify majority attendance, 3-5 members, individual GDG registration, selected track, one EdTech project idea, project starts at the hackathon, and loyalty claim if applicable.
Day 1, 17:30-18:15
Checkpoint 2: MVP Plan and AI Usage
Review demoable MVP scope, core AI feature, APIs/models/libraries, repo status, realistic scope, risks, and mentor blockers.
Day 2, 11:30-12:00
Checkpoint 3: Demo Readiness
Confirm demo flow, Google Slides preparation, GitHub/GitLab repo and README readiness, AI feature status, final submission awareness, and link risks before 14:00.
Day 2, 13:30-14:00
Final submission: Dashboard Lock
Team lead submits Google Slides and GitHub/GitLab links through the team dashboard. Organizers verify access after the 14:00 lock.
Presence rule
Teams must have a majority of registered members physically present during checkpoint verification unless organizers approve an exception.
Final submission unlocks only after Checkpoints 1, 2, and 3 are marked passed by organizers.
3 members
2 present minimum
4 members
3 present minimum
5 members
3 present minimum
Final Submission
Final materials lock at 14:00 sharp on May 24
The portal opens at 13:30. Teams should upload early, verify every link, and finish before the hard deadline. Permission fixes after the deadline may not be accepted.
Required package
- Google Slides presentation link only. PDF, Canva, PowerPoint, image, or other deck formats are not accepted.
- Official presentation template copied and used for final slides.
- Slides sharing set to Anyone with the link - Viewer.
- Public GitHub/GitLab repository accessible by link at and after the deadline.
- README.md with problem context, setup/run instructions, required environment variable placeholders, and demo notes if needed.
- Project summary, optional demo access notes, and public/sponsor review confirmation.
- Loyalty claims, if applicable, should be preclaimed separately in the team dashboard before Checkpoint 1.
Deadline rules
Final links are judged as submitted at the 14:00 deadline. Broken, private, restricted, wrong-format, or inaccessible links may disqualify the team.
Any platform issue must be reported to organizers before the deadline, not after judging begins.
Presentations
4 minutes per team, strictly enforced
Final presentations run from 14:30-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. Teams should prioritize a working demo over long slides.
3 minutes
Pitch + demo
Problem, user, solution, AI implementation, live or recorded demo, and impact.
1 minute
Judge Q&A
Focused clarification questions.
100-point judging rubric
Judges evaluate teams out of 100 points. Eligible loyalty points are added after the 100-point judging score.
Innovation & Creativity
Originality, quality of idea, creative AI use, and differentiation from standard solutions.
Problem-Solution Fit
Clarity of the EdTech problem, selected-track relevance, target user understanding, and practical usefulness.
Presentation & Completeness
Demo quality, story clarity, MVP completeness, and ability to explain value and implementation.
Technical Execution & Code Evaluation
Working implementation, architecture quality, AI integration, reliability, repository quality, README clarity, and build/run evidence.
Ideathon loyalty points
Loyalty points do not stack. Teams receive only the highest eligible category, and organizers make the final eligibility decision.
1st place Ideathon team in the same track+5 pts
2nd or 3rd place Ideathon team in the same track+3 pts
Other successful Ideathon finisher+1 pts
Eligibility requires the same track, the same core idea, and a majority of the same members from the Ideathon team.