hackathon submission checklist
---
title: Hackathon Submission Checklist
category: concepts
created: 2026-12-19
updated: 2026-12-21
tags: [hackathon-submission, project-validation, documentation, demo-preparation, technical-compliance, google-cloud-hackathon, rapid-agent-hackathon, verification-workflow, common-mistakes-prevention, deadline-management]
sources: [raw/conversations/2026-06-11-claude-code--code-hackathons-google-rapid-agent-hack-646b16a6.md]
confidence: high
---
# Hackathon Submission Checklist
Comprehensive validation framework for hackathon project submissions, focusing on technical compliance, documentation quality, and presentation readiness. Critical for avoiding common disqualification scenarios and maximizing competitive positioning.
Based on google-cloud Rapid Agent Hackathon requirements with generalizable principles for all competitive coding events.
## Universal Submission Requirements
### Technical Compliance
✅ **Required technology actually implemented** - Not just named in README, must be imported and called at runtime
✅ **Hosted project URL works** - Live, accessible application that judges can interact with
✅ **Public repository** - Open source license visible in About section
✅ **Clear setup instructions** - README with precise installation and run steps
### Documentation Package
✅ **Demo video** - Under time limit (typically 3 minutes), public on YouTube/Vimeo
✅ **Feature description** - Clear explanation of functionality, tech stack, and learnings
✅ **Team members listed** - All contributors properly credited in submission
✅ **Partner track selected** - For sponsored hackathons with multiple tracks
### Deployment Validation
✅ **End-to-end functionality** - Complete user stories work as demonstrated
✅ **Error handling** - Graceful failure modes for common edge cases
✅ **Performance testing** - Application responds within reasonable time limits
✅ **Mobile compatibility** - If applicable, works on mobile devices
## Common Failure Modes
### Technical Violations
1. **Ghost Integration**: Naming required technologies in documentation without actual implementation
2. **Broken Deployment**: Non-functional hosted URLs that return 404 or crash
3. **Environment Dependencies**: Application requires secret keys or local setup not provided to judges
4. **Competitor Technology**: Using prohibited services alongside required stack
### Submission Gaps
1. **Missing Demo Video**: Most critical component often forgotten until last minute
2. **Incomplete Team Info**: Forgetting to list all team members in submission form
3. **Wrong Partner Track**: Selecting incompatible sponsor track or none at all
4. **Late Documentation**: Poor README that doesn't explain setup or features
## Time Management Strategy
### Final Day Workflow
- **Morning**: Technical compliance verification using [full-story-verification](/concepts/full-story-verification)
- **Midday**: Demo video recording and documentation writing
- **Afternoon**: Final deployment testing and submission form completion
- **Buffer Time**: Reserve 2-3 hours before deadline for unexpected issues
### Crisis Protocols
- **Deployment Failure**: Have backup Vercel/Netlify deployment ready
- **Demo Recording Issues**: Pre-record multiple versions, test video upload
- **Feature Incompletion**: Document what works rather than hiding broken features
- **Technical Debt**: Clean up only user-visible bugs, leave internal code as-is
## Verification Workflows
### Automated Testing
```bash
# Full stack verification
npm run build # Ensures production build works
npm run test # Validates core functionality
vercel deploy --prod # Tests production deployment
Manual Validation
- Fresh Browser Test: Open incognito window, test complete user journey
- Mobile Device Check: Test on actual phone/tablet if mobile-targeted
- Network Simulation: Test on slow connections if performance-critical
- Judge Perspective: Follow setup instructions from README without prior knowledge
Google Cloud Specific Requirements
For google-cloud hackathons requiring Gemini + Agent Builder + MCP Server:
- Verify all three technologies are actually imported and invoked
- Remove any competing AI services (OpenAI, Anthropic) from codebase
- Test MCP server integration with concrete function calls
- Validate Agent Builder configuration is properly deployed
Documentation Template
# Project Name
## Overview
[2-3 sentence description of what the project does]
## Tech Stack
- Google Cloud Agent Builder
- Gemini Pro
- [Partner] MCP Server
- [Additional technologies]
## Setup Instructions
1. Clone repository
2. Install dependencies: `npm install`
3. Set environment variables: [list required vars]
4. Run locally: `npm run dev`
5. Access at: http://localhost:3000
## Demo
[Embed YouTube video or link]
## Features
- [Feature 1 with brief description]
- [Feature 2 with brief description]
- [etc.]
## Learnings
[What did you discover building this?]
See also