METROPOLIS

For Municipalities

Use urban twins to make better decisions, improve cross-department work, and communicate planning choices with clarity.

Why Municipal Teams Use This

This platform is built for real planning work: comparing alternatives, documenting assumptions, and improving coordination. It is a decision-support environment, not a promise of automatic planning.

  • Planning decisions often require input from multiple departments with different priorities.
  • Data is spread across systems, making it hard to compare alternatives with confidence.
  • Public communication is difficult when plans are technical and hard to visualize.
  • Teams need faster evaluation cycles without losing traceability and accountability.

Core Value for Municipalities

Better design before construction

Test options in the city context and identify conflicts earlier, before costly commitments.

Example: Spot a shadowing conflict between two massing proposals before going to tender.

Data-based decision support

Combine urban data layers with model outputs so policy and design discussions are evidence-informed.

Shared working space across departments

Planning, transport, environment, and engineering teams can review the same scenarios and assumptions.

Example: Share a scenario with a municipality and gather comments directly on the map.

More transparent communication

Use visual comparisons to explain trade-offs to leadership, partners, and the public.

Better day-to-day urban management

Keep a living digital reference of projects and decisions instead of scattered documents.

Community trust through clarity

Make it easier for residents to understand why a plan was selected and what data informed it.

Municipal Workflow on the Platform

01
Frame the decision

Define the question (density, mobility, heat, or public-space quality) and success criteria.

02
Assemble city context

Load the relevant base data and planning context into the twin workspace.

03
Compare scenarios

Run available models on multiple alternatives and review outcomes side by side.

04
Align stakeholders

Review trade-offs internally and prepare communication material for decision meetings.

05
Publish and track

Share approved scenarios, collect feedback, and keep a clear record of changes over time.

Working with Other Stakeholders

Municipal teams are not working alone. The platform creates a shared space where planners can bring design alternatives, tool creators can contribute analysis models, and residents can explore and comment on the same scenarios your team is evaluating. This reduces the translation cost between departments and the public.

  • Learn from how other cities structure scenario comparisons and governance workflows.
  • Find planning and model partners for specific local challenges.
  • Build trust through shared language between technical teams and the public.

Ready to start?

Start with one concrete municipal decision and run it as a pilot workflow on the platform. Most teams complete their first scenario comparison in a single session.

Further Resources

These articles are planned and will be published as documentation matures.

  • Municipal Onboarding Playbook coming soon
  • Governance and Decision Logging coming soon
  • Public Communication Kit coming soon
Typical pilot timeline
Load city dataDay 1
Define scenariosDay 1–2
Run first toolsDay 2–3
Review with teamDay 4
Share externallyDay 5