GuardFlow is rostering software for security companies. Your planner builds the schedule, guards clock in and register their patrol rounds from their phone, and at the end of the month every client gets a PDF of the hours, rounds and incidents on their sites.
Nobody retypes the roster into an invoice. Nobody drives out to the gatehouse to photograph a clipboard.
The proof today
Ahmet can’t make it tonight, Youssef is covering 22–06
Planning group · 21:12
Patrol log · gatehouse
The proof you send
NorthShield Security BV
Rotterdam Logistics Hub · 01–31 Aug 2026
Built from what the team registered on site
Active guards
8
of 13 on the team
Shifts today
12
3 completed
Open incidents
11
3 high or critical
Guard hours
635
+7% vs. last week
Checkpoint completion
93%Last 14 days
Locations requiring attention
Ranked by follow-up needed
Rotterdam Warehouse A
Rotterdam Logistics Hub
Amsterdam Retail Entrance
Urban Retail Center
Utrecht Construction Gate
SecureBuild
0
client contracts
0
locations
0
security officers
0
day roster window
0
incident reports
Fictional dataset shipped with the demo — every figure on every screen is calculated from it.
Shift swaps, sick calls and hand-overs sit in a chat nobody can search back three months later. None of it is structured, so none of it can go in a report.
One planner owns the file. Hours get retyped at month end for invoicing, and a single transcription error turns into a discussion with the client about what they are paying for.
Rounds are signed off on a clipboard in the gatehouse. When a client asks for proof of service, somebody drives out to collect it.
It works — until a contract comes up for renewal and the conversation turns on what you can actually show.
This is for you if
Probably not if
Nothing gets typed twice. What the planner schedules is what the guard sees on their phone, and what the guard registers is what the client reads at the end of the month.
Monday
The planner fills next week's roster — who is where, on which site, on which shift.
On shift
The guard opens their phone, clocks in, and sees the checkpoints they need to walk.
On the round
Each point is registered with a tap. If a round runs late, it is flagged there and then.
Month end
You pick a client and a month. The report is already written from what the team did.
Start and end the shift
They tap once at the start and once at the end. Those two times become the hours on the client’s report, so nobody fills in a timesheet later.
Register each round
One tap at each checkpoint. If a point is registered later than the interval you agreed with the client, it is marked late on the spot.
File an incident on site
The site and the shift are already filled in, so the guard only writes what happened. It takes about a minute.
Everything reaches the supervisor
The supervisor sees it straight away with the time and place attached, and can add a note or close it off.
Rounds are registered with a tap in this version. Every checkpoint already carries a QR value, so scanning is a small step from here.
Rotterdam Warehouse A
22:00 – 06:00 · Night · High risk
Pick a client and a month. You get a PDF with your company name on it, built from what your team actually did on site. Every export is logged, so you can always see what you sent and when.
NorthShield Security BV
Security service report
Rotterdam Logistics Hub
All locations · 01 Aug – 31 Aug 2026
Shifts
81
Hours
668
Rounds
94%
Incidents
6
| Shifts planned | 84 |
| Shifts delivered | 81 |
| Shifts not covered | 3 |
| Scheduled hours | 672 h |
| Guard hours delivered | 668.5 h |
| Checkpoints missed | 38 |
Generated with GuardFlow. Produced in a demo environment and contains fictional data.
A shift from 22:00 to 06:00 counts as eight hours, on the right day. Rosters built in a spreadsheet usually get this wrong.
Every checkpoint has an interval you agree with the client. Miss it and the round shows as late on the report, where the client can see it.
One client, several sites. Each site keeps its own risk level, its own guard count and its own patrol points.
A guard sees their own shifts and nothing more. Pay rates and deleting records stay with the owner. The database enforces it, so it holds even if someone goes looking.
No sign-up. Three logins, three different views: the owner plans, the supervisor reviews, the guard works from their phone.
Look around the demo
Sign in as the owner and open a month that already has data in it. Nothing to install, nothing to fill in.
Tell me how you actually run
How many sites, which shift patterns, what your clients ask for at the end of the month. That is the part software usually gets wrong.
Then the formalities
For work in the Netherlands, anything would begin only once the residence permit and KVK registration are complete.