Verdue for councils & government

Know what was done.
See where to look closer.

Every contractor visit lands on the site with its position, time, photos and notes. See what’s complete, what needs a closer look, and what residents have reported.

  • After photo: freshly mown grass
    Grevillea ParkGrounds maintenance · 09:02Inside boundary

    “Mown and edged. Wet ground by the eastern fence.”

  • Lillypilly ReserveMowing · 08:05 · before and after photosInside boundary
  • Banksia OvalEdging · 11:40Before photo missing

Illustrative visits at fictional sites.

01 · Was it done?

Every visit,
with its evidence.

The photos arrive with the visit's time, site and position. Every fact in the record shows where it came from: the crew's app, or the portal's own check.

Long grass around a park bench and bollards before the visit
BeforeVisit · Tue 14 Oct 2026 · 09:02Grevillea Park · GP-02−27.5293, 153.2307
The same bench and bollards with the grass mown and edged
AfterVisit · Tue 14 Oct 2026 · 09:02Grevillea Park · GP-02−27.5293, 153.2307
Grevillea ParkVisit record
Completed
Tue 14 Oct · 09:02
Contractor app
Service
Grounds maintenance
Contractor app
Contractor
Example Grounds Co.
Contractor app
Position
Inside the site boundary
Portal check
Photos
Before and after
Contractor app
Crew note
Mown and edged. Wet ground by the eastern fence.
Crew
Follow-up
Logged as an issue
Portal

Illustrative example: a fictional site, contractor, visit and coordinates.

02 · Was it done where it should be?

Each position,
checked against the site.

The portal checks every contractor visit’s position against the site’s boundary as it arrives. A visit logged outside the boundary raises an alert, so you know which records to look at.

A recorded position supports review. It doesn’t prove every task was done.

Illustrative example: a fictional site, crew and visit.

  • 09:02 · inside. The visit’s position is inside the Grevillea Park boundary.
  • 14:40 · outside. Service logged outside boundary: Grounds maintenance, Example Grounds Co.

03 · What's overdue?

See what's slipped,
and why it might have.

Each site is measured against how often it should be serviced. Beside each flagged site sit the crew's latest note and any open issue on that site, so you can see what might be holding the work up.

Needs attention · Coastal northMowing · today
Sites
28
On schedule
24
Due soon
1
Overdue
3
Flagged sitesReasons come from crew notes and open issues
  • Tea Tree Creek walkEvery 21 days · last visit 30 days ago
    Waterlogged near the creekFlagged by the crew on their last visit, still open.Open issue · from the crew, 18 Sep
    9 days overdue
  • Bottlebrush ParkEvery 14 days · last visit 20 days ago
    Gate locked on arrivalThe mower couldn't get in through the northern gate.Open issue · gate issue
    6 days overdue
  • Banksia OvalEvery 7 days · last visit 11 days ago
    Fallen tree across the eastern edgeSection left until the tree is cleared.Open issue · fallen tree
    4 days overdue
  • Wattle Street vergeEvery 28 days · last visit 26 days ago
    Dry, slow growth“Very little growth since the last cut. Light trim only.”Crew note · 22 Sep
    Due in 2 days

Illustrative example: fictional sites, notes and issues.

04 · What have residents reported?

From a pin on the map
to a job for a contractor.

Residents report a problem on a public form, no login needed, and drop a pin. A pin inside a park links the report to that site. Your team works it through, and can send it to a contractor as a work order with a due date.

Public form · no login
Leaking tap near the playgroundResident report · Mon 20 Oct · 07:48Linked to Grevillea Park
  1. Open
  2. In progress
  3. Resolved
Work orderFix leaking tapExample Grounds Co. · emailed
Due Fri 24 Oct

Illustrative example: a fictional report, site and contractor.

05 · What did the crew see?

Photos and notes,
kept with the site.

Each site keeps its history: before and after photos and the crew’s notes, visit by visit. A missing photo shows as missing, not hidden.

Illustrative example: a fictional site, crew and visits.

Grevillea Park · site history

Illustrative
  1. Grounds maintenance
    Overgrown grass before the visit
    Before
    The same grass mown after the visit
    After

    Mown and edged. Wet ground by the eastern fence.

  2. Mowing
    Before photo missing
    Mown parkland after the visit
    After

    Mown. Bins emptied by council crew the same morning.

  3. Mowing

    Mown. Edges left for the next visit.

06 · Can I show someone?

Evidence you can
hand to anyone.

Export the visits for any period, site or service as a compliance evidence PDF or a CSV. Contractor views show each measure with how many visits it covers, and nobody gets a score.

  • Meets the measure
  • Outside the boundary
  • Photo missing

Illustrative figures, one grain for each visit. A recorded position supports review. It doesn't prove every task was done.

Compliance Evidence ReportCoastal north · 1–14 October 2026
Generated 15 Oct
Illustrative
Within boundary

40 of 42 visits

Photo evidence

37 of 42 visits

SiteServiceCompletedContractorGPSPhotos
Grevillea ParkGroundsGrounds14 Oct 09:02Example GroundsInsideBefore · After
Lillypilly ReserveMowingMowing14 Oct 08:05Example GroundsInsideBefore · After
Banksia OvalEdgingEdging13 Oct 11:40Example GroundsOutsideAfter · before missing

Example Grounds Co. · last 90 days · 118 visits · Illustrative

Inside boundary · 113 of 118
With photos · 105 of 118
A public sports ground surrounded by eucalyptus trees

Public spaces, serviced by internal crews or contractors.

Designed around your service

Start with your sites
and delivery model.

Whether work is delivered by internal crews or contractors, the starting point is the same: understand the service, the records you need and who needs to see them.

A demonstration is the place to test that fit against your operating model.

A useful demonstration
starts with your questions.

Define a practical scope before discussing a pilot. Work through the evidence, access and reporting that your team needs.

SERVICE SCOPE

Sites and work.

The places you manage, maintenance activities and delivery arrangements you want to cover.

REVIEW PROCESS

People and decisions.

Who supplies the records, who reviews them and what should trigger follow-up.

PILOT REQUIREMENTS

Access and evidence.

Data sources, permissions, procurement questions and what a successful pilot must demonstrate.

Before we begin

A few practical questions.

Is this a live council deployment?

The council experience is offered as a demonstration. Operational scope, data connections, access and pilot requirements are confirmed with your organisation before rollout.

Can the demonstration cover internal crews and contractors?

Yes. Bring your delivery model to the demonstration so we can discuss the records, roles and review process for each team. The pilot scope will define what is supported.

Does a GPS position prove the work was done?

No. A position inside the site boundary supports review; it doesn’t prove every task was done. The photos, the notes and your team’s own follow-up complete the picture.

What about procurement and security?

Use the demonstration to identify your security and procurement requirements. Ask for the relevant evidence and agree any outstanding requirements before a pilot.

See how it could fit

Bring your questions
to a demonstration.

We will scope it around your sites and the evidence and decisions your team works with.