Tag: Security Reporting Software

  • Fire Watch Log: The Complete Guide to Compliance

    Fire Watch Log: The Complete Guide to Compliance

    I’ve seen fire watch logs handled two completely different ways. One kind gets pulled out during an inspection and the inspector barely glances at it before moving on. The other kind gets picked apart line by line and the facility manager standing there realizes halfway through that they’re in trouble. The difference almost never comes down to bad luck. It comes down to whether the person filling out the fire watch log understood why each line existed in the first place.

    This guide walks through everything you need to know about keeping a compliant fire watch log, not just the checklist version.

    Start with what a fire watch log is actually standing in for

    Every building with a fire suppression system is relying on automation. A sprinkler head senses heat and activates. A detector senses smoke and triggers an alarm. None of that requires a person to notice anything.

    The moment that system goes offline, even temporarily, the building loses that automatic response. A fire watch exists to replace it with a human one. A trained person walks the space, uses their senses instead of a sensor and is ready to pull an alarm or grab an extinguisher if something starts.

    A fire watch log is the only thing that proves that human backup was actually functioning during the gap. Nobody can retroactively prove they were paying attention during a window that’s already passed. The log is the substitute for that proof, which is why an accurate fire watch log matters as much as the watch itself.

    Real scenarios where a fire watch log is required

    It helps to think through actual situations rather than abstract rules.

    A restaurant’s kitchen suppression system needs annual servicing. The technician is on site for four hours doing the inspection and recharge. Depending on local code, that might fall under a window where a fire watch log isn’t required at all, or it might require one if the servicing runs long or if hot cooking equipment stays in use during the work.

    A mid-rise apartment building under construction has framing done on floors one through six, but the standpipe system for the fire department connection isn’t hooked up yet. Workers are doing electrical rough-in with power tools that create sparks near stored lumber. This is a textbook case where a fire watch log isn’t optional, according to guidance published by the National Fire Protection Association on construction and demolition fire safety.

    A hospital wing has its sprinkler system impairment shut down overnight for a valve replacement. Patients are still in adjacent rooms. This is one of the highest scrutiny situations you can be in, because occupant safety concerns stack on top of property concerns and fire marshals tend to inspect a healthcare facility’s fire watch log with a finer comb than almost any other occupancy type.

    A warehouse is hosting a private event with string lighting, a stage and folding chairs set up in a way that partially blocks two of the sprinkler zones. Even though the system is technically operational, the physical obstruction can trigger a fire watch requirement in some jurisdictions because the sprinklers can’t do their job through a blocked zone.

    Each of these looks different on the surface, but the underlying question is the same. Is there a period when the automatic protection can’t do its job and is a fire watch log being kept to document the person filling that gap?

    Getting the trigger conditions right

    This is the part people guess on most often and guessing wrong is expensive in either direction. Assume you need a fire watch log when you don’t and you’re paying for staffing that wasn’t required. Assume you don’t need one when you do and you’re sitting on a violation waiting to be discovered.

    The baseline framework in the US comes from NFPA 1, the Fire Code and NFPA 241, which covers construction and demolition specifically. Both give general guidance on impairment durations and hot work precautions that determine when a fire watch log becomes mandatory. But the actual enforcement sits with your local Authority Having Jurisdiction and that office can be stricter than the NFPA baseline. Some cities require a fire watch log the moment a system goes down, regardless of expected duration. Others give a grace window, commonly four hours, before one becomes mandatory. The U.S. Fire Administration also publishes general fire prevention guidance worth reviewing if you’re setting up a policy for the first time.

    Calling your local fire marshal’s office before starting any impairment work isn’t excessive caution. It’s the only way to know which version of the rule actually applies to your address and which fire watch log requirements apply to your specific occupancy type.

    What the entries in a fire watch log need to contain

    Break this down entry by entry rather than treating it as one lump requirement.

    Timestamp for every single round. If your required interval is 30 minutes, sixteen rounds happen across an eight-hour shift. Sixteen separate timestamps should exist in the fire watch log, not four broad time blocks.

    Signature per entry, not one signature covering the whole log. Individual accountability for each specific round matters if anything is ever questioned later.

    Named locations, specific enough that someone reading the fire watch log later could retrace the exact path. “Checked mechanical room, loading dock and east stairwell” holds up. “Checked building” does not.

    Genuine observations. This is the one people skip the most. If a round was uneventful, write down what was specifically checked and confirmed clear, not just the word “clear.” If something was slightly off, a space heater running unattended, an exit door propped open with a trash can, note it and note what was done about it.

    Equipment status per round or at reasonable intervals depending on your local requirements. Extinguishers present and accessible. Exits unobstructed. Alarm pulls undamaged and reachable.

    Communication method confirmed working. Whoever’s on watch needs an actual way to call for help immediately and that should be verified rather than assumed.

    Irregularities were logged even when nothing came of them. A pattern across several watches, the same door getting propped open every week, a storage area slowly accumulating boxes near a heat source, is often more valuable information in a fire watch log than any single clean round.

    Total watch period start and end times are tracked separately from the individual round timestamps.

    The reason for the watch is documented specifically. A permit number for hot work. A work order number for the impaired system. Vague reasons like “system down” without a reference number make the fire watch log harder to tie back to an actual authorized event.

    Supervisor sign-off at whatever interval your jurisdiction requires, commonly at the end of the shift or the end of the full watch period.

    (Related reading: see our guide on hot work permit requirements and our fire alarm system impairment checklist for related compliance steps.)

    The failure that catches people off guard

    Missing one round doesn’t just cost you that round. It tends to undermine the credibility of the entire fire watch log.

    Picture an eight-hour watch with a required 30-minute interval. If there’s a 90-minute stretch where nothing was logged, an inspector reviewing that fire watch log after an incident isn’t going to read it as “97 percent compliant.” They’re going to read it as evidence that the watch broke down at some point and that undermines the reliability of everything else on the page, even the rounds that were done correctly.

    There’s a second failure that’s less obvious but just as damaging. A fire watch log where every single entry says “all clear” in identical wording, shift after shift, starts to look manufactured rather than lived. Real buildings have small variations. Different foot traffic at different hours. A door that sticks sometimes and not others. Weather affects how a space feels. When a log shows zero variation across dozens of entries, it reads like it was filled out from memory or copied from a previous shift rather than walked in real time and that’s the exact impression that invites deeper scrutiny.

    Paper logs versus digital fire watch log tools, honestly compared

    Paper is nearly free and requires no training. The trade-off is that a paper fire watch log depends entirely on discipline. It is genuinely easy, on a slow overnight shift with nothing happening, to fill in the last three rounds from memory at 2am instead of walking them as they occur. Handwriting inconsistencies, a smudged timestamp, a page that got left in a truck instead of being filed properly, all of these are common paper-specific failures that show up during real audits.

    Digital fire watch log tools timestamp the moment an entry is submitted, which removes the ability to backfill rounds after the fact. Some tools use location verification to confirm the watch person was actually in the area they logged. The Occupational Safety and Health Administration also recommends documented monitoring procedures as part of a broader workplace fire safety program, which digital tools tend to make easier to maintain consistently.

    Neither format automatically wins in an inspector’s eyes. A meticulously kept paper fire watch log beats a careless digital one every time. But digital tools remove a lot of the human shortcuts that create problems, which is why larger facilities and construction sites increasingly default to them.

    What actually happens when a fire watch log falls short

    Fines are the most visible consequence and the range varies enormously by jurisdiction and severity, sometimes a few hundred dollars, sometimes into the thousands for repeat or serious violations.

    Construction sites face something often worse than a fine: a stop-work order. Every day of delay on an active job site can cost far more than any fine attached to the original violation.

    The insurance side tends to be the largest financial risk in the long term. If a fire happens during an impairment period and the fire watch log is missing, incomplete or clearly falsified, the insurer has a real basis to deny the claim outright, which can mean the facility absorbs the full cost of the damage with no coverage at all.

    Whoever supervised the watch can also face personal liability questions, particularly in a case involving injury, where negligence gets examined in detail by investigators and potentially in court.

    And there’s a compounding effect on future inspections. Fire marshals keep records of past violations at a given address and a facility with a documented fire watch log failure tends to get inspected more closely and more often going forward.

    Building a fire watch log system that holds up over time

    None of this requires a complicated system, just a consistent one.

    Pick one format, paper or digital and use it every time without exception. Inconsistency between shifts or between different staff members is where gaps in a fire watch log tend to open up.

    Train the actual watch person on hazard recognition, not just paperwork. Someone who doesn’t know what a fire risk looks like can produce a perfectly formatted fire watch log that misses everything that matters.

    Treat the interval requirement as fixed. If it’s 30 minutes, that stands regardless of how uneventful the shift feels.

    Retain completed fire watch logs for whatever period your local authority requires, commonly one to three years, sometimes longer for higher-risk occupancy types like healthcare or high-rise residential.

    Go back through old fire watch logs periodically instead of only filing them. Recurring small issues across multiple watches are often the earliest warning signs of a bigger hazard forming.

    (For a deeper dive into staff training requirements, see our fire safety training for facility staff guide.)

    A basic fire watch log template

    DateTimeArea CheckedObservationsEquipment StatusWatch Person Signature

    An eight-hour watch with a 30-minute interval should produce sixteen individual rows in the fire watch log, not one summary line at the end of the shift.

    Common questions people ask about fire watch logs

    Does a fire watch need to be a dedicated person or can existing staff rotate through it? This depends on your local code and the specific situation. Some jurisdictions allow existing staff to take on the role as long as they’re properly trained and it doesn’t pull them away from other safety duties. Others require a dedicated person with no other responsibilities during the watch. Check with your AHJ before assuming either way.

    How long does a fire watch log need to be kept after the watch ends? Most jurisdictions require one to three years, but certain occupancy types, especially healthcare and high-rise residential, sometimes require longer. Confirm with your local authority rather than assuming a standard timeframe applies everywhere.

    Can a fire watch log be handwritten and still hold up during an audit? Yes, as long as it’s filled out accurately and in real time. Handwritten fire watch logs are only a problem when they show signs of being filled out after the fact, inconsistent handwriting, timestamps that don’t match a plausible sequence of events or gaps that suggest rounds were skipped.

    What’s the difference between a fire watch log for an impaired system and one for hot work? An impairment fire watch log covers a period when an automatic system, sprinklers or alarms are offline. A hot work fire watch log covers the period during and often after welding, cutting or similar work, since sparks and heat from that work can ignite something nearby well after the actual work has stopped. The reason for the watch should always be documented clearly since the two situations sometimes carry different durations and monitoring requirements.

    Where this leaves you

    The rules themselves aren’t complicated once you’ve walked through them. What actually separates a fire watch log that holds up from one that falls apart under review comes down to the same handful of details every time. A real timestamp on every round. Observations that describe what was actually checked instead of a repeated phrase. Discipline to keep the intervals consistent even on the quietest shift of the month.

    Get those right and your fire watch log does its job the one time it’s actually needed. Skip them and you end up with a stack of paper that looks like compliance from a distance but won’t hold up the moment someone actually reads it closely.

    For information, visit our website https://avessecurity.com/

    FAQ

    How long does a fire watch log need to be kept after the watch ends? Most jurisdictions require one to three years, but certain occupancy types, especially healthcare and high-rise residential, sometimes require longer. Confirm with your local authority rather than assuming a standard timeframe applies everywhere.

    Can a fire watch log be handwritten and still hold up during an audit? Yes, as long as it’s filled out accurately and in real time. Handwritten fire watch logs are only a problem when they show signs of being filled out after the fact, inconsistent handwriting, timestamps that don’t match a plausible sequence of events, or gaps that suggest rounds were skipped.

    What’s the difference between a fire watch log for an impaired system versus one for hot work? An impairment fire watch log covers a period where an automatic system, sprinklers or alarms, is offline. A hot work fire watch log covers the period during and often after welding, cutting, or similar work, since sparks and heat from that work can ignite something nearby well after the actual work has stopped. The reason for the watch should always be documented clearly since the two situations sometimes carry different duration and monitoring requirements.

    How often does a fire watch log need to be filled out? Most codes require a new entry every 30 minutes, though some higher-risk occupancies or more severe impairments call for more frequent rounds, sometimes every 15 minutes. The exact interval depends on your local fire code and the nature of the hazard, so confirm with your AHJ rather than assuming 30 minutes applies universally.

    Who is legally responsible if a fire watch log is incomplete or inaccurate? Responsibility typically falls on whoever was assigned to conduct the watch, along with the supervisor or facility manager who signed off on it. In serious incidents, both parties can face liability questions, which is part of why signature and sign-off requirements exist at multiple levels of the log.

    Does a fire watch log need to be notarized or certified in any way? Generally no. A fire watch log doesn’t need notarization, but it does need to be signed by the person conducting each round and typically countersigned by a supervisor. Some jurisdictions may require the log to be available for review by the fire marshal on request, but formal certification isn’t standard practice.

    Can one person cover a fire watch for multiple buildings or zones at once? This depends entirely on local code and the size and layout of the area involved. Some jurisdictions allow one person to cover multiple adjacent zones if they can complete the required rounds within the mandated interval. Others require a dedicated watch per building or per zone, especially in higher-risk occupancies. Never assume one person can cover more ground than the interval realistically allows.

    What’s the difference between a fire watch log and a fire watch permit? A fire watch permit is often issued alongside a hot work permit and authorizes the watch to take place, sometimes required before work can even begin. A fire watch log is the ongoing record of what happened during that authorized watch period. Some jurisdictions require both, so check whether your permit process and your logging requirements are handled by the same office or separately.

    Do fire watch log requirements apply to residential buildings, or just commercial ones? Fire watch requirements can apply to residential buildings too, particularly high-rise apartments or buildings undergoing construction or major system impairment. Occupied residential buildings often face stricter scrutiny because life safety concerns are higher, so don’t assume residential properties are exempt just because they aren’t commercial or industrial.

    What should happen if a hazard is discovered during a fire watch round? The immediate priority is addressing the hazard directly, whether that means removing a combustible item, correcting a propped-open door, or in a serious case, evacuating and calling emergency services. The fire watch log should document what was found, what action was taken, and the time it happened. A hazard that gets fixed but never logged leaves no record that the watch was actually doing its job.

  • What Is a Performance Development Plan? A Guide for Security Teams

    What Is a Performance Development Plan? A Guide for Security Teams

    A performance development plan is a written agreement between a manager and an employee that sets specific goals, the support needed to reach them and the dates those goals will be reviewed. For a security team it turns a vague “improve your patrols” conversation into a documented plan the guard has seen, understood and formally accepted. That accepted record is what protects both sides when performance is later disputed.

    Security operations run on shift work, spread across sites, with supervisors who rarely sit in the same room as the guards they manage. Development conversations happen verbally at a gatehouse and are forgotten by the next roster. A performance development plan fixes that gap by putting the goal, the timeline and the acknowledgement in one place.

    Why a performance development plan matters for security staff

    Guarding is measured on consistency: patrols completed, checkpoints scanned, handovers logged, incidents reported correctly. When a guard falls short, most teams either ignore it or jump straight to disciplinary action. A performance development plan is the missing middle step. It gives the guard a fair, recorded chance to improve before anything escalates.

    It matters for three reasons. It creates accountability, because the guard has accepted a specific goal rather than a general complaint. It creates a paper trail, so if the same issue recurs the escalation is defensible. And it supports retention, because good guards stay where they can see a path to a supervisor or site-lead role rather than being managed only by punishment.

    Without a documented plan, the common failure is disagreement about what was ever agreed. The guard says no target was set; the supervisor says it was discussed. Neither can prove it. A plan the guard has formally accepted removes that argument entirely.

    How a performance development plan works

    A good plan follows a simple loop: agree the goal, record the guard’s acknowledgement, set a review date, then review against the same written target. The strength of the process is that nothing depends on memory.

    In AVES the Performance Development Plan module holds the plan as a formal record and requires the employee to accept or decline it. That accept or decline response is the part paper forms never capture. When a guard accepts, you have proof they saw and agreed the goal. When a guard declines, you have an early signal that a conversation is needed before the review period even starts, not after it has failed.

    Because the plan lives in the same system as the guard’s operational records, the review is grounded in evidence rather than impression. Patrol completion, shift handover submissions and incident reports already sit in the platform, so a supervisor reviews the plan against what actually happened on shift instead of relying on a gut feeling about the guard.

    What to include in a performance development plan

    Keep it short enough that a guard reads it on a phone at the start of a shift. Every plan should cover:

    • The specific goal. Not “be more reliable” but “complete all scheduled patrol checkpoints on every shift” or “submit the shift handover before leaving the post”.
    • The current gap. A plain statement of where performance stands today, so the target is measured against a known starting point.
    • The support offered. Retraining, a mentor, a refresher on the app, or a revised checklist. A plan that only lists demands and no support is a warning, not a development plan.
    • The review date. A fixed date when manager and guard sit down against the same written goal.
    • The acknowledgement. The guard’s formal accept or decline, with the name, date and time recorded automatically.

    That acknowledgement is the difference between a plan and a note. Everything above it is intention; the accept or decline is the evidence.

    Common mistakes to avoid

    The most frequent error is writing goals a guard cannot control. Tying a plan to “reduce site incidents” punishes the guard for events outside their influence. Tie it instead to the behaviours they own: patrols scanned, handovers logged, reports filed correctly.

    The second mistake is no acknowledgement step. A plan the employee never formally accepted is worth little if performance is later challenged, because there is no proof the guard ever agreed to it. Always capture the accept or decline.

    The third is setting a plan and never returning to it. A review date that passes unactioned tells the guard the plan was never serious, and every future plan carries less weight. If you set a date, hold the review.

    The fourth is confusing development with discipline. A performance development plan is a chance to improve. A disciplinary or show-cause notice is a separate, later step for when improvement has not happened. Keeping the two distinct keeps the development plan constructive and keeps your escalation defensible.

    Frequently asked questions

    What is a performance development plan?

    A written agreement between a manager and an employee that sets specific goals, the support to reach them and a review date, with the employee’s formal acknowledgement recorded. For security staff it converts a verbal coaching chat into a documented, accepted plan.

    How is a performance development plan different from a performance improvement plan?

    A development plan is generally forward-looking and can apply to any guard growing toward a target, including strong performers. A performance improvement plan is usually the more formal, remedial step when performance is already below standard. In practice the structure, of goal, support, review and acknowledgement, is much the same.

    Who should sign off a performance development plan?

    The supervisor or site lead who set the goal and the employee it applies to. The employee’s accept or decline is the essential record; a plan without the employee’s acknowledgement is incomplete.

    How often should a performance development plan be reviewed?

    Set an explicit review date when the plan is created, commonly 30 to 90 days out depending on the goal. The key is that the review happens against the same written target the guard accepted.

    Can a performance development plan lead to disciplinary action?

    It can, if the agreed goal is not met after fair support and a proper review. Kept separate and documented, the development plan becomes the evidence that the guard was given a fair chance before any escalation.

    Set fair, trackable development plans for your guards

    AVES holds each performance development plan as a formal record with a built-in accept or decline step, and reviews it against the patrol, handover and reporting data your guards already generate, so every plan is fair, tracked and defensible.

    Book a 30-minute demo and we will show you the actual Performance Development Plan screen, including how the accept or decline acknowledgement is captured: book a demo.

    See how security teams put this into practice on our Instagram.

    Prefer to explore first? Start a free trial and set up your first development plan today.

  • Supplier Management Guide for Companies

    Supplier Management Guide for Companies

    A truck pulls up at the gate. Driver hands over a box, gets a signature, drives off. Nobody writes down what arrived, when or who signed for it. Feels like nothing. Barely worth pausing the shift for.

    Three weeks later a client calls asking where their shipment went. And you realize… nothing was ever actually tracked. Just a chain of handoffs that nobody wrote down.

    If that’s why you’re reading this, you’re not alone and you’re definitely not behind. Most security companies find this gap the same way after something’s already gone wrong, when it’s too late to fix that one incident but not too late to fix everything after it.

    So let’s get into what real supplier management looks like for a security operation, why the gap matters more than people assume and how you close it without dumping extra work on your guards.

    Why Supplier Management Gets Overlooked Until It’s a Problem

    Most security teams treat access control and incident reports as the “real” job. Deliveries? That’s the side task. The thing that gets handled, not managed.

    Understandable, honestly. A driver shows up, drops something, leaves. Doesn’t feel like the kind of moment that needs paperwork the way an incident does.

    But here’s the thing an unlogged delivery is the same gap as an unrecorded key handover. Same gap as an unrecorded shift. If a client disputes what arrived, if something goes missing between the gate and its final stop or an invoice doesn’t line up with what actually showed up, your only defense is a timestamped record with a name on it. Nothing else holds up.

    This is exactly why supplier management deserves to be a real priority, not something bolted on later. Sites with strict receiving windows. Offices that won’t take deliveries outside business hours. Facilities where weekend or holiday drop-offs need extra eyes. These places feel the gap hardest. No system and you’re leaning on a guard’s memory and a driver’s word, months after it happened.

    What You’re Probably Worried About Right Now

    First time looking into supplier management? A few worries are probably sitting in the back of your head, even if you haven’t said them out loud.

    Will this slow my guards down. Is this yet another system to learn. Will people actually use it or will it end up like every other form filled out halfway, then forgotten.

    Fair worries. They deserve real answers, not just reassurance. Doing this right doesn’t mean more work. It means the same handoff your guards already do, just captured in a way that actually holds up months later.

    How Supplier Management Actually Works in Practice

    In AVES, this sits under a module called Receiving Supplier. Two actions, that’s it: Create and Records.

    Create is where a guard logs a delivery as it happens name of the person or company delivering, the item, the quantity and a time-window selector (Office Hours, Weekend, Holidays) so anything unusual gets flagged right away instead of slipping through. The Receiving Officer field fills itself in based on who’s logged into the app, so there’s no guessing later about who actually took the delivery. Add an Invoice Number field and the option to snap a photo of the invoice and that’s the record.

    Records is basically a calendar. Pick a date, see whatever got logged that day. Nothing there? It tells you straight up no data available for the selected date instead of leaving you wondering if the app just broke.

    Think about the difference between a guard’s memory and an actual paper trail. Memory shifts. It softens details, fills gaps without meaning to, changes a little every time it gets retold. A dated record with a name, an invoice number and a photo attached doesn’t do any of that. It just sits there, exactly as it was.

    What Good Supplier Management Doesn’t Include and Why That’s Fine

    Let’s be straight about this, because overselling helps nobody. This is a receiving and delivery log. Not a full vendor management system. No contracts, no purchase orders, no approved supplier lists living in here.

    You won’t find fields for ongoing vendor relationships, payment terms or supplier performance reviews. If your business needs that level of procurement machinery, what you’re getting here is the physical receiving side of things. Not the contractual side.

    Knowing that going in saves you from expecting something that was never meant to be there. Good supplier management, for a security company, means proof of what happened at the gate. Not running your whole purchasing department.

    The Mistakes That Undermine Supplier Management Even When the Tool Is Right

    Having the right tool doesn’t automatically mean good supplier management. The habits around it matter just as much, maybe more.

    Logging the delivery late is probably the most common one. Records pull by date, so an entry made hours later or the next morning, quietly misrepresents when the thing actually showed up. This only works as evidence if the timestamp is real.

    Skipping the invoice photo when there’s one available. Takes a few extra seconds and it’s the first thing that gets dropped when people are busy. Funny enough, it’s also usually the exact piece of paper a dispute ends up hinging on.

    Treating small deliveries like they don’t count. An envelope feels too tiny to log, until it’s the one thing someone’s asking about three weeks from now. Consistency means logging everything. Not just the stuff that feels important at the time.

    Not checking the receiving officer field. It auto-fills based on whoever’s logged in, which sounds convenient until a shared device or a borrowed login quietly puts the wrong name on a delivery.

    And then there’s the big one: treating a verbal handoff like it counts as a record. It doesn’t. If it never made it into the system, as far as your process is concerned, it never happened. Doesn’t matter how well everyone remembers it.

    Building Confidence Before You Commit

    Still on the fence about formalizing this? Here’s the honest trade-off. A little discipline now, a few extra seconds per delivery, buys you real protection later. Almost always a good trade.

    The cost of skipping supplier management shows up when you least expect it. Most weeks, nothing happens and the whole thing feels like overkill. Then one dispute, one missing item, one client asking pointed questions and suddenly the entire investment pays for itself in a single conversation.

    You don’t need to rebuild your whole operation to get here. You need one habit: log the delivery the second it happens. And a system simple enough that your guards actually keep doing it.

    Frequently Asked Questions

    What is supplier management for security companies?


    It means tracking deliveries, vendors and goods received on-site creating a record of what arrived, when and who accepted it, instead of relying on informal handoffs at the gate.

    How does AVES handle supplier management and deliveries?


    Through a Receiving Supplier module with two views: Create, where a guard logs delivery details like item, quantity, time window and invoice and Records, a calendar showing everything logged for a given date.

    Can I attach an invoice to a supplier management record in AVES?


    Yes. The Create form has an Invoice Number field plus the option to upload a photo of the invoice, so the documentation lives right there with the record.

    Does supplier management in AVES flag deliveries outside normal hours?


    Yes the Create form includes a time-window selector for Office Hours, Weekend or Holidays, so your team can categorize and later review anything outside standard hours.

    Is this a full vendor management system?


    No. It logs physical deliveries and receiving details. No contract management, no purchase orders, no ongoing vendor relationship tracking.

    How do I check what was received on a specific day?


    Head to Records. It’s a calendar pick a date and it shows what was logged or tells you plainly if nothing was recorded.

    What to Expect in the First Few Weeks

    Rolling out supplier management for the first time usually goes through a predictable pattern, and knowing it in advance removes a lot of the anxiety.

    Week one feels awkward. Guards forget to log a delivery here and there, not out of resistance, just because it’s a new habit competing with everything else they’re already tracking. This is normal, and it doesn’t mean the system has failed.

    By week three, most teams settle into a rhythm where logging becomes automatic, the same way checking a badge or signing a visitor in became automatic once. The friction that felt real in week one fades once supplier management stops being a new task and becomes just part of how deliveries happen.

    The companies that struggle long-term are usually the ones that gave up in week one, right when the habit was still forming. If you commit to the first month, consistent supplier management tends to take care of itself after that.

    Where This Leaves You

    Supplier management doesn’t have to be complicated and it shouldn’t slow your team down. It just needs to be consistent and it needs to produce a record that actually holds up the day someone questions it.

    AVES keeps it in the same system your guards already use for shifts, incidents and attendance so a delivery record is something you pull up in seconds, invoice photo included, instead of trying to piece it together from a driver’s word weeks later.

    Want to see how AVES handles supplier management and delivery records in practice? You can explore the platform and request a demo at avessecurity.com.

    CONTACT US

    Website : https://www.avessecurity.com

    Linkedin: https://www.linkedin.com/company/aves-security-management-system/

    Instagram: https://www.instagram.com/avessecurity/

  • Security Guard Performance Management Guide

    Security Guard Performance Management Guide

    A security guard performance review is not supposed to feel like a trip to the dentist. But that’s exactly how most security company owners run it. They dig up a dusty generic template, scribble a couple of half-hearted notes, sign the bottom and shove it in a filing cabinet for the next twelve months. That lazy habit is the actual reason your turnover keeps climbing.

    Here’s what that officer actually deals with. Twelve hours alone at a client site. Aggressive visitors at the gate. Access control. A 2 a.m. alarm going off with nobody around to back them up. And then you hand them a review that says “good job.” That’s it. That tells them nobody’s watching, nobody cares. Good guards pick up on that fast and they don’t stick around, they go find a company that treats them like it matters. If you want a security guard performance review process that actually works, forget the corporate HR playbook. Look at what the job really involves.

    Why traditional appraisals fail security teams

    Most evaluation templates were built for someone sitting at a desk under office lights. It’s a bit like scoring a race car driver on typing speed, the metrics just don’t apply. A perimeter fence or a lobby desk doesn’t behave like a cubicle. Judge a mobile patrol officer with corporate benchmarks and the whole security guard performance review feels fake before you’ve even asked the first question.

    Guards know within a minute whether you understand their job. If you don’t, they check out mentally right there and good luck getting honest engagement after that. It kills your credibility as a manager instantly. A strong security guard performance review keeps good people, because it’s built around what the work actually looks like, not what a handbook says it should look like.

    Most managers just inherited whatever system was already in place. Annual check-ins, because that’s tradition. But security isn’t an industry where you can afford to wait a year. One missed patrol turns into a break-in or a client walking away entirely. By the time the annual review comes around, bad habits are already baked in and your best officers have already mentally quit.

    The core framework of a security guard performance review

    A real security guard performance review or security guard evaluation, sticks to objective, observable behavior. You can’t grade someone’s vibe or general attitude. You grade what they actually did. A solid framework captures daily reliability and how someone handles a crisis, in equal measure.

    Start with operational reliability: punctuality at shift handover and how strictly someone follows post relief protocol. A guard who shows up ten minutes late forces the outgoing officer to stay late too and that quietly poisons morale across the whole roster. Let tardiness slide long enough and it becomes the norm and your most reliable people start to resent it.

    Next comes tour execution. Are your guards actually hitting checkpoint scans on schedule or are they pencil-whipping the log from inside the guard shack? Patrol integrity is what your client contract is built on. Skip checkpoints and the client is paying for protection they’re not getting.

    You also need to look at incident documentation, meaning how fast and how accurately reports get filed. A report riddled with spelling errors and missing timestamps can wreck your legal standing the moment a case goes to court. Round out your security guard performance review with professional conduct: uniform, grooming and how officers actually talk to clients and visitors.

    Tracking the guard performance metrics that matter

    A real security guard performance review runs on numbers you can actually track week over week, not vague advice about working harder. One of the most important security guard KPIs to start with is tour completion rate. Anything below ninety-five percent on scheduled checkpoint scans and you’ve got a problem worth investigating.

    Incident response time matters too. How long does it take an officer to acknowledge an alarm or check out something suspicious on the property? When someone unauthorized is already inside, minutes are the whole ballgame.

    Report accuracy is another one worth watching, specifically how often a supervisor sends a report back for corrections. If your supervisor’s spending half their morning rewriting other people’s paperwork, that’s not a discipline issue, that’s a training gap that needs fixing.

    Numbers strip out the bias. Nobody can argue with a system showing they missed twelve checkpoints last Tuesday, that’s just what happened. It turns what used to be a tense, emotional conversation into a coaching session grounded in fact. Officers trust a security guard performance review built on data a lot more than one built on whatever mood their supervisor happened to be in.

    Ditching the paper trail for digital tracking

    Paperwork slows everything down and eventually something gets lost. Try running a security guard performance review across dozens of officers using logbooks and scattered spreadsheets and watch how fast the whole system collapses. A dedicated platform removes that headache entirely. Every hour spent digging through last month’s attendance sheet is an hour that should’ve gone toward training or client calls.

    Paper gets coffee stains. It gets left in a glove compartment. It disappears into a filing cabinet somewhere and never resurfaces. Digital tracking keeps everything tied to the right officer’s profile from day one, no exceptions. Cutting the physical logbook out of the process turns admin work from a scavenger hunt into something manageable.

    Walk through the life cycle of a typical paper incident report. An officer scrawls it on a clipboard mid-shift. Hands it to the supervisor at change of shift. It gets tossed into a folder in the back of a patrol car. Weeks go by. Eventually it lands on someone’s desk back at the office and now an assistant’s squinting at bad handwriting trying to figure out what actually happened. By the time management sees it, the incident’s already two weeks old. A digital system just deletes that whole broken chain.

    How AVES Security Management changes the game

    Bring everything into one place and the whole equation changes. AVES Security Management System builds your security guard performance review process, scheduling and incident reporting into a single platform. Inside the performance module, managers log employee periods and departments in a matter of seconds. Pick the name, set the development period, that’s it. No spreadsheet juggling required.

    Supervisors get a structured space to log development goals and flag concerns instead of hunting through a filing cabinet for last month’s notes. You set an agreed improvement action and a clear success measure directly inside the app. Reviews stop being that once-a-year panic because the notes are already there, logged continuously as the year goes on.

    Once daily activity connects directly to long-term development tracking, the culture around here starts to shift. With a proper security guard performance review system in place, supervisors aren’t guessing what happened three months ago anymore. They open the profile, look at real completion numbers and have an honest conversation backed by actual data instead of fuzzy memory.

    Setting goals that actually change behavior

    A security officer performance plan without a deadline attached to each goal is just a wish. Target start and end dates give remedial training or a promotion track, an actual timeline to work against. The AVES calendar lets you set exact dates for any goal in a couple of taps. Officer struggling with report writing? Give them thirty days and pair it with focused training in the app.

    Measurable success criteria tell you, plainly, whether the error rate actually dropped over that window. Continuous feedback, tracked through the calendar, means notes get logged as things happen rather than everyone scrambling to remember details once a year. Real growth comes from small, steady corrections, not one giant overhaul once every twelve months.

    Tell someone to “be more professional” and you’ve told them nothing useful. Tell them “complete every checkpoint scan within ten minutes for the next thirty days” and now there’s an actual target. That’s the difference between vague advice and something a person can actually act on.

    Overcoming pushback from field supervisors

    Roll out a new security guard performance review system and somebody’s going to push back, usually a supervisor claiming they don’t have time for more paperwork. Fair enough, honestly, paperwork pulls them away from the site. Moving to digital cuts that friction down to almost nothing since entry takes seconds, not an afternoon. Officer skepticism around the review process fades too once it’s tied to metrics instead of whatever mood a supervisor’s in that day.

    Trust in the security guard performance review process comes from transparency.. When officers see their completion rate connecting directly to actual career growth, accountability just becomes part of how things work, not a rule being forced on them. Supervisors stop acting like enforcers and start acting like mentors who actually want their people to do well.

    Getting veteran supervisors on board really comes down to showing them the upside. Once they realize a review takes five minutes on a phone instead of a weekend buried in paper, most of the resistance just disappears on its own.

    Your next move

    A proper security guard performance review process turns your security team from a line-item cost into your biggest asset. Pair clear expectations with digital tracking and the administrative mess across your organization starts to clear up on its own. Stop relying on messy paperwork and habits that were never built for this job in the first place. Streamline your performance tracking and build a stronger team with the AVES Security Management System.

    CONTACT US

    Website : https://www.avessecurity.com

    Linkedin: https://www.linkedin.com/company/aves-security-management-system/

    Instagram: https://www.instagram.com/avessecurity/

  • Contractor Management Software for Security Teams: Gate Access, Not Payroll

    Contractor Management Software for Security Teams: Gate Access, Not Payroll

    By Nithish, AVES Security

    Why “contractor management software” searches lead you to the wrong tool

    If you’re searching for contractor management software as a security team, you’ve probably already noticed the results don’t match what you need.

    I get this question a lot from site managers: “We searched for contractor management software and none of it does what we need. Is that normal?”

    Yes. Completely normal and worth explaining, because it’ll save a few wasted demo calls.

    Type “contractor management software” into Google and you’ll get Deel, Workday, a handful of HR-compliance platforms and a Capterra listicle comparing all of them.

    Every one of these tools is built for the same job: onboarding a contractor as a worker.

    Collecting their W-9, checking that their insurance is current, paying them in the right currency, tracking whether a certification expires next month.

    According to OSHA’s contractor safety guidance, that side of contractor management is real and regulated. It’s just not what a guard at a gate needs at 7am when a plumber shows up claiming he has a job order for Building C.

    Two different questions, one confusing search term

    “Is this person allowed to be here right now?” and “Is this person set up correctly as a vendor in our system?” are not the same question, even though both are called contractor management software.

    A security team almost never cares about the second one, which is payroll and legal’s job.

    A guard cares about the first and most contractor management software marketed under this term doesn’t answer it at all.

    What actually matters at the gate

    Ask a guard what goes wrong with contractors and the same handful of things come up, over and over.

    The contractor arrives and nobody at the gate knew they were coming, so someone’s calling around trying to find whoever approved it.

    The job finished two days ago, but access was never switched off because turning it off required someone to remember to do it.

    There’s no record of when the contractor actually left, just a guess based on when the truck was gone.

    A contractor wanders into an area they weren’t supposed to be in because nothing stopped them and nobody was watching that door.

    A client asks for a report of every contractor visit last month and someone has to dig through a logbook where three different guards updated it inconsistently.

    None of these are payroll problems. Their access problems are closer to what our gate pass management system already handles for one-off visitors.

    They need a system built around the gate, not the vendor file.

    What good contractor management software for security actually looks like

    Pretty simple, honestly. A contractor’s visit is scheduled and approved in advance, not improvised at the barrier.

    Access has a start and an end and it expires automatically rather than relying on someone to revoke it.

    Entry and exit both get logged the same way our geofence attendance tracking timestamps a guard’s location on a round.

    That means a contractor who checked in but never checked out shows up as exactly that: an open question, not a closed record.

    If a job needs an escort or is restricted to one part of the site, the system knows that and flags it rather than leaving it to memory.

    That’s the whole job. Not glamorous.

    But it’s the difference between a guard answering “who’s on site right now and why” in ten seconds, versus fifteen minutes of phone calls.

    Where this sits next to gate pass

    If you already use a gate pass format, contractor site access is basically the same mechanism.

    It’s applied to people who come back regularly and often need specific rules attached to inductions, restricted zones and a longer access window than a one-off visitor would get.

    Same underlying event, different shape.

    What we’re not claiming

    This doesn’t replace a real HR or compliance platform and it shouldn’t try to.

    It won’t issue a 1099. It won’t chase down an expired insurance certificate covered under something like OSHA’s recordkeeping rules.

    If that’s the gap you’re trying to close, you want Deel, Workday or something in that category.

    The two tools solve different problems and most teams end up needing both eventually.

    The bottom line

    If you went looking for contractor management software because you wanted to know who’s allowed on your site and when, you were in the right neighborhood but the wrong building.

    What you actually need is contractor management software built around the gate approved before arrival, time-limited, logged coming and going, visible to whoever’s asking.

    For More Details: https://avessecurity.com/

    Visit Our visit: https://www.linkedin.com/company/aves-security-management-system

    FAQs

    Isn’t contractor management software just for HR and payroll stuff?
    Most of what shows up under that name, yes, W-9s, insurance certs, payments. That’s a real need, just not a security one. If you’re trying to answer “who’s on my site right now and why,” you need something built around the gate, not the vendor file.

    We already use Deel/Workday for our contractors. Do we still need this?
    Probably, if security is a concern. Deel and Workday tell you that a contractor is set up correctly as a vendor. Neither one tells your guard whether that plumber at the gate is actually supposed to be there today. Different jobs and most sites end up needing both.

    What happens if a contractor forgets to check out?
    It stays open on the record instead of getting quietly closed. No guessing based on when the truck left the lot; if there’s no exit log, the system shows it as unresolved so someone can actually follow up.

    Can we restrict a contractor to certain areas of the site?
    Yes. If a job only needs access to one zone or needs an escort, that gets attached to the visit when it’s approved, not left to whoever’s at the gate that day to remember.

    How is this different from your regular gate pass system?
    Mechanically, it’s close. Contractor access is usually recurring, tied to inductions and open for a longer window than a one-time visitor pass. Same underlying idea, just shaped for people who come back.

    Can we pull a report of every contractor visit for a client or audit?
    Yes and it’s the same log the guards are already using at check-in and check-out, not a logbook that three different shifts filled in differently.

    Does this handle things like expired insurance or certifications?
    No. That’s still HR/compliance territory. OSHA-covered stuff like insurance and certs belongs with a platform like Deel or Workday. This tool answers “are they allowed on site right now,” not “are they legally compliant to be a vendor.”

  • Training Management System for Security Guards: The Essential Guide to Tracking Training and Records

    Training Management System for Security Guards: The Essential Guide to Tracking Training and Records

    A training management system is supposed to fix one simple problem: training that nobody wrote down might as well not have happened. Ask most security companies how they track guard training, though, and you’ll hear the same answer nine times out of ten. A folder somewhere. A supervisor’s memory. Maybe a spreadsheet nobody’s touched since spring.

    A guard sits through a class. Nobody logs it anywhere searchable. Fast forward three months, a client wants proof that every officer on their site completed fire safety training, and now you’re digging through old attendance sheets and screenshots from a group chat, trying to reconstruct something a proper training management system would’ve handed you in thirty seconds.

    Here’s what most companies don’t want to face: training nobody wrote down doesn’t count, not to a client, an auditor, or an insurance adjuster. That’s the exact gap a training management system exists to close, and before you convince yourself your current setup is “fine,” it’s worth understanding what a good one actually looks like.

    Why a Training Management System Matters More Than Most Companies Realize

    Two reasons this matters, and most companies only ever think about one of them.

    First, client trust. When a client asks whether your guards are trained for their site, handing them dates and records from a real system builds a lot more confidence than “yeah, we handle that.” Contracts these days increasingly expect proof upfront, not a vague promise that training happens somewhere in the background.

    Second, and this is the one that really catches people off guard: liability. If something goes wrong on a shift and training becomes a question, a training management system that shows exactly what an officer completed and when is the difference between a defensible position and pure guesswork. Lawyers and insurers don’t ask fuzzy questions. “We train our guards” won’t cut it. A dated record will.

    Without one behind you, both of those things ride entirely on someone’s memory holding up months, maybe years, after the fact. That’s a bad place to be standing when it counts.

    How a Training Management System Works in AVES

    AVES builds its training management system into the Staff Development section of the mobile app, right next to Performance Development Plan. Open Training and two paths show up: All Trainings and Records. They do very different jobs, so it helps to know which one you’re actually in.

    All Trainings is where sessions get built and managed. You can add or update training programs here, and, this part matters, assign them to specific users or departments instead of blasting them out to the whole team. Not every guard needs every training. Fire marshal certification might apply to one shift only. A first-aid refresher might just be for one department. Being able to target instead of broadcast keeps the list something people actually pay attention to, instead of noise they scroll past.

    Records, labeled Security Trainings, is the other half, and it works nothing like the first. Picture a calendar. You flip through months, land on a day, and see whatever got logged for that date. Nothing there? It just says so: no data available for that date. That’s the piece that turns a one-off event into something you can actually revisit later. Instead of asking a supervisor “hey, when was that class again,” you click the date and there’s your answer.

    One thing you won’t find here: a certification-expiry tracker, or anything resembling a compliance-scoring dashboard. If tracking exact expiry dates and renewal reminders matters to your business, that detail lives inside the individual training entry itself. The list and calendar views don’t surface it automatically.

    Getting Real Value Out of Your Training Management System

    A training management system is only as good as the habits around it. A few habits separate a training record that’s actually useful from one that just looks fine sitting there.

    Name your sessions like they mean something. “class1” tells you nothing six months later, not even to the person who typed it in. “Fire Safety Refresher, Site 4, Q3” tells a whole story the moment someone opens it.

    Only assign by department when the entire department genuinely needs it. It’s tempting to go broad “just in case,” but that buries the training under noise for everyone who didn’t need it, and makes it harder to spot who actually still has to complete it.

    Log it the day it happens. Records sorts by date, so a session entered three days late lands under the wrong day. It chips away at accuracy quietly, until you notice it during an audit and it’s too late to fix.

    Check Records regularly. Not just when a client comes asking. A monthly look catches gaps while you can still do something about them.

    The Mistakes That Undo a Training Management System

    Same handful of mistakes, over and over, even at companies with a solid system already sitting in their pocket.

    Vague naming tops the list. A training log full of “class1,” “class2” technically counts as a record. It just fails the actual point, which is answering a real question later, quickly and without guesswork.

    Over-assigning is next. Push a single-department training out company-wide and you bury the people who actually need to act on it under a pile of people who don’t.

    Then there’s confusing scheduled with logged, a subtler trap. A session sitting in someone’s calendar or a group chat thread isn’t proof of anything. Only an entry under Records, for that date, counts.

    And the big one: waiting for a client to ask before you check your own records. By then you’re not reviewing, you’re scrambling. Scrambling almost never produces a clean answer.

    Where a Training Management System Fits Into the Bigger Picture

    It doesn’t live on its own island. It ties directly into your duty roster and shift assignments, because whether a guard was actually qualified for a given post on a given shift depends partly on their training record. It sits right beside Performance Development Plan too, both feeding into a documented picture of how ready your team really is, not just how ready you assume they are.

    A training session nobody logged is a session you can’t prove happened. In this line of work, what you can prove tends to matter more than what you simply know to be true. AVES keeps checklists and dated training records in one training management system your guards already use for shifts and attendance, with the option to assign precisely instead of blasting everything to everyone by default.

    If you want to see how AVES handles this as a training management system in practice, you can explore the platform and request a demo at avessecurity.com.

    Frequently Asked Questions

    What is a training management system for security guards?

    A training management system for security guards is a software that helps you keep track of the training that security guards have completed. It is a place where you can log, assign and track the training of security guards, which’s better than using paper sign-in sheets or trying to remember who did what. This system gives you a record of who completed what training and when which’s very useful.

    Why do security companies need a training management system for security guards?

    Security companies need a training management system for security guards because clients and insurers often ask for proof of training. A training management system for security guards gives you the proof you need so you can give them an answer instead of just guessing.

    How is training assigned in a training management system like AVES?

    In a system like AVES training can be assigned to security guards or to entire departments. This means that each security guard only sees the training that’s relevant to them instead of seeing a long list of training that does not apply to their job or the site they work at.

    Does a training management system track certification expiry dates?

    Not all training management systems track certification expiry dates automatically. For example in AVES you have to look at the training entry to see the expiry and renewal details. So if you need to keep track of these dates for compliance you should check them directly.

    How often should I check my training management systems records?

    You should check your training management systems records at once a month. If you do this you can catch any gaps in the training schedule. Fix them before it is too late. This is better than finding out about the gaps during an audit when it is already too late to do anything about them.

    Can a training management system prevent liability issues?

    A training management system for security guards cannot prevent incidents from happening. It can help protect you after an incident occurs. If someone asks about the training that security guards received during an investigation a training management system for security guards gives you a record of the training that you can use to defend yourself. This is much better, than guessing what training was completed.

    CONTACT US

    Website : https://www.avessecurity.com

    Linkedin: https://www.linkedin.com/company/aves-security-management-system/

    Instagram: https://www.instagram.com/avessecurity/

  • Lone Worker App: 3 Steps to Duty of Care

    Lone Worker App: 3 Steps to Duty of Care

    A lone worker app exists to answer one question: if a guard on a night patrol, a technician on a remote site visit or a caregiver doing a solo home visit runs into trouble, how quickly does anyone else find out? Duty of care doesn’t mean eliminating that risk; it means building a system that notices quickly if something’s gone wrong and gets help moving before too much time passes.

    A lone worker app is built from three pieces: a way to check in, a way to raise an alarm and a clear path for what happens next.

    This piece walks through what each of those three pieces should do in a lone worker app and why the gaps between them are usually where duty-of-care programs actually fail not in any single feature, but in the seams connecting them.

    Why a lone worker app isn’t one feature

    It’s tempting to think of a lone worker app as a single button press it, help comes. In practice it’s a chain: something has to prompt a check-in or accept a manual alert, something has to notice if that check-in doesn’t happen, someone has to be notified and someone has to actually respond.

    A lone worker app that’s strong on the alert button but has no defined escalation path leaves a worker’s safety depending entirely on them successfully pressing a button while in distress which is exactly the scenario the app is meant to cover for.

    Check-ins: what a lone worker app should log

    The simplest and most common layer is a scheduled or location-triggered check-in a worker confirms they’re safe at set intervals or a system logs their presence automatically as they move through defined zones.

    Geofence-based attendance is one practical way to do this: a check-in is recorded automatically when a worker enters or exits a defined area, tied to their shift and location rather than relying on them to remember to tap something on a schedule.

    AVES supports this model today geo-verified attendance that ties a worker’s location to their roster, so presence at a site is a timestamped, auditable fact rather than a guard’s word.

    That’s a genuinely useful foundation for duty of care: it gives a supervisor a record of where someone was and when, which is the raw material any escalation decision depends on.

    What it doesn’t do on its own is tell anyone that a check-in was missed and automatically start a countdown toward escalation that’s a distinct piece of logic, covered below.

    Manual alerts: what a lone worker app needs beyond check-ins

    The second layer is the one a worker triggers themselves when they know something’s wrong a duress or SOS alert. AVES provides this as a standing feature: real-time SOS alerts and notifications that fire the moment someone raises them, rather than waiting for a shift-end report.

    This is the layer that matters most in the seconds after an incident, because it doesn’t depend on a scheduled check-in cycle catching up it’s immediate and it’s under the worker’s control.

    The honest caveat here is that a manual alert only works if the worker is conscious, free and physically able to reach a device which is precisely the situation that fails after a fall, an assault or a medical event.

    That’s the gap that automated detection layers (below) are built to close and it’s worth knowing whether that gap matters for your specific risk profile before assuming a manual SOS button alone is sufficient duty of care.

    What a lone worker app should escalate to and what’s confirmed here

    This is where a genuine duty-of-care program typically adds two more pieces and it’s also where we want to be precise about what AVES currently offers versus what’s standard across the broader lone-worker category:

    • Missed check-in escalation if a scheduled or expected check-in doesn’t happen, the system automatically notifies a supervisor or escalation contact after a defined grace period, without anyone having to notice the absence manually.
    • Man-down / no-motion detection using device sensors to detect a fall, an impact or a prolonged period without movement and triggering an alert automatically, with no action required from the worker at all.

    Both of these are common in dedicated lone-worker platforms and both close the gap that manual SOS alerts and simple attendance check-ins leave open.

    As of this writing, we haven’t found either of these confirmed as a current AVES feature the site documents SOS alerts and geo-verified attendance clearly, but doesn’t describe automated missed-check-in escalation or motion-based man-down detection.

    If your program specifically needs those two capabilities, that’s worth confirming directly rather than assuming they’re bundled in.

    What duty of care asks of a lone worker app

    Setting aside any specific product, a defensible lone worker app generally needs to be able to answer a few questions after the fact, not just in the moment:

    • Who was working alone, where and during what window? this is what shift and roster data, tied to geo-verified check-ins, gives you.
    • Was there a way for that person to raise an alarm and did it reach someone in real time? this is what an SOS/alert feature answers.
    • If they couldn’t raise an alarm themselves, would anyone have known? this is the question that missed-check-in escalation and man-down detection exist to answer and it’s the one worth pressure-testing against whatever system you’re evaluating.
    • Is there a record of all of it afterward? for compliance and for reviewing what worked or didn’t after an incident.
    • Duty of care for lone and isolated workers isn’t just good practice in many jurisdictions it’s a legal obligation. In the US, the OSHA General Duty Clause requires employers to provide a workplace free from recognized hazards, which extends to workers operating without direct supervision.
    • In the UK, the HSE’s guidance on lone workers sets out specific expectations for risk assessment and monitoring. A lone worker app is one way to operationalize that obligation but the obligation exists independent of whichever tool you choose to meet it.

    Building the escalation path into a lone worker app

    Whatever combination of check-in and alert features a lone worker app provides, the escalation path itself is a policy decision that sits on top of the tooling, not inside it:

    • Define the grace period how long after a missed check-in before someone is notified. Too short and you get alert fatigue; too long and the point of the system is lost.
    • Name a real escalation contact, not “security” as an abstraction a specific role that’s staffed and reachable during the hours lone workers are actually out.
    • Set a secondary escalation tier if the first contact doesn’t acknowledge within a set window, who’s next.
    • Decide what “resolved” looks like a check-in resuming, a supervisor physically confirming the worker’s status or an explicit stand-down. Don’t leave an open alert quietly aging out.

    Where this leaves you

    If your lone worker exposure is mostly about knowing where people were and giving them a fast way to call for help, geo-verified check-ins paired with real-time SOS alerts both of which AVES supports today cover a meaningful part of that duty-of-care picture.

    If your risk profile specifically requires automatic detection when someone goes silent or goes down without pressing anything, that’s a distinct capability worth confirming directly before you build a program around the assumption it’s already there.

    FAQ

    What is a lone worker app?
    It’s software that keeps tabs on employees working alone a night guard, a field technician, someone doing a solo home visit. Check-ins, an alert button and someone on the other end who actually responds.

    What features matter most?
    A way to log that someone’s okay (usually location-based check-ins), a button they can press if something’s wrong and a plan for what happens if neither of those things checks out.

    Can the app handle everything on its own?
    Not really. The app can send alerts, but someone still has to decide the grace period, who gets called first and when an alert counts as closed. That part’s on the organization.

    Is this legally required?
    Often, yes. OSHA’s General Duty Clause in the US and HSE guidance in the UK both put the responsibility on employers to protect workers who aren’t directly supervised.

    Does AVES have this?
    AVES does geo-verified check-ins and real-time SOS alerts. Automatic missed-check-in escalation and man-down detection we’d check with AVES directly before assuming those are included.

  • Security Guard Duty Roster: Shift Patterns, Rules and Formats (2026)

    Security Guard Duty Roster: Shift Patterns, Rules and Formats (2026)

    Nobody tells you this part. The spreadsheet was never really the problem with your security guard duty roster. What breaks it is simpler than that nobody touches it once the shift’s already moving.

    Officer calls in sick at 6 AM. Another site’s got a gap on nights out of nowhere. And somewhere in your inbox three versions of the same file all slightly different and honestly? Even you can’t say which one’s current anymore. Everyone running a crew has lived this exact morning.

    Doesn’t mean you’re bad at the job. Means you inherited a mess that most security operations just. never actually fix. It’s common. More common than anyone admits out loud.

    So this guide gets into the real stuff shift patterns that survive contact with reality rest rules that keep you out of legal trouble formats that hold up when a client or inspector wants to see one. Read through and you’ll know what an actual working roster looks like not the textbook version.

    What a Duty Roster Meaning Actually Covers

    Drop the idea that a duty roster is just names sitting next to time slots. It’s a lot heavier than that.

    It’s proof. Who was supposed to be where starting when for how long. Payroll runs off it. So does client billing. Your whole attendance record hangs on this one document being right every time.

    Most people file it under “scheduling admin.” Ask anyone who’s been burned before though they’ll tell you it’s a liability record first scheduling tool second. Both true at once. That’s exactly why a messy schedule costs way more down the line than new managers assume going in. The roster is the document; security guard scheduling software is the system that keeps it honest once shifts start moving.

    Kind of like a flight log if you think about it. Nobody looks twice at it on a quiet day. Then something goes wrong and it’s suddenly the only piece of paper anyone trusts. Same logic applies here someone asks “who was on site at 2 AM last Tuesday” and that document’s the first thing anyone reaches for. Doesn’t match what actually happened? Now you’re dealing with something a lot worse than a scheduling hiccup.

    Common Shift Patterns That Actually Work

    No single pattern’s “correct” for a staff duty roster. Comes down to site risk actual headcount how much fatigue your team can take before things start slipping.

    2-shift system (12-hour shifts)
    Two officers 24 hours split down the middle. Easy enough to manage — until the same person keeps pulling nights and fatigue quietly builds underneath everything.

    3-shift system (8-hour shifts)
    Three shifts shorter each. Officers stay sharper no argument there. But now you’re staffing up more and running handovers three times a day instead of two and every handover’s a chance for something to fall through.

    4-on-4-off
    Shows up a lot on bigger industrial or warehouse jobs. Four days on four off looks generous on paper. Then you check and those four “on” days are 12-hour shifts anyway so run the actual math before you commit.

    Rotating nights
    Rather than parking one guy on permanent nights until he burns out the schedule cycles who takes it. Spreads the wear across the whole team instead of one person quietly reaching their limit.

    Same mistake over and over with first-timers building this duty roster. Pick a pattern because it looks clean on paper skip checking if the headcount actually supports it. Four officers on a 3-shift setup? Works fine. Drop to three on that same pattern and somebody’s losing their rest day. Every time. No exceptions.

    Fatigue and Rest Rules Nobody Warns You About

    Most guides skip straight past this which is a mistake because it’s the part that actually gets companies fined or dragged into court.

    Security sits near the top for fatigue-linked incidents in low-wage work generally and it’s not really a mystery why. Shifts run long rest periods get shaved down quietly whenever there’s a gap to cover fast.

    Worth locking into any duty roster before you finalize it:

    • Minimum rest gap between shifts usually 8 to 11 hours depending where you are. Back-to-back 12-hour shifts with barely a gap break this rule constantly more than most managers realize until someone points it out.
    • Consecutive nights need a cap. Three sometimes four in a row that’s about where alertness starts dropping off measurably.
    • Weekly hour caps exist basically everywhere. Push past them and you need actual paperwork not just someone nodding along and saying sure go ahead.

    None of this reads as exciting fair enough. But that’s precisely why it gets ignored and why most companies only sort out this staff duty roster structure after an audit or incident forces the issue into the open.

    How Coverage Gaps Actually Happen

    Gaps in a duty roster rarely come from bad planning. They come from the plan not keeping up once reality shifted underneath it.

    Guard calls in sick at 6. Supervisor scrambles has someone in by 7 crisis handled right? Except the paper schedule or that spreadsheet sitting unopened somewhere still lists the original guy as on shift. Payroll processes the wrong hours. Client’s report shows a name that was never actually on site that night and now someone’s got questions.

    This right here is the biggest failure point in manual rostering full stop. Not the planning. The tracking of what changed after the plan was already locked in.

    From Roster to Payroll: Where Most Companies Lose Money

    A security duty roster isn’t just paperwork gathering dust. It’s the direct input into payroll and that’s precisely where manual systems bleed money without anyone noticing for months.

    Your schedule says full shift worked. Officer actually left two hours early nobody flagged it. Now either you’re overpaying that guy or your client’s getting billed for hours that never actually happened on site. Neither’s great. Both happen constantly everywhere spreadsheet-based systems are still running things.

    Fix isn’t “tell supervisors to pay more attention” that’s not a real fix that’s a hope. Real fix is closing the distance between what the duty roster says happened and what actually happened on the ground automatically without relying on someone’s memory three weeks later.

    Common Mistakes First-Time Roster Managers Make

    Building it once treating it as finished.
    It’s not finished ever. Should update the moment something changes not get quietly patched up once the pay period wraps.

    Ignoring rest rules until something forces the conversation.
    By the time fatigue causes a missed patrol or an actual injury that violation already happened repeatedly probably for weeks.

    Choosing a format that can’t be audited.
    Client wants three months of history tomorrow can your security duty roster actually produce it clean? Or are you piecing it together from memory and half-updated spreadsheets at midnight hoping nothing’s missing?

    Assuming Excel just scales.
    Fine for six guards one site. Add more locations more supervisors touching the same file and the whole thing starts cracking. Fast.

    What a Trustworthy Roster Format Actually Needs

    A duty roster for security guards built to survive real scrutiny needs at minimum:

    • Officer name and ID
    • Site and post assignment
    • Shift start and end time including approved overtime
    • Actual clock-in and clock-out not the planned times the real ones
    • Sign-off on any swap or last-minute change and who approved it
    • Timestamp trail showing when the duty roster was last touched and by who

    Can’t produce this on demand? That’s not a risk sitting somewhere down the road. That’s a gap you’re carrying right now.

    Where This Usually Breaks Down and What Actually Fixes It

    Most security companies don’t fail their duty roster out of laziness. They fail because they’re using a static document to manage something that’s live and changing constantly hour by hour.

    Spreadsheet-based setups won’t catch a late clock-in. Won’t flag a guard about to blow past a weekly hour cap either. And there’s zero chance it hands you an audit-ready report in thirty seconds when a client calls asking for proof of coverage from last month.

    That gap right there is what AVES Security Management Software exists to close. The roster is the plan; security guard scheduling software is what keeps that plan tied to what actually happened on shift. Shift schedules stay tied directly to real attendance not floating around in some separate file someone remembers to update eventually. Shift swaps get logged with a real approval trail instead of disappearing into a deleted text thread nobody saved. Someone asks for historical duty roster records you pull a timestamped report on the spot instead of reconstructing three files’ worth of memory at midnight.

    Don’t need to rebuild your whole operation for this. Just need the duty roster and what actually happened to finally be the same document.

    Tired of chasing down what really went on during last night’s shift? Worth a look at how AVES handles a security guard duty roster attendance and shift management in the real world request a demo at avessecurity.com.

    Related reading: Security guard scheduling software covers the shift-assignment and ghost-shift side of this, and geofence attendance covers how location-verified check-in produces the actual clock-in data a roster needs.

    Frequently asked questions ( FAQ )

    What is the meaning of a duty roster?


    A duty roster meaning, in security operations, is a formal schedule that records which officer is assigned to which post, for what hours, on any given day. It is not just a plan. Once shifts start, it also becomes the record of who was actually present, which is why it doubles as an attendance and payroll document.

    How is a staff duty roster different from a general work schedule?


    A staff duty roster is built around post coverage, not just individual convenience. Every slot on the roster has to be filled by someone qualified for that post, so gaps cannot be left open the way they might be on a regular office schedule. That is what makes staff duty rosters harder to manage manually once you have more than one site.

    What should a security duty roster include?


    A proper security duty roster needs officer name and ID, site and post assignment, planned shift timing, actual clock-in and clock-out and a record of who approved any last-minute change. Without the actual attendance data, a security duty roster is just a plan on paper, not a real operational record.

    How do you build a duty roster for security guards with multiple sites?


    A duty roster for security guards across multiple sites needs to show post coverage per site, not just names against time slots. Most managers start in a single spreadsheet, but it becomes hard to track once you are juggling several sites and shift patterns at once. Centralizing rosters by site, with attendance tied in, is usually what keeps multi-site coverage from slipping through the cracks.

    Is a duty roster in Excel good enough for a growing security team?


    A duty roster excel template works fine for a single site with a handful of guards. It starts to break down once you add more officers, more shifts or more than one supervisor editing the file, because there is no audit trail and no way to catch a discrepancy between planned and actual attendance in real time.

    What is a 3 shift duty roster and when should you use one?


    A 3 shift duty roster splits 24-hour coverage into three 8-hour blocks instead of two 12-hour ones. It reduces fatigue per officer but needs more staff and tighter shift handover discipline, since shift changes happen three times a day instead of two. It tends to suit sites with higher risk profiles where alertness matters more than staffing cost.

    How does AVES help with duty roster management?


    AVES Security Management Software keeps the duty roster tied to real attendance instead of a separate spreadsheet someone updates later. Shift assignments, clock-in and clock-out times and shift swap approvals all live in one system, so the roster reflects what actually happened on site, not just what was planned. When a client or auditor asks for coverage history, you can pull a timestamped, audit-ready report instead of piecing it together from old files

    CONTACT US

    Website : https://avessecurity.com

    Linkedin: https://www.linkedin.com/company/aves-security-management-system/

    Instagram: https://www.instagram.com/avessecurity/

  • Essential Gate Pass Format: Material, Vehicle and Returnable Pass Templates

    Essential Gate Pass Format: Material, Vehicle and Returnable Pass Templates

    By NITHISH KUMAR, AVES Security

    If you’ve ever stood at a gate trying to figure out whether a laptop bag leaving the building actually belongs to the person carrying it, you already know why gate pass formats matter more than people give them credit for. It’s not glamorous paperwork. It’s the difference between a security guard being able to make a confident call in ten seconds and one who has to wave someone through because the form in front of them doesn’t ask the right questions.

    Most gate pass templates you find online are either far too generic a single box that says “item description” and nothing else or borrowed from a completely different industry and never adjusted. What actually works is a handful of purpose-built gate pass formats, one for each kind of thing crossing the gate, because a laptop leaving for repair and a delivery truck leaving with raw material are not the same problem.

    This piece stays on the formats themselves. The approval workflow, digital logging and serial-number tracking behind them are covered in our gate pass management system guide. Here’s what each gate pass format actually needs to capture.

    Material Gate Pass Format

    This is the one guards use most often and the one that goes wrong most often too – usually because the form doesn’t force enough specificity.

    A material pass needs, at minimum: the item description (not “electronics,” but “Dell laptop, serial ending 4471”), quantity, the department or person releasing it, the destination and a clear returnable or non-returnable flag right at the top, not buried in a footnote. Add a column for the expected return date if it’s returnable and a signature block for both the releasing authority and the gate guard checking it out.

    Every pass a guard checks off should also be logged somewhere the shift can review later most sites already do this in their security guard logbook, so the gate pass and the logbook entry point back to the same event instead of living as two disconnected records.

    The detail that gets skipped most often is a place for the guard to note discrepancies. If the pass says three boxes and only two show up at the gate, there needs to be a spot to write that down before the vehicle leaves, not after someone notices it’s missing three days later.

    Vehicle Gate Pass

    Vehicle passes fail for a different reason – people treat a vehicle gate pass format like a material pass with a number plate bolted on. They need their own fields: vehicle number, driver name and ID proof type, purpose of visit, time in and time out and – this one’s easy to forget – odometer reading on entry and exit if the vehicle is carrying goods. That single field catches more discrepancies than any other on the form.

    If the vehicle is a regular vendor delivery, a separate “frequency” tick box (one-time vs. recurring) saves the gate from re-verifying the same transport contractor’s documents every single day.

    When the driver or occupants are also entering the premises rather than just dropping off goods at the gate, the vehicle pass should hand off to your regular visitor management process – the two shouldn’t be tracked as if they’re the same event.

    Returnable Gate Pass

    This is really a variant of the material gate pass format, but it deserves its own template because the failure mode is different. Returnable items – laptops for repair, tools sent out for servicing, equipment on loan to another site – get lost in the system because nobody’s tracking the “return” half of the transaction.

    A returnable pass needs everything a material pass has, plus a due-back date and ideally a simple log elsewhere (a register, a spreadsheet, whatever the site uses) that gets checked weekly for overdue items. The pass itself is only half the control. The other half is someone actually following up when an item doesn’t come back on time.

    Non-Returnable Gate Pass

    Simpler by design – this non-returnable gate pass format covers scrap, waste material or genuine gifts and donations leaving the site. The key fields here are approval authority (this usually needs sign-off one level higher than a routine material pass) and a clear statement that the item will not return, so nobody chases it later thinking it’s overdue.

    Gate Pass Format Checklist: What Every Type Should Get Right

    Serial numbers on the pass itself, not just the register. A pass without its own serial number is hard to trace back to a specific gate entry later, especially across shifts.

    Legible approval, not just a signature. A scrawled signature next to a printed name is worth far more at 11 p.m. when someone’s trying to verify who actually approved an exit.

    One pass, one purpose. Don’t let a material pass double as a vehicle pass because someone’s in a hurry. Combining fields to save paper usually means neither set of fields gets filled in properly.

    None of these gate pass formats need special software to implement – they work perfectly well as printed pads or simple digital forms. What matters is that the fields on the page actually match the questions a guard needs answered in the moment, rather than a generic template that technically has a box for everything and useful information for nothing.

    At AVES, our gate pass format was built around exactly this principle – separate fields for material, vehicle and returnable passes, rather than one generic form stretched to cover all three.

    For a deeper look at how gate pass approval workflows, digital logging and serial-number tracking work end-to-end, see our gate pass management system page – this piece deliberately stays at the template level, since that system already covers the process side in full.

    Frequently Asked Questions

    What is a gate pass format?

    At its core, a gate pass format is just the set of fields a guard uses to record what’s moving through a gate an item, a vehicle or a person along with who authorized it and whether it’s coming back. Get the fields wrong and the format stops doing its job the moment something unusual happens.

    What are the different types of gate pass formats?

    Four, in practice: material gate pass (items and equipment), vehicle gate pass (transport in and out), returnable gate pass (things expected to come back, like a laptop sent for repair) and non-returnable gate pass (scrap, waste, donations, anything leaving for good). Trying to squeeze all four into one generic form is usually where things start going wrong.

    What should a material gate pass format include?

    A specific item description not “electronics,” but the actual make and serial number quantity, who’s releasing it, where it’s going, a returnable/non-returnable flag and signatures from both the releasing authority and the gate guard. If it’s returnable, add an expected return date too.

    Is a returnable gate pass different from a non-returnable one?

    Yes and they fail differently if you mix them up. A returnable pass needs a due-back date and someone actually following up when it’s overdue. A non-returnable pass usually needs one level higher approval, since whatever’s leaving isn’t coming back.

    Do vehicle gate passes need their own format?

    They do. A vehicle number, driver ID, time in and out and an odometer reading, if goods are involved, none of that lives on a standard material pass, which is exactly why bolting a vehicle entry onto a material form tends to leave gaps.

    Can a gate pass system work on paper or do I need software?

    Paper works fine for a lot of sites a printed pad with the right fields will hold up. Software mostly earns its place when you need serial-number tracking across sites, automatic alerts on overdue returnable passes or a gate pass tied directly into visitor records and the shift logbook.

    For a deeper look at how gate pass approval workflows, digital logging and serial-number tracking work end-to-end, see our gate pass management system page. This piece deliberately stays at the template level, since that system already covers the process side in full.

  • How Incident Reporting Software Improves Workplace Security

    How Incident Reporting Software Improves Workplace Security

    Incident reporting software lets security officers record an incident digitally from a mobile device at the moment it happens, in a standard format, and stores every report in a searchable, timestamped record. It replaces the handwritten incident book.

    Every security incident tells you something. Whether it is unauthorised access, damaged property or a near miss on the shop floor, the quality of the report decides how well the organization can respond — and whether it can prove what happened later.

    Handwritten reports rarely hold up. They arrive late, miss details, and have a habit of disappearing when you need them most. That is the gap incident reporting software is built to close.

    Why Incident Reporting Matters

    Done properly, incident reporting helps an organization:

    • Spot risks that keep recurring
    • Improve security procedures over time
    • Support investigations with solid evidence
    • Meet compliance requirements
    • Protect employees and visitors

    Done badly, it just creates paperwork nobody trusts.

    Where Manual Reporting Breaks Down

    The usual failure points are familiar to anyone who has run a security team:

    • Missing information
    • Reports submitted hours after the event
    • Paperwork that gets lost
    • Handwriting nobody can decipher
    • No central place to store any of it

    Individually these look minor. Together they quietly undermine the whole operation.

    What Incident Reporting Software Changes

    The core shift is simple: officers report from the device already in their pocket, the moment the incident happens, using a form that will not let them skip the important fields.

    From there you get:

    • Faster reporting, straight from the scene
    • A standard format for every report
    • Real-time notifications to supervisors
    • Photo and video evidence attached to the record
    • Centralised, searchable documentation
    • A complete audit trail behind every entry

    Better Information, Better Decisions

    When management sees an incident as it is logged rather than at the end of a shift, corrective action starts sooner. And once you have months of structured reports behind you, patterns start to surface — the same door, the same hour, the same weak point — which is where prevention actually begins.

    Why Choose AVES

    AVES Security Management System gives teams structured digital incident reports, complete audit trails, and a single dashboard to monitor operations across every industry and every site.

    Good incident reporting software saves time. More importantly, it means that when someone asks what happened, you can answer with evidence rather than recollection.

    Incident reporting is one part of a bigger picture. See how it fits into a full security guard management system, alongside patrols, scheduling and compliance.

    Explore AVES Plans
    Learn More About AVES

    Frequently Asked Questions

    What is incident reporting software?

    Incident reporting software lets security officers record incidents digitally, in a standard format, from a mobile device at the moment they happen, and stores every report in a searchable, timestamped record.

    Does AVES offer real-time incident reporting?

    Yes. Officers file reports in real time from the AVES mobile app and supervisors are notified immediately, so corrective action can begin before the shift ends.

    Can guards attach photos or video to an incident report?

    Yes. AVES incident reports support photo and video attachments, so evidence is captured with the report rather than described from memory afterwards.

    Does incident reporting software help with compliance audits?

    Yes. Because every entry is timestamped and stored centrally, historical incident logs can be filtered and exported as audit-ready PDF reports in seconds instead of being retrieved from paper files.

    Does AVES offer a free trial or a demo?

    Yes. AVES offers both a free trial and a personalised demo.