Project overview
Preparing a police duty roster by hand is slow and hard to keep fair. Officers must balance ranks, skills, leave and the importance of each duty point, and then do it again for elections, festivals and VIP movements. Websofy built this police duty roster software so that a senior officer sets the rules and the system prepares the duty chart.
Who uses it
There are two kinds of users. Officers such as the DCP, ACP and TI manage rules, duty points and approvals. Members of the force such as TSI, head constables and constables see their own duties, mark attendance and apply for leave.
Modules
- Force management: personnel details, rank and skill level.
- Duty points: zone-wise locations with category, priority and map coordinates.
- Shift schedules: shifts and timings for each kind of duty.
- Duty rules: the officer decides how many personnel of each rank a category of duty point needs.
- Automatic duty chart: weekly or monthly rosters generated from the rules and availability.
- Leave and attendance: leave requests and location-based attendance at the duty point.
- Alerts and reports: notifications for absence or late arrival, and deployment reports.
How a roster is prepared
| Step | Action |
| Set up | Force, duty points and shifts are entered once. |
| Rules | Rank-wise requirement is fixed for each category of point. |
| Generate | The system prepares the duty chart for the chosen period. |
| Adjust | Officers make changes for leave or special duties. |
| Notify | Personnel see their duty and point on their login. |
| Review | Attendance and deployment reports are checked. |
Fairness and control
Because the roster is generated from written rules, duty is distributed by rank, skill and availability rather than by habit. Officers can see how often each person has been given a demanding point, and changes made after generation are recorded. Sensitive deployments remain under the control of the authorised officer, who approves the final chart before it is released.
How Websofy delivered it
We began by listing duty points with their categories and map locations, then captured the rules senior officers already applied informally. After the first charts were generated, the rules were refined with the officers until the output matched operational needs. For elections and large events, a separate set of points and rules is created so that regular policing and special duty can be planned side by side.
What changed
Rosters that took hours are produced in minutes, allocation follows written rules rather than memory, and officers can see at any time who is deployed where. The same design is used for election, enumeration and special event duties. Related work: election duty management, VIP duty management and traffic duty planning.
How we approach engagements like this
- Requirement discovery mapped to the real workflow, users and data involved
- Solution architecture and module planning before any code is written
- Secure, tested engineering with clear documentation
- Structured handover, training and post-launch support