Have a say in policy WCAG 2.1 AA Feedback

Custom resident participation platform

A resident participation platform is the place where residents have a say in policy and plans: completing a survey, responding to a proposal, submitting an initiative or helping decide on a neighbourhood budget. Appfront builds such platforms to order for municipalities, provinces, water boards and partnerships. The hardest choice is rarely the technology, but the question of what is still open for each project.

What this page is about, and what it is not

In Dutch, the word "participatie" has two unrelated meanings. In the social domain it refers to the Participatiewet (Participation Act): work, income and reintegration. This page is not about that. It is about involving residents in decisions made by their government: contributing ideas on a redesign, responding to a draft environmental plan, voting on a neighbourhood budget.

Three things get mixed up digitally. A citizen portal deals with matters that concern the resident personally: submitting an application, tracking its status. Public space reports deal with something that is broken or unsafe, such as a faulty streetlight. A participation platform deals with the question that comes before that: should that streetlight be there at all, and where.

A report has a clearly defined outcome. Participation produces input that someone has to weigh up, and part of which will not be adopted. Push that into a case management system and you get processes that are administratively correct while participants never hear anything back.

An explicit framework for each process

What the question is, what has already been decided, who decides and when. Visible where people respond.

Input in multiple forms

A survey, a response to part of a plan, a point on the map or a vote on a budget.

The decision linked back to the input

The answer appears next to the response it relates to, including when it is a rejection.

The biggest risk is not in the software

Participation processes rarely fail because of technology. They fail because it was not clear beforehand what residents could actually influence. A municipality starts a process on a redesign, two hundred people contribute, and only at the council meeting does it emerge that the road layout was already fixed in an earlier mobility plan. The input was effectively about the benches. What you gather then is not support but distrust.

The most important design choice is therefore not a software choice but a governance one: what is still open, and what has already been decided. The participation ladder, from informing through consulting and advising to co-producing and co-deciding, is the usual tool for this. The problem is not that the ladder is unknown, but that the rung is often not set in advance and rarely communicated to participants. Software can enforce this by making the scope for policy influence a mandatory field, visible where people respond: which question is on the table, what has already been decided, who decides and when.

Feedback is the thing most often missing and it weighs the most. People who respond and never hear anything again will not take part a second time. A news item on the municipal website is not feedback; showing the decision with its reasoning next to the input it relates to is. The participation policy described by IPLO explicitly asks public bodies to state how participation results influence the decision.

That leaves the question of what the outcome is worth. Those who respond are rarely a cross-section: taking part requires time, language skills and the ability to read an abstract plan, and people with a direct interest come forward more readily. Alongside accessibility, the IPLO framework also mentions representativeness and underrepresented groups. Record for each process who took part and from which areas, and never present an outcome as "the neighbourhood thinks".

Four types of process, four different problems

A participation platform is not a single product but a collection of process formats that have little in common.

Polls and surveys

Technically the simplest, but substantively the most dangerous. The way the question is framed determines the outcome: three pre-packaged options suggest there are only three options. Open fields produce richer input, but someone has to read and code them. Without verification, an organised group can tip a poll in an afternoon; with verification, some people drop out.

Plans with a consultation period

The core is not the form but the integration: a response should be tied to the item it concerns, whether an article, a drawing or a location on the map. The real work comes afterwards, in the response report, and that should come out of the same system.

Resident initiatives

A resident submits a plan of their own, from a façade garden to managing a play area. The bottleneck is never the form but the handling route: who assesses it, against which criteria, within what timeframe, and what happens on rejection. Initiatives usually stall because nobody internally owns them. Now that the Right to Challenge is enshrined in law, that route must be traceable.

Participatory budgeting

Voting is the easy part; the phase before it determines whether the process succeeds. Proposals must be tested for feasibility, land ownership and maintenance costs after completion. A winning proposal that proves unfeasible does more harm than having no budget process at all. The voting method also steers the outcome: one vote, multiple votes, or allocating until the money runs out.

How a process should run through the system

1
Define the framework

The question, fixed constraints, the influence on offer, the competent body and the decision date. Without these fields, no publication.

2
Gather input

Digital input and input entered manually from meetings flow into the same stream.

3
Weigh and account for it

Cluster input into points, record a position and rationale for each point, and build the response report from them.

4
Report back and close

Publish the decision alongside the input it concerns and visibly close the process.

What the law does and does not require of you

For an environmental permit application, participation is not mandatory. The applicant must, however, state whether they have carried out participation and, if so, how and with what result; refusing a permit solely because participation is missing is not allowed. The exception: the municipal council can designate out-of-plan environmental plan activities for which participation is mandatory when the municipal executive is the competent authority. The form is free, although a single letter to the neighbours is insufficient according to IPLO. For the environmental vision and programme there is a duty to give reasons; for the environmental plan and project decision, a prior notification is added.

More broadly, the Act strengthening participation at local level applies, which came into force on 17 December 2024. It broadens the public consultation bylaw into a participation bylaw: participation also covers the implementation and evaluation of policy. The Right to Challenge is also enshrined. The VNG maintains that municipalities have until 1 January 2027 to replace their public consultation bylaw.

First adopt the bylaw and then set up the system, because the bylaw determines which process types, deadlines and roles you need. None of these rules requires a digital platform, but they do require you to show what happened to the input. A process that comes out of the system as an exportable file carries that justification.

Not sure about a large project yet?

Test your idea first: a working prototype in 1 day

With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.

View OneDayBuild →

Accessibility, privacy and technology

For public bodies, digital accessibility is not an ambition but an obligation. The Digital Accessibility Decree for government bodies, part of the Digital Government Act since July 2023, designates the EN 301 549 standard. It refers to WCAG 2.1 level A and AA, fifty success criteria in total, and also applies to apps. For each website you publish an accessibility statement, updated annually and based on research that is valid for three years.

The difficult parts are in predictable places. A map on which you can only place a point with the mouse cannot be operated with the keyboard; there should be a route via address or street name. Technology is also only half of it: a plan written in legal jargon excludes people just as effectively.

Responses from residents count as personal data, even without a name, because a comment about the trees behind someone's own home can usually be traced back to a single household. Public bodies generally base this kind of processing on their public task; consent is a difficult legal basis here, because it has to be freely given. Publishing is a separate consideration: it makes it possible to verify how input was handled, but it stays findable for years. See the Dutch Data Protection Authority.

  • WCAG 2.1 level AA and the EN 301 549 standard
  • Map and voting usable without a mouse
  • Legal basis and retention period per project type
  • Project exportable as a case file

When a standard platform is the better choice

For many readers, a custom build is not the right answer, and we would rather say so. The market has mature products: Go Vocal, formerly CitizenLab, and the open source platforms Decidim and Consul Democracy, with users such as Barcelona and Madrid. They offer surveys, idea collection, comments on a map, voting and participatory budgeting.

If you run a handful of projects a year without any special integrations, the limiting factor is almost never the software. It lies in the capacity to weigh input and report back, and in the willingness to say what is still open. A platform of your own solves neither; it adds something you are then responsible for.

A custom build becomes defensible once your situation differs structurally: when participation has to be tied into your decision-making route, the council information system or the planning cycle of the environmental plan; when a partnership has to serve several organisations from a single environment; or when you have requirements for accessibility, data storage or archiving that you would otherwise have to wait for on a supplier's roadmap. There is also a middle route: building only the part that differs yourself, alongside a standard platform.

Frequently asked questions

The questions we get asked most often about this.

No. The Participation Act (Participatiewet) is about work, income and reintegration in the social domain. This page is about involving residents in policy and plans: contributing ideas on a redesign, responding within a consultation period, submitting an initiative or helping decide on a budget. If you are looking for software for the Participation Act, you are not in the right place.

By making the framework of a project a mandatory field rather than a sentence in the introduction. Before a project opens, it is fixed what the question is, what has already been decided or is laid down by law, who decides and when. A project only closes once the decision, with its reasoning, is visible alongside the input it relates to, including what was not adopted.

No, the Environment Act (Omgevingswet) prescribes neither a channel nor a form. When applying for an environmental permit, the applicant must state whether they have carried out participation and, if so, how and with what result; refusing a permit solely because participation is missing is not allowed. The municipal council can, however, designate off-plan environmental plan activities for which participation is mandatory if the municipal executive is the competent authority. Duties to give reasons apply to the core instruments.

For a considerable share of organisations, that is the better choice. Go Vocal, formerly CitizenLab, and the open source platforms Decidim and Consul Democracy offer surveys, idea collection, comments on a map, voting and participatory budgeting. If you run a handful of projects a year, the limiting factor is the capacity to process input and report back, not the software.

Your organisation should own the source code and the data, in a repository you can access yourself, with documentation that allows another party to take it over. Agree this before the build starts. With an off-the-shelf package, accessibility testing and security maintenance partly sit with the supplier; with a platform you build yourself, they become your responsibility.

That is a judgement call, not something to do automatically. Publishing responses makes it possible to check how input was handled, but responses are personal data, even without a name attached. Decide per project what will be made public, use pre-moderation and a fixed retention period, and communicate this before anyone responds.

Related services

Building a citizen portal

For matters that concern residents personally: submitting applications and tracking their status after logging in with DigiD. About handling cases, rather than weighing input and accounting for it.

Public space reports

For anything that is broken, dirty or unsafe. A report goes to a work crew and has a clear end point.

Considering a participation platform?

Tell us which projects you want to run and how much room you can genuinely offer residents. That conversation starts with your bylaw and your capacity to feed input back, and only then turns to software. Sometimes the outcome is that a standard platform is enough.

Edit content