chch.live how nz actually works

How New Zealand actually works, reporting a problem

Reporting a problem, what happens after you tap send

A dumped couch, a leaking toby, a pothole with ambition. The report takes a photo and a pin; what happens next is a route through a call centre, a triage queue and a crew, and, in Christchurch, a public record that says how long it took.

The front door

Most public reports arrive through Snap Send Solve, the app that photographs a problem, reads the pin, and routes it to the right authority by location and type. The council's own phone and web channels take the same reports; Snap Send Solve is simply the door that publishes its half of the ledger, which is why this site's feed and the problems pages are built from it. A report is a notification to the record: a person, a place, a problem, a timestamp.

Who actually owns the problem

The first real question isn't what the problem is, it's whose it is. The same street corner can belong to four different agencies:

Snap Send Solve's routing is the service, the app knows the boundaries so you don't have to. A report sent to the wrong desk is the most common reason a report dies quietly.

What "fixed" means in the record

When the problem is resolved, the record gets a matching entry, the report and its resolution pair up. This site keeps both halves: the problems pages count what gets reported where, and the fix entries say how long the record took between the two events. Read those numbers as the system's own account of itself, a fast "fixed" is the record saying a crew closed it, not an auditor certifying the repair. The honest caveat is built into the data: what isn't reported isn't measured.

Why is the same pothole reported every winter?

Because the record measures the report, not the repair. A surface fix on a failed road base is a calendar invitation, the report stream on a street page will show the same fault recurring seasonally until the rebuild reaches it. Recurrence in the record isn't noise; it's the record arguing for a bigger fix.

What makes a report work

In Christchurch

The feed you read on this site is this exact machinery in public: every report a datapoint, every fix a pair. The suburb and street pages are the same reports sorted by place, so the answer to "does the council ever fix my street" is on your street's page, in its own numbers.

Last reviewed 23 September 2026, sources: Snap Send Solve, CCC contact and report-a-problem pages, this site's problem and fix records. Corrections: /corrections.

Questions, answered briefly

How do I report a problem in Christchurch?

Most public reports go through Snap Send Solve, the app takes a photo and a pin and routes the problem to the right authority by location and type. The council's own phone and web channels take the same reports; genuinely dangerous situations go to 111, not the app.

Who is responsible for fixing a reported problem?

It depends whose problem it is: Christchurch City Council owns roads, footpaths, drains, parks, trees, kerbside bins and noise bylaws; Environment Canterbury owns rivers and drain assets; NZTA owns the state highways like Moorhouse and Brougham; power and phone lines go to their utilities. A report sent to the wrong desk is the most common reason one dies quietly.

What does "fixed" mean on the problems record?

The report and its resolution pair up in the record, a fast "fixed" says a crew closed it, not that an auditor certified the repair. What is not reported is not measured; the problems pages count both halves.

Why does the same pothole get reported every winter?

Because the record measures the report, not the repair, a surface fix on a failed road base recurs seasonally until the road is rebuilt. The report stream on a street page shows the same fault coming back, and recurrence in the record is the argument for a bigger fix.