Urban planning
consultation.
Make remote specialists and proposed changes easier to understand in a public room.
The opportunity
Design for the moment that matters.
What breaks today
Public meetings combine technical information, strong opinions and limited time. Remote presenters are hard to hear and visual material becomes detached from discussion.
The presence pattern
A planner appears beside the relevant model or map, explains bounded decisions and participates in a moderated, recorded question process.
Design requirements
Make it useful before making it magical.
- 01
Design from the viewpoint
Specify scale, sight line, circulation, ambient light and acoustic behavior from the places people will actually stand.
- 02
Belong to the architecture
Treat frame, finish, service access and idle state as part of the built environment.
- 03
Plan operations early
Define ownership, content changes, accessibility, privacy and maintenance before opening day.
Operator runbook
Design the complete service—not only the scene.
- 01
Frame the service
Planning agencies and community-design teams should document the intended audience, room, session length, approved content or knowledge, human escalation path and the current baseline for plan comprehension.
- 02
Invite with clarity
Before the urban planning consultation experience begins, explain why the presence is there, whether it is live, recorded or AI-assisted, what it can do and how a participant can leave or reach a person.
- 03
Operate the moment
A planner appears beside the relevant model or map, explains bounded decisions and participates in a moderated, recorded question process. The operator should be able to observe state, recover the session and protect the physical activity already happening in the room.
- 04
Close the loop
End with a visible next step, capture only consented information and record plan comprehension, questions resolved, participation breadth. Review failures and handoffs before repeating or expanding the experience.
Pilot scorecard
Prove a real outcome in the room.
Plan comprehension
Define the starting event, completion event and current-workflow baseline for plan comprehension. Count only observable outcomes.
Questions resolved
Review questions resolved by audience, session stage and operator. Use the pattern to find where confidence is gained or lost.
Participation breadth
Set a minimum threshold for participation breadth before launch. Name the owner and recovery action when a session misses it.
Decision gates
Know when presence is—and is not—the answer.
Presence must earn the room
If the same urban planning consultation outcome can be achieved by a well-designed phone, kiosk or conventional video call with equal trust and clarity, use the simpler tool.
The boundary must stay visible
Do not launch urban planning consultation until participants can identify the role, source, live or synthetic state, information boundary and human fallback without guessing.
The operation must survive novelty
Planning agencies and community-design teams should be able to run, pause, recover and measure the experience repeatedly. Do not scale while success depends on a founder or engineer standing beside it.
Evidence status. This page is a product-design field brief, not a claim that Reality Relay has already produced the stated customer outcome. Replace the hypothesis with measured pilot evidence before presenting it as proof.
Build the first pilot
Start narrow enough to learn.
For Urban planning consultation, begin with one real environment, one defined audience and one repeatable interaction. Establish who operates the experience, what information or tools it can access and exactly when a person must take control.
Reality Relay Platform coordinates content, session state, approved intelligence and operations. Reality Relay Spaces give the experience a calibrated physical endpoint with intentional scale, eye line, sound and grounding. The pilot should earn expansion by improving the scorecard above—not by novelty alone.
- Primary audience
- Planning agencies and community-design teams
- Experience family
- Built environment & public space
- First decision
- Choose the room, baseline and accountable operator
- Expansion rule
- Scale only after the scorecard beats the current workflow