Road & Highway Crossings in the DC Region
Nowhere else does the question 'whose pavement is it?' have this many answers. District streets run on DDOT's public-space permitting; Virginia's arterials and interstates on VDOT's land-use permit process; Maryland's state system on the highway administration's utility permits; county and municipal roads on their own machinery; and the parkways — the green corridors everyone drives daily — on federal land managers whose crossing processes resemble no state DOT's. We identify the actual owner first, because the wrong application is the slowest application.
The regional pricing truth is the fall line: a crossing in Bethesda or Reston prices piedmont, with rock classes stated; a crossing in Waldorf or Upper Marlboro prices coastal plain, with water-table manners. Blended rates are wrong on one side or the other; ours name the province.
Homeowner straight talk, standing network policy: open ground on your own property trenches cheaper than it bores — first call, no charge. Where a public road forces a real crossing, projects start at a $10,000 minimum; a rig, crew, locates, and traffic control have a floor in every jurisdiction, including the federal ones.
Straight answers
What happens when a route touches a federal parkway?
The land manager's crossing process joins the stack — its own application, review, and conditions, on its own clock, separate from any state DOT. It's the region's most commonly underestimated permit, which is why our scope sheet asks about parkway and park-unit touches before anything gets priced.
Do the three DOTs really differ that much?
In substance they want the same things — a competent bore plan, proper cover, restoration — but the machinery differs: different applications, drawing conventions, fee structures, and review cultures. Programs that span jurisdictions get parallel permitting from day one so the borders stay administrative.