Custom public space reporting software
Appfront builds custom public space reporting software that lets residents easily report issues in the public space — from broken street lighting and litter to a loose paving stone or overhanging greenery. The report is placed on the map, automatically routed to the right department or contractor, handled by the field team and reported back to the person who submitted it. One system for office and field staff, aligned with your own report categories and management process.
What is public space reporting software?
MOR software (software for public space reports) is the application that lets residents report problems in their neighbourhood and lets the municipality receive, locate, route, handle and record those reports. Think of broken street lighting, litter, a loose paving stone, overhanging greenery, a blocked drain or a vandalised bench. The resident marks the report on the map, adds a photo and chooses a category; the software then passes the report to the right department or contractor.
A good MOR application connects three worlds: the portal for residents, the back office that assigns and monitors reports, and the field team that carries out the work on site. Between them, location detection, automatic routing and status feedback make sure a report doesn't get left behind and that residents know what is happening with it. That speeds up handling and builds trust in the municipality.
Off-the-shelf packages often force your workflow into a fixed structure and are awkward to integrate with your asset management or case management system. Custom software is a better fit when your report categories, handling deadlines, maintenance areas or contractor agreements differ, or when you work with several municipalities in a single reporting point. Appfront builds MOR software that follows your actual process and integrates cleanly with existing systems. See also our broader software for municipalities.
Report on the map
The resident drops a pin on the exact spot or uses their phone's location, adds a photo and description, and chooses a category. The software determines the address and the responsible maintenance department.
Automatic routing
Based on category and location, the report goes straight to the right department, neighbourhood team or contractor. You set the routing rules yourself, including maintenance areas, contracts and handling deadlines.
Feedback to the reporter
The resident receives a confirmation of receipt with a report number and can follow progress: received, in progress and completed. This happens automatically via email or a status page, and optionally via a resident portal.
A report about a playground item follows a different path from a report about a paving stone, because an inspection regime sits behind it. We cover that on the page about the equipment inspection app.
Our development process for MOR software
We work with an approach that removes uncertainty early and delivers a stable application. From an initial analysis of your report categories, maintenance departments and integrations through to go-live and ongoing maintenance, every step is aimed at software that your back office and field teams can understand and trust. Have questions while reading? Feel free to contact us.
We map out your report categories, maintenance areas, handling deadlines, departments and contractor agreements, plus the integrations with your asset management and case management systems that are needed.
We design the reporting portal, the map and routing model and the field team flow, with attention to accessibility (WCAG) and a logical, fast reporting form experience.
Implementation with automated tests, structured logging and monitoring. You try out interim builds with real reports, so that routing and feedback are right before go-live.
Controlled go-live with data validation and a safety net, followed by ongoing maintenance, monitoring and further development of categories, routing and integrations.
What MOR software can do in practice
Every MOR application is set up for your report categories, maintenance process and neighbouring systems. Below are the features we deliver most often for municipalities and maintenance organisations that want to receive, route and handle public space reports.
Reporting portal with map
An accessible reporting form for residents with map location, photo upload and category selection. It works on mobile and desktop, and can be offered as a standalone web app or within your municipal website, without the reporter having to log in.
Routing and workload distribution
Rules link category and location to the right department, neighbourhood team or contractor, with automatic assignment and escalation when resolution deadlines are exceeded. The back office keeps a full overview and can adjust manually where needed.
Field service app
A mobile workspace for the field: reports on the map, navigation to the location, a photo on arrival and on completion, and immediate sign-off with a resolution outcome. It also works with an unreliable connection, so records stay complete.
Status feedback
The reporter receives an acknowledgement with a report number and follows the status via a status page or email. On completion, an explanation or photo can be included. Feedback can also run through a citizen portal or MijnOverheid.
Category and SLA management
You manage report categories, subcategories and the associated resolution deadlines yourself. The software monitors deadlines per category (street lighting, after all, has a different deadline from litter) and flags when a report is about to expire.
Dashboards & reporting
Insight into volumes, turnaround times, hotspots on the map and resolution by category and neighbourhood. Useful for steering on liveability and for accountability to the executive board and council, with exports for open data where required.
Who we build public space reporting software for
Reports about public space come in from many places, and the organisations that handle them vary widely in size and set-up. We see a number of variants come up often, each with its own emphasis on categories, routing and integrations.
Municipalities
The reporting point for a municipality's own residents: one accessible portal for all categories, linked to the management departments and the case management system. Often embedded in the municipal website and complemented by a citizen portal where residents can see their reports.
Public space management
Departments for city management, neighbourhood management and green space that direct the work in the field. For them it is about fast routing to the right crew or contractor, a workable field service app and reliable recording of what has been carried out, linked to the asset management system and GIS.
Partnerships
Multiple municipalities or a joint arrangement handling reports through a single shared reporting point. Custom software makes it possible to use separate categories, management areas and contractors for each participant, while the portal remains one recognisable experience for residents.
Contractors and delivery partners
External contractors carrying out maintenance on behalf of the municipality receive only the reports intended for them, via a restricted portal or integration. Sign-off with a result and photo flows back to the municipality, so deadlines and quality remain demonstrably monitored.
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 →Technology and integrations
We build public space reporting software with a modern, maintainable web stack and open standards, so your own team can manage the application or a future supplier can take over the software. The strength lies in the integrations: enriching reports with location and address data and recording them as cases in your existing landscape, without double entry.
If you want to exchange your asset management data according to IMBOR, take a look at our IMBOR integration.
For trees, with inspection cycle, measures and history per tree, there is our software for VTA tree safety registration.
For address and object validation we use a BAG API integration, so a report on the map automatically gets the right address and the right management unit. Handling and archiving run through a ZGW API integration, which records every report as a case in your case management system. If you want reporters to be able to log in to follow their reports, we add a DigiD integration. Also see our custom software and AI for municipalities.
Why Appfront for your MOR software?
Appfront builds custom software for organisations in the Netherlands, with an understanding of the government domain and the standards that apply there. We always start with a thorough analysis of your work process: a reporting point must not only be technically correct, but also add practical value for residents, back-office staff and fieldwork.
On every project we write clear documentation and make sure your own team, or a future supplier, can understand and manage the software. No black box, but transparent code, open standards and clear agreements on monitoring and maintenance, so you are not locked in to a single party.
You work with a single point of contact who understands both the technical and the functional side. That keeps communication short, prevents miscommunication and speeds up decisions when choices need to be made during the build about categories, routing or integrations.
Also take a look at our wider services for the public sector, such as software for municipalities, housing association software and software for water boards.
- Experience with custom software for the government domain
- Familiar with BAG, ZGW (case-based working) and DigiD integrations
- Strong in maps, geolocation and GIS integration
- Attention to both office and field staff in one workable system
- Built to be accessible in line with WCAG 2.1 AA
- Open standards and transparent code, with no vendor lock-in
- Extensive logging and monitoring from day one
- Clear documentation that your team can read and maintain
- A single point of contact, no passing you between account managers
- Ongoing maintenance and proactive further development
Security, privacy and accessibility
A report quickly contains personal data: a location, a photo and sometimes the reporter's contact details. Appfront builds MOR software in line with the GDPR using data minimisation, collecting only what is needed to handle the report, and with clear retention periods, so data is not kept longer than necessary.
The set-up follows the Baseline Informatiebeveiliging Overheid (BIO, the Dutch government information security baseline): role-based access, least privilege, encryption and logging of who did what and when. Because the reporting portal is a digital government service, we build to the WCAG 2.1 AA and DigiToegankelijk accessibility requirements, so that every resident can submit a report.
More about our approach to security: information security policy and CVD policy.
- GDPR-compliant processing and data minimisation
- Clear retention periods for each type of report data
- Set-up in line with BIO (Baseline Informatiebeveiliging Overheid)
- Encryption in transit (TLS 1.2+) and at rest
- Role-based access and least privilege
- Audit logs with traceable data flows
- Accessible in line with WCAG 2.1 AA / DigiToegankelijk
- Documentation for your record of processing activities
Frequently asked questions about MOR software
Answers to the questions we get asked most often about software for public space reports.
MOR stands for meldingen openbare ruimte (public space reports). MOR software is the application that residents use to report issues in the public space, such as broken street lighting, litter, a loose paving stone or overhanging greenery, and that the municipality uses to receive the report, place it on the map, route it to the right department or contractor, resolve it and give feedback to the reporter. Custom MOR software fits your own report categories, resolution times, management departments and existing systems, instead of forcing your working process into an off-the-shelf package.
Every municipality has its own report categories, management departments, contractor agreements and resolution times. An off-the-shelf package often forces you into a fixed structure and integrates poorly with your management system or case management system. Custom MOR software follows your actual process: from report and routing to field-staff resolution and feedback. You stay in control of categories, routing rules and integrations, and the software grows with you as your organisation or partnership changes.
Yes. The core of public space reporting software is location detection: the reporter drops a pin on the map or uses their phone's location, adds a photo and description, and selects a category. The software uses the location to determine the address and the right management department. Through a BAG integration we validate the address and can enrich the report with object data, so a report goes straight to the right department or contractor.
Based on report category and location, the software determines which department, neighbourhood team or contractor is responsible. A report about street lighting follows a different route than litter or a loose paving slab. You set the routing rules yourself, and they can take into account management areas, contracts and handling deadlines. Through a ZGW integration, every report can be recorded as a case in your case management system, so handling and archiving fit in with your existing processes.
Yes. Status feedback is an important part of public space reporting software and has a major influence on how residents experience your services. The reporter receives an acknowledgement with a report number and can follow progress: received, in progress and completed. Feedback can be sent automatically by email or through a status page, and optionally via a citizen portal or MijnOverheid. That way residents know where their report stands without having to call again.
Yes. Alongside the portal for residents and the back office, we provide a working environment for field teams: a mobile view with the report on the map, navigation to the location, a photo on arrival and on completion, and the ability to close a report straight away with a resolution result. This way the back office and field teams work in a single system and the records stay complete, even when working in the field with an unreliable connection.
Yes. We connect public space reporting software to your existing landscape using standards: a BAG integration for address and object validation, a ZGW integration to record reports as cases in your case management system, and, where desired, DigiD login for reporters who want to follow their reports. We also integrate with public space management systems, GIS and contractor portals, so data is never entered twice.
Yes. We build in line with the GDPR, using data minimisation and clear retention periods, and set up the software according to the Baseline Informatiebeveiliging Overheid (BIO, the Dutch government information security baseline). Because the reporting portal is a digital government service, we build to the WCAG 2.1 AA accessibility requirements and the Dutch Digital Accessibility Decree for government (Tijdelijk besluit digitale toegankelijkheid overheid), so every resident can submit a report. Data flows, logging and authorisations are documented for your record of processing activities.
Ready to build your public space reporting software?
Tell us which report categories you handle, how your management departments and contractors are organised, and which systems the software needs to integrate with — we're happy to think along on the map, routing, field teams and feedback. A no-obligation first conversation gives you a clear picture of what's possible for your municipality or partnership.