From gatekeeper to partner: gathering citizen input for property valuation

Fewer permits, less data

The Environment Act, in force since 1 January 2024, has reduced the permit requirement for many activities: more can be done under general rules or with a notification, and less requires a full permit procedure. For residents that means less red tape and faster processes.

But every permit application was also a data source for government. Someone who renovated, added a dormer or an extension supplied detailed information about their property almost automatically. Now that those applications partly fall away, that stream of data dries up — and a blind spot appears exactly where government needs those details.

Without that data, carrying out the task gets harder

That data is no side issue. For property valuation, renovations, extensions and quality changes provide exactly the details needed to determine a home's value accurately. Where those details used to arrive automatically via the permit, government must now actively track them down. Without that information, valuation becomes less accurate — and that goes to the heart of the task.

That inaccuracy also carries downstream. A value set on incomplete data is more likely to be experienced as wrong by the citizen. That leads to objections, and sometimes to a formal appeal before the courts. And since the pressure on the judiciary is already high, every avoidable case adds further strain to a system that is already creaking — with all the consequences that entails. The chain comes with considerable extra workload and cost; the data you miss at the front end, you pay back at the back end.

That forces alternative methods to gather the data anyway. You can wait until someone reports something or objects, but that is reactive and incomplete. The most direct source is the citizen: proactively asking whether the picture is still correct. Citizen input thus becomes not a burden but an instrument to keep data current and reliable — exactly the theme of our pillar on data governance.

Property valuation as a concrete example: the KOUDVL factors

Nowhere does this become more tangible than in the WOZ. A home's primary characteristics — surface area, volume, type, year of construction — can still be determined reasonably well by models. But value is also shaped by the secondary, value-determining characteristics: the KOUDVL factors — quality, maintenance, appearance, functionality, amenities and location.

Those factors in particular are subjective and hard to keep current from a distance. Is the bathroom renovated or dated? Is there deferred maintenance? Without an inspection or input, that is guesswork — and it is no coincidence that this is exactly what many WOZ objections are about. Reliable citizen input on these characteristics makes the valuation not only more accurate, but also easier to explain.

Why many services are still searching

The will is there, but the approach is not yet common practice. Actively seeking out the citizen is, moreover, not a natural reflex at many government bodies — they are more used to channelling contact than seeking it. And the services that do want to, wrestle with legitimate questions. How do you prevent people from colouring their input to lower their assessment? Is what you gather representative, or do you only hear the vocal citizen? Is it allowed under the GDPR, and how do you record what you use it for? And do existing systems accommodate this kind of interaction at all?

There are initiatives — pre-filled data that residents can check, portals, photo uploads — but a standard is missing. Many organisations experiment in isolation and keep reinventing the wheel.

How to gather good citizen input

Start by reversing the question. Instead of asking the citizen for loose data, present what you already think you know — "this is what we have recorded; is it still correct?" — and let them confirm or correct it. That lowers the threshold and yields cleaner data than a blank form. Ask at the right moment, keep it short, and make clear what you do with the input.

Combine input with what you already have: citizen input enriches the model-based valuation, it does not replace it. A photo or a confirmation of the maintenance state fills exactly the KOUDVL gap a model cannot see. And give feedback — someone who notices that their input leads to something will take part again next time.

Safeguard both quality and trust

Input is only valuable if you can build on it. That requires verification: sampling, a trail of who supplied what and when, and healthy scepticism towards input that comes out too conveniently. At the same time the GDPR rules apply — purpose limitation, asking only what you need, and being clear about retention periods.

The greatest return, however, lies in trust. A citizen who sees that you handle their input carefully, are transparent about its use and take them seriously becomes a partner rather than an objector. That turns the relationship from gatekeeper-and-applicant into government-and-partner — precisely the shift the Environment Act set in motion.

How to take the first step

You do not have to build this out fully in one go. Pick one data point or one neighbourhood, set up a simple "check your data" flow, measure what it yields in quality and response, and scale from there. It is exactly at that intersection of data quality, citizen interaction and the WOZ domain that we work as DWDA.

Want to know where your organisation stands? Take our free maturity scan, or use our entry-level vouchers to run a first exploration at a fixed price. Feel free to get in touch — and together we will look at how you turn the citizen from objector into data source.