If your council or asset portfolio runs contracted robotic mowers, sprayers, or solar-cleaning units, the primary WHS duty sits with you, not just the contractor. Under the Work Health and Safety Act 2011, the person with management or control of the workplace carries a non-delegable duty to ensure safety “so far as is reasonably practicable” — even when a third party supplies and operates the equipment.
Before you sign off on any deployment, demand three things:
- Standards evidence — a current compliance certificate or test report against AS/NZS 60335.2.107 for battery-powered robotic mowers, or the equivalent standard for the equipment class.
- A site-specific risk assessment aligned to the Safe Work Australia code, covering exclusion zones, public interaction, and terrain hazards.
- Documented commissioning and firmware controls — a competent-person sign-off plus a written policy on how software updates get tested and rolled back.
Any supplier who can’t produce all three on request shouldn’t be on your shortlist.
Key Takeaways
Asset owners remain the primary WHS duty holder for contracted autonomous equipment, so compliance evidence, not just service delivery, has to be part of every procurement decision.
| Point | Details |
|---|---|
| Duty stays with you | The WHS Act’s non-delegable duty means asset managers and councils can’t contract away safety responsibility. |
| Demand standards evidence | Request a current AS/NZS 60335 certificate or test report before any robotic mower is deployed. |
| Treat updates as WHS events | Require pre-deployment reassessment and rollback capability for every firmware or map change. |
| Build audit rights into contracts | Insist on telemetry access, log retention, and scheduled audit rights at tender stage, not after an incident. |
| Choose a compliance-first supplier | Brightview Solar & Groundskeeping documents commissioning, shares risk assessments, and enforces firmware controls as standard practice. |
Table of Contents
- What autonomous equipment regulations in Australia actually cover
- Who holds WHS duties for autonomous plant on your site?
- Which technical standards and import rules apply?
- Building a procurement checklist that actually holds up
- How do you control risk during day-to-day operation?
- Do firmware updates count as a WHS risk?
- What does proper commissioning and maintenance look like?
- How BrightView builds compliance into every deployment
- Ready to review your autonomous equipment compliance position?
- Sources
- FAQ
What autonomous equipment regulations in Australia actually cover
Australia doesn’t have a bespoke “robot law.” Autonomous mowers, sprayers, and solar-cleaning units fall under the same WHS framework that governs any other item of plant, which is precisely why so many procurement teams underestimate the paperwork involved. The regulatory framework for autonomous vehicles used on public roads is a separate legal area entirely. This article does not deal with self-driving cars or on-road autonomous vehicle guidelines. What matters here is autonomous plant operating on private, commercial, or council-managed land.
Three layers apply in practice:
- The Work Health and Safety Act 2011 sets the overarching duties for a “person conducting a business or undertaking” (PCBU) and for anyone with management or control of a workplace, plant, or fixtures.
- The Model WHS Regulations, adopted with local variations across states and territories, translate those duties into specific requirements for plant design, registration, and operation.
- Safe Work Australia’s approved codes of practice, including the code on managing the risks of plant in the workplace, are admissible as evidence of what a reasonable operator ought to have known about a hazard. If a regulator or court asks whether you exercised due diligence, the code becomes the practical yardstick.
That last point matters for procurement. A contractor claiming their robot is “self-managing” doesn’t remove your obligation to check the code’s requirements were actually followed on your site.
Who holds WHS duties for autonomous plant on your site?
The WHS Act doesn’t let asset owners hand off responsibility just because a contractor owns and drives the robot. Here’s how the duty structure actually works:
- Non-delegable duty — the person with management or control of the workplace retains WHS obligations even after signing a service contract. Contracting the work out creates concurrent liability, not a transfer of it.
- Consultation and worker engagement — you’re expected to consult with contractors, council staff, and anyone else whose work might intersect with the robot’s operating zone, and to keep records of that consultation.
- Recordkeeping — daily pre-start checks, maintenance logbooks, training records, and incident logs need to exist and be retrievable, not just promised verbally.
- Registration and licensing thresholds — some plant categories trigger design registration or require operators to hold specific licences; check this against the equipment class before deployment, not after.
- Competent person sign-off — commissioning, major maintenance, and any isolation procedure should be certified by someone with documented training on that specific equipment, not just “someone from the contractor’s team.”
Councils in particular get caught out on point three. A verbal assurance that “the contractor checks it daily” isn’t a record. If an incident occurs on a public reserve, the first thing an inspector asks for is the logbook.
Which technical standards and import rules apply?
Procurement teams often assume “the supplier handles compliance.” That’s true only if you ask for proof. Two technical regimes matter most for robotic groundskeeping and solar-cleaning fleets.
AS/NZS 60335.2.107 is the safety standard covering battery operation, charging systems, and safety functions in robotic rotary mowers. A genuine compliance certificate references this standard by number and version, names the specific model tested, and comes from an accredited testing body. Verbal claims of “it’s compliant” without a document aren’t evidence of anything.
Product Emissions Standards apply to any equipment carrying a spark-ignition engine, which still shows up in some hybrid solar-cleaning rigs and edge-trimming attachments. Since mid-2018, importers and suppliers of non-road spark-ignition engines have needed to hold certification against these standards or a recognised international equivalent. Equipment without it can be seized at the border, which is a supplier’s problem until it stalls your contracted service delivery.
Ask for the certification number, not just a certificate mention in a brochure. Cross-check it against the equipment model actually being deployed, since suppliers sometimes certify one model and roll out a later revision without updating the paperwork.
Building a procurement checklist that actually holds up
Tender documents and service contracts are where most compliance gaps get baked in early. Build these requirements into the document before award, not as an afterthought once the robot’s already on site.
- Pre-award evidence — require a site-specific risk assessment, a written commissioning plan, current standards test reports, and valid insurance certificates as tender conditions, not optional attachments.
- Data and telemetry access — your contract should give you a contractual right to logs, telemetry, and incident data, not just a promise to “share if asked.”
- Firmware and update governance — specify that software or map changes require supplier notification and a documented re-assessment before deployment, with rollback capability if something goes wrong.
- Audit rights — build in the right to audit the contractor’s risk assessments and maintenance records on a set schedule, not only after an incident.
- Liability framing — word indemnity clauses so the contractor cooperates and shares information; don’t let contract language imply WHS duties have been “contracted out,” because legally they can’t be.
Pro Tip: Ask your legal team to review indemnity clauses specifically for “contracting out” language. Courts have consistently found that WHS duties survive even airtight commercial indemnities, so a clause that implies otherwise just creates false confidence at contract signing.
BrightView’s machine risk assessment resources for groundskeeping outline what a genuinely fillable risk assessment template looks like for this equipment class, which is worth reviewing before you draft tender language.
How do you control risk during day-to-day operation?
The hierarchy of controls still applies to a robot the same way it applies to a ride-on mower, even if the failure modes look different. Elimination and isolation should always be considered before you fall back on administrative controls or PPE.
- Exclusion zones and signage — physically mark and sign the robot’s operating area, especially where public foot traffic crosses mowing or cleaning zones.
- Remote monitoring — someone needs to be watching telemetry or camera feeds during operation, not just checking in at the end of the shift.
- Emergency stop and escalation — every unit needs an accessible, tested emergency stop, and staff need a clear escalation path if something behaves unexpectedly.
- Lock-out/tag-out for maintenance — batteries and, where relevant, solar array isolation need documented energy-isolation procedures before anyone works on the unit.
Solar-panel-cleaning robots add a wrinkle here: working at height or near live electrical infrastructure means isolation procedures need to cover both the robot’s own battery and the array it’s cleaning. BrightView’s guide on safe access landscaping covers how these access controls translate to difficult or restricted terrain.
Pro Tip: Ask contractors to demonstrate their emergency stop procedure during commissioning, not just describe it in the manual. A control that exists on paper but hasn’t been physically tested on your site isn’t a control yet.
Do firmware updates count as a WHS risk?
Yes, and this is the part most asset managers miss entirely. Safe Work Australia’s guidance on AI and digital technologies confirms that automated systems and firmware changes are WHS issues, not just IT maintenance items. A map update or software patch can alter how a robot navigates, overriding safety interlocks that were tested and approved during commissioning.
Require these controls in every contract:
- Pre-deployment risk reassessment for any firmware or mapping change, with rollback capability if the update introduces new behaviour.
- Supplier evidence of a patching policy, access controls, and an incident response plan for cyber events.
- Retained telemetry and black-box logs, with contractual audit access if an incident needs investigating later.
Legal commentators note that regulators expect employers to actively monitor these systems rather than assume they self-manage safety. Treating a software update the same way you’d treat a mechanical modification, with sign-off before redeployment, is the difference between a defensible safety case and a gap that surfaces during an incident investigation.
What does proper commissioning and maintenance look like?
Commissioning isn’t a one-off event you tick off before the first mow. It’s the start of a maintenance cadence that needs to be documented for the life of the contract.
- Site acceptance testing — the robot needs to be tested in your actual operating environment, not just against a generic factory benchmark, with results recorded.
- Operator and staff training — anyone who might interact with the equipment needs documented training, including isolation and emergency procedures specific to that model.
- Inspection cadence — daily pre-start checks recorded in a logbook, with a more detailed annual inspection and manufacturer-specified major overhaul intervals.
- Competent person sign-off — maintenance and isolation work should be certified by someone with documented training, and that sign-off needs to be retrievable, not just assumed.
BrightView’s robotic lawn mower safety guide sets out a fuller version of this cadence if you’re building it into a formal maintenance schedule.
How BrightView builds compliance into every deployment
We treat commissioning as a documentation exercise as much as a technical one. Every deployment gets a site-specific risk assessment shared with the client before the first robot touches the ground, not after. Firmware updates go through a controlled process: our team reviews changes against the original commissioning baseline before anything gets pushed to equipment operating on client sites.
Safe access procedures matter just as much on a suburban council reserve as they do on a large-scale solar farm. Isolation protocols for battery-powered mowers and solar-cleaning units follow the same lock-out discipline the Safe Work Australia code sets out, applied consistently whether we’re maintaining a sports field or a commercial rooftop array.
Ready to review your autonomous equipment compliance position?
If you’re comparing robotic mowing, spraying, or solar-cleaning contractors, the paperwork gap is usually where things fall over, not the equipment itself. Brightview Solar & Groundskeeping builds commissioning documentation, standards evidence, and firmware change controls into every contract from day one, so councils and asset managers aren’t left chasing test reports after a robot’s already deployed on site.
Our approach centres on giving you the records a regulator would actually ask for: site-specific risk assessments, competent-person sign-offs, and a documented process for handling software updates before they reach your grounds or solar assets. That’s the difference between a contractor who says “trust us” and one who hands you a file you can put straight into a tender pack or council audit.
If you manage solar assets specifically, our page on solar panel cleaning robot providers breaks down what compliant robotic cleaning looks like for commercial sites. For grounds maintenance, our machine risk assessment resource is a solid starting point for building your own procurement checklist. Get in touch to request an onsite assessment and see exactly what documentation we’d provide before day one.
Sources
- Managing the risks of plant in the workplace (Safe Work Australia)
- Work Health and Safety Act 2011
- Autonomous vehicles without a driver: What do WHS laws require of employers in Australia? (Dentons)
FAQ
Who is legally responsible for a contracted autonomous mower on council land?
The council or asset manager with management or control of the workplace holds the primary WHS duty under the Work Health and Safety Act 2011, even when a contractor supplies and operates the equipment.
What standard applies to robotic lawn mowers in Australia?
AS/NZS 60335 is the primary safety standard for battery-powered robotic mowers, covering charging systems and safety functions; procurement teams should request certification against the current version.
Do firmware updates need a new risk assessment?
Yes. Safe Work Australia’s guidance treats software and mapping changes as potential alterations to a system of work, requiring a documented reassessment before redeployment.
What should be in a robotic equipment procurement checklist?
At minimum: a site-specific risk assessment, standards test reports, a commissioning plan, insurance certificates, and contractual access to telemetry and maintenance logs.
Does Brightview Solar & Groundskeeping handle compliance documentation for clients?
Brightview Solar & Groundskeeping documents commissioning, shares site-specific risk assessments with clients, and applies firmware change controls consistently across mowing, spraying, and solar-cleaning deployments.
