Most Perth businesses sign security contracts without reading the Service Level Agreement (SLA) properly. When something goes wrong, they find their SLA doesn’t protect them.
An SLA isn’t just a legal formality. It defines what happens when your security provider fails to show up, misses a patrol, or doesn’t respond to an alarm. Without the right clauses, you may pay for protection that isn’t there when you need it.
We’ve seen commercial projects across Perth, from Kwinana industrial sites to Mandurah retail developments, where vague SLAs left businesses exposed to theft and liability claims. This guide breaks down what your security SLA must include to protect your commercial project.
What A Security SLA Actually Does (And Why Most Don’t Work)
A Service Level Agreement sets out the service standards your security provider commits to delivering. It defines response times, guard qualifications, patrol frequencies, and what happens when these standards aren’t met.
The problem is most SLAs protect the provider, not you. They use vague terms like “reasonable efforts” and avoid specific timeframes. They limit liability so a serious security failure might cost you thousands, while the provider’s liability is capped at the monthly fee.
An effective SLA sets measurable standards, defines clear consequences for missed targets, and ensures accountability. If a security guard doesn’t show up at your Rockingham construction site and equipment gets stolen, a weak SLA means you bear that cost. A strong one means your provider must compensate you.
Response Times That Actually Mean Something
The most critical part of any security SLA is response times. This is where most agreements fall short.
A weak SLA might say: “Security personnel will respond to alarms in a timely manner.” But what does timely mean? Your SLA needs specific, measurable response times for different scenarios:
Priority 1 alarms (break-ins, panic buttons, confirmed threats): Maximum 10-15 minutes response time for Perth metro sites, 20-30 minutes for regional locations.
Priority 2 alarms (motion sensors, perimeter breaches, unconfirmed triggers): Maximum 20-30 minutes metro, 40-60 minutes regional.
Scheduled patrols: Exact times documented, with a tolerance window of no more than 15 minutes.
After hours support calls: Initial response within 30 minutes, on-site attendance within 2 hours if needed.
These timeframes should adjust based on your location. A Broome mining operation will have different logistics than a Kwinana warehouse, and your SLA should reflect that.
The SLA should also specify what happens when these timeframes aren’t met. One missed response might be excusable. Three in a month indicates a problem, and there should be consequences.
Guard Qualifications And Vetting Requirements
You’re not just paying for a warm body in a uniform. You’re paying for trained, licensed, vetted security professionals.
Your SLA must specify minimum qualifications for every guard assigned to your site. In Western Australia, that starts with a valid Security Agent’s Licence.
For commercial projects, we recommend SLAs include:
First Aid certification for all guards, current and verified. If someone gets injured on your site, your security team should respond before paramedics arrive.
Site-specific training documented before any guard’s first shift. They should know your site layout, high-risk areas, emergency procedures, and who to contact.
Background checks completed within the past 12 months. For sensitive sites, you want assurance that your guards have been properly vetted.
Experience requirements for complex sites. A new guard might be fine for basic access control, but if you’re securing a construction site with millions in equipment, you want someone experienced.
The SLA should also address guard rotation. Some providers rotate guards frequently, meaning you never have consistent coverage. Others assign dedicated guards who learn your site. Specify which model you’re getting and whether you can approve guard assignments.
Patrol Schedules And Proof Of Completion
If you’re paying for mobile patrols, your SLA needs to define what you’re getting.
How many patrols per shift? What route do they follow? How long does each patrol take? And how do you verify they actually happened?
Modern security uses digital verification systems. Guards scan checkpoints using NFC tags or QR codes, creating timestamped proof that patrols occurred. GPS tracking shows patrol routes and timing.
Your SLA should specify:
- Minimum number of patrols per shift (typically 2-4 for overnight coverage)
- Specific checkpoints that must be scanned each patrol
- Maximum time between patrols (usually 2-3 hours)
- Electronic reporting requirements (you should receive timestamped patrol reports)
- Escalation procedures if a checkpoint can’t be accessed
For construction sites across Perth, patrol frequency often increases based on theft patterns. If your Mandurah site has had three attempted break-ins in a month, your SLA should allow you to request increased patrols without renegotiating the contract.
The reporting matters as much as the patrols. You should receive daily summaries showing every patrol completed, every checkpoint scanned, and any incidents. This creates an audit trail that’s invaluable if you need to make an insurance claim.
Incident Response And Reporting Obligations
When something happens on your site, the speed and quality of your security provider’s response matters.
Your SLA must define procedures for different incident types:
Immediate notification for serious incidents (break-ins, injuries, fires). You or your designated contact should be called within minutes.
Incident reports submitted within 24 hours, including photos, witness statements, and a clear timeline. These reports need to support insurance claims and police investigations.
Police liaison when required. Your guards should know when to call police and how to preserve evidence.
Follow-up actions documented. If a patrol identifies a damaged fence, when will it be reported, to whom, and what’s the expected timeframe for resolution?
The quality of incident reporting separates professional security providers from amateur ones. Businesses have lost insurance claims because their security company’s report was inadequate.
Your SLA should specify report formats, mandatory information fields, and submission timeframes. For commercial projects, these reports are legal documents that might determine whether your insurance pays out.
Liability Caps And Insurance Requirements
This is where most SLAs protect the provider, not you.
Many agreements cap the provider’s liability at one or two months of service fees. If you’re paying $3,000 a month and a guard’s negligence leads to $50,000 in stolen equipment, the maximum you can claim is $6,000.
That’s not adequate protection for a commercial project.
Your SLA should address:
Professional indemnity insurance held by the provider, with minimum coverage of $5-10 million. You should be named as an interested party and receive a certificate of currency annually.
Public liability insurance covering guard actions on your site. If a guard injures someone, their insurance should respond first.
Workers compensation for all guards. You should never be in a position where an injured guard makes a claim against your business.
Liability caps that reflect realistic risk. For high-value sites, consider negotiating removal of caps or setting them at a meaningful level (e.g., $100,000 minimum).
The SLA should also specify what happens if the provider’s insurance lapses. This should trigger an immediate right to suspend payment and potentially terminate the agreement.
Performance Metrics And Review Processes
A good SLA doesn’t just set standards. It measures whether they’re being met and creates a process for improvement.
Performance metrics might include:
- Percentage of patrols completed on time (target: 98%+)
- Average response time to Priority 1 alarms (target: under 12 minutes)
- Number of missed guard shifts (target: zero)
- Incident report completion rate within 24 hours (target: 100%)
- Client satisfaction scores from quarterly reviews
These metrics should be tracked monthly and reported to you quarterly. For larger projects, monthly reviews make more sense.
The SLA should include a formal review process, typically quarterly or biannually. These reviews assess whether the security plan is still fit for purpose and whether metrics are being met.
There should also be a clear escalation process. If performance drops below acceptable levels for two consecutive months, what happens? Typically this should trigger:
- A formal performance improvement notice
- A 30-day correction period with weekly check-ins
- Right to terminate without penalty if standards aren’t met
This protects both parties. It gives the provider a chance to fix problems, but it also gives you an exit if they can’t deliver.
Termination Rights And Service Continuity
Most security contracts lock you in for 12-24 months with significant break fees. But what if the service is substandard? What if your project timelines change?
Your agreement should include:
Termination for cause if SLA standards are repeatedly missed, with a reasonable notice period.
Termination for convenience after an initial period, with 60-90 days’ notice.
Service continuity requirements during the notice period. Some providers reduce service quality once they know you’re leaving. The SLA should require full service delivery until the final day.
Final reporting and handover obligations. You should receive all patrol reports, incident logs, access codes, and site documentation before final payment.
For commercial projects, timing matters. If you’re securing a Geraldton construction site and the builder extends the project, you need flexibility to extend security coverage without renegotiating the entire agreement.
Perth-Specific Legal Considerations
Western Australia has specific regulations that should be reflected in your security SLA.
All security guards must hold a current WA Security Agent’s Licence. Your SLA should require proof of licensing for every guard assigned to your site.
For crowd control work at licensed venues, guards need additional licensing. If your project includes public-facing elements, verify your guards have the correct licensing category.
The Security and Related Activities (Control) Act 1996 sets standards for security operations in WA. Your SLA should include a compliance clause requiring the provider to meet all relevant WA legislation.
For projects in regional WA, distance can affect response times and service delivery. An SLA for a Kalgoorlie-Boulder mining operation will look different from one for a Perth CBD office building.
If your project involves government contracts or regulated industries, additional security requirements might apply. Your SLA should address how these requirements are met.
Don’t sign a security contract based on price alone. The cheapest provider often has the weakest SLA. Read the SLA carefully, negotiate terms that reflect your needs, and ensure you have measurable standards with real consequences.
We work with commercial projects across Perth to develop security solutions with SLAs that protect your interests. If you’re reviewing a security proposal or need to strengthen an existing agreement, get in touch with us and we’ll walk you through what your SLA should include.
Frequently Asked Questions
What’s the difference between a security contract and an SLA?
The contract is the overall legal agreement covering pricing and obligations. The SLA is a section that defines measurable service standards and performance metrics. You can’t have a good contract without a detailed SLA.
Can I negotiate SLA terms with a security provider?
Absolutely. Most providers work from a standard template, but nearly every term is negotiable. Response times, reporting requirements, and liability caps should all be tailored to your needs.
How often should we review our security SLA?
Quarterly reviews work well for most projects. This gives you enough data to spot trends without excessive admin work. For high-risk sites, monthly reviews make more sense.
What happens if my security provider consistently misses SLA targets?
Your SLA should specify this. Typically there’s a formal warning process, followed by a correction period, then a right to terminate without penalty if standards aren’t met. Document every breach carefully as this becomes your evidence.
Do we need different SLAs for different types of security services?
Yes. Mobile patrols, static guards, alarm response, and event security all have different performance standards. Your SLA should define specific metrics for each service type you’re using.