Submitting a Traffic Control Plan for Approval: The Process, Start to Finish

On permit work, the approval timeline is frequently the largest single schedule risk on the job, and it is the one contractors have the least visibility into. A plan submitted a week later than it should have been does not delay the job by a week — it delays it until the next available window, which on a restricted corridor can be considerably longer.

This is a walkthrough of how the process generally works and where the time actually goes.

Requirements vary by state, county and city. What a submittal contains, who reviews it, and how long it takes are set by the agency having jurisdiction. Nothing here substitutes for that agency's requirements. Verify with them, every time — and get the answer in writing before your first submittal rather than during it.

What the manual expects of a plan

Worth grounding first, because a plan that satisfies the manual and not the agency still gets rejected, and vice versa is worse.

FHWA publishes the MUTCD 11th Edition with Part 6 available in full at no cost. Section 6B.01 governs plans, and several of its provisions bear directly on submittals.

On scope, the manual states that plans range from very detailed to simply referencing typical drawings in the manual, standard approved agency drawings and manuals, or specific drawings in the contract documents, with the degree of detail depending entirely on the nature and complexity of the situation. A plan does not have to be elaborate to be complete.

On authorship, the guidance is that plans should be prepared by persons knowledgeable — trained and/or certified — about the fundamental principles of temporary traffic control and the work to be performed, with design, selection and placement based on engineering judgment. Whether a licensed engineer's seal is required is a separate, state-specific question; see who can prepare a traffic control plan.

On contractor-developed plans, the manual contemplates bid provisions allowing an alternate plan, and provides that any alternate or modified plan should have the approval of the responsible agency before implementation. Federal regulation mirrors this: 23 CFR 630.1012 allows either an agency-developed transportation management plan or contractor development subject to state approval.

On content, two items are frequently missed. The manual directs that provisions for effective continuity of accessible circulation paths for pedestrians be incorporated into the plan, and that provisions for continuity of transit service be incorporated into planning, including accessible temporary stops where applicable.

And on speed, the manual advises against reducing the regulatory speed limit as much as practical, advises that any reduction apply only to the specific portion of the zone where restrictive features exist, and advises designing so that vehicles can travel through the zone with a reduction of no more than 10 mph. Plans that drop the limit further than the geometry requires get questioned.

What a submittal package generally contains

The specific list is the agency's, but most packages consist of some combination of:

• The plan, in the agency's required format and sheet template
• The proposed schedule — dates, working hours, and the closure windows requested
• Device layout and quantities, keyed to the agency's typical applications where they apply
• Pedestrian and bicycle provisions, shown explicitly rather than implied
• Any requested exception to a standard requirement, with justification
• The responsible person, where the agency requires a named and certified individual

MDOT SHA's utility permit general provisions give a concrete example of how prescriptive this gets. They require an approved work zone traffic control plan for all work performed within the agency's right of way, submitted to the District Utility Engineer, in complete accordance with the temporary traffic control typical applications in the agency's Book of Standards and the state manual. The plan must address vehicular, bicycle and pedestrian traffic; it should indicate the time during which work is to be performed as well as the proposed placement of signs and device layout; and a certified Traffic Manager must be specifically designated for each permit application with a 24-hour contact number.

That is one state's utility permit process, not a universal template — but it is a fair picture of the level of specificity to expect.

Who reviews it, and why that is often more than one person

The single biggest source of surprise in submittal timelines is discovering a second or third reviewer after the clock started.

Jurisdiction. A closure or detour that touches more than one agency's roads needs each of them. See detour route planning and signing for how quickly that multiplies, and multi-jurisdiction permit tracking for keeping the conditions straight afterwards.

Specialist review. Some agencies route plans involving closures or detours to a dedicated bicycle and pedestrian coordinator. MDOT SHA's provisions require exactly that for all proposed road closings or detours.

Separate closure permits. Approval of the plan is sometimes not the same as authorisation to close a lane. Maryland's utility permit provisions, again as an example, require the permittee to apply for and obtain a Traffic Control Permit from the appropriate district office before closing any lanes, with the district approving the schedule and number of lanes.

Establish the full list of approvals for a given job at the start. A plan approved by one of three agencies is not an approved plan.

Revisions have their own clock

This is the part that most often turns a manageable delay into a missed season.

A revision is not a quick email. MDOT SHA's provisions require that all changes, modifications, or alterations to an approved work zone traffic control plan be submitted in writing to the District Utility Engineer at least ten business days in advance for review and approval, and note that the agency reserves the right to modify or expand the specified traffic control if the operation is judged a detriment to safe and efficient traffic flow.

Ten business days is two calendar weeks. A company that treats plan changes as a same-week activity will miss windows, and on a restricted corridor the next window may be a month out.

Two implications:

Front-load the accuracy. Every avoidable revision is two weeks. The cheapest place to catch an error is before the first submittal.

Distinguish a revision from a field adjustment. Some changes require resubmittal and some do not, and knowing which is which in advance is worth a conversation with the reviewer. Our post on field changes to an approved traffic control plan covers the line.

Reducing rejections

Rejections cluster, and the clusters are boring — which is good news, because boring problems are fixable. The pattern is covered in more depth in traffic control plan rejections; the submittal-side habits that prevent most of them:

Work from the agency's current standards, not a downloaded copy. Agencies revise standard sheets, and a two-year-old PDF is a superseded standard.

Confirm how the agency defines design speed. Some define it as the higher of posted or prevailing speed, which changes taper and advance-warning distances relative to a plan drawn off the posted limit. See taper length and buffer space.

Show pedestrian and bicycle provisions explicitly. Absence reads as omission, not as "not applicable," unless you say so.

Use the agency's typical application when one covers your condition. Drawing something different invites scrutiny you do not need.

Build a template library from plans that were actually approved. This is the highest-return habit for a company doing repeat work with the same agencies, and it compounds.

Track the submittal like a job, not an email

The last operational point. A submittal has a state — drafted, submitted, under review, comments received, revised, approved — and a date attached to each. Companies that keep that in an inbox lose track of which version is current, which is how a crew ends up building from a superseded plan.

Attach the current approved plan to the job so the crew is working from the version that was approved, and keep the revision history, because on a job with a ten-business-day change process several versions can legitimately be in circulation. That is the same problem covered from the field side in reading a traffic control plan in the field, and it is the seam where plan production and operations either connect or do not. A demo will show what that handoff looks like against one of your own permits.