Night Mowing Safety for Councils: WHS First, 60–90 Day Pilot

For councils: embed a WHS risk assessment in an electronic register, require fail safe controls, and test night mowing with a 60–90 day pilot.

Robotic night mowing is safe to run on commercial and public grounds, including solar sites, but only when it starts with a formal, site-specific WHS risk assessment. That assessment has to be embedded in an electronic risk register before any machine runs unsupervised after dark. SafeWork NSW guidance and Standards Australia’s product requirements give asset managers the framework; service providers can give councils a practical way to implement it. The next step is simple: book the risk assessment and document every control before scheduling a single night shift.

TL;DR:

  • A formal, site-specific WHS risk assessment must be completed and embedded in an electronic risk register before any robotic mower is operated unsupervised at night.
  • Risk assessments should involve a cross-functional team and prioritize hazards using risk priority numbers, applying the hierarchy of controls and setting re-assessment triggers for any changes or incidents.
  • Governance policies must include clear operational windows, privacy statements, incident response plans, public feedback channels, and signage to build transparency and trust with local communities.
  • Operational runbooks require confirmed site closures, pre-mapped boundaries, a designated supervisor with a remote emergency stop, and meticulous documentation of maintenance and shift checks.
  • Technical safeguards must include reliable geofencing, collision detection, dual emergency stops, encrypted communications, and tested firmware updates to ensure cybersecurity and physical safety.

Table of Contents

Risk assessment and WHS integration: the mandatory first step

A night mowing program should never start with the machine. It starts with a documented, cross-functional risk assessment that becomes part of the site’s existing WHS framework, not a bolt-on afterthought.

SafeWork NSW’s guidance on collaborative robot deployment recommends a structured, repeatable process, and it applies just as well to autonomous mowers as it does to industrial cobots. Here’s how to run it properly:

  1. Assemble a cross-functional team. Pull in safety officers, operations staff, IT (for connected machines), maintenance, and someone who owns stakeholder or legal relationships. A risk assessment written by one department in isolation misses obvious blind spots.
  2. Score every hazard with an RPN. SafeWork NSW’s risk priority number model assigns action thresholds: 1–2 is low, 3–8 medium, 9–18 high, and 27 demands immediate action. This turns a vague hazard list into a prioritised action plan.
  3. Apply the hierarchy of controls. Eliminate the hazard first, then substitute, isolate, engineer, administer, and only fall back on PPE or procedure as a last resort.
  4. Set clear re-assessment triggers. Any incident, site layout change, or hardware/software update should automatically reopen the assessment, not wait for an annual review cycle.
  5. Log everything in an electronic risk register. Controls, owners, and review dates need to sit somewhere auditable, not in someone’s inbox.

Council teams evaluating a provider should ask to see exactly this process documented, not just a sales pitch about sensors. Our machine risk assessment guidance breaks down what a defensible register actually looks like for groundskeeping equipment.

Pro Tip: Build the re-assessment trigger list into your contract with the mowing provider, not just your internal policy. That way a firmware update on their side automatically forces a documented review, instead of relying on them to tell you.

Risk assessment and WHS integration: the mandatory first step — overview diagram

Governance, stakeholder communication and maintaining public trust

A risk assessment protects the site. Governance protects the relationship between the council and the people who use that site.

Australia’s national robotics strategy makes trust and transparency central to responsible automation adoption, and that framing matters more for local government than almost any other sector, because ratepayers expect to be told what’s happening on public land after dark.

A workable governance policy for night mowing should include:

  • A published, plain-language operations window (which nights, which hours, which zones)
  • A privacy statement covering any cameras or sensors on the mower
  • A named incident response commitment, including expected response time
  • A public feedback channel for residents who notice something unusual
  • A review cadence tied to the WHS risk register, not a separate calendar

Brimbank City Council’s work on governance for machine-vision systems shows how a tailored framework, built around clear management pillars and an action plan, defuses privacy and ethical concerns before they become complaints. Councils running solar-site or sportsground mowing at night can borrow the same structure. Transparent signage at site entrances, stating exactly when autonomous equipment operates, does more to prevent pushback than any technical spec sheet.

Operational controls and runbook for night mowing

The governance policy sets the rules. The runbook is what actually happens on the ground, shift by shift.

  1. Confirm the closed-access window before start-up. Night mowing should only run when public access is formally prohibited, following a documented site-closure checklist, not just an assumption that “nobody’s around at 11pm.”
  2. Pre-map boundaries and manually clear high-risk perimeters. Commercial autonomous mowing practitioners recommend keeping mowers within 10 to 15 feet of taught safety zones around obstacles, and clearing those zones by hand before the first automated pass. “Teach once” is not “set and forget”; boundaries need revalidation whenever the site changes.
  3. Assign one accountable supervisor per shift. That person carries a remote emergency-stop device and runs a daily verification checklist before the mower is released for the night. One name, one device, no ambiguity about who’s on point.
  4. Keep a full paper trail. Runbooks, shift checks, firmware version logs, and incident reports all belong in the same system as the risk register, so an auditor or council committee can trace exactly what happened on any given night.

Pro Tip: Rotate the supervisor role deliberately rather than letting one person “own” night mowing indefinitely. A second set of eyes every few weeks catches complacency that a single long-term operator often stops noticing.

Technical safeguards and cybersecurity expectations for connected mowers

Engineering controls are non-negotiable, and AS/NZS 60335.2.107:2020 sets the baseline for what a robotic battery-powered lawnmower should be able to do before it’s trusted with unsupervised night work.

At minimum, demand:

  • Reliable geofencing with lift-detection and automatic tip-over shutoff
  • Collision detection that stops the machine, not just slows it
  • Dual-channel emergency stop with hardware-level fail-safes, so no single point of failure disables the stop function
  • Isolated control networks and encrypted communications
  • A documented, testable firmware-update procedure

Cybersecurity deserves the same weight as physical safety here. Design guidance for safe cobot workplaces treats control-channel isolation and redundant emergency stops as core design requirements, not optional extras, and that logic transfers directly to connected mowers operating on public infrastructure. Every update pushed to a fleet should trigger a validation test before the next night shift, not after a problem shows up.

Maintenance, testing and change-management rules

Safety on paper doesn’t hold up without daily discipline on the ground.

  1. Run a pre-shift check every day. Sensors, battery charge, and emergency-stop function all get verified before the mower leaves the depot.
  2. Schedule weekly and monthly maintenance with documentation. Blade condition, sensor calibration, and firmware status all need a written record, not a verbal “yeah, it’s fine.”
  3. Treat every hardware or software change as a trigger. A new firmware version or a site layout change reopens the risk assessment automatically, no exceptions.
  4. Follow a strict near-miss workflow. Stop the operation, investigate, fix the root cause, re-run the risk assessment, and record the outcome before resuming night work.

AS/NZS 60335.2.107:2020’s revalidation guidance is explicit on this point: skipping re-calibration after a landscaping or infrastructure change is one of the most common causes of aborted or unsafe operations.

How Brightview implements night mowing safety on the ground

Deployments should be built around the same cross-functional risk assessment model described above, with controls recorded in an electronic register rather than left to memory or a paper file.

  • Site-specific procedures for mowing under solar arrays and on steep slopes, where obstacle clearance and slope stability change the risk profile entirely
  • Operator training tied to documented runbooks, so shift handovers don’t lose institutional knowledge
  • Ongoing maintenance logs that feed directly into the change-management trigger process
  • Practical experience adapting safe access landscaping procedures for solar-panel sites, where access constraints are tighter than a standard sportsground

That combination, formal risk assessment plus site-specific procedure plus documented maintenance, is what turns a general safety standard into something an auditor can actually verify on a specific property.

What often goes wrong in real deployments

The biggest failure isn’t the machine. It’s councils treating a robotic mower as set-and-forget once it’s deployed, when continuous monitoring and revalidation are what actually keep it safe. Pick operators for judgement and adaptability, not just technical comfort, and be upfront with the community early. A 60 to 90 day pilot with clear KPIs, uptime, incidents, and stakeholder feedback, tells you far more than any spec sheet before you scale.

— BrightView

How Brightview Solar & Groundskeeping can help you pilot night mowing safely

Getting night mowing right isn’t about buying a machine and hoping the sensors do the work. It’s about pairing a documented, site-specific WHS risk assessment with a provider who’s already built that process into daily operations. Service providers may offer a combination of a formal risk assessment, a structured pilot program, and operator training, bundled as one package rather than three separate procurement headaches.

Brightview Solar & Groundskeeping

For asset managers and councils weighing up whether autonomous night mowing suits their site, a 60 to 90 day pilot is the sensible way to test uptime, incident rates, and stakeholder feedback before committing to a wider rollout or locking in SLA terms. Explore how the robotic lawn mowing service works, then get in touch to scope a site assessment for your grounds or solar asset.

Sources

FAQ

What is the first step before running robotic mowers at night?

A documented, site-specific WHS risk assessment comes first, embedded in an electronic risk register with named owners and review dates, per SafeWork NSW guidance.

What standard governs robotic lawnmower safety in Australia?

AS/NZS 60335.2.107:2020 sets the particular safety requirements for robotic battery-powered electrical lawnmowers, including sensor and fail-safe expectations.

How often should the risk assessment be reviewed?

Any incident, site layout change, or hardware/software update should trigger an immediate re-assessment, not just an annual review.

Does night mowing require public access to be closed?

Yes. Operations should only run within a formally closed-access window, backed by a documented site-closure checklist and clear signage for the public.

Can a service provider help with the risk assessment itself?

Yes. Brightview Solar & Groundskeeping runs cross-functional machine risk assessments and documents controls in an electronic register as part of its pilot and service offering.

What technical safeguards should a council demand from a provider?

Reliable geofencing, lift-detection, collision detection, dual-channel emergency stop, and encrypted, isolated control networks are the minimum baseline before approving unsupervised night operation.

Share the Post:

Related Posts