Custom resident participation platform
A resident participation platform is where residents help shape policy and plans: completing a survey, responding to a proposal, submitting an initiative or deciding on a neighbourhood budget. Appfront builds such platforms to measure for municipalities, provinces, water boards and partnerships. The hardest choice is rarely the technology, but the question of what is still open in each process.
What this page covers, and what it does not
In the Netherlands, the word participatie has two separate meanings. In the social domain, it refers to the Participatiewet: work, income and reintegration. This page is not about that. Here, it concerns involving residents in decisions made by their government: giving input on a redevelopment, responding to a draft environmental plan, or voting on a neighbourhood budget.
Three things are often confused digitally. A citizen portal covers matters that personally concern the resident: submitting an application, tracking its status. Public space reporting covers something broken or unsafe, such as a faulty street lamp. A participation platform covers the question that comes before that: should that street lamp be there at all, and where?
A report has a clearly defined outcome. Participation yields input that someone must weigh, and part of which will not be adopted. Forcing that into a case management system produces processes that are administratively correct, while participants get nothing back.
An explicit framework for each process
What the question is, what is already fixed, who decides and when. Clearly visible where people respond.
Input in multiple forms
A survey, a response to a plan component, a point on a map, or a vote on a budget.
The decision fed back to the input
The answer sits alongside the response it relates to, including when it is a rejection.
The biggest risk isn't in the software
Participation processes rarely fail on technology. They fail because it was never made clear in advance what residents could actually influence. A municipality starts a process on a redesign, two hundred people take part, and only at the council meeting does it emerge that the lane layout was already fixed in an earlier mobility plan. The input was really about the benches. What you collect then is not support but distrust.
The most important design decision is therefore not a software choice but a governance one: what is still open, and what has already been decided. The participation ladder, running 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 recorded in advance and rarely communicated to participants. Software can enforce this by making the scope of influence a mandatory field, visible wherever people respond: which question is on the table, what is already fixed, who decides and when.
Feedback is the most often missing and carries the most weight. Anyone who responds and never hears 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 alongside the input it relates to is. The participation policy described by IPLO explicitly asks administrative bodies to state how participation results affect the decision.
The question remains what the outcome is worth. Those who respond are seldom a cross-section: taking part requires time, language skills and the ability to read an abstract plan, and people with a direct stake are quicker to speak up. Alongside accessibility, the IPLO framework names 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 processes, four different problems
A participation platform is not a single product but a collection of process types that have little in common.
Polls and surveys
Technically the simplest, substantively the most hazardous. The wording of the question determines the outcome: three pre-cooked options imply there are only three options. Open fields yield richer input, but someone has to read and code it. Without verification, an organised group can tip a poll in an afternoon; with verification, some participants drop out.
Plans with a response deadline
The core is not the form but the link: a response should be tied to the part it concerns, an article, a drawing or a location on the map. The real work comes afterwards, in the response report, and that should come from the same system.
Resident initiatives
A resident submits a proposal themselves, from a façade garden to the management of a play area. The bottleneck is never the form but the handling route: who assesses, 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 embedded in law, that route must be traceable.
Participatory budgeting
Voting is the easy part; the stage before it determines success. Proposals must be tested for feasibility, land ownership and post-completion maintenance costs. A winning proposal that proves unworkable does more harm than no budgeting process at all. The voting method also shapes the outcome: one vote, multiple votes, or allocating until the money runs out.
How a process should run through the system
Question, existing constraints, level of influence offered, competent body and decision date. Without these fields, nothing is published.
Digital input and input recorded manually from meetings flow into the same stream.
Cluster input into points, record the position and reasoning for each point, and build the response report from these.
Publish the decision alongside the input it relates to, and formally close the process so it is visibly complete.
What the law does and does not require of you
For an application for an environmental permit, participation is not mandatory. The applicant must state whether they have carried out participation and, if so, how and with what result; refusing solely because participation is lacking is not permitted. Exception: the municipal council may designate extra-plan environmental plan activities for which participation is mandatory where the executive board is the competent authority. The form is free, although a single letter to the neighbours is, according to IPLO, insufficient. 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.
Breder work the Wet versterking participatie (Strengthening Participation Act) at local level, which came into effect on 17 December 2024. It broadens the public consultation ordinance into a participation ordinance: participation now also covers the implementation and evaluation of policy. The right to challenge is also now anchored in law. The VNG maintains that municipalities have until 1 January 2027 to replace their public consultation ordinance.
First adopt the ordinance, then set up the system, as it determines which process types, timeframes and roles you need. None of these rules requires a digital platform, but they do require you to show what has happened to the input. A process that can be exported from the system as a dossier carries that reasoning with it.
Test your idea first: a working prototype in 1 day
With OneDayBuild, we turn your idea into something tangible in one day for €1,150, so you can see whether further development is worth the investment. Decide to go ahead with the full build? Then we credit the full cost.
Explore OneDayBuild →Accessibility, privacy and technology
For government bodies, digital accessibility is not an aspiration but an obligation. The Digital Accessibility of Government Decree, part of the Digital Government Act since July 2023, designates the standard EN 301 549. That refers to WCAG 2.1 levels A and AA, comprising fifty success criteria, and also applies to apps. For each website you publish an accessibility statement, updated annually and based on an audit valid for three years.
The difficult elements sit in predictable places. A map where you can only place a point with a mouse cannot be operated by keyboard; there should be a route via address or street name. Technology is, moreover, only half the battle: a plan written in legal jargon excludes people just as effectively.
Comments from residents are personal data, even without a name, because a remark about the trees behind someone's home is usually traceable to one household. Governments generally base such processing on their public task; consent is a difficult basis here, since it must be freely given and withdrawable. Publishing is a separate consideration: it makes it possible to show how input was handled, but it remains 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 too
- Legal basis and retention period per type of process
- Process exportable as a case file
When a standard platform is the better choice
For most readers, custom development 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, used by cities such as Barcelona and Madrid. They offer surveys, idea collection, comments on a map, voting and participatory budgeting.
If you run a handful of consultations 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 then become responsible for.
Custom development becomes justifiable once your situation structurally differs: when participation must be tied to your decision-making route, your council information system or the planning cycle of the environment plan; when a partnership must serve several organisations within one 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 path: build only the deviating part yourself, alongside a standard platform.
Frequently Asked Questions
The questions we are asked most often about this.
No. The Participatiewet concerns work, income and reintegration in the social domain. This page is about involving residents in policy and plans: contributing to a redevelopment, responding within a deadline, submitting an initiative or deciding on a budget together. If you are looking for software for the Participatiewet, this is not the right place.
By making the framework of a process a mandatory field rather than a sentence in the introduction. Before a process opens, it is settled what the question is, what has already been decided or is legally fixed, who decides and when. A process only closes once the decision, with its reasoning, is visible alongside the input it relates to, including what was not adopted.
No, the Environment and Planning Act (Omgevingswet) does not prescribe a channel or a format. 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 lacking is not permitted. The municipal council can, however, designate out-of-plan environmental plan activities for which participation is mandatory where the executive board 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 gathering, comments on a map, voting and participatory budgeting. If you run a handful of consultations a year, the limiting factor is the capacity to process input and report back, not the software.
The source code and data should belong to your organisation, held in a repository you have access to yourself, with documentation that would allow another party to take over. Settle this before the build begins. With a packaged product, accessibility testing and security maintenance rest partly with the vendor; with a platform built in-house, that responsibility falls to you.
That is a judgement call, not an automatic decision. Publishing responses makes it possible to check how input has been handled, but responses are personal data, even without a name attached. Define for each process what becomes public, work with moderation before publication, set a fixed retention period, and communicate this before anyone responds.
Related services
Building a citizen portal
For matters that personally concern the resident: submitting applications and tracking their status after logging in with DigiD. Handling cases, rather than weighing and justifying decisions.
Public space reporting
For anything broken, dirty or unsafe. A report goes to a field crew and has a defined endpoint.
Are you considering a participation platform?
Tell us which consultations you want to run and what room for input you can genuinely offer residents. That conversation starts with your ordinance and your capacity to report back on input, and only then with software. Sometimes the outcome is that a standard platform will do.