# Time tracking for security companies > Time tracking for security companies: 12-hour and night shifts across midnight, rosters with rest-time checks, posts and rounds, client approval per object. URL: https://timetracking.tech/for/security-services Language: en Last updated: 2026-10-26 Your officers work 12-hour shifts, nights and weekends. They staff fixed posts and drive rounds past many client objects. TimeTracking keeps every shift on the right object. A night shift counts as one shift. Planners get a warning before rest time is broken. Each client approves the hours on their own object. Start free for up to 5 users. ## How security companies use TimeTracking 1. **Objects, posts and rounds**: Every client object becomes a site. You plan fixed posts and rounds as shifts on that object. Permanent posts use repeating patterns. 2. **Check the roster before publishing**: The roster is checked against rest-time rules and approved leave. The planner sees a warning before an officer gets too little rest between shifts. 3. **Officers start and end the shift**: Officers clock in with the app, or with a personal PIN at a kiosk tablet at the post. A shift from 19:00 to 07:00 counts 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 logs shifts across midnight as one shift, with the right totals. Breaks are logged on their own. Night, weekend and irregular-hours allowances are hour types. You link each one to a payroll code in the export. So the payslip matches the roster. - 12-hour and night shifts across midnight - Breaks logged on their own - Night and weekend allowances linked 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 calls in sick. Suddenly an officer who finished at 07:00 is planned again at 15:00. The rule engine checks the roster against your rest-time rules. It warns the planner before the roster goes out. Dutch presets come first. You can offer open shifts to a group of officers. For example, the team that already knows the object. The planner decides who gets the shift. Swaps between officers only count 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 repeating shifts at one object. Mobile officers drive rounds past several objects in a night. Sometimes they respond to an alarm. An officer on a round can book time per object as separate entries. So each client sees its own share. Travel time and kilometres between objects are logged on their own. TimeTracking tracks time. It is not a guard tour system. It does not log checkpoint scans. 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. Many officers would rather not use their own phone for work. Put a kiosk tablet at the post, tied to that object. Each officer clocks 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. The timer keeps running after a restart. In places without signal, hours wait on the phone until it is back online. ## Client approval per object Security clients pay for the hours on their object. They want to see them. The contact for each object gets a secure magic link. It shows the shifts on that object, with start and end times and any notes. They approve, or reject a line with a comment. No account needed. Their name and the time of approval are saved. So you have a clear record if an invoice is questioned later. Clients with many objects can split approvals per object. Then 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. Today you get an SD Worx-format export and CSV and XLSX files you set up yourself. Loket, Nmbrs and AFAS connectors are coming soon. Exported periods are locked. A fix becomes 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. All from €1 per user per month, with no add-ons. ## Frequently asked questions ### Are night shifts across midnight handled correctly? Yes. A shift from 19:00 to 07:00 counts as one 12-hour shift. It has the right totals and its own logged break. ### Does the roster warn about rest-time violations? Yes. Before the roster goes out, the rule engine warns planners about shifts that break your rest-time rules. Dutch presets come first. ### Can TimeTracking register checkpoints on a round? No. TimeTracking logs 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 ongoing location tracking. Geofence nudges are coming soon. They will only send a reminder near sites you choose. ### Can clients approve the hours per object? Yes. The contact for each object approves through a secure magic link, without an account. Their name and the time of approval are saved. ### What does it cost? Free for up to 5 users. Then €1 per user per month on Core. That includes rosters, rest-time warnings, client approvals and payroll exports. No add-ons.