A web and mobile platform that lets users, officers, and test centres register, apply, schedule, and issue QR-coded digital certificates for weighing and measuring instruments.
Ministry of Consumer Affairs, Food & Public Distribution · Department of Consumer Affairs (DoCA) · 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.
Stakeholder Registration
Secure role-based login and profile management for instrument users, officers, and test centres.
Application and Workflow
Online submission of verification applications, document uploads, and scheduling of inspection tasks.
Digital Certificates
Generation of inspection records and QR-coded digital certificates with an online authentication system.
Alerts and Dashboards
Automated renewal reminders and monitoring dashboards for tracking verification status and pending tasks.
Mobile Field Support
Mobile application support for field officers to record verification observations and results.
Both columns are read off the brief's own wording. Nothing here is inferred from the ministry's name.
Evaluators will check role-based secure logins, QR-coded certificate generation and authentication, mobile field app support, and end-to-end workflow management from application to dashboard monitoring.
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.
Specific database schema requirements?
The brief never answers this, so a panel will. Whatever you decide, say it the same way twice.
Integration details with existing state systems?
The brief never answers this, so a panel will. Whatever you decide, say it the same way twice.
SMS or email gateway provider details?
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 specifies functional modules but provides no quantitative targets for performance, concurrency, or load times.
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 stakeholder registration. How would you build that?
Decoded from SIH26036 itself — Secure role-based login and profile management for instrument users, officers, and test centres. The brief asks for it by name.
The brief asks for application and workflow. How would you build that?
Decoded from SIH26036 itself — Online submission of verification applications, document uploads, and scheduling of inspection tasks. The brief asks for it by name.
The brief asks for digital certificates. How would you build that?
Decoded from SIH26036 itself — Generation of inspection records and QR-coded digital certificates with an online authentication system. The brief asks for it by name.
The brief asks for alerts and dashboards. How would you build that?
Decoded from SIH26036 itself — Automated renewal reminders and monitoring dashboards for tracking verification status and pending tasks. The brief asks for it by name.
The brief asks for mobile field support. How would you build that?
Decoded from SIH26036 itself — Mobile application support for field officers to record verification observations and results. The brief asks for it by name.
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: evaluators will check role-based secure logins, QR-coded certificate generation and authentication, mobile field app support, and end-to-end workflow management from application to dashboard monitoring.
This is the evaluator read for your problem statement, decoded from the brief's own wording.