Citizen Portal
Sign In

Get Full Government Meeting Transcripts, Videos, & Alerts Forever!

Get email alerts on the Economic Development topic

No spam. Unsubscribe anytime.

Draft food‑cart pod rules aim to spur downtown activation while setting design and utility standards

Tualatin Planning Commission · August 3, 2026
AI-Generated Content: All content on this page was generated by AI to highlight key points from the meeting. For complete details and context, we recommend watching the full video. so we can fix them.

Summary

Staff presented a draft code framework to allow food‑cart pods in commercial zones, proposing a definition (pod = two or more carts), permitting tiers by size, design standards (setbacks, screening, paved pedestrian areas) and utility requirements including restrooms and grease interceptors.

Senior planner Erin Ingram introduced draft code amendments to enable multi‑vendor food‑cart pods in several commercial zones, saying pods can activate underutilized sites and support small businesses. Under the draft, a "food‑cart pod" is defined as a site containing two or more carts; staff proposed a three‑tier review process (Type 1–Type 3) where large pods (20+ carts) would require conditional‑use review.

Ingram said the proposal includes required amenities — covered seating, restrooms, and connections for sewer/water/electricity — to help a pod function as a destination. "The purpose of this project is to develop clear, predictable standards that can support economic opportunity while also ensuring compatibility with surrounding development," Ingram said. The draft also proposes a 20‑foot setback and screening where a pod abuts residential zones, paved pedestrian paths and shared waste/recycling facilities.

Commissioners and stakeholders questioned thresholds and costs. Staff said stakeholders recommended larger pods (8–12 or more) to pencil infrastructure investments like restrooms and grease interceptors; staff favored a flexible default definition (2+ carts) so developers can size projects while triggering stricter review for larger proposals. Staff will return with code language refinements and examples.