Guard Management Software for a 10–100 Guard Company: Shifts, Patrols and Incidents in One App

Guard management software is one app where a small security company keeps guard shifts, patrol checkpoints, incident reports and the records a client asks for — instead of a spreadsheet for the schedule, a group chat for the patrols and paper for everything else. If you run 10 to 100 guards across several sites, you already know where the gaps are: a shift nobody confirmed until the client called at 23:10, a patrol that "was done" with no record, and an incident that reached you as a voice message three hours later. We covered incident reports in detail in security incident reporting from the guard's phone; this article looks at the whole picture — what a company of this size actually needs in one place, what it can skip, and how to choose without buying enterprise software you will never configure.

What guard management software has to cover for a 10–100 guard company

At this size you do not have a control room with three operators. You have an owner or an operations manager, a couple of shift supervisors, and a phone that never stops. So the software has to do four things without a dedicated administrator: put the right guard on the right site at the right time, make patrols provable, turn incidents into a record within a minute, and give you the history when a client or an inspector asks for it. Everything else — dashboards, KPI reports, integrations — is optional until those four work.

Shifts: who is on which site tonight

The schedule is the foundation, because a patrol or an incident is always tied to a guard on a shift. A schedule kept in a spreadsheet or a chat breaks in the same places every month: rotations that repeat with a mistake copied from last month, vacations nobody entered, and replacements agreed by phone that never reached the plan. What the schedule in guard management software should handle:

• Recurring patterns per site — 2/2, 1/3, day/night — created once and repeated, so that a 30-guard month is not typed by hand (we walked through this in guard shift scheduling software: cover every shift, every time).

• Vacations and replacements inside the same calendar, so the replacement guard is the one who gets the site's tasks and notifications that night.

• A day view the supervisor can open at 19:00 and see every site with an avatar on it — and every site without one.

• Custom one-off shifts for events, escorts and short contracts that do not fit a pattern.

Patrols: checkpoints as recurring tasks

A patrol is a set of checkpoints that must be visited at intervals. In software built for small companies, each checkpoint is a recurring task assigned to the shift: "Warehouse gate — every 2 hours — photo required". The guard opens the task on the phone, takes a photo of the checkpoint, and the app stores the time and location with it. If the checkpoint has a reference image, AI compares the guard's photo with it and scores the match; a photo of the ceiling instead of the gate does not pass. A missed interval shows up as an overdue task in the supervisor's calendar and as a notification — no wand, no RFID tags, no readers to buy.

This is the part most companies get wrong when they choose a system: they pick a hardware guard tour system for the checkpoints and keep the schedule elsewhere. Then the patrol log says "checkpoint 4 at 02:14" but nobody can tell which guard was on that shift without opening a second file. When shifts and patrols live in one calendar, the answer is on the same screen.

Incidents: a report the guard can file in a minute

An incident report written at the end of a shift is a memory, not a record. The guard needs to file it at the moment: a photo, the time and position from the phone, and two sentences said out loud. With a voice assistant, the guard says "Broken window on the north side of building B, 01:40, photo attached, notify the supervisor" — and the app creates the task with the site, the time, the attachment and the person to notify. The supervisor gets a notification and can answer in the task's comments; the client gets a record with a timestamp, not a retelling.

How to choose guard management software: a checklist for a small security company

Before a demo, write down how your operation works today — sites, shift patterns, number of checkpoints per site, how incidents are reported. Then check each candidate against this list:

1. Shifts, patrols and incidents are in one calendar. If the schedule is a separate module or a separate product, you will keep two systems in sync by hand.

2. No hardware to buy or maintain. A checkpoint should be a task with a photo and a location, not a tag glued to the wall that falls off in winter.

3. Photo proof is verified, not just stored. Ask whether the system compares the photo with a reference or simply saves whatever the guard sent.

4. Guards can work from an ordinary phone with a few taps. Test it with your oldest guard, not with your most technical supervisor.

5. Replacements and vacations are part of the schedule, not a note in a chat. Assign a replacement and confirm that the new guard receives the site's tasks.

6. The supervisor is notified of an overdue checkpoint or a new incident without checking the app every ten minutes.

7. History per site is exportable for a period, so a client's "show me last month's patrols" takes minutes, not an evening.

8. Pricing fits a company of 10–100 people, without a per-site fee, an implementation project or a yearly contract.

What "one app" means in practice

Take one night at one site. At 19:00 the supervisor opens the day view and sees the guard's avatar on the 20:00–08:00 shift. At 20:00 the guard's phone shows the shift and the checkpoints tied to it: six tasks repeating every two hours. Each check-in is a photo with time and location; the AI scores it against the reference image. At 01:40 the guard files an incident by voice; the supervisor answers in the comments at 01:44. In the morning the site's history contains 36 check-ins, one incident and one comment thread — and the owner can send the client that period's record without asking anyone what happened. None of this required a second app or a paper log.

What it costs and how to start

For a company of this size the price matters as much as the features, because a system that costs more than a guard's shift will be dropped after the first quiet month. CosaNostra is free for a team of up to 2 people, and paid plans start from $5.99/month — so a 10-guard company can run shifts, patrols and incidents for less than an hour of a guard's pay. Start with one site: enter its shift pattern, create the checkpoints as recurring tasks with reference photos, and ask the guards to file incidents by voice for a week. Add the next site when the first one runs without you.

"We stopped asking 'was the patrol done?' and started asking 'why did checkpoint 3 fail at 02:00?'. The second question has an answer in the app; the first one never had one." — operations manager, private security company with three sites.

How CosaNostra brings shifts, patrols and incidents into one calendar

CosaNostra is guard management software for small teams: shifts with recurring patterns, vacations and replacements; patrol checkpoints as recurring tasks with AI photo verification, time and location; incidents created by voice in a minute, with attachments, comments and a notification to the supervisor; and a per-site history you can export for any period. Everything sits in one team calendar with day, week and month views, on an ordinary phone, with no hardware to buy.

See how it works for security companies on the guard tour system page, and set up your first site tonight.

Frequently asked questions

What is guard management software?

Guard management software is an app where a security company keeps guard shifts, patrol checkpoints, incident reports and the per-site history in one place, so the schedule, the patrols and the incidents are tied to the same guard and the same shift instead of living in a spreadsheet, a chat and a paper log.

Do we need hardware checkpoints for patrols?

No. A checkpoint can be a recurring task with a required photo: the app stores the time and location with the photo and, if there is a reference image, AI compares the two and scores the match. A missed interval shows up as an overdue task and a notification to the supervisor.

How does a guard file an incident?

By voice, at the moment it happens: the guard says what happened, where and whom to notify, attaches a photo, and the app creates a task with the time and position from the phone. The supervisor gets a notification and answers in the task's comments.

How much does it cost for a company of 10–100 guards?

CosaNostra is free for a team of up to 2 people, and paid plans start from $5.99/month. There is no per-site fee and no hardware to buy, so a 10-guard company can run shifts, patrols and incidents from the first month.

Security Incident Reporting From the Guard's Phone: What to Log and How

Security incident reporting from the guard's phone means the guard records what happened at the moment it happens — with a photo, the time, the position and a spoken description that the app turns into a structured card — instead of writing a report from memory at the end of the shift. The operational problem is familiar to any owner of a small security firm: at 02:40 a guard finds a warehouse door open, calls the supervisor, tapes it shut and moves on; at 07:00 the client asks what happened, and the only record is a line in the logbook written at 06:30 that says "door 3 open, secured". No photo, no exact time, no idea whether anything was taken. If your rounds are already recorded as an automatic patrol report from the guard's phone, incidents are the piece that still lives on paper — and this article is about moving it.

Why incident reports written at shift end are useless

An incident report has two readers: the supervisor who has to decide what to do now, and the client who will ask about it later. A report written at the end of the shift serves neither.

By 06:30 the guard has done four more rounds. The time becomes "around 2:30", the description shrinks to one sentence, and the details that matter — was the padlock cut or missing, were the lights on inside, which way the tracks in the snow went — are gone. The supervisor learns about the incident from a phone call and has nothing in front of him. The client gets a sentence and a signature, and a disputed claim turns into two stories with no evidence on either side.

The fix is not a longer form. Guards will not fill in a long form at 02:40 in the cold, and they should not have to. The fix is to capture three things at the point, in under a minute, and let the phone do the rest.

What to log in security incident reporting

Every incident record needs the same four elements, and none of them should require typing.

Photo first, before anything is touched

The photo is the evidence. It should be taken before the guard closes the door, moves the object or steps into the area — the state as found, not the state after the guard fixed it. Two or three photos are better than one: the wide shot showing where it is, the close-up showing what is wrong. If the guard's rounds already use AI photo checks at each checkpoint, the guard is used to this, and the incident photo simply goes on the same task.

Time and position, recorded by the phone

The time and the location must come from the device, not from the guard's memory. A record created at 02:41 at the position of warehouse door 3 is a fact; "around 2:30 at the warehouse" is a recollection. This is the same principle that makes security patrol tracking without RFID work: the phone already knows where and when, so the guard should never be asked to enter it.

What was found and what was done, spoken, not typed

The description is where reports fail, because typing on a phone with gloves on at night does not happen. The guard should be able to say it: "Warehouse door 3 open, padlock missing, no one inside, closed the door, called Mark." Voice AI turns that sentence into a structured card — a task with the site, the time, the person to notify and the photo request — and the guard confirms it with one tap. What the guard said stays as the description, in the guard's own words, which is what a client or a police officer will later want to read.

Who was told, and when

An incident record without an owner is a note nobody acts on. The card must name the person who was notified — the supervisor on that night's shift — and the notification must go out the moment the card is saved, not when someone reads the logbook in the morning. The supervisor then sees the photo, the position and the description on his phone and decides whether to drive out or wait for the day shift.

How to set up incident reporting from the guard's phone

The steps below assume the guards already carry a phone with the app used for their rounds. Nothing is installed on the site.

• Decide who receives incident notifications on each shift and put that person into the shift schedule. If the supervisor changes on weekends, the notification must follow the schedule, not a name typed into a form.

• Write a short rule for guards: photo first, then speak, then act. Three lines on the wall of the guard room are enough. The order matters — a photo taken after the door is closed proves nothing.

• Give the guards three example sentences to say, in the form the app understands: what, where, what was done, who to tell. "Fire exit on the second floor propped open with a brick, removed it, photo attached, notify the supervisor." Guards copy patterns; give them good ones.

• Agree with each client which incidents they want to hear about immediately and which can wait for the shift report — an open door at 3 a.m. and a broken lightbulb are not the same call.

• Ask guards to add one comment on the incident task when it is closed: what the outcome was. "Site manager arrived 03:20, door locked, nothing missing." That closes the record.

• Run one drill on each site in the first week: stage a fake incident, time how long the record takes, read it from the client's side. If it takes more than a minute or reads badly, fix the example sentences.

Mistakes that make incident records worthless

Letting the guard write the time. Any field the guard fills in by hand is a field a lawyer can question. Time and position come from the phone or they do not count.

Keeping a paper incident book as a backup. If both exist, the guard fills in the one that takes less effort, and the app history has gaps that the client will notice on the day it matters.

Reporting to a person instead of a shift. The supervisor who was on duty last Tuesday is on holiday this Tuesday. The notification must go to whoever is in the schedule tonight.

Making incident reporting a punishment. If a report leads to a lecture, guards stop reporting. A record with a photo and a timestamp protects the guard from the accusation that he did nothing; say that out loud at the next shift briefing.

Where the incident records live afterwards

Once each incident is a task with a photo, a time, a position, a spoken description and a closing comment, the history of a site becomes the incident log the client asks for. Open the site for a month and every incident is there in order, next to the rounds that were done and the shifts that were on duty, so a question like "how many times was the back gate found open in August?" is answered by looking, not by reading a paper book page by page. The same history exported for a period is what goes to the client together with the patrol report, and what goes to the insurer or the police when a single night has to be reconstructed.

That is what security incident reporting looks like for a small firm when it is done from the guard's phone: a photo taken as found, a time and a position the guard never typed, a description spoken in the guard's own words and turned into a card by AI, a notification that reaches the supervisor on that shift within the minute, and a closing comment that ends the record. CosaNostra is built around exactly these pieces — voice creation of tasks with a site, a time, an assignee and a photo request, photo attachments and comments on the task, notifications to the person on shift, and a site history you can open or export for any period, with shifts in the same calendar. See the full setup for security companies on the CosaNostra guard tour system page.

Frequently asked questions

What should a security incident report from the guard's phone contain?

Four things: a photo of the situation as found, taken before anything is touched; the time and position recorded by the phone rather than typed by the guard; a description of what was found and what was done, spoken and turned into a card by the app; and the name of the person who was notified. A closing comment with the outcome completes the record.

How does security incident reporting work without typing?

The guard takes the photo and says what happened in one sentence — what, where, what was done, who to tell. Voice AI converts that sentence into a task with the site, the time, the assignee and the photo attached, and the guard confirms it with one tap. The spoken words stay as the description, so nothing is retyped and nothing is written from memory at shift end.

Who gets notified when a guard logs an incident?

The person who is in the shift schedule for that night — the supervisor or the senior on duty — receives a notification with the photo, the position and the description the moment the card is saved. Because the notification follows the schedule and not a name in a form, a weekend replacement receives it without any change to the setup.

How does the client receive incident records?

Each incident is stored in the site history as a task with its photo, time, position, description and closing comment, next to the rounds and shifts of the same period. The history is opened or exported for the agreed period and sent together with the patrol report, and the same export for a single night answers a dispute or an insurer's request.

Proof of Patrol App for Clients: Automatic Patrol Reports Instead of Paper Logs

A proof of patrol app replaces the paper patrol log with a record the guard's phone creates on its own: every checkpoint visit is stored as a completed task with the time, the GPS position and a photo checked by AI, and the site history for any shift or month becomes the report the client receives. The problem it solves is not that guards refuse to fill in the log. It is that a paper log proves nothing. A line that says "02:00 — round done — signature" was written by the person whose work it is supposed to confirm, at a time nobody can verify, and the client knows it. When a door is found open in the morning, the logbook turns into a piece of paper both sides argue about. If your rounds are already recorded with GPS check-ins and AI photo proof at each point, this article is about the next step: turning that record into a report a client accepts without a phone call, and doing it without anyone typing a report at the end of the shift.

Why the paper patrol log fails the client

A patrol logbook exists for one reader: the client who pays for the site to be covered. It is supposed to answer two questions — were the rounds done, and what was found. On paper it answers neither in a way the client can check.

The entries are written by the guard, often at the end of the shift from memory, and they look the same whether the round happened or not. The times are round numbers because the guard writes "02:00", not "02:07". Findings are compressed to "all in order" because writing more takes time and invites questions. And the book lives in the guard room, so the client only sees it during a site visit, or as a photographed page sent by the site manager once a month.

The result is a report that costs the firm effort every month and still cannot settle a dispute. The client's real question, "prove that the 2 a.m. round was done on the 14th", is answered with a signature.

What a proof of patrol app records instead

The change is not a nicer form. It is that the record is created at the checkpoint, by the phone, at the moment the guard completes the point — not written afterwards.

One entry per checkpoint, created at the point

Each checkpoint on the route is a recurring task in the team calendar with a due time and a location attached. When the guard completes it, the app stores the time and the device position. The task either exists as done at a verified position, or it becomes overdue when the due time passes.

Photo, position and time in one record

The task also carries a reference photo taken when the route was set up and a one-line description of the correct state — "gate chained and locked", "fire exit clear". The guard takes one photo, AI compares it with the reference and returns a score. The photo is stored with the position and the time, so a single checkpoint entry shows where the guard stood, when, and what the point looked like.

Exceptions logged when they happen

A photo that does not match the reference flags the task and sends a notification to the supervisor the same minute, with the photo attached. The guard adds a comment on the task — "padlock missing, called the site manager" — and that comment sits in the same history as the photo. The report later shows the exception at the time it occurred, not as a sentence written from memory at shift end.

Turning the shift history into the client report

Once every checkpoint occurrence is a task with a state, a time, a position and a photo, the report stops being a document someone writes. It is the history of the site filtered by period.

What the client actually wants to see

Clients rarely read a full round-by-round list. What they check is simple: every scheduled round exists and was completed on time; skipped or late points are visible rather than hidden; the exceptions have photos and a note about what was done; and the shift schedule shows who was on duty when each of those things happened. A history where done, overdue and flagged tasks are shown as such gives them all four without interpretation.

Weekly and monthly reports without typing

For a weekly or monthly report the supervisor opens the site history for the period and exports it. Each checkpoint occurrence is there with its state, time, position and photo, and the shift schedule for the same days sits next to it. For a dispute, the same history opened for one night answers the question in minutes: a real round is a chain of done tasks a few minutes apart at the right positions with photos that passed.

Setting up automatic patrol reports for a site

The steps below assume the route already exists; if it does not, set that up first.

• Build the route as recurring checkpoint tasks with a location and a reference photo at each point, as described in the guide to QR code patrol checkpoints and setting up a guard route. The report is only as good as this setup: a location attached from the office produces false flags the client will ask about.

• Write the description of each point in the words the client uses. "Warehouse door 3 closed and sealed" reads well in a report; "point 7 OK" does not.

• Agree with the client which exceptions they want to hear about immediately and which can wait for the report. Put the person who takes the immediate ones into the shift schedule so the notification has an owner.

• Ask guards to add a comment on any flagged or unusual task before moving to the next point — one sentence, while it is fresh. This replaces the "findings" column of the paper log.

• Decide the reporting period with the client — weekly for a new site, monthly for a stable one — and export the history on the same day each period.

• Before the first report, walk one round yourself and read the history from the client's side. If you cannot tell where the guard stood and what the point looked like, fix the setup before the client sees it.

Common mistakes when replacing the paper log

Keeping both. If the paper book stays in the guard room "just in case", guards fill it in instead of completing tasks, and the app history has gaps the client will notice. Remove the book on the day the route goes live.

Not reviewing flags before the report goes out. A flagged photo with no comment looks like a problem nobody handled. Ten minutes on the morning after each shift, in the first two weeks, keeps the report clean and trains the thresholds.

Assigning tasks to a named guard instead of the shift. When a replacement covers Tuesday night, the route must follow the shift, or the report shows a night with no rounds while a guard was in fact on site.

Treating the record as a stick. Guards accept a history that protects them from an accusation and resent one that exists only to catch them. Show the shift the first report and point out what it proves for them.

Put together, this is what a proof of patrol app looks like for a small security firm with a handful of ordinary sites: a printed label at each point, the phone the guard already carries, a checkpoint record with time, position and an AI-checked photo, and a site history that is exported for the period and sent to the client instead of a photographed page from the logbook. CosaNostra is built for exactly this: patrol routes as recurring tasks with locations and reference photos, notifications on overdue or flagged points, comments on the task where the exception happened, and a site history you can export for any period, with shifts in the same calendar. See the full setup for security companies on the CosaNostra guard tour system page.

Frequently asked questions

What is a proof of patrol app?

It is an app that records each checkpoint visit from the guard's phone as a completed task with the time, the GPS position and a photo checked by AI against a reference image. The history of those tasks for a shift, a week or a month is the patrol report — nothing is written up afterwards and nothing is installed on the site apart from printed labels.

What does the client receive instead of the paper patrol log?

The site history for the agreed period: every scheduled checkpoint occurrence with its state — done, overdue or flagged — the time, the position and the photo, next to the shift schedule showing who was on duty. It is exported for the period and sent to the client, so the same file answers a routine monthly review and a dispute about one night.

How are incidents and findings recorded without a "findings" column?

A photo that does not match the reference flags the task and notifies the supervisor immediately. The guard adds a comment on that task — one sentence about what was found and what was done — and the comment is stored with the photo and the time, so the report shows the exception at the moment it happened.

Can a guard still fake a round in the app?

Each entry is created only when the task is completed at a verified position with a timed photo, and every occurrence has a due time after which it becomes overdue. A round completed from one spot within a minute, a photo that does not match or a chain of overdue tasks is visible in the history, which is exactly what a signed line in a logbook could never show.