Who Can Prepare or Seal a Traffic Control Plan?

"Does this need an engineer's seal?" is one of the most common questions in traffic control, and one of the few where the honest answer really is: it depends, and you have to ask.

That is unsatisfying, so this explains what it depends on and what to ask.

Standing caveat that is doing real work here: engineering practice requirements are set by state law, and plan requirements are set by the agency having jurisdiction. This describes how the question is generally structured. It is not legal advice and it does not tell you what your project requires. Confirm with the agency and, where the answer is unclear, with an attorney or a licensed engineer in your state.

Two separate questions

People collapse these, and they have different answers.

Who may prepare the plan — who produces the document.

Whether it must be sealed — whether a licensed professional engineer must affix a seal, taking professional responsibility for the engineering judgment it contains.

A plan can be prepared by trained staff and sealed by an engineer who reviews and accepts it. It can also be prepared and sealed by the same engineer. And for routine work, many agencies require no seal at all.

Sealing is not a signature of convenience. A professional engineer applying a seal is taking on professional liability for the adequacy of the design, which is why engineers are appropriately careful about sealing work they did not supervise.

What the answer depends on

The agency having jurisdiction. The primary variable. A state DOT's requirements for a state highway differ from a small city's for a residential street, and both can differ from a county's. Some agencies publish this clearly; others answer only when asked.

Roadway classification and speed. Higher-speed, higher-volume facilities generally attract stricter requirements. A closure on a fifty-five mile per hour divided highway is more likely to require sealed engineering than one on a low-speed local street.

Complexity. A routine daytime lane closure matching a standard detail is treated differently from a multi-phase closure with detour routing, temporary signals, or pedestrian rerouting.

Whether standard details apply. Many agencies publish approved standard details for common situations. Where one genuinely fits, contractor-prepared plans referencing it are frequently acceptable. Where the site deviates — an unusual intersection, restricted sight distance, a driveway conflict — the standard detail stops covering you, and that boundary is a judgment call worth being conservative about.

State engineering practice law. Independent of agency preference, each state defines what constitutes the practice of engineering and who may perform it. This constrains what non-engineers may produce regardless of whether an agency would accept it, and it is the part contractors most often overlook.

Contract terms. The prime contract or owner may impose stricter requirements than the agency, and contractual requirements bind you separately.

The technical basis, whoever prepares it

Regardless of who produces the plan, its technical content rests on the same foundation.

The national floor is Part 6 of the Manual on Uniform Traffic Control Devices, covering temporary traffic control. The current edition is the MUTCD 11th Edition, published December 2023 with Revision 1 dated December 2025, and Part 6 is published in full. Your state manual and the agency's standards layer on top.

Two cautions for anyone building plan templates in-house.

Section numbering changed from the 2009 edition that the industry used for many years. Templates citing 2009-era sections are citing sections that have moved.

Typical applications are illustrations, not designs. They demonstrate principles. They do not account for your sight distance, driveway conflicts, pedestrian route, or queue length. Treating one as a drop-in plan is how a setup ends up resembling the manual while being wrong for the site. The figures are also part of a copyrighted publication and state manuals are separately copyrighted, so template content should be your own work product built against those requirements rather than reproduced material.

Preparation is not implementation

An important separation, because contractors get this wrong in a way that costs them.

A sealed plan says a licensed professional took responsibility for the engineering judgment in the document. It says nothing about whether the field setup matches it.

Implementation responsibility generally sits with the contractor building the setup, though allocation depends on the contract. Building something other than what was approved is a contractor problem regardless of who sealed the document.

And conformance is enforced from a second direction entirely. OSHA's construction standards incorporate the traffic control manual by reference at 29 CFR Part 1926 Subpart G, making conformance an occupational safety obligation enforceable against the employer. So the same setup is judged by the permitting agency against the approved plan and by OSHA against the manual — and an agency inspector's sign-off is not a defense on the worker-protection side.

Which raises the question that matters more than the sealing question: can you demonstrate, later, that what you built matched what was approved? For most companies the honest answer is no, because the plan is a PDF and the setup lives in a foreman's memory. A GPS-stamped, timestamped field record captured at setup — and again at each reconfiguration — is what closes that gap.

What to ask the agency

Ask these early, before you commit to a schedule:

Does this project require a sealed traffic control plan, and under what circumstances would that change? Are there approved standard details for this situation, and what makes a site fall outside them? Who may prepare plans you will accept? What is the review timeline and typical resubmittal turnaround? What are the most common reasons plans from contractors get returned?

That last question is the highest-yield one and almost nobody asks it. Reviewers know exactly what they send back most often and will usually tell you.

The short version

Whether a plan needs an engineer's seal depends on the agency, the roadway, the complexity, and your state's engineering practice law. There is no universal answer, and reasoning from what worked in another jurisdiction is unreliable.

For routine closures matching approved standard details, contractor-prepared plans are frequently acceptable. As speed, volume, and complexity rise, sealed engineering becomes more likely.

Preparation and implementation are different responsibilities. A sealed plan does not protect you if the field setup differs from it — and being able to show that it did not differ requires a record, not a recollection.

Ask the agency. Every time, and early.

For more on how the document fits into permitting, see how lane closure permits work, or book a walkthrough to see how plan conditions reach the crew.