Student Innovation

The receipts 🧾

Every red flag on this statement, in full. These are the four places it bites.

1. Exhibit A

   The description defines a theme, not a problem — you must supply the actual problem, users and success criteria yourself, and a vague idea reads as vague

2. It gets worse

   Open-theme tracks attract a very wide field of submissions, so a generic or common idea disappears against genuinely novel ones

3. Still reading?

   With no acceptance criteria given, judging leans heavily on originality and execution, so a polished but unoriginal idea underperforms

4. And the finisher

   It is easy to over-scope when nothing constrains you, and an ambitious idea left half-built loses to a focused one that works

The damage report 📉

Every score this statement earned, and what each one actually costs you.

• Feasibility

  4/5

  Actually buildable, which on this slate is rarer than it sounds. Do not squander it on scope.

  Feasibility is entirely in your hands because you choose the scope — an open theme means you can pick an idea that is genuinely buildable with the data and skills you have, so a well-chosen project is very achievable and an over-ambitious one is not.

• Innovation scope

  5/5

  There is something genuinely new here. Do not bury it under another dashboard.

  The scope for innovation is total — nothing is prescribed, so the idea is entirely yours, which is both the opportunity and the challenge, since originality is exactly what an open-theme track is judged on.

• Clarity

  1/5

  Nobody is sure what is being asked, quite possibly including the people who asked it.

  There is no problem statement to be clear about — the description is a one-line theme, so all the definition of problem, users, scope and success criteria must come from you.

• Acceptance potential

  3/5

  Middle of the pack. This statement will not win the room for you — you will have to.

  Open-theme tracks are a double-edged pick: total freedom to play to your strengths, but a very wide field and judging that rests almost entirely on originality and execution, so a generic idea disappears while a genuinely novel, well-built one can stand out sharply — the outcome is entirely down to the idea you bring.

• Effort

  Heavy

  Heavy. Somebody on this team is not sleeping in week three. Pick who, on purpose.

  Effort depends entirely on the idea you choose, but a submission strong enough to place in an open-theme track generally needs a genuinely working, well-scoped build rather than a concept.

• Demo-ability

  Medium

  Demoable, if you rehearse it. Nobody rehearses it.

  Demo-ability is yours to determine — choose an idea with a concrete, visible outcome and it demos well, choose an abstract one and it will not, so pick for demonstrability from the start.

• Data

  None supplied

  No dataset comes with this one, so every accuracy figure you quote is a number about labels you invented.

  Nothing is provided with the statement. You are sourcing, cleaning and labelling it yourself, and that work is invisible in the demo but very visible in the questions.

The demo they will have already seen 🪞

Somewhere around 310–500 teams are heading here, and the description is doing the choosing for most of them. They will read the same brief, reach the same architecture, and build a version of the same demo you are planning. Being correct is the floor. If your five minutes could be swapped with the team before you and nobody in the room would notice, you have not picked badly — you have built predictably, which costs exactly the same and hurts more.

What survives 🛡️

The ground worth standing on when the questions start.

• The theme is wide open, so you can choose an idea that fits your team's actual strengths rather than being handed a fixed problem
• A well-scoped, genuinely working demo of a focused idea beats an ambitious half-built one — the freedom rewards discipline
• You control the scope entirely, so you can pick something achievable and polish it to a finish