01 — Overview
A portal built for a state police department managing thousands of personnel
The Andhra Pradesh State Police Department Portal was developed to modernise internal processes by transforming from manual, paper-based workflows to a fully digitised, efficient system — spanning 26 districts and multiple ranks from constables to IPS officers.
The platform had no unified digital infrastructure. Each district managed its own records manually. Attendance, leave, payroll, complaints, and transfers were tracked on paper or in disconnected spreadsheets. The task was to design a governance platform that served every tier of the hierarchy simultaneously — while being simple enough for field personnel with minimal digital literacy.
02 — Problem
Manual processes. No accountability trail.
The department relied entirely on paper registers, manual ledgers, and phone calls to coordinate across stations. Tracking file movements and employee actions was impossible at scale, creating gaps in accountability and delays in decision-making.
HR managers could not access real-time attendance data. Finance teams reconciled payroll manually every month. IPS officers had no single view of district-level status. The absence of digital infrastructure wasn't just inefficient — it was a governance risk.
"Every morning I have to call each station to get attendance figures. By the time I compile them, decisions have already been made without the right data."
— HR Manager, District HQ, Vizag
Personnel pain points
No digital channel to apply for leave or check approval status. Overtime logged manually with frequent disputes. Transfer requests required physical paperwork routed through multiple offices. No visibility into own service records.
Management pain points
No real-time attendance dashboard. Manual payroll reconciliation every month. Complaint tracking was entirely paper-based with no escalation workflow. Reports required days to compile from multiple sources across districts.
03 — Research
Understanding the system before redesigning it
Research was conducted across four weeks with IPS officers, HR managers, finance officers, and beat-level police personnel. Sessions included on-site interviews at District HQ, contextual observation of daily shift-change routines, and a competitive analysis of existing government digital platforms.
01
Stakeholder Interviews
14 sessions across IPS officers, HR managers, finance staff, and constables. Mapped current workflows and identified the biggest friction points at each role level.
02
Contextual Observation
Shadowed shift change at two district stations. Observed how attendance is recorded, how orders are communicated, and where delays compound.
03
Competitive Analysis
Audited 6 existing state government portals nationally. Benchmarked IA patterns, role-based access models, and dashboard structures for hierarchical orgs.
04
Quantitative Survey
68 respondents across 4 districts. Measured tool usage patterns, attendance tracking habits, and feature expectations ranked by role group.
Three primary user archetypes emerged: the Field Officer (mobile-first, minimal digital exposure), the District Coordinator (data-driven, needs dashboards and batch actions), and the IPS Senior Officer (strategic oversight, needs district-wide summaries). Every design decision was weighted across all three lenses.
04 — Design Process
From hierarchy to hierarchy-aware design
The core design principle: one system, multiple views. The same portal surfaces different dashboards, actions, and data depending on the user's rank and role — without requiring separate products or logins. Navigation was structured around six primary destinations — Dashboard, Attendance, HR Management, Reports, Finance, and Complaints — each adapted per role via permission-based rendering.
For field personnel, the interface was stripped to the essentials: clock in, view duty roster, submit leave. For coordinators, a full data grid with batch approval, attendance analytics, and escalation flags. For IPS officers, district-level KPIs and exception reports front and centre.
IA Architecture
Flat six-module structure replacing fragmented department silos. Card sorting with 18 personnel validated navigation labels and groupings. Role-based access controls built into every node of the hierarchy.
Dashboard Redesign
Prioritised daily duty status, pending approvals, and exception alerts above the fold for every role. Removed legacy widgets not used by 85%+ of users. Reduced cognitive load significantly across all tested roles.
Design System
Built a component library in Figma with accessible contrast ratios throughout. Type scale, colour tokens, and spacing grid documented and aligned to government accessibility guidelines.
Mobile-First Attendance
92% of field personnel preferred mobile-first attendance tracking. Designed geo-tagged check-in flow with offline queuing — critical for stations with intermittent connectivity.
Portal structure before & after — from fragmented paper registers to a unified, role-aware digital system
Design Timeline
05 — Outcomes
Measurable shift, across every district
The portal launched across three pilot districts before a phased statewide rollout. Post-launch usability testing and department feedback showed significant improvement across every tracked metric — and, more importantly, a genuine shift in how staff approached their daily work.
Attendance reporting time reduced from 3 hours to under 10 minutes
District HR managers previously spent 2–3 hours every morning collating attendance via phone calls. The portal auto-aggregates geo-tagged check-ins, surfacing real-time status in a single dashboard view.
Leave approval turnaround: 5 days → same day
Paper-based leave requests previously routed through 3–4 offices over multiple days. Digital workflow with role-based approval chains reduced approval time to hours — with full audit trail preserved.
92% of tested users completed core tasks without assistance
Moderated usability sessions post-launch with field officers, HR managers, and IPS officers. Task success rate rose from an estimated 35% on legacy workflows to 92% on the new portal across 6 core flows.
Monthly payroll reconciliation time cut by 68%
Finance teams integrated attendance data directly into payroll workflows, eliminating manual cross-referencing of registers. Errors from data re-entry dropped to near zero in pilot districts.
First digital audit trail in department history
Every action — leave approval, complaint escalation, transfer recommendation — now carries a timestamped, user-attributed log. The governance impact extends well beyond efficiency into accountability and transparency.
06 — Reflection
What I learned
Government UX asks something different of a designer. The stakes are not engagement metrics or conversion rates — they are the daily working lives of thousands of public servants, and the quality of governance experienced by millions of citizens downstream. That weight sharpens every decision.
The single most valuable moment in this project was spending a morning at a district station, watching the shift-change ceremony. I saw how attendance is called aloud and marked by hand, how orders are passed verbally, how a constable has no way to check his own leave balance without asking his supervisor. That morning produced more insight than any workshop could.
If I were to do this again, I would push earlier for a mobile-first prototype in the hands of constables — not just officers. The hierarchy of access in government projects often means the loudest voices in research are the most senior ones, which risks designing a portal that serves leadership at the expense of the people who use it most daily.