A digital platform to crowdsource societal challenges and facilitate collaborative problem solving through universities and industry partnerships

The receipts 🧾

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

1. Exhibit A

   The platform organises problem-solving rather than solving anything, so in a five-minute pitch you are asking a judge to imagine the value rather than see it

2. It gets worse

   This is structurally identical to the placement and collaboration portals that appear at every hackathon, and judges recognise the shape immediately

3. Still reading?

   Faculty expertise directories for Jharkhand's institutions do not exist as data, so the routing module — the whole point of the platform — runs on a directory you fabricated

4. And the finisher

   Seven modules for four user types is far beyond what can be built well, and the usual outcome is seven login screens and one working flow

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.

  Nothing here is technically out of reach — submission, text classification, deduplication and workflow routing are all standard, and the classification can be trained on public civic complaint corpora, though matching problems to faculty expertise needs an institutional capability directory that does not exist and would have to be assembled.

• Innovation scope

  2/5

  Nothing here is new. Your only edge is execution — and execution is also everyone else's only edge.

  Seven components are enumerated in full, each with its own capability list, so the platform architecture is entirely determined and your only real design decisions are inside the classification and routing logic.

• Clarity

  4/5

  The ask is unambiguous, which quietly removes your favourite excuse.

  The modules, the stakeholder types, the thematic domains and the analytics contents are all specified in detail, but the statement never defines what a good routing decision is or how solution quality is judged, which is the outcome the whole platform exists to produce.

• Acceptance potential

  2/5

  The numbers do not like you. Bring something the numbers cannot see.

  This is a coordination portal whose only technical substance is a text classifier, structurally the same shape as the placement and marketplace portals that judges see repeatedly, and it is meta — a platform for organising problem-solving rather than solving a problem, which is a much harder thing to make anyone care about in a five-minute pitch.

• Effort

  Massive

  A semester of work wearing a hackathon costume. Something is getting cut; decide what now, not in week five.

  A citizen app, a classification and deduplication engine, a routing service, separate university and industry portals, a project lifecycle tracker, an analytics dashboard and a notification system is seven products for four distinct user types, and even stubbing them all consumes the whole event.

• Demo-ability

  Medium

  Demoable, if you rehearse it. Nobody rehearses it.

  The submit-classify-route sequence is demonstrable and the deduplication moment is mildly satisfying, but nothing here produces an outcome a judge can feel — the platform's actual value only materialises months later when a project finishes.

• 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 🪞

Enough teams are heading here to fill the 500-idea cap before entry even closes, 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.

• Deduplication of near-identical citizen reports is a genuinely useful and demonstrable capability, and it is the one part of this statement with real technical content — twenty people reporting the same broken handpump should become one challenge, not twenty
• Public civic complaint corpora exist, so the classifier can be trained and evaluated on real citizen-written text rather than synthetic samples
• The NEP 2020 framing gives the statement institutional backing that a state sponsor will recognise