Case study · Palghar District Police
Utsav Prahari.
One linked record of every mandal, officer and visit.
A web system and Android app that replaces paper registers, phone calls and spreadsheets during large public festivals. Mandals register, officers are assigned, visits are verified on site, and supervisors see the whole district live.
- Client
- Palghar District Police
- Sector
- Public safety
- Status
- Deployed
- Roles modelled
- 6
01 · Context
Large public festivals such as Ganeshotsav and Navratri involve hundreds of mandals, dozens of police stations and officers in the field. Palghar District Police uses Utsav Prahari for the 2026 festival season, covering 16 police stations and 4 sub-divisions (per utsavprahari.in).
02 · The challenge
Coordination on paper and phone
Festival monitoring traditionally runs on registers, phone calls and spreadsheets. Each is a separate record that someone has to reconcile.
Knowing a visit actually happened
A supervisor needs more than a note saying an officer visited. The visit has to be verifiable and not something that can be quietly edited later.
One chain of command, many views
Constables, station in-charges, sub-divisional officers and the SP’s office all need different slices of the same truth.
Field reality
Officers work outdoors on phones, often in Marathi. The system has to be fast, simple and forgiving.
03 · The approach
- 1
Model the organisation first
Police stations, sub-divisions and the one-mandal-one-officer rule are part of the data model, so reports roll up the way the force is actually organised.
- 2
Make verification physical
The QR receipt ties a record to a real mandal. Scanning it on site, with location captured, creates the visit record.
- 3
Records that hold
Verified visits are stored as non-editable records with an audit trail, so history can be trusted when it is reviewed.
- 4
Mobile and Marathi first
An Android app and a Marathi-first interface keep the workflow usable by the people doing the work.
04 · The system
One visit, from phone to command view
The verified visit is the heart of Utsav Prahari. Run one.
Press “Run a visit” to follow a single visit from the officer’s phone to the command view.
Illustration · A simplified walkthrough of the visit-verification workflow. No real mandal, officer or location data is shown.
System architecture
Mandal registration
Each mandal is registered once, receives a registration number and a printable QR receipt.
Station & sub-division structure
Police stations and sub-divisions are modelled directly, so every record sits where it belongs in the chain of command.
One mandal, one officer
Every mandal has a single accountable officer, each with an individual login.
Verified visits
A visit is confirmed by scanning the mandal’s QR with the officer’s location captured, then stored as a record that cannot be edited.
District map & live dashboards
Supervisors see coverage and activity across the district as it happens, on an interactive map.
Reports & notifications
Analytics, PDF and Excel reports, and targeted push notifications to the people who need them.
Mandal-president portal
Mandal presidents have their own portal, including an SOS function.
Marathi-first interface
The interface prioritises Marathi and is also available in English.
05 · Workflow
Mandal registers. Registration number and printable QR receipt issued.
06 · What it provides
A single linked record
Mandals, officers and visits live in one system, replacing separate registers, calls and spreadsheets.
Verifiable field activity
Each visit is confirmed by QR scan and location and kept as a record that cannot be edited.
Live supervision
District map and dashboards give supervising offices current visibility.
Reporting without re-keying
PDF and Excel reports are generated from the same records.
We describe what the system provides rather than quoting performance numbers. Measured results will be published here once verified.
07 · What we don’t show
This case study describes the product as published on utsavprahari.in. Operational details of individual deployments, officer data and mandal data are not shared. Deployment with a government body does not imply government endorsement.
Next case study
EMTSLet’s build
Have a process that deserves better software?
Tell us what you’re trying to run. We’ll tell you honestly how we’d build it.