Security companies run 24 hours a day. There is no quiet week in which to switch systems. A rollout plan for security workforce software has to work around live deployments, officers who are asleep during the day, and clients who will notice if anything changes at their posts.
This plan is built from rollouts we have run with companies between 25 and 2,000 officers. It assumes a two-week window, one internal owner, and a platform that is ready to configure on day one. Larger companies run the same plan per region.
Before day one: pick the owner and the pilot
The rollout needs a single owner with the authority to make decisions about posts, rates, and officer assignments. In most companies this is the operations director or a senior operations manager. The owner's time commitment is roughly two hours a day for two weeks.
Choose a pilot scope: two or three client sites with a mix of static posts and patrol routes, covered by 10 to 30 officers. The pilot sites should have cooperative clients and a supervisor who will champion the change. Everything else stays on the old system until week two.
Days 1 to 3: data and configuration
Day 1. Import the roster. Export officers from your existing system or spreadsheet with name, phone, email, employee reference, and credential expiry dates. Import them. Check that every officer has a phone number, because the app sign-in code goes by SMS.
Day 2. Model the posts. Create each client, then each post under that client. Use the names from the client's contract. Draw the geofence for each post on the map and set the grace period for late arrival according to the contract. Add contract bill rates and officer pay rates with their differentials.
Day 3. Build the patrol routes. Walk each pilot site with the supervisor and decide where checkpoints go. Order NFC tags for permanent outdoor points and print QR codes for indoor points. The comparison in NFC vs QR checkpoints for security patrols covers the trade-offs. Place the checkpoints and create the routes with expected durations.
Days 4 to 5: operators first
Operators and supervisors should be comfortable with the console before any officer uses the app. Train the dispatch team on the exception queue, the actions available on each exception, and the resolution codes. Run a tabletop exercise: a late arrival, a missed checkpoint, an open incident. Have each operator resolve one.
Configure the escalation chains for incident types during this window, because operators will have opinions once they have seen the console.
Days 6 to 8: officer app on the pilot sites
Day 6. Install at the briefing. Rather than sending instructions, install the app at a shift briefing. Officers sign in with an SMS code, see tonight's deployment, and do one practice check-in and one practice checkpoint scan. Ten minutes per officer. Cover both the day and the night shifts by running two briefings.
Day 7. First live shift. The pilot sites go live on the new system while the old sign-in sheets remain in place as a backup. An operator watches the pilot posts on the coverage map. Expect a few officers to check in late because they forgot; expect a few checkpoint scans to be missed because a tag was placed on metal. Fix the tags.
Day 8. Review and adjust. Look at every exception from the first live shift. Adjust grace periods that were too tight, move checkpoints that were awkward, and talk to any officer who struggled. This is the day the plan either earns trust or loses it, so the owner should be present at the start of the night shift.
Days 9 to 10: the first client report
By day 9 the pilot sites have two or three nights of arrival records and patrol scans. Generate a coverage and patrol report for each pilot client and send it with a short note explaining what they are seeing.
Then set up the scheduled report so it arrives every Monday at the same time. Create a client user in the portal for the client's main contact and walk them through it on a short call. ClientView is simpler to show than to describe, and the client's reaction to seeing their own posts live is often the moment the rollout gains internal momentum.
Days 11 to 12: hours and the first export
Run the pilot shifts through exception review. Approve the clean ones, correct the few with missing check-outs, and export the verified hours in the payroll format mapped during configuration. Compare the export against the old timesheets for the same period. Differences will usually be in your favour: shifts that ran long, differentials that were missed. This comparison is also the business case for the finance team, as described in reducing disputed hours on security invoices.
Days 13 to 14: expand or pause
If the pilot sites have run for a week with exceptions handled and a report delivered, expand. Schedule briefings for the remaining officers, create the remaining posts, and set a date for retiring the paper sign-in sheets. Companies with more than 300 officers usually expand region by region over the following month rather than all at once.
If the pilot has surfaced a structural problem, such as a client contract with rates the platform does not yet model, pause and resolve it. A two-week rollout that becomes three weeks is fine. A rollout that expands with an unresolved problem is how companies end up running two systems forever.
What usually goes wrong
Three issues come up in nearly every rollout.
Phone numbers. Officer records with missing or outdated phone numbers delay sign-in. Clean them before day one.
Metal. NFC tags placed directly on steel gates or railings will not read. Use ferrite-backed tags or mount on a plastic spacer.
Grace periods. Operators set grace periods too tight in the first week and the exception queue fills with five-minute lates that no client cares about. Set grace periods from the contract, not from ambition.
None of these is serious. All of them are easier to handle in a pilot of three sites than across the whole company.
After the rollout
Two weeks is enough to prove the system on real shifts and real clients. What follows is the habit: operators working the exception queue, supervisors reviewing hours before export, clients opening their Monday report. The owner's two hours a day drop to a weekly check within a month. The sign-in sheets go in a box, and after a quarter nobody asks where they are.