Lane Closure Restriction Windows and Curfews: The Hours You Cannot Work

An estimator reads a scope, counts the devices, prices the crew, and submits. Nowhere in that sequence does anyone establish when the work is allowed to happen — and on a busy corridor, that single fact can double the cost of the job.

Restriction windows are the hours an agency prohibits you from occupying a lane. They are published, they are specific, and they are routinely discovered after the bid.

Standing caveat: restrictions vary by state, agency, corridor, and permit, and change over time. Nothing here tells you what applies to your job. Get the current published restrictions and the permit conditions from the agency having jurisdiction.

What a published restriction actually looks like

Some agencies publish this material in a level of detail that surprises people who have not seen it.

South Carolina's DOT publishes an interstate route hourly lane closure restriction document that runs segment by segment, direction by direction, and day by day. The December 2024 edition sets out, for example, restrictions on I-20 in Aiken County on the four-lane section from milepost 1 to milepost 6, prohibiting eastbound closures Monday through Thursday from 7 a.m., with Friday running 7 a.m. to 10 p.m. and Sunday 10 a.m. to 9 p.m., with separate and different hours westbound.

Read that as an operator rather than as a table. On that segment, in that direction, a single-lane closure is a night operation and nothing else. Every cost assumption in the bid follows from that: night differential, lighting, reduced productivity, a crew pattern that does not overlap the day shift, and setup and teardown inside a window that does not forgive a late start.

The same document states the general policy that closures which would impact the efficient flow of traffic during peak travel hours or days, holidays, holiday weekends, extended holiday periods, weekends, special events, or any time volumes are high may be restricted, and that closures on high-volume highways during peak periods are prohibited. It also notes that holiday restrictions are handled separately under their own specification section rather than by the hourly tables.

Not every agency publishes at this resolution. Many put the equivalent into project special provisions or permit conditions, where it is harder to find and just as binding.

Where the hours come from

Restrictions are generally derived from traffic count data, and the good ones say so.

The SCDOT document is explicit that the restrictions are intended to cover the hours a queue would be expected to occur, that both July and September count data are used because July is representative of rural and coastal areas while September represents urban and upstate areas, and that hourly data is adjusted by a factor where a segment's AADT differs materially from the count station's.

Two useful implications.

The restriction is a proxy for a queue, not a rule for its own sake. That is why waivers exist and why they turn on data.

Restrictions get more conservative where the agency has less confidence. A segment with variable volumes between interchanges tends to be restricted to the tightest case. If your job sits in one of those, the published restriction may be more conservative than your specific location warrants — which is exactly the argument a waiver request makes.

The federal backdrop is the Work Zone Safety and Mobility Rule at 23 CFR 630 Subpart J, which drives agencies toward assessing and managing work zone impacts on federal-aid projects. Restriction windows are one of the most direct expressions of that policy, and the underlying trade-off — delay against exposure — is the subject of work zone impacts and road user cost.

Waivers are a process with a lead time

Where an agency publishes restrictions, it usually publishes a way to request relief, and the shape is consistent.

In the SCDOT case, waivers are considered with a site-specific review, requested under a named engineering directive and specification section, and require approval from a deputy secretary level with concurrence from the director of traffic engineering. Requests go through the project manager or district engineering administrator. Supporting studies may be submitted, and the agency reserves the right to use different data or require more.

And waivers come with conditions. That same document notes that waivers will require implementation of work zone intelligent transportation systems for queue warning and camera coverage where data indicates queues can be expected, and that other mitigations — detour route improvements, law enforcement presence, signal retiming — may be required depending on expected impacts.

The estimating consequence is the one that gets missed: a granted waiver is not free. It buys daylight hours at the price of queue warning equipment, cameras, or law enforcement in the work zone. Whether that trade is worth taking is an arithmetic question, and it is answerable only if you priced both versions.

Reading restrictions before you bid

A short routine that costs an hour and occasionally saves a job.

Find the governing document for your specific segment, in the right direction, for the current year. Restrictions are revised; a copy from a prior job is not evidence about this one.

Convert the restriction into a usable window and then subtract. Setup and teardown live inside the window, not outside it. A window from 9 p.m. to 5 a.m. is eight hours; after installing and removing a closure it may be five hours of production. That ratio is what determines how many nights the job takes.

Check the holiday and special-event provisions separately. They are usually a different section and cover continuous multi-day blocks that can sit directly on your schedule.

Check whether the restriction differs by direction. It frequently does, and a job requiring both directions may have no common window at all.

Ask about the waiver route early if the restriction makes the job uneconomic — early enough that the answer arrives before the bid, and with a rough price for whatever mitigation the agency is likely to attach.

On local roads, ask rather than look up. Municipal restrictions live in permit conditions and ordinances: school-hour restrictions, business-access requirements, noise limits that rule out the night work a state road would demand. This is a large part of why multi-jurisdiction permit tracking matters on utility contracts crossing several municipalities.

Restrictions are a scheduling constraint, not just a permit line

Once a job is won, the restriction stops being paperwork and becomes the thing dispatch schedules against. A crew that arrives ninety minutes late to a five-productive-hour window has lost a third of the night. A closure not fully removed before the morning restriction resumes is a violation and a phone call.

That makes the permitted window a field the schedule needs to carry, not a note in a folder. Where the restriction lives on the job record alongside the plan and the permit, the dispatcher can see that Tuesday's job cannot start before 9 p.m. Where it lives in an email, they cannot. Our daily dispatch routine covers the wider pattern, and the features page shows how job records carry this kind of constraint.

The one-line version: the drawings tell you what to build, and the restriction tells you whether it is a day job or a night job. The second fact moves the price more than the first one, and it is the one nobody sends you.