Should Vancouver publish and meet a citywide public-toilet service standard?
An advisory proposal for public targets covering location, hours, accessibility, cleaning, outages and response times.
The problem being tested
Residents, visitors, workers and unhoused people often cannot tell where a usable public toilet is available or how quickly an outage will be fixed. Capital announcements alone do not show whether the service is working.
Proposed action
Publish a baseline inventory and a measurable service standard, identify priority gaps, report uptime and cleaning performance, and present a costed 100-day improvement plan for public review.
- Origin label
- Platform position
- Submitter disclosure
- Campaign platform concept; wording prepared for this independent public beta.
- Responsible jurisdiction
- City of Vancouver (ca-bc-vancouver)
- Rule under test
- 60% of Yes + No responses, plus a 1000-response demo quorum
- Evidence period
- Aug 14, 2026, 11:45 p.m. PDT to Aug 15, 2026, 11:45 p.m. PDT
- Participation window
- Aug 15, 2026, 11:45 p.m. PDT to Aug 26, 2026, 11:45 p.m. PDT
- Participation tier
- Open beta — identity, residence and elector status are not verified
- Eligibility rule
- Self-selected browser participation; no identity, residence or elector verification
- Response update rule
- Last valid confirmed response during the half-open window replaces that browser’s earlier choice without increasing turnout.
- Small-cell publication rule
- Withhold every exact count and result when any nonzero choice group has fewer than 5 responses.
Version provenance
Sources and origin for version 1
- Campaign Platform: Great Scott platform concept — public beta wording
Change summary: Recovered beta proposal recorded as immutable version 1.
Public accountability
Proposal version history
- Version 1 — current · Aug 14, 2026, 11:45 p.m. PDT
Platform position — Recovered beta proposal recorded as immutable version 1. Open exact version
Lifecycle history
- Open For Participation · Aug 14, 2026, 11:45 p.m. PDT
Initial public-beta lifecycle state recorded.
Structured deliberation
Evidence, arguments, challenges and unresolved questions
Evidence
No reviewed contributions yet.
Support
Publishing uptime, accessibility, hours and response targets would shift debate from the number of facilities announced to whether people can actually use them.
Quoted proposition: Publishing uptime, accessibility, hours and response targets would shift debate from the number of facilities announced to whether people can actually use them.
Stored reference retained for restricted human review; no public file is exposed.
Submitter disclosure: Seeded demonstration contribution; no participant identity is verified. This label is not identity or institutional-authority verification.
Oppose
A rigid citywide standard could understate site-specific security, maintenance and staffing constraints and may create an unfunded service commitment.
Quoted proposition: A rigid citywide standard could understate site-specific security, maintenance and staffing constraints and may create an unfunded service commitment.
Stored reference retained for restricted human review; no public file is exposed.
Submitter disclosure: Seeded demonstration contribution; no participant identity is verified. This label is not identity or institutional-authority verification.
Challenges
No reviewed contributions yet.
Unresolved questions
No reviewed contributions yet.
Review layer
Provisional analysis
The proposal is measurable and within conventional municipal service planning, but targets should be costed and adjusted for accessibility, safety, staffing and site constraints.
Potential benefits
- Clear service accountability
- Better public-health access
- Comparable neighbourhood performance
Risks and constraints
- Unfunded targets
- Overly simple uptime measures
- Displacement of maintenance costs
Questions to resolve
- What is the current verified baseline?
- Which accessibility standard applies?
- How are closures and cleaning verified?
Do not treat scores as facts. They are editable design prompts showing how a future source-linked AI/human review might surface trade-offs. They are not a recommendation or automated decision.
Optional AI assistance
Accountable human-reviewed drafts
Only approved outputs are public. Provider drafts remain provisional and restricted until a named human records a final review.
No AI-assisted draft has received accountable human approval for this exact proposal version.
Civitas response record
Attributable review and implementation history
Civitas demonstration: this attributable workflow record remains separate from the advisory participation aggregate and the lawful decision-maker's record.
Case scope
Define the public-toilet baseline, responsible operating bodies, accessibility and service standards, costed options and measurable reporting obligations.
Responsible authority recorded: Authority unverified — possible City and contracted service-provider responsibilities
Response deadline: Sep 15, 2026, 11:45 p.m. PDT
Public response
Demonstration only: staff would confirm the current inventory, operating ownership, accessibility requirements, complaint data, cost baseline and measurable service levels.
Evidence considered
The demonstration considers the exact proposal wording; a verified inventory, uptime record and cost baseline are still required.
No separately linked public evidence item is recorded; consult the evidence summary and exact proposal version.
Legal and policy constraints
Accessibility, public-health, procurement, labour, property, safety and records obligations may constrain service design.
Feasibility and dependencies
A baseline inventory, ownership map, operating data and cost model are not yet recorded.
Facilities, engineering, sanitation operations, contracted providers, accessibility review, capital and operating budgets, and public reporting systems.
Cost range and confidence
No defensible range recorded. No defensible cost range has been prepared for this demonstration.
Rights, privacy and safety
- Rights/equity: Service standards should account for disability, dignity, gender safety, homelessness and equitable geographic access.
- Privacy: Service monitoring should avoid surveillance or identifiable user tracking unless separately justified and approved.
- Safety: Cleaning, sharps, ventilation, accessibility, worker safety and emergency response require operational review.
Position and reasons
The first output should be a verified baseline and options report rather than an unsupported numerical promise.
Accountable approver: Independent Agora demonstration reviewer
Response date: Aug 15, 2026, 11:45 p.m. PDT
Response and correction history (1)
- Response version 1 — Under Review · Aug 15, 2026, 11:45 p.m. PDT
Initial response version.
No implementation plan is recorded for this exact-version case.
Public Civitas audit history (2)
- Case.Created · Aug 15, 2026, 11:45 p.m. PDT
Legacy demonstration case migrated to the exact proposal version. - Response.Published · Aug 15, 2026, 11:45 p.m. PDT
Initial demonstration response recorded for the exact proposal version.