What is already running in production.

An urban platform grows by accumulation: every municipal department asks for its module and every regulation adds a requirement. The challenge was not building an application, it was taking charge of a living product that cannot stop.

On its core we built the test base every change goes in with today, made sure the data arrives complete from end to end, brought the background work inside the platform and left onboarding a new council down to configuration.

A citizen report starts the moment someone sees a street light out. The conversational channel takes that message and turns it into a report a council technician can act on: with the place checked, with the photograph inside it and with no questions that do not apply.

The flow adapts to each type of report and asks only what applies, validates the location and takes in the photograph; after that, the council's comments on the case and its announcements are read and answered in the same thread.

A dashboard is worth what the figure it shows is worth. When the dashboard and the platform do not give the same number for the same status, the conversation is spent working out which of the two is right, and the dashboard stops being opened.

On the dashboards that measure the reports of Mejora tu Ciudad we extended the breakdowns to the detail each team was asking for, matched the figure against the platform service by service, strengthened the daily load and put in writing the path for more people on the team to build their own.

Behind every online procedure, every municipal map and every appointment there is a layer nobody sees: the servers the platform runs on, the databases where the data lives and the access each team comes in through. Holding it up means keeping it available while it changes completely inside.

On that layer we built the environments, automated the daily backup off the servers that produce it, set up the monitoring that opens the follow-up task by itself and ran the migrations —the internal messaging, the databases, the search engine— with the service running.

Renewing a web client someone is using at that very moment asks for a different discipline: every change is tested against an open screen with data inside it, not against an empty environment. What changed was the base it is built on, with the app in use the whole time.

We took the engine that draws the reporting map to a new version, organised the component system the views are built with so that the same piece serves several, and left in one place the rules every form is checked against.

The app worked and was already rolled out, which is exactly what makes it hard to touch: any interruption reached clinicians who were reading a health record in the middle of seeing a patient.

Both native clients were modernised with the app in production the whole time, and on that base complete modules went in without rewriting what already worked. In a health record a half-finished entry is wrong clinical data, so the validations live in the architecture and not screen by screen.