SYNQ
Discuss your project

Civic Wallet

05 / 2026 · Civic Service Wallet

A personal service wallet for requests, evidence, documents, appointments, and simulated fees in one connected interface.

Role
Product design and frontend
Focus
Citizen services, application processes, and evidence
Status
Implemented client system · anonymized
Read case study

Municipal Services

Municipal citizen service

Challenge

Applications, evidence, appointments, and fees were spread across separate administrative systems. Citizens had to infer status and next steps from different messages.

Implementation

Civic Wallet brings personal cases into one secure overview. Documents, deadlines, payments, and messages are assigned directly to the relevant request.

System view

The project view shows a case-specific path for next steps, evidence, simulated fees, and communication.

Civic Wallet — Case study

Editorial case narrative

A visual account of the work, built only from confirmed scope and behavior visible in the project material.

  1. Context Municipal Services
  2. System Citizen services, application processes, and evidence
  3. Evidence Working view
Civic WalletCivic Service Wallet · 2026
Role
Product design and frontend
Focus
Citizen services, application processes, and evidence
Status
Implemented client system · anonymized

Overview

A personal service wallet for requests, evidence, documents, appointments, and simulated fees in one connected interface.

Challenge

Applications, evidence, appointments, and fees were spread across separate administrative systems. Citizens had to infer status and next steps from different messages.

Implementation

Civic Wallet brings personal cases into one secure overview. Documents, deadlines, payments, and messages are assigned directly to the relevant request.

Explore the complete case8 documented fields

01 · Context

Municipal citizen service. A personal service wallet for requests, evidence, documents, appointments, and simulated fees in one connected interface.

Reconstructed from the visible product and recorded scope. It does not add undisclosed client facts or measured outcomes.

02 · Starting point

Applications, evidence, appointments, and fees were spread across separate administrative systems. Citizens had to infer status and next steps from different messages.

Application status, required evidence, documents, and fees needed to be understandable in one place for citizens.

03 · People and responsibility

Residents manage requests and evidence, service staff review the same state, and appointment teams coordinate the next step.

  • Role: Product design and frontend
  • Focus: Citizen services, application processes, and evidence
  • Status: Implemented client system · anonymized

04 · Workflow

A resident identifies an open action, handles evidence, checks appointment and fee state, and follows the request into messages and final documents.

The route connects overview, decision, and detail so that state changes and handoffs remain traceable.

05 · Product decisions

Civic Wallet brings personal cases into one secure overview. Documents, deadlines, payments, and messages are assigned directly to the relevant request.

  • Organise around requests and next actions.
  • Explain evidence status beside the request.
  • Keep documents, appointments, messages, and simulated fees on one timeline.

06 · System and safeguards

The system logic centres on Citizen services, application processes, and evidence. Critical states remain visible at the point of work.

  • Browser-local changes are not production transactions.
  • Fees remain simulated.
  • Every action links back to request and evidence.

07 · Validation

Review checks the path to the next step, missing evidence, document history, appointment state, fee language, navigation, and mobile readability.

The interactive project view provides an inspectable state for the interface, navigation, and visible rules.

08 · Result and handover

Eight connected work areas with browser-local state, clear next steps, traceable documents, and fully interactive service flows.

The project view shows a case-specific path for next steps, evidence, simulated fees, and communication.

The case excludes real resident data, payment processing, adoption, and authority performance claims.

Customer identity, production integrations, adoption figures, and measured outcomes remain omitted where public evidence is not available.

01 / Challenge

Application status, required evidence, documents, and fees needed to be understandable in one place for citizens.

02 / System view

Eight connected work areas with browser-local state, clear next steps, traceable documents, and fully interactive service flows.

More projects

Continue to another project detail.

Project view

Project