Skip to content

Time tracking for security companies

Security officers work 12-hour shifts, nights and weekends, on fixed posts and mobile rounds across many client objects. TimeTracking keeps every shift on the right object, counts a night shift as one shift, warns planners before rest time is broken and lets each client approve the hours on their own object.

Animated demo: a security officer clocks in at the post for a 12-hour night shift, the shift crosses midnight and stays one shift, the roster warns that the next shift leaves too little rest until the planner moves it, and the client approves the hours on its object. Shift starts at the post, Across midnight, Rest time check, Client approves.

How security companies use TimeTracking

  1. Objects, posts and rounds

    Every client object becomes a site. Fixed posts and rounds are planned as shifts on that object in the roster, with recurring patterns for permanent posts.

  2. Check the roster before publishing

    Rest-time rules and approved leave are checked against the roster, so a planner sees a warning before an officer gets too little rest between two shifts.

  3. Officers start and end the shift

    Officers clock in with the app or at a kiosk tablet at the post with a personal PIN. A shift from 19:00 to 07:00 is recorded as one shift.

  4. Client approval per object, then payroll

    The contact for each object approves the hours through a magic link. Approved hours, night allowances and overtime go to payroll.

Night shifts that stay one shift

A shift from 19:00 to 07:00 is twelve hours of work, not two half days. TimeTracking records shifts that cross midnight as one shift with correct totals, and breaks are recorded explicitly. Night, weekend and irregular-hours allowances are hour types that you map to your payroll codes in the export, so the payslip matches the roster.

  • 12-hour and night shifts across midnight
  • Breaks recorded explicitly
  • Night and weekend allowances mapped to payroll codes
  • Planned versus worked per shift and object

Rest time checked before the roster goes out

In security, overwork starts in the roster. A late cancellation, a colleague who calls in sick, and an officer who finished at 07:00 is suddenly planned again at 15:00. The rule engine checks the configured rest-time rules against the roster and warns the planner before it is published, starting with Dutch presets.

Open shifts can be offered to a group of officers, for example the team that already knows the object. The planner decides who gets the shift, and swaps between officers only take effect after the planner approves them.

  • Rest-time warnings, starting with Dutch presets
  • Open shifts offered to a group
  • Swaps approved by the planner
  • Approved leave taken into account

Posts, rounds and call-outs

Fixed posts, such as a reception desk or a gatehouse, run on recurring shifts at one object. Mobile officers drive rounds past several objects in a night and sometimes respond to an alarm. An officer on a round can book the time per object as separate entries, so each client sees its own share, while travel time and kilometres between objects are recorded separately.

TimeTracking is a time tracking system, not a guard tour system. It does not register checkpoint scans and it does not follow officers with GPS. QR codes and NFC tags for clocking in are planned but not available today.

Clocking in at the post

Many objects have a post with a desk, and many officers prefer not to use their own phone for work. A kiosk tablet at the post, limited to that object, lets each officer clock in and out with a personal 6-digit PIN. After 5 wrong PINs the tablet locks for 15 minutes. The kiosk takes no photos and uses no face recognition.

Officers who move between objects use the mobile app, with a timer that keeps running after a restart and an offline queue for places without signal.

Client approval per object

Security clients pay for the hours on their object, and they want to see them. The contact for each object receives a secure magic link with the shifts on that object, including start and end times and any notes, and approves or rejects lines with a comment. No account is needed. Their name and the time of approval are stored, which gives you a clear record if an invoice is questioned later.

For clients with many objects, approvals can be split per object, so each local contact only sees their own.

Payroll exports and an open stack

Approved hours, allowances, overtime, travel and expenses go to payroll in one export: an SD Worx-format export and configurable CSV and XLSX files today, with Loket, Nmbrs and AFAS connectors coming soon. Exported periods are locked, and corrections become a line in the next period.

Incident reports, control room software and invoicing stay in the tools you already use. TimeTracking connects to them through exports and the REST API.

Frequently asked questions

Are night shifts across midnight handled correctly?

Yes. A shift from 19:00 to 07:00 is recorded as one 12-hour shift with correct totals and an explicit break.

Does the roster warn about rest-time violations?

Yes. The rule engine warns planners about shifts that break the configured rest-time rules before the roster is published, starting with Dutch presets.

Can TimeTracking register checkpoints on a round?

No. TimeTracking records working time, not checkpoint scans. QR codes and NFC tags for clocking in are planned but not available today.

Does it track officers' location?

No. There is no continuous location tracking. Planned geofencing will only send a prompt around configured sites.

Can clients approve the hours per object?

Yes. The contact for each object approves through a secure magic link, without an account. Name and time of approval are stored.

What does it cost?

Free for up to 5 users, then €1 per user per month on Core, including rosters, rest-time warnings, client approvals and payroll exports.

Try TimeTracking free

Free for up to 5 users. Core from €1 per user per month, everything included.