Final submission checklist

Draft status: this is initial content, not reviewed domain expertise yet.

The first principle

Final submission is operational risk. The project can be good and still lose value because the links, video, repository, or description fail to communicate.

The final hour should not be a creative writing session. It should be a controlled handoff.

Freeze the artifacts

• Project name.
• One-line description.
• Demo URL.
• Repository URL.
• Video URL.
• Slide deck URL.
• Team member names.
• Sponsor or track requirements.

Submission sequence

1. Read the submission form before the last hour.
2. Put all answers in a shared document first.
3. Make every link public or accessible.
4. Test links in an incognito window.
5. Export the video and verify audio.
6. Submit before the final minute.
7. Screenshot the confirmation page.

Draft quality bar

The submission should answer the same story as the pitch: who it helps, what changes, what was built, and why the hackathon context matters.

Avoid turning the submission into a feature inventory. The reader should understand the project even if they never saw the live pitch.