Shift management for a security company
The client requires a guard on a post. In practice someone was replaced in the middle of the night, and the incident was written in a group. In the morning nobody can show who was there and what was handled.
Who it is for
For a company with several sites, posts, and rotating shifts. A poor fit for a single guard at a one-off event with no report back to a client.
Problems this page addresses
A post with no name on the shift
The roster says "north site, night". It does not say who should be at the gate and who in the lobby, so a replacement leaves a post empty.
An incident with no time and no closer
A hazard was reported in the group. There is no open time, no one who handled it, and no line that says the client was updated.
The client report is assembled in the morning
Someone collects overnight messages and writes a report. What was never written in the group does not exist, even if it happened.
What you get
Post and shift
Each site has posts. Each shift has a name on every post. A replacement closes the previous person and opens the next, with a time.
An incident on the shift
Open, what was done, and close. Logged from the phone at the post, not at the end of the night from memory.
A shift summary for the client
Who was on the posts and which incidents were closed. Built from the log, not rewritten from the WhatsApp group.
Common questions
How do you go live without breaking tomorrow’s roster?
Start with one site and one shift. The other sites stay on the old roster until replacement and incident logging work on a real site.
Will a guard open an incident from the phone?
Yes, if it is short: what happened, what was done, closed or handed on. Not a long form in the middle of an incident. Extra detail can be added when the post is calm.
How is this different from cleaning?
Cleaning closes a visit against a checklist of what was cleaned. Here a shift closes against a staffed post and an incident that was handled. The same client can buy both services, and the records do not mix.
Related pages
A CRM shaped around how you already work
An off-the-shelf CRM asks the team to adopt someone else’s stages and fields. We build the record around the approvals, statuses, and fields that already decide who the customer is and what happens next.
A mobile app on the same core as the web
The office works comfortably on a large screen, and the field stays on screenshots and group chats. We build the phone actions on the same server and the same permissions, not as an app with a database of its own.
Job management for a cleaning company
The client calls to say something was not cleaned. The office does not know whether the crew was on site, whether a skipped room was marked, or whether this is a repeat complaint on the same building.