City traffic-calming programs (Portland's PBOT Neighborhood Greenways, Salem's Neighborhood Traffic Calming Program, Eugene's Vision Zero, Beaverton's Residential Traffic Calming) all share similar device requirements. The hump must meet ITE Traffic Calming Manual Chapter 3 standards, must be approved by the city traffic engineer, must include MUTCD-compliant signage and pavement marking, and must fit within the city's standard-detail set. Five speed hump products consistently meet program requirements across Oregon cities.
Selection criteria
Five program-driven factors:
- ITE compliance. Profile, length, height per Chapter 3.
- MUTCD signage compatibility. Standard W17-1 advance warning works with all listed devices.
- City standard-detail match. Each city publishes a standard-detail drawing; product must match.
- Cost-share-program eligibility. Many cities require certain device types for cost-share funding.
- Long-term maintenance compatibility. Asphalt humps integrate with city pavement management cycles.
1. Asphalt Watts profile, 12 ft (program default)
Every Oregon city traffic-calming program we have worked with accepts the 12-foot Watts profile as the default residential device. ITE's Chapter 3 references it as the U.S. residential standard, and city standard details typically reproduce its parabolic geometry directly.
Program fit: Portland PBOT, Salem PW, Eugene PW, Beaverton ER, Hillsboro DC, Gresham PW. Cost share fit: Eligible for cost-share matching in Portland (50%), Beaverton (33%), and Eugene (varies).
2. Asphalt sinusoidal, 14 ft (greenway-friendly)
Cities with strong cycling networks (Portland's bike-greenway system, Eugene's neighborhood greenways) frequently spec the sinusoidal profile on streets that double as designated bike routes. The Federal Highway Administration's Traffic Calming ePrimer documents reduced cyclist discomfort with this profile (FHWA ePrimer).
Program fit: Portland (greenway streets), Eugene (4J greenway corridors), Corvallis. Cost share fit: Same as Watts.
3. Asphalt flat-top (speed table), 22 ft (transit-eligible)
Streets that carry transit buses (TriMet, Lane Transit, Cherriots, Sandy Area Metro) typically require speed tables instead of humps. Cities that operate transit on residential streets default to the 22-foot flat-top profile to maintain bus speeds at 20 mph.
Program fit: All cities with transit on residential streets. Cost share fit: Often eligible for transit-agency cost-share supplements.
4. Modular rubber, 12 ft (pilot programs)
Cities running 6-month traffic-calming pilots use modular rubber humps to test geometry before committing to permanent asphalt. Bend, Portland (some neighborhoods), and Eugene have all run pilot programs with rubber humps.
Program fit: Pilot-program use across most Oregon cities. Cost share fit: Limited; typically a city-funded pilot rather than cost-share.
5. Asphalt sinusoidal asymmetric, 14 ft (one-way street programs)
For one-way street segments inside larger calming projects, the asymmetric profile (steeper trailing edge) discourages re-acceleration. Used selectively in Portland's Northwest District and Eugene's Whiteaker neighborhood.
Program fit: Cities with one-way street networks where calming is part of a broader plan. Cost share fit: Same as standard sinusoidal.
How to pick between them for a program submission
Three steps:
- Get the city's standard detail. Most Oregon cities publish standard details for residential traffic-calming devices. The product spec must match the standard. Portland publishes via PBOT; Salem via PW; Eugene via EPP.
- Confirm transit and fire status with the city traffic engineer. This decides whether tables or cushions are required versus humps.
- Confirm cost-share eligibility. Cities that offer cost-share programs (Portland, Beaverton) restrict eligible devices. Verify before submission.
In a 2025 program submission to the City of Beaverton for a Cedar Hills neighborhood greenway, our crew submitted a 14-foot sinusoidal profile because the street is on the city's designated cycling network. The standard-detail match plus the cost-share eligibility cleared review in 30 days versus the typical 60.
What it costs
Industry Baseline Range
| Profile | Installed Cost | Cost-Share-Eligible Cities |
|---|---|---|
| Asphalt Watts, 12 ft | $1,500 to $4,500 | Portland, Beaverton, Eugene |
| Asphalt sinusoidal, 14 ft | $1,800 to $5,500 | Portland, Eugene, Corvallis |
| Asphalt flat-top, 22 ft | $5,000 to $15,000 | Portland, Salem, Eugene |
| Modular rubber, 12 ft | $2,000 to $4,500 | Pilot programs only |
| Asphalt sinusoidal asymmetric, 14 ft | $1,800 to $5,000 | Portland, Eugene |
Current market reality
Program-funded installs in 2026 face budget pressure from rising hot-mix costs (roughly 18% increase over 2024 to 2025). Cities with annual traffic-calming budgets are funding fewer streets per year at the same dollar amount. Cost-share programs have generally held the percentage match constant but the city contribution caps have become more frequently exceeded. For the program request process, see how to request a speed hump.
How program eligibility works
Each Oregon city traffic-calming program has its own eligibility criteria. Common thresholds:
- Speed. 85th-percentile speed exceeds posted speed by 5+ mph (most programs) or 8+ mph (some Portland thresholds).
- Volume. Daily traffic between 500 and 3,000 vehicles per day. Below 500 is too light to justify; above 3,000 may require a different device class (medians, chicanes).
- Petition. Signed by 60 to 75% of affected residents (varies by city).
- Crash history. Some programs prioritize streets with documented crash records.
Frequently asked questions
Which speed hump is approved by the City of Portland? Portland's PBOT standard accepts the 12-foot Watts profile, the 14-foot sinusoidal profile (on greenways), and the 22-foot speed table (on bus routes). Standard details are published on the PBOT website.
Can I use a rubber speed hump in a city traffic-calming program? Usually only as part of a city-funded pilot, not as a permanent program install. Permanent program installs default to asphalt for lifecycle and pavement-management reasons.
Is there cost-share funding for residential speed humps? Yes, in several Oregon cities. Portland's PBOT cost-share program covers up to 50% of project cost; Beaverton offers a similar program at lower percentages. Confirm with the city traffic engineer.
How long does program approval take? 60 to 120 days typical from petition submission to project programming, plus 30 to 90 days for design and procurement, plus install scheduling. Total: 6 to 12 months in most cities.
Can I install a hump faster outside the program? Only on private property (HOA streets, private driveways). On public streets, the city traffic-calming program is the only path.
Submit a Program-Compliant Project
Cojo installs speed humps that meet Oregon city traffic-calming program standards across Portland, Salem, Eugene, and the I-5 corridor. Contact Cojo for a quote, or see how to request a speed hump for the program process.