Before and after
The same complaint, two journeys
The left column describes the public journey on the National Cyber Crime Reporting Portal as a citizen encounters it today. The right column is what this prototype does instead.
The same hour, twice
What each journey does with the sixty minutes after money moves.
The portal today
Bank is told · 45 min
- 1Choose a door
- 2Register with OTP
- 3Pick category, then sub-category
- 4Incident form
- 5Suspect details
- 6Your details
- 7Preview and submit
Here
Bank is told · 4 min
- 1Say what happened
- 2Freeze request out
- 3Details
- Filed · 12 min
- The rest of the hour belongs to the bank, not the form.
| Measure | Today | This prototype |
|---|---|---|
| Entry points to choose from | 3 | 1 |
| Steps before you can describe the problem | 3 | 0 |
| Login required to start | Yes | No |
| Category chosen by | You | Us — you confirm |
| Money-freeze before full form | No | Yes |
| Status detail | “Under Process” | Stage, holder, deadline, escalation |
8 steps
Choose between “Women/Children Related Crime”, “Financial Fraud” and “Other Cyber Crime” — before you know which one your case is.
Register or log in with a mobile number and OTP before you can describe anything.
Pick a category, then a sub-category, from dropdowns written in police terminology.
Complete a long incident form where most fields are mandatory and few are explained.
Enter suspect details, even when you have none of them.
Enter complainant details on a separate page.
Preview and submit.
Receive an acknowledgement number. Status thereafter reads “Under Process”.
6 steps
Describe what happened in your own words — typed or spoken, in English, Hindi or a mix.
We map it to the official category, show our reasoning, and let you override it.
If money has just moved, a freeze request goes out first, using only the six fields a bank needs.
Fill a shortened form that asks only what your category actually requires, pre-filled from your description.
Review everything in plain language and give explicit, itemised consent.
Track a timeline that names the unit holding your case, what it is doing, its deadline, and how to escalate.
Beyond the interface
A nicer form does not by itself recover anyone's money. These are the changes behind the screen that the design assumes.
A freeze request that fans out
Today the citizen calls 1930 and an operator re-enters the details. The freeze request should be a structured message emitted the moment the six critical fields exist, delivered simultaneously to the debiting bank, the beneficiary bank and the payment network — with the complaint following behind it.
Classification as a service, not a dropdown
The category taxonomy becomes an API that any channel — portal, helpline operator, police station — calls with a free-text narrative. One classifier, consistently applied, instead of every operator guessing.
SLA clocks that are public
Each stage carries a deadline under the relevant Right to Service commitment. When a stage breaches, escalation opens automatically rather than requiring the citizen to discover the route.
Evidence captured once
Screenshots and statements attach to the case, not to a stage, so a transfer between units does not restart the collection.
How we describe the current journey