Once you choose a competition, preparation should produce a reliable submission, a defensible demonstration and a follow-up record. This checklist covers delivery; use the hackathon-versus-pitch decision guide if the event choice is still open.
Create a rules and deadline record
- Save the organiser’s current eligibility and judging criteria.
- Confirm the deadline, time zone and submission channel.
- Record limits on prior work, outside assistance, team size and demo length.
- Check ownership, confidentiality, publicity and sponsor terms.
- Name the person responsible for final submission and confirmation.
Do not rely on last year’s rules or a teammate’s recollection. Keep the authoritative event link in the preparation record and resolve unclear conditions with the organiser.
Define the smallest credible demonstration
For a build event, select one user journey that demonstrates the core idea. Label mock data, simulated components and unavailable integrations clearly. For a pitch event, connect the problem, customer evidence, proposed solution, business model and next milestone without claiming validation that has not occurred.
An illustrative logistics demo might show how a dispatcher assigns one delivery using test data. It should not imply that live route optimisation, customer notifications and fleet integrations are operational if those parts are simulated.
Assign delivery roles
| Role | Owned output | Check |
|---|---|---|
| Submission owner | Final files and form | Acceptance receipt retained |
| Demo owner | Repeatable user journey | Run on the presentation device |
| Evidence owner | Claims and supporting material | Sources match what is stated |
| Presenter | Timed explanation and questions | Rehearsal within the event limit |
Rehearse failure as well as success
Test the actual presentation environment where possible. Prepare a permitted backup such as screenshots or a local recording, and identify it honestly if used. Check that no private credentials or customer information appear on screen. Reserve time to submit before the deadline rather than treating the last minute as a normal target.
Turn feedback into follow-up work
Record each objection, who raised it, the evidence behind it and whether it concerns customer need, technical feasibility or presentation. Assign a next action and date. A judge’s positive comment is not a purchase commitment; a contact’s interest is not investment.
Use the weekly milestone review to check what the event actually changed. More launch resources are in the Business section.
