Build next week's rota before your tea goes cold
Assign officers to sites and shifts, publish to every phone at once, and see instantly where booked hours and worked hours do not match.
The spreadsheet is costing you more than you think
Ask most security operators how long the rota takes and you will hear "a day, maybe two". Then add the calls to tell people about changes, the officer who turns up at the wrong site, the shift nobody covered because it was in row 47, and the Friday spent reconciling what was booked against what was worked.
None of that is a scheduling problem. It is a communication problem — the rota lives in one place and your officers live somewhere else. Put the schedule on their phones and most of it disappears.
What the rota tools actually do
Week, month or site view
Look at the whole company by week, or drill into one client's sites to check coverage before you commit.
Copy a week forward
Most security rotas repeat. Duplicate the pattern and edit only what changed.
Clash and availability checks
Overlaps, approved leave and unavailable officers are flagged before you publish, not after.
Publish to every phone
One button. Officers see their shifts instantly and get told when something changes.
Open shifts and cover
Leave a shift unassigned and it shows up as a hole in the rota until somebody fills it.
Site notes on the shift
Gate codes, key locations, client contacts and site rules travel with the booking, so relief staff are not guessing.
Leave and absence
Officers request holiday in the app; approved leave blocks scheduling automatically.
Booked vs worked
The clock-on record sits beside the booking, so late starts and short shifts are obvious the same day.
Straight into billing
Confirmed hours feed timesheets and client invoices without re-keying.
Read moreFrom published rota to paid invoice
The reason scheduling belongs in the same system as tracking is that the two halves check each other.
- You publish the shift. The officer sees site, time and notes on their phone.
- They clock on. Time and GPS position recorded against that booking.
- They patrol. Checkpoint scans and incidents attach to the same shift.
- They clock off. Actual hours are now sitting next to booked hours.
- You approve the week. Anything that does not match is flagged for review.
- You invoice. Verified hours become the client bill and the payroll figure.
Rota patterns security companies actually run
All of these are ordinary in SMS-Patrol — you are not fighting a tool designed for retail shift work.
- Static site cover — the same officer, same gatehouse, 07:00 to 19:00, five days a week.
- Nights across midnight — 19:00 to 07:00, correctly attributed to the right shift and the right day's invoice.
- Four on, four off — rotating patterns copied forward months at a time.
- Mobile patrol runs — one officer, eight sites, a set number of visits each per night.
- Relief and cover pools — a group of officers who fill gaps across several contracts.
- Event surges — forty stewards for one Saturday, then back to normal on Monday.
- Split shifts — a morning school run and an evening close-down on the same site.
Rota and scheduling questions
Security rota software is a scheduling tool built for shift patterns rather than office hours. You assign officers to sites and shifts, publish the schedule to their phones, and the system tracks who actually turned up against who was booked. It replaces the spreadsheet, the WhatsApp group and the phone calls.
In the app. As soon as you publish, every officer sees their own upcoming shifts with site, times and any notes you have added. Changes push through instantly, so nobody is working from last week's version.
Yes. If you try to place an officer on two overlapping shifts, or on a shift while they are booked off, the system flags it before you publish.
Yes — security patterns are what it was built for. Nights that cross midnight, four-on-four-off, split shifts, relief cover and long-term static postings are all normal here.
Yes. Most security schedules are largely repeating, so you can duplicate a week or a pattern forward and then edit only the exceptions. That is usually the difference between an afternoon and twenty minutes.
Officers request leave in the app and you approve or decline it. Approved leave blocks them from being scheduled, so you cannot accidentally roster someone who is away. When somebody calls in sick you can see at a glance who is free and qualified for that site.
Yes, and this is the point. Booked hours sit next to actual clocked hours, so the difference is visible before it becomes a payroll problem or an invoice dispute.