Lost property in Monza: from information to a clear next step
A real municipal service examined through content, contacts and hierarchy: an independent before-and-after concept informed by the .italia design system.
Published · 17 September 2026Updated · 7 September 2026
00 · Premise
A clearer service does not always need another form.
Imagine losing a bag or finding a bicycle: before understanding the council’s organisation, you want to know whom to contact. I examined Monza’s public lost-property page on 7 September 2026 without submitting a request. The scope is the initial information lookup, not the complete return procedure. This is not commissioned work for the municipality and uses no service analytics.
UX Clinic · Real external case
Two recognisable intentions, one shared point of contact.
The original captures the main content reached through the page’s skip link. The proposal is an unofficial static concept, at the same 1280 × 720 desktop size, without simulated outcomes or digital services. Open either image for detail; the proposed interface remains in Italian for its intended local audience.
Before · original website
After · independent proposal
Preserve what already works
The original page is short and provides email, an address, opening hours and telephone references. Contact information is not hidden behind authentication, which is worth preserving. My hypothesis therefore concerns interpretation rather than content volume: the title is repeated and similar details appear in two blocks, without explicit guidance for the two starting situations.
Practical actions
- Keep direct access and readable contact details.
- Place the person’s need before administrative metadata.
- Do not turn a simple lookup into account registration.
Clarify the contact source before refining the layout
The captured content lists both 039.2816313 and 039.2816.303. This comparison alone cannot establish whether both are valid or whether the content is inconsistent. The organisational office page provides another reference to check with service staff. The concept does not arbitrarily choose a number: it groups the email into a recognisable contact panel and links to the office page for contact information. Before a real launch, the discrepancy would need resolving rather than merely moving it to another page.
Practical actions
- Confirm contact details and update ownership with the office.
- Use a shared source for repeated information.
- Separate content verification from interface revision.
Separate intentions without inventing procedures
The proposal distinguishes losing an item from finding one. Both lead to the office because the reviewed sources do not support designing a complete digital application. The person’s question changes, not the available channel. I do not introduce appointments, an item catalogue, guaranteed response times or undocumented collection requirements. The copy also states that the page does not submit an online report: a more visible action must not promise more than the service can deliver.
Practical actions
- Name concrete situations in the headings.
- Explain what happens after the click.
- Confirm documents and procedures before describing them.
Use .italia as a reference, then test the hypothesis
The .italia reference concerns content order, language and recognisable interface elements, not certification of the mockup. Implementation would require appropriate components, accessibility checks and collaboration with service staff. I would test two tasks: finding whom to email after losing something and understanding what to do after finding an item. The comparison should examine next-step comprehension, hesitation and channel expectations. The two cards might also feel repetitive: if they do not help, one contact action with concise instructions would be preferable.
Practical actions
- Test both intentions with residents and staff.
- Check keyboard use, focus, contrast and mobile reading.
- Measure comprehension without claiming unobserved improvements.
Ready to use
Before launching a similar proposal
- The description matches the service actually available.
- An accountable owner confirms and updates contact details.
- Actions do not promise a nonexistent online application.
- Opening hours and procedures are checked with the office.
- The hierarchy works on mobile and with assistive technology.
- Hypotheses are tested rather than presented as results.
Hypothesis to validate
Service quality starts with a dependable next step.
The proposed change is narrow: more explicit orientation and less fragmented contact information. It does not demonstrate an effectiveness gain. It illustrates why a design system becomes useful alongside verified content, editorial ownership and testing of a real task.