Road Diet on a State-Owned Freight Arterial
A city of 85,000 adopted a corridor plan calling for a road diet on a four-lane arterial: two through lanes, a center left-turn lane, and bike lanes. The arterial carries 18,000 vehicles per day with 6% trucks and serves a warehouse district. The state DOT owns the road and applies a level of service D standard at signalized intersections; two intersections currently operate at E in the PM peak. Business owners fear losing delivery access, and the fire chief objects that narrower lanes will not accommodate ladder trucks. The council wants the plan adopted within 90 days.
1. How do you reconcile the DOT's LOS D requirement with the corridor plan's goals?
Read the worked answer
First, get the facts straight: LOS D is typically applied to intersections or segments under a defined methodology, and "operating at E" in the PM peak describes the existing condition, not necessarily the post-project condition. The road diet removes through capacity but adds a center turn lane, which often improves intersection operation by removing left-turn blocking. A competent analysis may show the two critical intersections are not degraded - or may show they are. Either way, staff must run the analysis rather than argue from principle.
If degradation is real, the reconciliation options, in order of preference:
- Change the metric, not the goal. Ask the DOT whether the applicable standard can be satisfied through an alternatives analysis or a context-based approach permitted under the state's design manual. Many states allow a documented exception where the project advances adopted local plans and safety.
- Buy back performance. Signal timing optimization, access management, turn-lane extensions, or freight routing changes may recover enough to meet D without widening.
- Phase the diet. Implement the segment with the strongest safety case and adequate operation first, monitor, and extend.
- Accept a documented deficiency with a formal exception request and a safety justification.
Adopting a plan that the owner will not permit is a plan that does nothing. The 90-day timeline should be used to obtain a written DOT position early, not to adopt and litigate later.
2. What analysis would resolve the truck and fire access objections?
Read the worked answer
These are empirical questions dressed as values questions, and they dissolve fastest when answered with data.
Freight access
- Count truck movements by time of day and by driveway, and identify the specific loading/unloading locations.
- Check whether the center turn lane and remaining through lanes preserve turning radii into the warehouse driveways. The usual real conflict is not lane width but turning radius and driveway spacing.
- Assess on-street loading: if trucks currently double-park, the diet may require designated loading zones. Budget for them.
- Verify the 6% truck share reflects peak periods; a corridor average can hide a midday freight peak that conflicts with peak-period assumptions.
Fire access
- Obtain the department's actual apparatus dimensions and turning templates rather than debating "narrower lanes" in the abstract. Standard fire apparatus often fits within 11-12 ft lanes; the binding constraint is usually intersection turning geometry and the ability to pass a stopped vehicle.
- Run a vehicle-turning simulation at the driveways and intersections of concern.
- Verify emergency response times on the corridor and on parallel routes.
Bringing the fire chief and two or three warehouse operators into a technical working session with the simulation results converts an objection into an engineering problem with a cost. That cost then goes into the plan.
3. What decision framework and sequencing do you recommend for the 90-day window?
Read the worked answer
Ninety days is enough to adopt a plan but not enough to resolve every design question, and pretending otherwise produces a plan that stalls at permitting.
Recommended sequence:
- Days 1-20: Secure a written DOT position on the applicable standard and exception path. Without it, nothing else matters. In parallel, request apparatus dimensions and run the operations analysis.
- Days 20-45: Technical working sessions with freight and fire stakeholders; produce costed mitigations (loading zones, signal timing, turn radii, phased implementation).
- Days 45-70: Public open house focused on the mitigations, not on re-litigating the concept; brief council on the trade-offs and the cost of each mitigation.
- Days 70-90: Adoption with an explicit implementation plan: which segment first, what monitoring (speeds, crashes, volumes, travel times, truck complaints), and what triggers would prompt modification.
The framework to give council is straightforward: the plan is adopted with conditions, and the conditions are monitored. Committing to a monitoring-and-adjustment clause is what makes a 90-day adoption responsible rather than rushed. Build the evaluation metrics into the adoption motion so the first review at 12 months has data to review.