The Security Officer Is Asleep – But Who Has Actually Failed?
It's probably one of the most damaging calls a security company can receive.
“Your security officer is asleep.”
The immediate reaction is obvious.
The officer has failed.
And let's be clear from the outset: if somebody is employed to provide security and is asleep when they should be working, there is personal responsibility involved. Security officers are trusted to protect buildings, people and assets, often during the hours when nobody else is there.
But I think there is another question security companies and their clients should be asking:
How did nobody know?
Because if the first person to discover that an officer has been asleep for several hours is the client arriving on site in the morning, I don't think that's simply an officer problem.
It's potentially a management problem.
Night security is a very different environment
I've worked nights.
I've also spent years managing people who work nights.
Sitting alone in a quiet building at 3am is completely different from working a busy daytime security position.
There may be very little activity. The building could be dark. The officer may be working a 12-hour shift with long periods of monotony and limited human interaction.
Fatigue is a genuine operational issue.
The Health and Safety Executive recognises that fatigue can reduce reaction times, concentration, awareness and decision-making, and that long or poorly designed shifts can increase risk.
That doesn't excuse sleeping on duty.
But pretending fatigue doesn't exist doesn't manage the problem either.
A professional security provider should be asking whether the working environment, shift pattern, workload, welfare facilities, breaks and supervision are helping officers remain effective throughout the shift.
Recruitment matters
Not everybody is suited to every security assignment.
Someone who is excellent in a busy corporate reception may struggle sitting alone on a construction site from 19:00 until 07:00.
Equally, an experienced night officer who is comfortable working independently may thrive in that environment.
Recruitment shouldn't simply be:
“Do you have an SIA licence and can you start tonight?”
You need the right person for the assignment.
You also need to understand what else that person is doing.
Are they working excessive hours elsewhere?
Are they regularly accepting additional shifts?
Are shift swaps creating fatigue problems?
Is somebody finishing one job and travelling directly to another?
There is a point where filling the rota and effectively managing the security operation become two very different things.
A timesheet doesn't prove the service happened
This is one of my biggest frustrations with traditional security contracts.
An officer signs in at 19:00.
They sign out at 07:00.
The client receives an invoice for 12 hours.
But what evidence demonstrates what actually happened during those 12 hours?
Being physically present isn't the same as delivering a security service.
If the assignment requires six patrols, checking particular doors, inspecting vulnerable areas or carrying out specific tasks, there should be some way of demonstrating that those activities actually happened.
This is where technology has fundamentally changed what security companies can provide.
How we monitor our lone workers and patrols
At Blue Light Security Solutions, we've introduced a patrol and lone-worker system specifically because we don't believe overnight officers should simply disappear into a site for 12 hours with nobody knowing what they're doing.
Our system allows us to set specific activities throughout the shift.
That might include scheduled patrols, checks of particular locations or other site-specific security tasks.
Officers use the system to confirm those activities have been completed.
But the important part isn't simply recording successful patrols.
It's what happens when something doesn't happen.
Our officers are also required to respond to scheduled lone-worker welfare checks.
If an officer doesn't respond or fails to silence the welfare alarm, an alert is generated for our team.
We can then make contact with the officer and establish what's happening.
That could identify somebody who has fallen asleep.
But there is a much more important reason for it.
It could identify an officer who has become unwell, suffered an accident, encountered an incident or is otherwise unable to call for assistance.
That is why I don't see this technology simply as an anti-sleeping device.
It's a management and welfare system.
The HSE specifically identifies security staff as potential lone workers and says employers should train, supervise and monitor lone workers, maintain contact and have arrangements for responding when something goes wrong.
Technology gives us another way of doing that.
Technology doesn't replace management
This distinction is important.
I don't believe the answer to every security problem is another app.
You can have the most sophisticated patrol system available and still provide a terrible security service.
Someone has to respond to the information.
If an officer repeatedly misses patrols, what happens?
If they don't respond to a welfare check, who calls them?
If they still don't respond, what is the escalation procedure?
If patrol completion suddenly deteriorates during the night, does anybody notice?
And if an officer repeatedly fails to perform, does management actually deal with it?
Technology should give managers better information.
It doesn't remove the requirement to manage.
Patrol verification should be meaningful
There is also a danger of turning technology into another box-ticking exercise.
Putting an NFC checkpoint next to the security desk and asking somebody to tap it every hour proves very little.
A properly designed patrol should make sense for the site.
Where are the vulnerable areas?
Which doors need checking?
Are there areas susceptible to trespass?
Are there fire risks?
Are there particular assets requiring inspection?
Has something changed because the construction project has progressed?
The technology should support the security plan rather than becoming the security plan.
At some of our assignments, NFC checkpoints form part of the patrol arrangements so we can verify that officers have physically reached particular locations.
Combined with scheduled tasks and welfare monitoring, this gives our management team considerably greater visibility of what is happening during an overnight shift.
But we're deliberately keeping the system straightforward.
Technology only works operationally if officers actually understand and use it.
Welfare and performance aren't opposites
There is sometimes an attitude in security that welfare is about being soft on officers.
I think that's completely wrong.
Looking after officers and demanding high standards can exist at exactly the same time.
If somebody is cold, isolated, exhausted and working in an unsuitable environment for 12 hours, their performance is likely to deteriorate.
The SIA's current strategic plan itself recognises that security officers often work long shifts in isolated or challenging environments and specifically highlights workforce welfare and fair working conditions.
Good welfare is therefore not separate from service delivery.
It contributes to service delivery.
Give officers appropriate welfare facilities.
Make sure they can take proper breaks.
Give them meaningful work to do.
Maintain contact.
Check they're okay.
Supervise them.
And then hold them accountable for delivering the service.
Price matters more than clients sometimes want to admit
There is another uncomfortable part of this conversation.
Security is often purchased almost entirely on hourly rate.
One provider charges £X.
Another is 50p cheaper.
Someone else comes in £1 cheaper.
Procurement understandably wants value.
But the hourly charge has to pay for far more than the person standing on site.
There are wages, holiday entitlement, employer costs, recruitment, vetting, training, uniforms, insurance, management, supervision, technology, administration, sickness cover and operational resilience.
Eventually, relentless downward pressure on price has consequences.
That doesn't mean the most expensive security company automatically provides the best service.
It clearly doesn't.
But buyers should ask what sits behind the hourly rate.
Interestingly, the SIA's 2026–2029 strategy specifically warns buyers about purchasing security on cost alone and argues for understanding the value of quality security provision.
The question shouldn't simply be:
“How much is the officer per hour?”
It should also be:
“How are you managing that officer at 3am?”
So who failed?
If I discover one of our officers asleep on duty, I'm not going to pretend the officer has done nothing wrong.
They have.
We would investigate it and deal with it appropriately.
But as a security provider, I also think we have to look at ourselves.
Was the right officer recruited?
Were they properly inducted?
Was the assignment realistic?
Were suitable welfare arrangements available?
Were patrols properly designed?
Were we monitoring them?
Were welfare checks being completed?
Had there been previous warning signs?
And, crucially:
Why didn't we know before the client did?
That's the uncomfortable question.
Because professional security management shouldn't just respond when something goes wrong.
It should create systems capable of identifying when something is starting to go wrong.
The 3am test
If you purchase overnight security, there is one question I'd suggest asking your provider:
“How do you know what your officer is doing at 3am?”
Not what they're supposed to be doing.
How do they know?
If the answer is simply:
"They're an experienced officer and we trust them."
I'd ask another question.
“What evidence would you have if they weren't?”
Trust your officers.
Support your officers.
Look after their welfare.
But verify that the security service being paid for is actually being delivered.
Because a signed timesheet tells you somebody was rostered for 12 hours.
It doesn't necessarily tell you what happened during those 12 hours.
Sean Keelan
Blue Light Security Solutions Ltd
What should happen if a security officer is found asleep on duty?
A security officer sleeping on duty should be investigated as a performance issue. But the investigation shouldn't stop with the officer.
The security provider should also ask why its supervision and monitoring arrangements failed to identify the problem.
If an officer has missed scheduled patrols, failed to complete tasks or stopped responding to welfare checks, there should ideally have been warning signs before the client arrived on site and discovered the problem.
Effective overnight security therefore needs more than simply placing an officer on site. It should include appropriate recruitment, welfare arrangements, meaningful patrols and tasks, lone-worker monitoring, management oversight and a clear escalation process when expected activity is missed.
That's why, when I hear:
“The security officer was asleep.”
My next question is:
“How did nobody know?”
How can security guards be monitored overnight?
Historically, monitoring an overnight security officer could amount to little more than an occasional telephone call or supervisor visit.
Technology now allows considerably better oversight.
At Blue Light Security Solutions, we use a patrol and lone-worker system that allows specific activities to be scheduled throughout an officer's shift.
These can include:
scheduled patrols;
checks of specific areas or assets;
site-specific security tasks;
NFC checkpoints at designated locations; and
scheduled lone-worker welfare checks.
This gives us greater visibility of what is actually happening during a shift.
However, the most important part of the system isn't recording everything that goes right.
It's identifying when something doesn't happen.
If an officer fails to respond to a scheduled welfare alarm, for example, an alert can be generated for our team.
We can then make contact with the officer and establish what's happening.
Perhaps they've fallen asleep.
But perhaps they've become unwell.
They may have suffered an accident.
They could be dealing with an incident.
Or there may be another reason they are unable to respond.
That's why I don't see lone-worker technology as simply a way of catching officers sleeping.
It's a management and welfare tool.
How can a client verify that security patrols actually happened?
This is another important distinction.
A timesheet can demonstrate that an officer was scheduled to work between 19:00 and 07:00.
It doesn't necessarily demonstrate that six required patrols happened during that period.
Where appropriate, we can use NFC checkpoints at designated locations around a site.
An officer physically attending that location as part of their patrol records the activity through the system.
That creates considerably greater visibility than simply relying on somebody writing:
"02:00 – patrol completed."
But even patrol technology needs to be designed intelligently.
Putting an NFC checkpoint next to the security desk and requiring somebody to tap it every hour achieves very little.
The checkpoints and tasks should reflect the actual security risks.
Which doors need checking?
Where are the vulnerable access points?
Are there areas susceptible to trespass?
Are there particular assets requiring inspection?
Are there fire or safety risks that form part of the assignment?
Has the construction project progressed and created different vulnerabilities?
Technology should support the security plan. It shouldn't become the security plan.
How can you stop security officers sleeping on night shifts?
There isn't a piece of technology that can guarantee an officer will never fall asleep.
The answer is a combination of measures.
Recruit the right people for night work. Manage working hours and fatigue. Provide appropriate welfare facilities. Give officers meaningful tasks and patrols throughout the shift. Maintain contact with lone workers. Monitor expected activity. Investigate missed tasks or welfare checks. Carry out management checks. And deal appropriately with repeated performance failures.
Technology gives managers information.
Someone still has to manage.
If an officer repeatedly misses patrols but nobody reviews the information, the technology has achieved very little.
If an officer doesn't respond to a welfare alarm, somebody needs to act.
If performance starts deteriorating during a shift, there needs to be an escalation process.
That's the difference between having a patrol system and actually managing a security operation.
Then, immediately before the Sean/Blue Light sign-off, I'd add:
Frequently asked questions
Can a security officer sleep while on duty?
Where an officer is employed to provide active security throughout a shift, they would normally be expected to remain awake and capable of carrying out the assignment requirements, subject to the specific working arrangements and authorised breaks. If an officer is found asleep while responsible for active security duties, the circumstances should be investigated.
How do security companies know officers are completing patrols?
Patrol-management technology can provide evidence that scheduled activities have taken place. This can include NFC checkpoints positioned at designated locations, scheduled tasks and electronic patrol records. The technology is most effective when missed activities are actively monitored and investigated rather than simply recorded.
What is lone-worker monitoring for security officers?
Lone-worker monitoring helps a security company maintain contact with officers working alone. Scheduled welfare checks can require an officer to confirm they are safe. If the officer fails to respond, an alert can trigger an escalation process so their welfare can be checked.
Can technology prevent security officers sleeping?
Not completely. Technology can identify missed patrols, tasks or welfare checks that may indicate a problem, but it cannot replace appropriate recruitment, fatigue management, welfare, supervision and management.
What should I ask my security company about night guarding?
One of the simplest questions is:
“How do you know what your officer is doing at 3am?”
Ask how patrols are verified, how lone workers are monitored, what happens when a welfare check or patrol is missed, how often management checks take place and what evidence of service delivery is available.
If the only evidence available is a timesheet at the end of the month, you know how many hours were invoiced.
You don't necessarily know what happened during those hours.
Need Greater Oversight of Your Overnight Security?
If you have concerns about overnight officer performance, missed patrols, lone-worker welfare or simply want greater visibility of what is happening on site when nobody else is there, Blue Light Security Solutions can help.
Our security services are supported by patrol verification, scheduled task monitoring and lone-worker welfare technology, backed by active management and escalation when expected activity is missed.
Because providing an officer is only part of the service. Knowing the service is actually being delivered matters too.
Contact Blue Light Security Solutions to discuss your overnight security requirements. 0800 999 1829 - office@bluelightgroup.uk