The minimum evidence package for robotic mowing contracts includes site visit and completion logs, geo-tagged before and after photos, vegetation-height and weed-control entries, and incident reports, each mapped to your contract KPIs.
TL;DR:
- Contractors must provide GPS-tagged logs, before and after photos, and measured vegetation or weed-control entries for accurate verification.
- Incident reports require timestamped photos, GPS coordinates, and specific details to serve as actionable evidence.
- Evidence should be directly linked to contract KPIs such as safety, quality, environmental, and responsiveness metrics for audit relevance.
- Reporting should be automated during robotic runs, with immediate notification of incidents and structured validation by human reviewers.
- Tender and SOW documents must specify evidence types, file formats, retention periods, and evaluation criteria centered on proof of performance.
Table of Contents
- What to include in service reports and evidence packages
- How reporting maps to contract KPIs, audits and statutory recordkeeping
- Operational workflow: from robotic run to delivered report
- How to specify reporting capability in a tender or statement of work
- BrightView’s perspective: how we deliver compliant reporting and rapid validation
- The reporting gap nobody budgets for
- Request a pilot, sample audit pack or SOW template
- FAQ
- Sources
What to include in service reports and evidence packages
A contractor’s report is only useful if every field is unambiguous and every claim can be checked against raw evidence. Specify these fields in advance rather than accepting whatever format a contractor already uses.
Standardised site visit and completion logs should capture, as seen in examples of comprehensive landscaping services in Tucson, AZ, to ensure consistency and verifiability:
- Date, time, and robot or operator identification number.
- GPS footprint of the work area, with start and end times.
- Total area worked, in square metres, and percentage of the scheduled area completed.
Operational metrics worth requesting alongside the log include cut height, any interruptions or manual interventions, and battery or charge status where that affects service continuity. These details let you spot a pattern, such as a mower repeatedly stalling on the same slope, before it becomes a recurring complaint.
Media requirements matter as much as the written log. Geo-tagged before and after photos should accompany every visit, with a short timestamped video for any incident. Set a file-naming convention up front (site code, date, visit number) and require that metadata, including the original EXIF data, stay intact rather than stripped during upload.

Vegetation and weed-control entries need measured heights rather than vague descriptions, species notes where relevant, and a chemical-use record whenever herbicide is applied. On solar sites, vegetation height limits are frequently enforced during declared fire danger periods. Operators are often expected to supply annual environmental and quarterly HSE reports as part of that duty.
Finally, build a non-conformance and incident template with its own fields: what happened, when it was first noticed, immediate action taken, and the formal follow-up. A vague “mower damaged fence” entry is not evidence. A structured one, with photos, GPS coordinates and a timestamp, is.
How reporting maps to contract KPIs, audits and statutory recordkeeping
Every piece of evidence you request should trace directly to a KPI category in your contract. Otherwise you end up with files nobody uses when it is time to score performance.
- Safety KPIs rely on incident logs and the time-to-notify record.
- Quality KPIs rely on completion records paired with before and after photos.
- Environmental KPIs rely on weed-control logs and vegetation-height entries.
- Responsiveness KPIs rely on how quickly a contractor escalates a notification and closes a non-conformance.
For councils, this mapping matters beyond a single contract. Victorian public construction procurement has operated under a shared supplier performance reporting regime since mid-2018, under DTF’s Guidance 8.2, meaning a poor reporting record on one job can follow a contractor into the next tender evaluation, across agencies. A council that lets reporting slide is not just tolerating a weak file. It is failing to feed a system other agencies rely on.
Retention is the other half of the picture. NSW government recordkeeping guidance sets out retention and disposal authorities for administrative and operational records, and councils typically apply longer retention windows to statutory compliance records than to routine maintenance logs. Build that distinction into your contract rather than defaulting to one retention period for everything.
The audit consequence of weak reporting is concrete: a failed performance assessment does not stay contained to the file you are reviewing. Where shared reporting regimes apply, it becomes part of a supplier’s record for future work elsewhere.
Operational workflow: from robotic run to delivered report
A compliant report starts the moment the robot begins work, not when someone sits down to write a summary at the end of the week.
- Automated capture. The machine should log GPS-tagged run metadata and timestamped media as it works, not after the fact.
- On-site verification and notification. Where an incident occurs, the contractor should give immediate verbal notice, commonly expected within around 30 minutes under contractor HSE handbooks, followed by a formal written report within a few days.
- Data validation and QA. A human reviewer checks the automated log, tags any non-conformance, and attaches the corrective work record before the file is considered closed.
- Packaging the deliverable. Daily or weekly summaries feed a quarterly KPI dashboard, and the full audit pack links each piece of evidence back to its contract line item.
Integration is the step most contracts skip. Rather than accepting a PDF dump at the end of the quarter, ask for delivery through a portal or a structured export (CSV or JSON) that your contract-management system can ingest directly. That single change turns a pile of files into something your team can actually query during an audit.
Pro Tip: Ask contractors to include a manifest file with every audit pack, listing each media file and log entry against its corresponding work order and KPI line.
How to specify reporting capability in a tender or statement of work
Procurement teams get the reporting they specify, not the reporting they hoped for. Build these elements into the statement of work before the tender closes.
Minimum deliverables to list:
- Evidence types required (logs, photos, vegetation records, incident reports).
- File formats, metadata requirements and delivery cadence.
- Retention period aligned to your agency’s recordkeeping schedule.
Acceptance criteria should be prescriptive rather than general. Set a completeness threshold for each visit (for example, every log paired with at least one photo) and sample a percentage of entries during each audit cycle rather than reviewing only on complaint.
Evaluation criteria for bidders should include:
- Whether the contractor offers portal access or only emailed files.
- Whether raw audit packs can be exported on request.
- Whether evidence carries authenticity features such as geo-tags or tamper-evident logs.
- How the bidder’s notification and escalation protocol compares to your required timelines.
Tender documentation for parks and open space maintenance increasingly lists reporting and KPI measurement as explicit evaluation criteria, and reporting quality can outweigh small price differences at renewal. Finally, write in contractual clauses for escalation when reporting fails, an obligation to preserve records through any audit period, and an explicit right to demand raw evidence, not just a summary, on request.
BrightView’s perspective: how we deliver compliant reporting and rapid validation
Our simulator-validated four-phase roadside mowing approach gives us a consistent framework for capturing run data the same way on every site, which is what makes evidence comparable across a contract’s life. We run pilot programs over 60 to 90 days specifically because that window gives asset managers enough reporting cycles to validate performance claims against real evidence, not a single visit. Sample audit packs and service guides are available on request for teams building a tender around these requirements.
The reporting gap nobody budgets for
Most procurement conversations focus on cut quality, coverage and turnaround. Reporting gets treated as paperwork to tidy up after the contract is signed, and that is backwards. The report is the only thing an asset manager actually sees of the work performed. If it is incomplete, vague or stuck in someone’s inbox, the quality of the mowing underneath it is irrelevant to your audit trail.
The conventional advice, get photos and a sign-off sheet, falls short because it treats reporting as proof of attendance rather than proof of performance against a KPI. A photo with no geo-tag and no link to a specific work order is barely better than nothing once a dispute arises.
What should come first is the mapping exercise: before writing a single tender clause, list your actual KPIs and work backwards to the evidence each one needs. Everything else, portals, file formats, retention periods, is just infrastructure to support that mapping. Get the mapping wrong and no amount of dashboard software will fix it.
— BrightView
Request a pilot, sample audit pack or SOW template
If you are drafting a tender and want reporting language that actually holds up under audit, we can help you skip the trial and error. Our pilot programs run over 60 to 90 days, giving you enough reporting cycles to validate a contractor’s performance before committing to a longer term.

We offer:
- Site assessments that identify what evidence your property or solar array actually needs tracked.
- Sample audit packs showing how our logs, photos and KPI summaries are structured.
- Templated SOW language you can drop into a tender, covering evidence types, cadence and retention.
Reach out through our robotic mowing and spraying services page to request a briefing, or look at our pilot program details if you want to see the 60 to 90 day structure before you write it into a contract.
FAQ
What should a robotic mowing contractor report after every visit?
At minimum, expect a completion log with date, time, GPS footprint and area worked, paired with geo-tagged before and after photos. Any vegetation height or weed-control work should be logged as a separate entry with measured figures rather than a general description.
How quickly must a contractor report an incident?
Industry practice in government and industrial contracts commonly requires immediate verbal notice, often within about 30 minutes, followed by a formal written report within a few days. Build both timeframes into your contract rather than leaving the written report open-ended.
How long must councils retain robotic mower service records?
Retention periods depend on the record type: NSW recordkeeping guidance sets longer windows for statutory compliance records than for routine maintenance logs. Check your agency’s specific retention and disposal authority before setting a contract clause.
Why does supplier reporting quality affect future tenders?
Under regimes such as DTF Victoria’s shared supplier performance guidance, performance records on significant public construction work can be shared across agencies. A poor reporting history on one contract can affect a contractor’s standing in a later, unrelated tender.
Does BrightView provide sample audit packs for tender preparation?
Yes, sample audit packs and SOW template language are available on request through our pilot program page, built around the same evidence structure we use for live contracts.
Sources
- Energy Safe Victoria — General duties for solar farm owners and operators
- NSW government — Records retention and disposal authorities (administrative records)
- DTF Victoria — Supplier performance and shared reporting regime (Guidance 8.2)

