Hackathon submission acceptance checklist
Check judge access, preserve the submitted commit and reproduce a documented demo. Copy the acceptance record and track each blocked step.

Check judge access, preserve the submitted commit and reproduce a documented demo. Copy the acceptance record and track each blocked step.

A reusable record for checking whether a submitted project is accessible and whether its documented scenario can be reproduced. Technical acceptance does not determine a competition score or confirm production readiness.
For each submission, copy the record below into your event's approved working space. Use a submission identifier instead of participant names. Keep private links, credentials, recordings and raw logs in the approved restricted location.
Copy these fields into your working record. Replace each bracketed value with the result of your check.
submission_id: [identifier]commit: [full submitted commit]environment: [OS and required tool versions]route: [local reproduction or hosted demo]input: [safe sample reference]steps: [documented sequence]expected: [observable result]observed: [what happened]blocked_at: [step or none]evidence: [approved restricted reference]fallback: [what a recording showed; what remains untested]status: [reproduced | access_blocked | runtime_unconfirmed | partial]next_action: [specific action]responsible_role: [event role]approval_reference: [authorized decision or none]Do not put secrets or personal data in this record. A passing scenario confirms only the stated scenario in the recorded environment. A video does not confirm behavior on a new input. Preserve the original evidence when a repair is approved.
Take it further
Open the JSON template and validator