Free printable

Hackathon Calendar Template — Free Printable Web3 Event Tracker

Free

Most hackathon misses are deadline misses. You pick an event, bookmark the page, and by the time you check back the submission window closed three days ago. This template fixes the tracking part: one printable sheet with every event you're watching, its deadline in your own timezone, and a checkbox that only gets filled when the submit button actually worked.

Event tracker — 12 slots

My hackathon tracker

#EventDatesSubmission deadlineFormatSubmittedResult
1write-inwrite-inwrite-inonline / IRLwrite-in
2write-inwrite-inwrite-inonline / IRLwrite-in
3write-inwrite-inwrite-inonline / IRLwrite-in
4write-inwrite-inwrite-inonline / IRLwrite-in
5write-inwrite-inwrite-inonline / IRLwrite-in
6write-inwrite-inwrite-inonline / IRLwrite-in
7write-inwrite-inwrite-inonline / IRLwrite-in
8write-inwrite-inwrite-inonline / IRLwrite-in
9write-inwrite-inwrite-inonline / IRLwrite-in
10write-inwrite-inwrite-inonline / IRLwrite-in
11write-inwrite-inwrite-inonline / IRLwrite-in
12write-inwrite-inwrite-inonline / IRLwrite-in

Fill the deadline column in your local time plus the organizer's timezone, e.g. "Sep 27, 23:59 UTC (Sep 28, 06:59 my time)". Tick "Submitted" only after the platform confirms receipt. Hit Ctrl+P (or Cmd+P) to print this sheet.

Deadline hygiene

Track submission cutoffs, not event end dates. Many hackathons list a final day, but the project submission form closes earlier, and some close a full day before the closing ceremony. Write the actual form-closing time from the event page, then convert it to your timezone and put both on the sheet. Timezones are where most people slip: a "23:59 deadline" is 23:59 somewhere, and if that somewhere is UTC, an evening in Jakarta or a morning in New York can already be too late. Check the deadline the day before, not the day of, because organizers do move cutoffs and announce it in Discord channels you may not have open.

Prep checklist — do these before kickoff

4 tips for first-time hackers

Opinions, from watching a lot of submissions land:

  1. Scope small. One feature that works end-to-end beats three that almost work. Judges can only score what runs.
  2. Sleep at least once. All-nighters feel committed but they show up in the demo: wrong clicks, forgotten steps, dead air. A rested team demos better than a heroic one.
  3. Submit an ugly version early. Get a rough project in hours before the cutoff, then polish. A submitted 7/10 beats an unsubmitted 9/10, every time.
  4. Talk to mentors mid-event. Ask for feedback while you can still change direction, not in the last Q&A slot when it's too late to act on it.

Results log — 6 rows

Results & what to reuse

EventDateResultWhat I'd reuse next time
write-inwrite-inwin / placement / feedbackwrite-in
write-inwrite-inwin / placement / feedbackwrite-in
write-inwrite-inwin / placement / feedbackwrite-in
write-inwrite-inwin / placement / feedbackwrite-in
write-inwrite-inwin / placement / feedbackwrite-in
write-inwrite-inwin / placement / feedbackwrite-in

The reuse column is the valuable one. Contracts, design assets and pitch structure from one hackathon feed the next one, so note them while fresh.

Want the events pre-filled?

This template gives you the structure. If you'd rather not hunt down 45 events yourself, the 2026 Web3 Events & Hackathons Calendar lists them with dates, locations, ecosystems and official registration links, ready to copy into the tracker above.

Get the full 2026 Web3 Events & Hackathons Calendar →

one-time · CSV + Markdown · checkout on Getly

Also on this site: the Web3 Remote Jobs & Hiring Database and the full catalog.