Security welfare check frequency: how often and why

There is no single correct interval, only a correct method

The most common question about lone-worker welfare checks is how often they should happen. There is no fixed number in Australian law that applies to every duty. Regulation 48 of the model Work Health and Safety Regulations requires a business to manage the risks of remote or isolated work and to provide a system of work that includes effective communication with the worker. It mandates an effective communication system, not a frequency. Safe Work Australia and the state regulators describe building a check-in plan from the risk assessment, and none of them set a numeric interval. The interval is therefore an output of a risk assessment of the specific duty, not a number copied from another company.

That means the defensible answer is not a single figure. It is a documented interval that matches the risk of the duty, an escalation path that runs when a check is missed, and a record that shows both were followed. The rest of this guide covers how to set the interval, how to escalate, and what to keep.

What determines the right check interval

A risk assessment for a lone security duty usually weighs the isolation of the site, the time of day, the history of incidents at the location, the nature of the work, how quickly help could reach the guard, and the guard's own experience. The higher the risk, the shorter the interval. The table below shows intervals that are commonly used as starting points. Treat them as a guide to calibrate against your own assessment, not as legal minimums.

A single site can move between rows across a duty. A shopping centre car park is a moderate-risk static post during the day and a higher-risk isolated post at 3am. Building the interval around the risk as it changes, rather than a fixed number for the whole duty, is what a risk-based approach means in practice.

Where the "every hour" idea comes from

You will find advice online that security welfare checks should happen every hour. It is worth knowing where that number comes from before you adopt it. The hourly figure traces to overseas good-practice guidance, including New Zealand security industry guidelines and British lone-worker monitoring standards, rather than to Australian law. No Australian WHS regulation sets an hourly welfare check, or any other fixed interval.

Treat any single quoted number, including the ones in the table above, as a starting point to test against your own risk assessment, not as a rule you can rely on for compliance. If your interval is ever questioned, a regulator or an insurer will ask how you arrived at it, not whether it matched someone else's figure.

What happens when a welfare check is missed

The interval only protects the guard if a missed check triggers something. A welfare system without a defined escalation path is a log, not a safety control. The escalation should run the same way every time so nobody has to decide what to do under pressure. A typical sequence:

1. Automated reminder to the guard. A prompt that a check is due, before it is treated as missed.
2. Grace window. A short defined period for a genuine delay, so a guard who is thirty seconds late is not treated as an emergency.
3. Flag to the monitoring operator or supervisor. Once the grace window passes, the missed check is surfaced to whoever is responsible for that guard.
4. Direct contact attempt. The supervisor tries to reach the guard by call and by any duress or check-in function available.
5. Secondary contact or dispatched responder. If the guard cannot be reached, escalate to a secondary contact or send someone to the site.
6. Emergency services. If welfare cannot be confirmed and there is reason to be concerned, contact emergency services. It is better to call and stand down than to wait.

Each step should have a defined time trigger, and the whole sequence should be recorded automatically. If an incident is ever reviewed, the question is not only whether the guard was safe but whether the escalation ran as designed.

Methods of checking, and the risk of over-monitoring

A welfare check can be as simple as a phone call or as automated as an app prompt the guard confirms with one tap. Common methods include a scheduled app check-in, a call to or from a monitoring operator, a location or geofence confirmation, and a physical scan at a checkpoint. The right method is the one a guard can complete quickly without leaving their post exposed.

There is a trade-off to manage. Set the interval too long and a guard in trouble waits too long for help. Set it too short and the checks become noise: the guard rushes through them and the monitor stops reading them, which is its own safety failure. A shorter interval is not automatically safer. The interval that matches the risk, paired with an escalation that actually runs, protects a guard better than the shortest possible timer.

What to record for each welfare check

The record is what turns a welfare process into evidence. It supports client reporting, insurer audits, and any WHS investigation. For each duty, keep at least:

• The time each check was due and the time it was completed
• The guard and the site the check relates to
• The method used to confirm welfare, for example an app confirmation, a call, or a location check-in
• Any missed check and the escalation steps that were taken, with their times
• Any incident, hazard, or observation the guard raised during the check

Records that depend on a supervisor remembering to write them up after the fact tend to have gaps exactly where they matter most. A system that timestamps each due check, each completion, and each escalation removes that gap and produces the record as a by-product of the process.

Turning the policy into practice

A welfare policy in a document protects nobody by itself. The gap between a written interval and a real one is usually where things go wrong. A few practical points help close it:

• Set the interval per site or per duty type, not as one number for the whole company, so the interval reflects the actual risk
• Make the check-in something the guard can complete quickly, or it will be skipped when they are busy
• Make a missed check impossible to ignore, with escalation that runs on its own rather than relying on a supervisor watching a screen
• Extend the same obligation to subcontractors working alone under your direction on your client sites
• Review intervals after any incident or near miss, and after any change to a site's risk

For the broader legal basis and the full welfare check process, see the lone-worker welfare checks guide. For how welfare checks fit alongside rostering and licence compliance, see the security guard rostering guide.

Related guides

• Lone-worker welfare checks for security guards
• Security guard rostering in Australia: a practical guide
• Guard tours and patrol accountability
• Lone-worker welfare in OnDuty365

Frequently asked questions