Right of way management: encroachment permits, dig once, and small cell shot clocks

Reference article · 5 min read

A contractor cuts a street to reach a water lateral, a fiber provider trenches a block of conduit, a carrier attaches a small cell to a streetlight. Each is an encroachment or excavation permit carrying plan review, traffic control, inspection, restoration, and a liability tail that runs for years.

The permitting system is where right of way policy actually lives. A pavement moratorium exists only if the counter sees it before issuing. A dig once policy is real only if a planned resurfacing project reaches the utility that was going to trench the same block next spring. A shot clock is met only if the agency can show when the clock started and what it did before it ran out.

What the permit record has to carry

A right of way permit is a small contract with a long memory. It should carry:

• Parties and standing. Applicant, contractor of record, licenses, insurance, and bonds, with expirations that block issuance when lapsed.
• Location as geometry. The work area snapped to the street network rather than typed as an address. Geometry is what makes conflict detection possible.
• Work type and dimensions. Cut versus bore, longitudinal versus transverse, area, and depth. Restoration standards and degradation fees key off these fields.
• Conditions and referrals. Which reviewers saw the application, what each attached as a condition, and whether it was verified in the field.
• Inspection and closeout. Each inspection with result and photos, the restoration acceptance date, and the warranty start, which is a different date from issuance.

Most delay in encroachment permitting is queue time, not review time. A view of each reviewer's open items by age, with reassignment that does not require email, often does more than rewriting standards.

Moratoriums, degradation fees, and bonds

These protections work only when enforced at intake rather than discovered later. Maintain moratoriums as mapped segments with start and end dates, tied to the project that created them, so an application inside one is flagged during review and routed to the exception path your policy defines: denial, a waiver with enhanced restoration, or an emergency exemption.

Degradation fees usually depend on cut area and remaining pavement life, so the fee engine needs permit dimensions and a condition or age attribute on the segment. Bonds, per permit or blanket, need expiration tracking, claim history, and a release step that will not fire until the warranty period ends. Standards vary by jurisdiction, so configure from your own ordinance.

Shot clocks and the wireless queue

Federal law limits how long a local government may take to act on wireless siting applications, and the Federal Communications Commission has adopted presumptive review periods by application type. Small wireless facilities are generally subject to shorter periods than other siting, collocations on existing structures move faster than new builds, and certain modifications to existing facilities carry their own deadline and remedy. Those rules have been shaped by several FCC orders and by litigation, so confirm current requirements with counsel.

Several points hold regardless of the exact periods:

• The clock generally runs from submission, covers the local approvals needed for the site including zoning, and does not restart because the file moved between departments.
• An incompleteness notice tolls the clock only if issued within the allowed window and only if it identifies missing items specifically. Generic requests for more information are a common failure point.
• Applications often arrive in batches. Track each site's clock separately.

Store the deadline as a computed date with a countdown, alert the owner before expiration, and log every status change. If an application is contested, that log is the defense.

Making dig once operational

A dig once policy that lives in a memo produces nothing. Coordination comes from a shared, forward looking view of planned work.

1. Publish the capital and resurfacing program as mapped segments with planned year and quarter, not as a spreadsheet attachment.
2. Require utilities and franchisees to file periodic work plans in the same map, at whatever precision they can commit to.
3. Run conflict detection across planned utility work, planned paving, and active moratoriums, and put the results in front of a standing coordination meeting.

One call damage prevention notice is separate, running on a cycle of days. Dig once works on a horizon of months to years.

Agreements, rates, and the base map

Franchise agreements, master license agreements, and pole attachment agreements set the terms individual permits implement. The system should know which agreement an applicant works under, what it allows without further approval, and when it expires. Fees for wireless access to the right of way are constrained by federal rules that generally tie them to a reasonable approximation of agency cost, so document your cost basis and review it with counsel periodically.

All of it rests on a usable linear network: a maintained centerline with stable segment identifiers, a pavement layer with construction history, and permits carrying a spatial footprint.

What to ask vendors and how to start

• Ask how deadline clocks are configured, whether tolling and extension events are first class records, and what the audit export contains.
• Ask to see moratorium and conflict checking run during intake on your own data, not a demo dataset.
• Require in the contract that permit, inspection, and spatial data, including attachments and status history, are exportable in open formats on demand and at termination.
• Require documented integration to your GIS and financial system, specified in the contract rather than a later statement of work.

Start by measuring cycle time by permit type and reviewer queue, and by inventorying your agreements and active moratoriums. Configuration is easier once you see where time goes.

HQT works with state and local agencies on permitting systems, GIS, and systems integration.

Frequently asked questions