QR Fault Reporting for Councils & Public Facilities

The problem with phone and email fault reporting

A ratepayer who notices a broken BBQ or an overflowing bin has to find the right number, explain where they are, and hope someone writes it down correctly. Councils get vague, hard-to-locate complaints; the same fault often gets reported three different ways, or not at all, because reporting it is more effort than the problem is worth.

A QR code fixed to the facility itself removes the two hardest parts: finding who to contact, and describing where the problem is. The sign already tells you exactly which asset it is.

What it looks like on the ground

Each sign links to the same facility's own feedback QR — a small, weatherproof label near the asset it describes, not one generic sign for the whole park. The category list and wording are yours to set per facility.

How a report actually moves — scan to resolved

A visitor scans, picks a category (plumbing, electrical, BBQ, locks, accessibility, graffiti, overflow/waste, a missing fixture, or a general maintenance issue), writes a short description, and optionally attaches a photo. Your team can acknowledge it, assign it, mark it awaiting a contractor, and resolve or close it — with a duplicate/invalid state so the same pothole reported five times doesn't inflate your open-issue count.

What your team sees

Filter by status and category, flag priority (including a dedicated safety-hazard flag), note who it's assigned to, add an internal note nobody outside your team ever sees, and export the lot to CSV for a handover or a council report.

Privacy and anonymity, explained honestly

Reporting works with no account and no required contact details — a visitor can report a hazard without giving their name. If you'd rather collect a name or phone number, you can require it instead; that's a setting per form, not a fixed rule.

An optional anonymous tracking code lets a reporter check back later and see the status and any reply you write — without identifying themselves at any point, even to you. The lookup never reveals the original message or any contact details, so a leaked or guessed code still exposes nothing. Photos and submission details are never public — only your own account can see them.

This is operationally credible privacy design — access-controlled, auditable, and careful about what it collects — not a claim of compliance with any specific law or standard. Check that against your own council's requirements.

This is not an emergency reporting system

Submissions are not monitored in real time. For anything urgent — a safety hazard needing an immediate response, a medical emergency, or a crime in progress — direct people to the appropriate emergency number instead. The public form itself says so.

Built on what FreeQR already does, not a separate product

This uses the same QR Feedback & Issue Reporting product already available on FreeQR Pro and above — the same dynamic QR, scan analytics, and dashboard. Council/public-facility use just means enabling the categories and workflow that fit a park or amenity block, rather than a retail feedback form.