Traffic Control Plan Templates: When They Work and When They Don't

Every traffic control company eventually asks the same question: we do the same six kinds of job over and over, so why are we drawing a plan from scratch every time?

It is a fair question with a nuanced answer. Some reuse is exactly right and saves real time. Some reuse is how you get a submission rejected and lose a week.

Three different things called "a plan"

The confusion starts with vocabulary, because three quite different documents get referred to interchangeably.

A MUTCD typical application. National illustrations of commonly encountered situations. The 11th Edition indexes 54 of them in Chapter 6P, each with accompanying notes.

An agency standard drawing. A specific jurisdiction's approved treatment for a situation, which that jurisdiction will typically accept by reference. More prescriptive than the national illustration and, where one exists for your situation, generally the governing document.

A site-specific traffic control plan. A design for one location, accounting for that location's geometry, speeds, access points, pedestrian routes and constraints.

The MUTCD itself acknowledges the whole range. It notes that plans "range in scope from being very detailed to simply referencing typical drawings contained in this Manual, standard approved highway agency drawings and manuals, or specific drawings contained in the contract documents," and that "the degree of detail in the TTC plan depends entirely on the nature and complexity of the situation" (Section 6B.01, 11th Edition Part 6).

So: reference-a-standard-drawing is a legitimate form of plan. The question is when.

What typical applications actually are

Worth being precise, because this is the most-misused document in the trade.

The manual describes typical applications as presenting situations commonly encountered, with information that "can generally be adapted to a broad range of conditions." Then two qualifications that change everything:

They are minimums. "In general, the procedures illustrated represent minimum solutions for the situations depicted."

Most of the content is Guidance, not Standard. Except for notes explicitly classified using Standard, Guidance, Option or Support headings, "the information presented in the typical applications can generally be regarded as Guidance."

And the manual explicitly contemplates departure: plans may deviate from the typical applications to allow for the conditions and requirements of a particular site or jurisdiction; devices may be added and spacing adjusted to provide additional reaction time or delineation; fewer devices may be used based on field conditions.

The manual also gives a worked example of why one is rarely enough on its own: work at an intersection might present a near-side zone for one street and a far-side zone for the other, drawing on two different typical applications, with a third covering pedestrian crosswalk closure.

The upshot: a typical application is an input to a plan, not a plan. Treating it as a finished document is the single most common reason a submission comes back — one of several covered in common reasons plans get rejected.

Where reuse genuinely works

Reuse is appropriate and valuable in three situations.

Recurring work at the same location. An annual event, a maintenance program that returns to the same intersections, a utility contract covering a defined corridor. The plan was site-specific when it was drawn and it is still site-specific the second time. Keep the approved version with the jurisdiction and approval date attached, and reuse it with a fresh review for changed conditions.

Genuinely standardised situations under a jurisdiction that publishes standard drawings. A routine shoulder closure on a particular road type where the agency has an approved treatment and accepts a reference to it. Use the agency's drawing rather than a national typical application, because the agency's is the one they will accept without discussion.

Your own approved plans as a starting geometry. A previously approved plan for a similar site is a much better starting point than a blank page — provided the next step is adapting it to the new location rather than changing the address and submitting it.

Where reuse fails

Different geometry, same paperwork. Two shoulder closures on roads with the same posted speed can require quite different treatments if one has a crest, a driveway, or a bus stop in the transition. Sight distance and access points are site facts, and they are what a plan exists to account for.

Different jurisdiction. A plan approved by one agency does not carry weight with the next one, and reviewers can tell instantly when a submission was drawn for somewhere else. This is a fast rejection and, more expensively, a credibility cost with that reviewer.

Changed speed assumptions. Taper lengths derive from the offset width and the speed, so a plan reused on a faster road is wrong in the element that matters most. The relationship is explained in taper length and buffer space explained.

Changed duration. The MUTCD's duration categories drive device requirements, and a plan drawn for a one-day operation may not carry the retroreflectivity and illumination provisions required once work extends into nighttime or across days.

Stale edition references. The 11th Edition renumbered Part 6 — what was Chapter 6C in the 2009 Edition is now 6B, and high-visibility apparel moved from 6D.03 to 6C.05. A library of plans citing 2009 section numbers is not wrong about the road, but it is citing a superseded edition, and reviewers notice.

Building a library that helps

The version that works is less a template library than a records library.

Store, per plan:

• the jurisdiction and the approving contact
• the approval date and any expiry
• the location it was approved for, precisely
• the conditions attached to the approval
• the speed, offset and duration assumptions it was built on
• whether it was accepted as-is or required revisions, and which

That last field is the one that compounds. After a year, you know which reviewers ask for what, which is worth more to your submission success rate than any drawing.

Two rules keep the library from becoming a liability:

Nothing gets reused without a documented review against the new site. Even a short one. The review is the thing that turns reuse from a shortcut into a method.

Assumptions travel with the drawing. A plan without its speed and duration assumptions recorded is a drawing whose correctness cannot be checked.

Who is permitted to prepare or adapt a plan varies by jurisdiction — some require an engineer's seal, some accept a certified designer, some accept a contractor's submission. That question is covered in who can prepare a traffic control plan, and the cost drivers in what drives traffic control plan cost.

The economics of getting this right

Plan revision cycles are a real cost that mostly disappears from job costing because they feel like overhead rework rather than job cost. They are not — a job that needed three submission cycles cost more than one that needed one, and if that never lands on the job, you will keep bidding that customer and that jurisdiction the same way. The routing question is covered in job costing for traffic control companies.

The library pays for itself through the same mechanism in reverse: fewer cycles, faster approvals, and an estimator who can price permit lead time per jurisdiction because the history exists.

Standing caveat, as always: requirements vary by state, county and city, and the authority having jurisdiction decides what it will accept. Ask them what form they want before you draw it, not after they return it.

Traffic OS keeps plans, approvals, conditions and revision history on the job and the jurisdiction they belong to, so the reuse decision is made with the approval record in front of you. Pricing is flat monthly tiers rather than per user. If plan cycles are eating your schedule, bring a recent rejection to a walkthrough. The field-side counterpart — how a crew should read whatever plan arrives — is in reading a traffic control plan in the field.