What is a right-of-way permit?

Broadly, an authorization to occupy or work within public right of way — the land a road and its shoulders, sidewalks and utility corridors sit on. It is about the right to be there at all, which is distinct from a lane-closure permit's question of how traffic will be handled while you are. Terminology and scope vary considerably by jurisdiction.

How is it different from a lane-closure permit?

A right-of-way permit generally addresses occupancy and the work itself; a lane-closure permit addresses the traffic impact and its timing. Many jurisdictions bundle them, some issue both, and some use entirely different names. Do not assume the structure of one agency applies to the next one over.

Whoever owns the road. State DOT for state highways, county for county roads, city public works or engineering for city streets, and occasionally a separate authority for a toll road, a park, or a bridge. A single job can cross two owners, which means two permits.

How long does approval take?

It varies enormously — days for a routine city street occupancy, considerably longer where a state DOT and a utility accommodation process are involved. TxDOT's guidance for one utility permit process advises allowing at least 90 days. Ask the specific authority for their current timeline rather than assuming.

What happens if the permit expires mid-job?

That is jurisdiction-specific and never good. The practical answer is to track expiry dates as hard scheduling constraints and to know each agency's extension process before you need it, because extension requests submitted after expiry are usually treated as new applications.

Right-of-Way Permits for Traffic Control Work

What a right-of-way permit is, how it differs from a lane-closure permit, who typically issues one, what a submission usually contains, and how to track permit obligations across multiple jurisdictions without losing a job to an expired approval.

A traffic control company can have the right plan, the right devices and the right crew, and still be shut down on arrival because someone did not have permission to be on that piece of road.

Right-of-way permitting is the least interesting part of the trade and one of the most reliable ways to lose a morning. This is an orientation to how the process generally works and what to track — not a statement of what you need, because that is a question only the authority having jurisdiction can answer.

What "right of way" means here

Public right of way is the corridor of land a public road occupies — typically wider than the pavement, taking in shoulders, verges, sidewalks and the utility corridors alongside. Working in it, occupying it, or placing anything in it generally requires authorization from whoever controls it.

The distinction worth holding onto:

A right-of-way permit is broadly about occupancy — may you be here, doing this, for this long.

A lane-closure permit is broadly about traffic impact — how will road users be handled while you are.

Some agencies issue both, some fold them into one instrument, and many use different names entirely: street use permit, encroachment permit, road occupancy permit, utility installation permit, work-in-the-right-of-way permit. The vocabulary is not standardised across jurisdictions and neither is the scope. Treat the names as local dialect and ask what each instrument actually authorises. The traffic-impact side is covered separately in lane closure permits and road closure versus lane closure permits.

Who issues what

The issuing authority follows road ownership, and the ownership boundary is not always where an intuition would put it.

State DOT for state highways and their right of way. A state route running through a city is usually still the state's, even though everything around it is municipal.

County for county roads.

City public works or engineering for city streets.

Special authorities for toll roads, bridges, park roads, port and airport property, and campuses.

A single job can straddle two of these. A closure that begins on a city street and runs into a state highway intersection is two jurisdictions, two applications, two timelines and two sets of conditions — and the conditions can conflict, which is a conversation to have before the job rather than during it.

Railroad crossings deserve a special mention. Work near a grade crossing typically pulls in the railroad or transit agency as an additional party, and the MUTCD flags early coordination with the railroad company or light rail transit agency as something that should happen when a work zone includes a grade crossing (Section 6A.02, 11th Edition Part 6). Railroad coordination timelines are frequently the longest item on a project.

What a submission usually contains

Requirements vary, but applications commonly ask for some combination of:

the exact location, described precisely enough to be unambiguous
the work being performed and who is performing it
proposed dates, times and duration
a traffic control plan or a reference to an approved standard drawing
proof of insurance, often with the agency named as additional insured
a bond or deposit in some jurisdictions
contractor licensing or registration with that jurisdiction
an emergency contact reachable outside business hours

Two of these cause most of the delays. Insurance certificates are frequently wrong in a specific way — the named insured, the additional-insured endorsement, or the limits do not match what the agency requires, and the application sits until a corrected certificate arrives. Contractor registration with the specific jurisdiction is a prerequisite some companies discover mid-application; it is worth establishing in every jurisdiction you plausibly work in before you have a job there.

The traffic control plan attached to the permit is a common rejection point in its own right, for reasons covered in common reasons plans get rejected.

Timelines, and why to ask rather than assume

Approval times range from same-week for routine municipal street occupancy to months where a state DOT process, a utility accommodation review, or a railroad is involved.

As one concrete data point rather than a general rule: TxDOT's guidance on one utility permit process advises allowing at least 90 days to receive the necessary permit. TxDOT has also been moving utility permit applications onto RULIS, the Right of Way Utility and Leasing Information System, a web-based system for managing utility permit applications and leasing — an example of a broader trend toward agency portals, each with its own account setup and submission format. The wider policy and procedure set sits in TxDOT's Utility Accommodations Toolkit, and the state's work zone expectations for contractors more broadly are covered in TxDOT work zone requirements.

The practical guidance: ask each authority for their current typical timeline, and record it against that jurisdiction. Timelines drift with agency workload and staffing, and a number that was accurate last year may not be. What you want is not a national average but a per-agency figure your estimator can price against and your scheduler can plan against.

Permit conditions are job constraints, not paperwork

An issued permit usually carries conditions, and those conditions are operational requirements the crew has to satisfy. Common ones:

Time-of-day restrictions. No closure during peak hours, or work permitted only overnight. This is a scheduling constraint that has to reach dispatch, not just the office file.

Notification obligations. Notify the agency, the police department, transit, or adjacent businesses a set number of hours before starting. Missed notification is a common and entirely avoidable violation.

Restoration requirements. Pavement, markings, landscaping returned to a specified condition within a specified period.

Specific device or plan requirements beyond the general standard.

Named expiry. The permit is good until a date, and no further.

The failure mode is that these conditions live in a PDF in an email thread, while the crew's instructions live in a schedule. When the two diverge, the crew builds to the schedule.

Tracking permits across jurisdictions

Multi-jurisdiction permit tracking is a real operational discipline once you are working in more than three or four places, and most companies do it with a spreadsheet until it fails.

What actually needs tracking, per permit:

the jurisdiction and the issuing instrument
the job it belongs to
application date, issue date, expiry date
conditions that constrain scheduling
notification obligations and their lead times
renewal or extension process and its own lead time
who at the agency to call

The two things that make this useful rather than decorative: the expiry date has to be visible to whoever schedules the job, and the conditions have to travel to the crew with the rest of the job's instructions. A permit attached to a job record, where the schedule and the crew's job details already live, does both without anyone remembering to check a folder.

The second-order benefit is estimating. Once permit lead times and fees are recorded per jurisdiction over a year, they stop being guesses in a bid — which is the point where permit cost starts showing up correctly in job costing and in bidding.

The standing caveat, said plainly

Requirements, terminology, fees, insurance minimums, timelines and conditions vary by state, county and city, and they change. Nothing here tells you what you need for a specific job. The authority having jurisdiction is the only source for that, and asking them directly — early, before the bid rather than after the award — is both faster and cheaper than any alternative.

If your permits currently live in email and your schedule lives somewhere else, that gap is where the lost mornings come from. Traffic OS keeps permit records, conditions and expiry dates on the job they belong to, priced in flat monthly tiers rather than per user. Bring a multi-jurisdiction job to a walkthrough if you want to see how the constraints land in dispatch.