A mobile application and web platform that lets cooperative workers offer household and community services to customers while managing bookings and payments.
Ministry of Cooperation · National Council for Cooperative Training (NCCT) · Software
Signing in saves it for your whole team — everyone on your invite link sees the same two entries. Anything you shortlisted while signed out comes with you.
Decomposed from what the description asks for. Nothing added.
Service Provider Registration
Allows workers and societies to register and complete verification.
Customer Booking System
Enables customers to book and schedule services with geo-location matching.
Federation Dashboard
Provides administrators with an overview to manage workers and operations.
Multilingual Mobile App
Supports multiple languages so workers and customers can easily navigate.
AI Demand Forecasting
Allocates workforce based on predicted demand using artificial intelligence.
Both columns are read off the brief's own wording. Nothing here is inferred from the ministry's name.
The evaluators will check if you included all expected features such as skill profiling, geo-location matching, digital payments, and the administrative dashboard. They will test the multilingual capabilities and whether the platform correctly handles worker welfare and insurance integration points.
A jury can still ask about these. Decide them deliberately rather than by accident.
Generated from the brief's own wording and the competition's published rules — never from a guess about what this ministry prefers.
Which specific languages the mobile application must support?
The brief never answers this, so a panel will. Whatever you decide, say it the same way twice.
What payment gateway integration should be used?
The brief never answers this, so a panel will. Whatever you decide, say it the same way twice.
How worker identity and skill verification should be authenticated?
The brief never answers this, so a panel will. Whatever you decide, say it the same way twice.
Has any part of this been shown at a previous event, hackathon or college project?
The guidelines are explicit: your solution must not have appeared in any previous event or programme, of any sort. A recycled project is what a team under time pressure reaches for.
Each one is quoted from a gap in the brief, not a guess about your team.
No measurable target
The description lists expected features but never specifies quantitative targets for performance, accuracy, or adoption.
What the organisers attached, and what the brief assumes you can get.
Same organisation, same year. Reading two of theirs tells you more about what they care about than reading one.
Pick what you are about to do and copy the prompt. It carries the organisers' own wording, the constraints they never spell out, and an instruction not to invent requirements they never set.
Who has this problem, what already exists, and what you would have to find out.
The brief asks for service provider registration. How would you build that?
Decoded from SIH26089 itself — Allows workers and societies to register and complete verification. The brief asks for it by name.
The brief asks for customer booking system. How would you build that?
Decoded from SIH26089 itself — Enables customers to book and schedule services with geo-location matching. The brief asks for it by name.
The brief asks for federation dashboard. How would you build that?
Decoded from SIH26089 itself — Provides administrators with an overview to manage workers and operations. The brief asks for it by name.
The brief asks for multilingual mobile app. How would you build that?
Decoded from SIH26089 itself — Supports multiple languages so workers and customers can easily navigate. The brief asks for it by name.
The brief asks for ai demand forecasting. How would you build that?
Decoded from SIH26089 itself — Allocates workforce based on predicted demand using artificial intelligence. The brief asks for it by name.
Where does your data come from — a published source, one you collect, or one you generate?
No dataset is attached to this problem statement, so sourcing it is part of the work and nobody told you that.
Why not use what already exists? Name the closest thing to this that is already running.
A team that has not named the alternative themselves is answering this for the first time in the room.
Which single thing will you demonstrate end to end, start to finish, with nothing skipped?
Ours, not a rule: a narrow thing that fully works survives questioning better than a broad thing that half works. If nobody on the team can name it, that is the finding.
Show me this working: the evaluators will check if you included all expected features such as skill profiling, geo-location matching, digital payments, and the administrative dashboard.
This is the evaluator read for your problem statement, decoded from the brief's own wording.
Show me this working: they will test the multilingual capabilities and whether the platform correctly handles worker welfare and insurance integration points.
This is the evaluator read for your problem statement, decoded from the brief's own wording.