Skip to content
DT Nova
Services

Police scheduling software for law enforcement agencies

Police scheduling software that starts from minimum staffing: every shift, sector and unit covered by officers with the right qualifications, on the shift pattern your agency runs, with overtime, court time and training counted by your work period and agreement. It runs shift bids by seniority, fills open shifts in a fair order, keeps qualifications current and sends approved hours to payroll. We build it as custom law enforcement scheduling software for police departments, sheriff's offices and other agencies, hosted in the EU, and your agency owns the code.

  • You see the result before it goes live
  • Fixed price for the agreed scope, in writing before work starts
  • Source code, domain and accounts in your company's name

Request a quote

Why police scheduling is its own problem

General employee scheduling software fills shifts with people. Scheduling software for police has to answer a harder question every day: is each sector, each shift and each specialist unit at minimum staffing, with a supervisor on duty, enough officers trained for the vehicles and equipment in use, and nobody past a fatigue limit? The answer changes when an officer is subpoenaed to court on a day off, when a firearms qualification day takes a squad off the street, or when a long arrest at the end of a shift turns into overtime.

On top of that come the agreements. Shifts and days off are often bid by seniority once or twice a year. Overtime is offered from a list in an order the union agreement defines, and forced holdovers are spread by another rule. Many agencies also run paid details, where officers work for outside clients off duty, and those hours affect rest and overtime. Most of this lives in spreadsheets and in the memory of the shift sergeant.

What the system does

Shift patterns and bids by seniority

Most agencies run one of a handful of patterns. Eight-hour days on a 5/8 schedule are simple to staff but leave no overlap. Ten-hour shifts on a 4/10 schedule create overlap periods that can be placed where demand peaks, such as Friday and Saturday nights. Twelve-hour patterns, such as the Pitman 2-2-3, give officers every other weekend off but make fatigue and holdovers matter more. Specialist units, investigators and school resource officers often work fixed day schedules beside the patrol rotation.

The system holds each pattern as data: shift times, the cycle, overlap periods and which squads rotate. For a bid, the agency publishes the shifts and days off on offer, the system builds the seniority order from your agreement, and officers pick in turn. Each pick is checked at once: if taking a slot would leave a sector short of a qualified supervisor, the officer sees why before choosing. The finished bid becomes the schedule for the period, and the record shows who picked what and when.

Overtime, work periods and working time rules

A police schedule is a working time calculation, and the rules depend on where the agency is.

In the United States, the Fair Labor Standards Act lets public agencies use a work period of 7 to 28 days for employees in law enforcement activities. The regulations define those employees as uniformed or plainclothes members of a body of officers empowered by state statute or local ordinance to enforce laws, with the power to arrest and with the training that typically includes firearms, law and investigative techniques (29 CFR 553.211). For them, overtime is due after 171 hours in a 28-day work period, which is 6.11 hours a day, and the threshold for a shorter period is proportional (29 CFR 553.230):

Work periodOvertime after (law enforcement)For comparison: fire protection
28 days171 hours212 hours
14 days86 hours106 hours
7 days43 hours53 hours

Employees in public safety work may accrue no more than 480 hours of compensatory time under section 7(o) of the Act (29 U.S.C. 207). Agreements often set stricter limits, and civilian staff in the same department usually follow ordinary weekly overtime.

In the EU, the Working Time Directive applies to police officers too. In case C-211/19 (30 April 2020), the Court of Justice held that its rules on working time apply to law enforcement officers carrying out border surveillance, except where the tasks are carried out in the context of exceptional events whose gravity and scale require measures that would be jeopardised if all the rules were observed. Ordinary patrol work is therefore planned within the Directive's limits on weekly hours and rest, set out in national law and collective agreements. (All sources read on 11 November 2026.)

The system holds these rules as configuration per employee group: the work period, the overtime threshold, compensatory time limits, rest periods and which hours count. Every placement, trade and overtime offer is checked before it is saved, and supervisors see each officer's hours against the threshold for the current period, not only the current week.

Fair overtime and forced holdovers

Overtime is where most scheduling grievances start. The system offers open shifts to eligible officers in the order your agreement defines, for example by overtime hours already worked in the period, by seniority, or by a rotating list. Officers accept or decline on the app, and each offer, answer and time is recorded. When nobody volunteers, forced holdovers follow their own rule and are spread across the squad. Because every step is logged, the fairness rule can be checked by the officer, the union and the chief, without reconstructing it from text messages.

Court time, training and qualifications

Court appearances often fall on days off or straight after a night shift. The system records each subpoena as an assignment with its date, time and case reference, flags a clash with the schedule or with minimum rest, and counts the hours by your pay rules, including any minimum guaranteed hours in your agreement. Mandatory training works the same way: firearms qualification, defensive tactics, driving and state or national continuing education are scheduled as assignments, and their expiry dates sit with each officer's record.

The system warns the officer and the supervisor well before a qualification lapses, shows who is at risk in the next quarter and will not place anyone in a role that needs a qualification they will not hold on that date, such as a field training officer slot or a specialist vehicle.

Paid details and outside employment

Many agencies let officers work paid details for outside clients, such as traffic control at road works or security at events. The system lists open details, lets eligible officers sign up in the agency's order, checks the hours against rest rules and any cap on total weekly hours, and records the client, rate category and hours worked so the agency can invoice the client and pay the officer correctly. A detail that would push an officer past a fatigue limit is blocked before it is accepted.

The officer app

Officers see their schedule for months ahead, their squad, sector and unit for each shift, and open shifts and details they are eligible for. They request leave, propose a trade with a qualified colleague, answer overtime offers and enter bid picks from their phone. Supervisors approve requests and see live coverage on the same app or on a laptop. We build for iPhone and Android from one codebase, or as a web app installed to the home screen if your agency prefers no store apps on personal devices. Private guarding firms with licensed guards on client posts have different rules; see security guard scheduling software.

Connections to CAD, payroll and HR

The schedule is the source of truth for who is on duty, where and in which unit. Computer-aided dispatch and records management systems stay as they are, and the scheduling system can send them the on-duty roster and unit assignments through their interfaces, so dispatchers do not retype the shift. Payroll receives approved hours, overtime, compensatory time, court pay, differentials and detail hours already calculated. HR systems supply new hires, ranks and leave balances. In the US, an interface that touches criminal justice information brings the FBI CJIS Security Policy into scope, so we keep the scheduling system to roster data and agree the interface design with your IT and CJIS contacts first.

Ready-made police scheduling or custom?

There are established law enforcement scheduling products, such as UKG TeleStaff, InTime and PlanIt, and national products in several European countries. For many agencies one of them fits, and we will say so. Custom software pays off when your bid rules, overtime order, detail program or integrations do not match what the product assumes, or when sergeants keep a spreadsheet next to it.

SituationReady-made productCustom software
One pattern, one bargaining unitUsually enoughRarely worth building
Several units with different agreementsSettings and manual correctionsEach agreement's rules, as written
Seniority bids and overtime orderStandard bid and list featuresYour exact order and tie-breaks
Paid details with client billingOften a separate productIn the same schedule and payroll export
Data location and ownershipThe vendor's platform and regionYour account, EU data region

Data protection

A police schedule holds sensitive personal data: officers' names, contact details, home addresses for recall to duty, leave reasons, sometimes health information behind sick leave, and assignments that should not be public, such as undercover or protection duties. In the EU, staff scheduling falls under the GDPR rather than the directive for law enforcement data processing, which covers data processed for preventing and investigating crime. The design keeps data to what scheduling needs, restricts sensitive assignments to named roles, logs every change and runs in an EU data region under a written data processing agreement.

How we build it

  1. Scheduling workshop. Your sergeants and schedulers show how a month is built today, including the unwritten rules about overtime order, holdovers and court days. We write them down for approval by command staff and, where relevant, the union.
  2. Scope and fixed price in writing. Units, patterns, rules, integrations and what the first phase leaves out.
  3. First version on real data. Last quarter's staff and schedule, so the draft can be compared with the one built by hand on coverage, overtime and fairness.
  4. Pilot with one shift or district. Officers use the app for a few cycles, and the rules are tuned.
  5. Roll out and measure. Short-staffed shifts, forced holdovers, overtime hours and scheduling time are compared with the numbers recorded at the start.

As a standard term, the source code sits in a repository in your agency's own account, and the database and hosting are in your name. For ambulance crews and fire departments, see EMS scheduling software; for the wider loop of forecasting, absence and labour cost, see workforce management software; for standby and recall rotas, see our guide to standby rotas and scheduling tools. See prices.

Questions we get

What makes police scheduling different from ordinary shift scheduling?

A police schedule is built around minimum staffing for each shift, sector and unit, not around a headcount. Officers bid for shifts by seniority, overtime may follow a work period of up to 28 days, court appearances and mandatory training land on days off, and paid details for outside clients add hours that count toward fatigue limits. A general shift tool does not check those things together.

Can the system run shift bids by seniority?

Yes. A bid round is set up with the shifts, days off and assignments on offer, the eligible officers and the seniority order from your agreement. Officers pick in turn on the app or a laptop, the system shows what is left and checks each pick against qualification and staffing rules, and the result becomes the schedule for the bid period.

Does it handle the 7(k) overtime rules?

Yes. For US agencies, the work period, the overtime threshold and compensatory time rules are set per employee group. For law enforcement employees under section 7(k), overtime is due after 171 hours in a 28-day work period, with proportional thresholds for shorter periods, and the system shows each officer's hours against the threshold for the current period.

Can it track court time and training?

Yes. Court appearances, firearms qualifications and other mandatory training are entered as assignments with their dates and times. The system flags conflicts with the schedule, counts the hours by your pay rules and warns before a qualification lapses.

Does it replace our CAD or records management system?

No. Computer-aided dispatch and records management stay where they are. The scheduling system can send the on-duty roster and unit assignments to CAD through its interface, and payroll receives approved hours with overtime already calculated.

Who owns the system and the data?

Your agency. The source code sits in a repository in your own account, and the database and hosting are in your name in an EU data region. You can keep us for maintenance, run it yourself or hand it to another team.

Get a written quote

Tell us in a few lines what you need. We reply within one working day with a written quote: scope, timeline and a fixed price or an hour estimate. Asking is free and commits you to nothing.

See every price · Contact details

Request a quote