Skip to content
SIH Buddyby Ganeev Singh
Dev

🔥 Roast My Pick · SIH26238

Unified Scholarship Mobile Application for Tribal Students

Ministry of Tribal Affairs

Medium35/100

Reasonable choice. The scoreboard liked it. The scoreboard is not the one asking questions on the day.

Worth considering. Precisely specified and genuinely useful, but the differentiating verification integrations are exactly what you must mock — build a credible, well-architected verification layer and an excellent student-facing UX, and be clear how this differs from its administrative sibling SIH26239. Roughly 120–270 teams are expected to go here.

The receipts

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

  1. Exhibit A

    The differentiating value — verification against AISHE, UDISE+, APAAR, UIDAI, UGC-NTA — needs integrations a student team cannot access, so it must be mocked and framed honestly

  2. It gets worse

    It overlaps SIH26239 from the same ministry, so be clear this is the student-facing unified app and that one is the administrative management system

  3. Still reading?

    A unified-dashboard-over-existing-systems is a familiar shape, so UX quality and the verification architecture must carry the differentiation

  4. And the finisher

    Handling ST/PVTG, income and identity data raises real privacy and correctness expectations even in a prototype

The damage report

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

  • Feasibility

    3/5

    Buildable. Not comfortably. There is a week in here you have not planned for yet.

    The app, dashboard, document wallet and chatbot are standard build work, but the core value — API-based verification against DigiLocker, AISHE, UDISE+, APAAR, UIDAI and UGC-NTA — depends on integrations a student team cannot actually access, so those must be mocked, and a judge knows the real difficulty and value lives in integrations you can only simulate.

  • Innovation scope

    2/5

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

    A unified dashboard-plus-chatbot over existing scholarship systems is a well-defined integration-and-UX product, and the description prescribes it in detail, so there is little novel design beyond the verification-layer architecture.

  • Clarity

    5/5

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

    Exceptionally detailed: the five schemes, the three source systems, the named data sources to integrate, the dashboard, wallet, chatbot and verification-layer requirements, and even the unreached-beneficiary matching are all specified.

  • Acceptance potential

    3/5

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

    Genuinely useful and precisely specified, and the consolidation directly solves a real fragmentation pain, but the differentiating value — real verification integrations — is exactly what a student team must mock, it overlaps SIH26239 from the same ministry, and a unified-portal dashboard is a familiar shape, so the win is a credible, well-architected verification layer and a genuinely good student-facing UX.

  • Effort

    Heavy

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

    A multi-scheme dashboard, DigiLocker wallet, multilingual chatbot and a verification-integration layer (mostly mocked) is a solid full build, though every piece uses standard components.

  • Demo-ability

    Medium

    Demoable, if you rehearse it. Nobody rehearses it.

    The consolidated dashboard and the auto-verify-or-route-to-review flow demo well, but the verification against real government sources is mocked, so the demo shows the architecture rather than live integration.

The demo they will have already seen

Somewhere around 120–270 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 consolidation across five schemes and three portals directly solves a real, concrete fragmentation pain students face
  • DigiLocker integration and document reuse are genuinely buildable and immediately useful
  • Routing verification mismatches to manual review rather than blocking is a mature, sensible design the description asks for

Nothing here is fatal. It is just the list of places this statement pushes back, and you now get to push there first.

Full analysis ↗Roast another

The framing is a joke. The findings are not — they are the same analysis on the statement page, and every line above is attached to a score or a fact in the record. It is one opinion with its reasoning attached, so argue with it before you trust it.