Files
OKF_Vault/knowledge/events/preselection-prepitch.md
Noel Sabia c02d2ea621
release-please / release-please (push) Failing after 3s
feat: add final pitch format and scoring
Document the Sunday 15 November 14:00 final: 8-minute pitch, 8 minutes of questions, and scoring of idea and implementation (50%), pitch and storytelling (30%), and vision (20%). Link it from the preselection and event indexes.
2026-11-13 18:30:32 +01:00

105 lines
5.3 KiB
Markdown

---
type: Hackathon Event
title: "Preselection | TechCampus — Sunday pre-pitch"
description: Sunday preselection schedule for the Future City Hackathon 2026, including the pitch mission, the selection criteria, the 13:00 submission deadline, and advancement to the final jury pitch.
tags: [event, future-city-hackathon-2026, preselection, prepitch, pitching, judging, criteria, techcampus]
status: stable
generated: { by: opencode/deepseek-v4.1-flash, at: 2026-11-13T17:29:44Z }
---
# At a glance
| Field | Value |
|---|---|
| When | Sunday, from 10:00 (see the date note below) |
| Where | TechCampus, Heilbronn University of Applied Sciences |
| Format | In-person pitch, live demonstration, and explanation |
| Submission deadline | 13:00 — stop hacking and submit the final presentation and code |
| Outcome | Each challenge provider selects the best solution from its teams; the selected team advances to the [final pitch](/events/final-pitch.md) in front of the jury |
| Selection criteria | **Idea:** problem and benefit, originality, feasibility and future. **Implementation:** reliability, understanding of your own solution, teamwork, documentation, choice of technology. |
| Preparation | Arrange a time slot with your challenge provider on Saturday; bring a pitch deck and a working version of the solution |
# Schedule
| Time | Session | What happens |
|---|---|---|
| From 10:00 | Make a strong first impression | Meet your challenge provider and showcase your solution. |
| Until 13:00 | Final touch-ups | Fix any remaining minor issues and rehearse the final pitch. |
| 13:00 | Stop hacking | Submit your final presentation and code. |
| From 13:00 | Preselection | Each challenge provider selects the best solution from its teams. The selected team advances to the final pitch in front of the jury. |
# Your mission
**Pitch. Demonstrate. Explain.** Present your idea, demonstrate your solution, and explain what makes it stand out.
To do that:
- Be there in person.
- Arrange your time slot with your challenge provider on Saturday.
- Have your pitch deck and a working version of your solution ready.
# Selection criteria
The preselection slide groups the criteria into two parts. It names the criteria only; the guidance column is an interpretation to help prepare the pitch.
## Part A — The idea
| Criterion | What to demonstrate |
|---|---|
| Problem and Benefit | The problem is real, the target user is clear, and the solution creates a benefit worth caring about. |
| Originality | The idea is distinctive rather than a generic dashboard or an off-the-shelf wrapper. |
| Feasibility and Future | The solution can realistically be built and operated, and it has a credible path beyond the hackathon. |
## Part B — The implementation
| Criterion | What to demonstrate |
|---|---|
| Reliability | The demo works consistently, including with realistic data and conditions. |
| Understanding of Your Own Solution | The team can explain how it works, why it works, and where it breaks. |
| Teamwork | The team can show how it collaborated, divided the work, and integrated the pieces. |
| Documentation | The code, setup, and approach are documented clearly enough for someone else to understand and run. |
| Choice of Technology | The technology fits the problem, the data, and the deployment constraints. |
# Checklist
## Logistics
- [ ] Time slot arranged with the challenge provider on Saturday.
- [ ] Pitch deck ready.
- [ ] Working solution ready to demonstrate.
- [ ] Remaining minor issues fixed and pitch rehearsed before 13:00.
- [ ] Final presentation and code submitted at 13:00.
- [ ] Team present in person for the preselection.
## Criteria evidence
- [ ] A clear problem statement and user benefit.
- [ ] A clear statement of what is original about the idea.
- [ ] Evidence that the solution is feasible and has a future path.
- [ ] A reliable live demonstration.
- [ ] A clear explanation of how the solution works and where it fails.
- [ ] A short teamwork story.
- [ ] Documentation ready to hand over.
- [ ] A justification for the technology choices.
# How the preselection works
Each challenge provider selects the best solution from the teams working on its challenge. The selected team advances to the [final pitch](/events/final-pitch.md) in front of the jury.
| Challenge provider | Challenge |
|---|---|
| AI TRAQC | [Measure where it matters](/challenges/ai-traqc-sensor-placement.md) |
| aim | [Learning Guide](/challenges/aim-learning-guide.md) |
| HNVG | [LoRaWAN network planning](/challenges/hnvg-lorawan-network-planning.md) |
| PreZero | [WasteRouting.AI](/challenges/prezero-waste-routing.md) |
| Schwarz Digits | [Pulse of the City](/challenges/schwarz-digits-pulse-of-the-city.md) |
| Stadt Heilbronn | [Riding the Sentiment](/challenges/stadt-heilbronn-cable-car-sentiment.md) |
# Date note
The preselection slide says "Sunday" and "Saturday" but does not print calendar dates. The [final pitch slide](/events/final-pitch.md) confirms **Sunday, 15 November 2026**, so the preselection is on the same day. Confirm the exact time slot with the organizer.
# Source
The schedule comes from the organizer's "Preselection | TechCampus" slide, and the criteria come from the "Criteria Preselection" slide. Both were supplied on 2026-11-13. No file copies of the slides are stored in this repository.