Organization Clock - Eastern Time (ET) ()
Hack University Hacker Guide

Submission Requirements

Use this page as the final packaging guide for your team. It covers GitHub structure, demo videos, slides, Devpost, live presentation timing, and the last checks judges expect before review.

Back to Hacker Guide Judging Criteria Rules

Before You Submit

This submission flow applies to all three competition paths: Technical Competition, Start-Up Competition, and Analytics Competition. Opening ceremony and live demos run through codecrunch-zoom.vercel.app (Zoom Meeting button will be enabled before the event starts. Access it at the event calendar), and teams should review the event agenda regularly for updates.

Competition Framework

Your repo, slides, video, and presentation story should make your competition type obvious so judges can review the project in the right context.

Submission Flow

Follow these four steps in order. The goal is simple: give judges one clean, public package with working links, clear documentation, and enough media to understand the project quickly.

1

Create the Public GitHub Repo

  • Make the repository public and include all source files.
  • Add a `README.md` with project description, setup, usage, features, technologies, and theme alignment.
  • State the competition type clearly: Technical, Start-Up, or Analytics.
  • Organize folders for source, slides, videos, screenshots, datasets, diagrams, and branding assets.
2

Prepare Slides and Live Demo Material

  • Upload an exported slide file in `ppt`, `pptx`, or `pdf` format.
  • Include a public Google Slides link for the live presentation.
  • Recommended slide flow: team and title, problem, solution, workflow or business model, impact and citations.
  • If your team misses the live slot, the video may be used, but the live presentation score can drop to zero due to absence.
3

Add Both Demo Videos

  • Create a 10-minute feature demo showing the full build and completed work.
  • Create a 5-minute backup video for quicker judge review or replay.
  • Upload both videos as MP4 files and include public links.
  • Keep the same video links visible on GitHub, slides, and Devpost.
4

Finalize README and Devpost

  • List team members, contributions, screenshots, slide links, and both video links.
  • Cite AI tools, datasets, open-source code, or outside templates if used.
  • Submit the public GitHub repository and project details on Devpost before the deadline.
  • Use the same competition type and same working links everywhere.

Judge-Ready Checklist

These are the high-friction items that usually cause review delays. Fix them before judges open your project.

Public Repository

The repo is public and includes code, README, slides, video files or links, and supporting assets.

Two Demo Videos

The 10-minute feature demo and 5-minute backup demo are both uploaded as MP4 and publicly accessible.

Complete README

The README includes theme alignment, competition type, setup steps, technologies, features, team, screenshots, and citations.

Slide Access

The exported deck and the public Google Slides link are both included and open without requesting permission.

Devpost Match

Devpost uses the same project title, same competition type, and same repo, video, and slide links.

Live Demo Ready

Your team has checked the demo order, reviewed the event agenda, and is ready to join Zoom early. (Zoom Meeting button will be enabled before the event starts. Access it at the event calendar)

Final Verification

  • No broken links on GitHub, YouTube, Google Slides, or Devpost.
  • The competition type is visible in the README and Devpost description.
  • AI usage, data sources, and outside assets are cited clearly if used.
  • Judges can understand the project without asking for access permissions.
  • The team is ready for the live slot at codecrunch-zoom.vercel.app (Zoom Meeting button will be enabled before the event starts. Access it at the event calendar).

Need Help?

If something is unclear, fix it before submission instead of hoping judges can infer it. Use support channels early.

Submission Support

Use the live community channels for help with repo setup, link checks, slides, video access, or judging-readiness questions. Message the team on Discord or Microsoft Teams.

Discord support Microsoft Teams