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 | Dates | Submission deadline | Format | Submitted | Result |
|---|---|---|---|---|---|---|
| 1 | write-in | write-in | write-in | online / IRL | write-in | |
| 2 | write-in | write-in | write-in | online / IRL | write-in | |
| 3 | write-in | write-in | write-in | online / IRL | write-in | |
| 4 | write-in | write-in | write-in | online / IRL | write-in | |
| 5 | write-in | write-in | write-in | online / IRL | write-in | |
| 6 | write-in | write-in | write-in | online / IRL | write-in | |
| 7 | write-in | write-in | write-in | online / IRL | write-in | |
| 8 | write-in | write-in | write-in | online / IRL | write-in | |
| 9 | write-in | write-in | write-in | online / IRL | write-in | |
| 10 | write-in | write-in | write-in | online / IRL | write-in | |
| 11 | write-in | write-in | write-in | online / IRL | write-in | |
| 12 | write-in | write-in | write-in | online / IRL | write-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.
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.
Opinions, from watching a lot of submissions land:
| Event | Date | Result | What I'd reuse next time |
|---|---|---|---|
| write-in | write-in | win / placement / feedback | write-in |
| write-in | write-in | win / placement / feedback | write-in |
| write-in | write-in | win / placement / feedback | write-in |
| write-in | write-in | win / placement / feedback | write-in |
| write-in | write-in | win / placement / feedback | write-in |
| write-in | write-in | win / placement / feedback | write-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.
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.