Client
A partner of municipalities in Germany, providing street-cleaning and public-space maintenance services.
Delivered Scope
Engagement
Chudovo built the system from scratch.
Outcome
The client gained a working tool to monitor and manage the quality of street-cleaning services across public spaces.
Evidence-Based Municipal Planning
Chudovo ties every inspection and report to a location, a timestamp, and photo evidence, giving departments a verifiable record behind each decision.
Configurable Inspection Standards
Municipal administrators configure checklists, scoring criteria, and asset categories to match how their department already works.
Accessibility by Design
Citizen-facing interfaces are built to be usable by residents with disabilities and residents with limited digital experience.
Privacy and Data Protection by Design
A citizen's photo of a pothole can also catch a license plate or a face in the background. Chudovo designs the reporting flow so what a resident submits publicly isn't automatically what a department stores internally, and limits how long location and photo data stay on file once an issue closes.
Four actors drive this workflow: the citizen or inspector who reports an issue, the system that validates and routes it, the responsible department or field team that resolves it, and the inspector or supervisor who verifies the result.
The confirmed parts of this workflow are map-based object selection, condition assessment, and photo evidence. The table below uses routing, SLAs, and department hand-off to illustrate a target workflow; the delivered case did not confirm these specific functions.
| Step | Inspector Path | Citizen Path |
| 1 | Selects an assigned object on the map | Selects an issue category |
| 2 | Assesses condition against a checklist or scale | Sets location on the map or allows geolocation |
| 3 | Attaches photos, measurements, and comments | Adds a description and a photo |
| 4 | Submits the inspection | Submits the report |
| 5 | System creates a task for the responsible team | System routes the report to the responsible department |
| 6 | The field team completes the task, and an inspector or supervisor verifies the result | The system notifies the resident after the responsible team closes the issue |
Map-based object selection and geolocation have been shown in the Street Cleaning Software example. Chudovo takes this further to include a complete link between assets and their histories:
municipality → zone → asset → inspection template → inspection → evidence → issue → work order → verification → history
Each asset is uniquely defined in terms of its ID, category, and location. All reports or inspections of that asset build up one history for that asset, which helps departments know about any repeated problems, previous inspections, and current status all at once, rather than having to search different systems.
This shows a typical path from pilot to full rollout, not two fixed product tiers.
| Stage | What’s Typically Included | Status |
| Pilot | One district or asset category, citizen and inspector intake, map, photos, basic statuses | Delivered pattern |
| Operational Rollout | Department routing, configurable inspection templates, permissions, reporting | Common extension |
| Integration | Existing GIS, asset or work-order system, notifications, data migration | Project-specific option |
| Advanced Extension | Offline field work, cross-municipality setup, advanced analytics | Project-specific, scoped only where needed |
| Phase | What Happens | Timeframe |
| Discovery and Assessment | GIS and data discovery, accessibility and security/privacy review, pilot district or asset category selection | 2–4 weeks |
| Pilot | Citizen and inspector intake, map, photos, basic statuses, for one district or asset category | 3–5 months |
| Operational Rollout | Department routing, configurable inspection templates, permissions, reporting, staff training | 5–9 months |
| Integration and Migration | Existing GIS, asset or work-order system, notifications, data migration, acceptance testing | Scoped per project |
Customizable to Work the Way a Municipality Is Built
Chudovo makes checklists, asset types, and scoring based on how a municipality wants to inspect things, instead of making its employees fit their workflow into a fixed process.
Designed to Serve Both Citizens and Inspectors
Most municipal systems make a choice – one either serves citizens or inspectors, but not both. Chudovo unites both sides within one application, with the same map, asset data, and status rules.
All Assets Have Their Whole History Attached to Them
A closed case does not show a municipal department that a streetlight broke down three times in the current year. Chudovo attaches all inspections and citizen reports to their particular asset.
Part of Chudovo's Public Sector & Smart City Practice
Street sweeping and public space inspections have exactly the same data architecture as other municipal applications: an asset managed by location and history of its actions.
