A complete submission consists of three components. All three must be finished by the Day 7 deadline. A Devpost project page alone does not constitute a submission.

1. Devpost Project Page

Each team must publish a project page to the Blueprint hackathon page. The page must state the problem identified, the proposed solution, an implementation outline addressing cost and timeline, and the names of all team members. The solution artifact must be attached to or linked from this page, whether as an uploaded file, an embedded design link, or a repository link. The project page must be published rather than saved as a draft. 

2. Recorded Presentation

Each team must record a presentation of no more than 8 minutes explaining the solution and the reasoning behind it. Where practical, each team member should appear or speak.

The recording must be uploaded to YouTube with the visibility set to Unlisted. Recordings set to Private cannot be accessed by the judging panel and will not be scored. Teams are advised to test the link in a private browsing window before submitting.

3. Official Submission Form

The submission form is the step that formally enters a team into the competition. The form requires the team name; the names, ages, schools, and countries of all members; a team contact email address; the Devpost project link; the YouTube presentation link; an artificial intelligence usage disclosure; and confirmation that the team has read and accepts these rules.

A confirmation email will be sent within 24 hours of submission. Teams that do not receive confirmation should contact the Organizers immediately rather than assume the submission was received.

Teams may resubmit the form at any point before the deadline; the most recent entry will be treated as final.

Submission Checklist

• Devpost project page published

• YouTube recording

• Presentation within the stated time limit

• All team members named

• Contact email address monitored

• Submission form completed and confirmation email received