Skip to content
SIH Buddyby Ganeev Singh
Dev

🔥 Roast My Pick · SIH26036

Development of an Online Verification System for Weighing and Measuring Instruments

Ministry of Consumer Affairs, Food & Public Distribution

Medium35/100

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

Worth considering. Completely achievable with a rare tangible demo in the QR scan, but it is one of several workflow portals this cycle, so make the certificate cryptographically real rather than decorative — that is the one thing here a judge can distinguish you on. Roughly 250–500 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

    Several statements this cycle are structurally the same product — registration, workflow, mobile capture, dashboard, audit trail — so the shape will be familiar to judges before you begin presenting

  2. It gets worse

    A QR code containing only a record identifier proves nothing and is easy to forge, so if you skip the signing you have built the appearance of verification rather than verification

  3. Still reading?

    Field verification happens in shops and weighbridge yards with poor connectivity, and the statement asks for mobile support without mentioning offline, so decide early whether you handle that or concede it

  4. And the finisher

    Four stakeholder portals means four sets of screens, and teams routinely build the officer view well and leave the other three as stubs

The damage report

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

  • Feasibility

    5/5

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

    Nothing here requires data you cannot get, a model you must train or hardware you must buy — registration, workflow, certificate generation, QR resolution and dashboards are all standard engineering, and the governing rules that define the process are published.

  • Innovation scope

    2/5

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

    The stakeholders, the workflow stages, the certificate format, the alerting, the dashboards and the mobile requirement are all enumerated, so the product is fully determined and your latitude runs to the certificate authentication design and little else.

  • Clarity

    5/5

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

    Comprehensively specified with the stakeholder roles, the process stages, the certificate requirements, the alerting behaviour and the functional requirement list all set out individually, and the statutory basis linked so the process itself is externally defined.

  • Acceptance potential

    3/5

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

    Clear, buildable and with one genuinely tangible demo moment in the certificate scan, but it is another government workflow portal in a cycle that has several, so it will be compared against structurally identical submissions and judged on execution rather than idea.

  • Effort

    Heavy

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

    Four distinct stakeholder portals, an application and scheduling workflow, a mobile field application, a certificate issuance and verification service, validity tracking with alerting and multiple dashboards is a broad build even though each part is individually routine.

  • Demo-ability

    Easy

    Easy to demo — and so is everyone else's. Working is the floor here, not the achievement.

    The QR scan is the moment — a judge takes out their own phone, scans a certificate you just issued and sees it verify, which converts an otherwise invisible workflow into something tangible in three seconds.

The demo they will have already seen

Somewhere around 250–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 QR certificate verification is a genuinely tangible demo in a category of statements that usually have none, and it takes a judge's own phone to complete
  • Signing certificates cryptographically rather than just encoding an ID in the QR is a real security decision that separates a considered submission from a superficial one — an unsigned QR that just contains a database key is trivially forgeable
  • The process is defined by published rules, so the workflow stages are externally validated rather than invented

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.