# Hackathon project listing brief

Use this sheet to prepare your own portfolio page and record what happened to any event entry. Keep dashboard receipts with the team. Copy only the public-facing fields into the listing.

## Public listing draft

- Project name ____________________
- In one sentence, who can use it and what can they finish? ____________________
- Event build date and version (tag, release or recording) ____________________
- What someone could do in that build ____________________
- Which steps a person still performed by hand ____________________
- Portfolio revision date and version ____________________
- What changed after the event, and why? ____________________
- Authors and their contributions to each version, as they agreed to be credited ____________________
- Screenshots, code, recordings or sample data the team has permission to publish ____________________
- Synthetic examples used in place of private data ____________________
- Public project URL ____________________
- Public demo or recording URL and version ____________________

### One task a visitor can try

- Starting state (device, sample record and what should already be visible) ____________________
- Single task to give the visitor ____________________
- Expected observable result ____________________
- How to reset the demo for the next visitor ____________________
- Signed-out check date, version seen and whether the demo worked ____________________

## Team record of the event entry

If you only published a portfolio project, record “no event entry.” Use “unknown” when the dashboard or organizer has not confirmed a status.

- Event and link to its rules ____________________
- Official submission deadline and time zone ____________________
- Team member responsible for the event submission ____________________
- Team eligibility or check-in requirement, and what was confirmed ____________________
- Status shown inside this event’s dashboard, with date and time ____________________
- Exact event build tag, demo link or recording attached to that entry ____________________
- Where the team saved the private submission receipt ____________________
- Is the event gallery entry publicly visible? Date checked ____________________
- Is an organizer-only action needed (late entry, extension or correction)? ____________________
- What did the organizer explicitly permit, through which route and by what time? ____________________
- Status and version actually received after any permitted change ____________________
- Any separate judging result the organizer has confirmed ____________________

[Read the publication guide and worked tool-library example](https://creditable.vc/guide/hackathon-project-after-deadline).
