Software for Drawing Traffic Control Plans: What Actually Matters

Ask five traffic control companies what they draw plans in and you will get five answers, two of which are "the engineer does it" and one of which is "we mark up the standard sheet." All three are legitimate. The question of what software to use is genuinely secondary to two others: who is going to review this plan, and how many of these are we going to produce?

This post covers the categories of tool honestly, what the manual actually requires of a plan and its author, and — the part usually left out of software comparisons — what has to happen after the plan is approved for it to do any good.

One caveat up front that is not boilerplate: plan requirements vary by state, county and city, and change over time. What an agency will accept, and who has to sign it, is set by that agency. Nothing here substitutes for the requirements of the authority having jurisdiction over your specific work. Verify with them, every time.

What a TTC plan is required to be

Before evaluating tools it is worth reading what the manual actually says, because it is less prescriptive than most people assume.

FHWA published the MUTCD 11th Edition in December 2023 and publishes Part 6 in full at no cost. Section 6B.01 is the section that governs plans, and three of its provisions shape every tooling decision.

On scope and detail. The manual states that TTC plans range in scope from being very detailed to simply referencing typical drawings contained in the manual, standard approved highway agency drawings and manuals, or specific drawings in the contract documents — and that the degree of detail depends entirely on the nature and complexity of the situation.

That single sentence disposes of the idea that every job needs a bespoke CAD drawing. A short-duration shoulder closure on a low-volume road referencing an agency typical application may be a complete and compliant plan. A phased urban reconstruction with pedestrian rerouting is not.

On who prepares it. The manual's guidance is direct: “TTC plans should be prepared by persons knowledgeable (for example, trained and/or certified) about the fundamental principles of TTC and work activities to be performed.” It adds that the design, selection, and placement of devices should be based on engineering judgment.

Note what that does and does not say. It speaks to knowledge and judgment. Whether your state requires a licensed professional engineer's seal on a given plan is a separate question answered by state engineering practice law and agency policy, not by the MUTCD — and the answer differs. Our post on who can prepare a traffic control plan covers the variation; the operative advice is to establish the answer for your jurisdictions before you build an in-house capability around an assumption.

On contractor-developed plans. The manual contemplates bid documents that let contractors develop an alternate TTC plan, and provides that such an alternate or modified plan should have the approval of the responsible highway agency before implementation. The same structure appears in federal regulation: 23 CFR 630.1012 allows plans and specifications to include either an agency-developed transportation management plan or provisions for the contractor to develop one, with state approval required before implementation.

Two more provisions from 6B.01 are worth carrying because they change the drawing itself. Plans should incorporate provisions for effective continuity of accessible circulation paths for pedestrians, and for continuity of transit service where applicable. And on speed, the manual advises that reduced speed zoning be avoided as much as practical, that any reduction apply only to the specific portion of the zone where restrictive conditions exist, and that a plan be designed so vehicles can travel through the zone with a speed limit reduction of no more than 10 mph.

That last one is a design constraint that a lot of contractor-drawn plans violate reflexively, by dropping the limit further than the geometry requires because it feels safer.

The three categories of tool

General CAD with a traffic control library

What most engineering firms and larger contractors use. AutoCAD, MicroStation, or an equivalent, plus a symbol library and often an agency-supplied sheet template.

Good for: anything geometrically unusual, anything requiring survey or existing-conditions accuracy, anything that must be produced to an agency's CAD standards for inclusion in a plan set, and anything that will be sealed.

Bad for: volume. Producing twenty near-identical utility closure plans a month in full CAD is expensive per plan and does not get much cheaper with repetition unless somebody builds and maintains a template discipline.

The hidden cost: the drafting skill. CAD is not the constraint; a drafter who understands tapers, buffer space, device spacing, and the agency's standards is. Buying the software does not buy the second thing.

Agency standard sheets, referenced or marked up

Underrated, and for a large share of routine work it is the correct answer.

Most state DOTs publish standard traffic control sheets and typical applications, and expect them to be used. TxDOT publishes a TCP and work zone reference guide and maintains standard TCP sheets within its plan set structure. MDOT SHA's utility permit provisions require a work zone traffic control plan to be in complete accordance with the Temporary Traffic Control Typical Applications in the agency's Book of Standards. When the agency has already drawn the layout it wants, drawing a different one from scratch is work that adds risk rather than value.

Good for: routine, repeatable work on standard geometry; permit work; anything where the agency's typicals cover the condition.

Bad for: conditions the typicals do not cover, and any situation where you need to communicate site-specific detail — driveway access, a pinch point, a staging area.

The hidden cost: version drift. Agencies revise standard sheets. A company working from a PDF somebody downloaded two years ago is building to a superseded standard and will not find out until an inspector says so.

Purpose-built TCP drawing tools

A category of products aimed specifically at traffic control plan production, typically carrying device libraries, typical-application templates, automatic taper and device-spacing calculations, and satellite or map backgrounds.

Good for: volume production of moderately varied plans; getting a non-CAD-trained but knowledgeable person productive; consistency across multiple people producing plans.

Bad for: relying on the automation uncritically. A tool that computes taper length from inputs is only as right as the inputs and the rule set behind them — and the rule set is jurisdictional. MDOT SHA's utility permit provisions, for instance, define speed for these purposes as the posted speed or the prevailing travel speed, whichever is higher, unless otherwise specified. A tool defaulting to posted speed will silently produce short tapers under that rule. Our post on taper length and buffer space covers the underlying arithmetic; the point here is that automation moves the error from the drafter to the configuration, it does not remove it.

The hidden cost: lock-in on output format. Ask what the plan exports as and whether the reviewing agency accepts it. A beautiful plan in a proprietary format that the district wants as a specific sheet size and template is a re-draw.

How to choose: three questions, in order

How many plans a year, and how similar are they?

Count honestly, over the last twelve months. Under roughly one a week with high variability, buying design services is usually cheaper and carries less risk. Weekly or better on similar geometry — utility work, recurring closures on known corridors, repeat customers — and in-house production with a reviewed template library starts to win on both cost and turnaround. Turnaround is often the real prize: a company that can produce a plan in a day wins work that a company waiting a week on an outside firm cannot bid.

Who reviews the plans, and what do they require?

This determines format, template, and sealing more than any product feature does. Get the answer from each agency you work with before choosing. If two of your three main agencies require a sealed plan for the work you do, an in-house drawing capability solves a smaller part of the problem than it appears to.

Who is going to draw them?

Not which software. Which person. The MUTCD's "trained and/or certified" language is the floor, and there is a credential path — ATSSA's certification program includes a Traffic Control Design Specialist designation alongside Traffic Control Supervisor and Traffic Control Technician, with certifications valid for up to four years and recertification required every four years. Deciding to bring plan production in-house is a hiring-and-training decision with a software purchase attached, not the reverse.

The build-versus-buy arithmetic, done properly

Most companies decide this on instinct. The arithmetic is not complicated and it usually changes the answer.

The cost of buying design services is straightforward: fee per plan times plans per year, plus the schedule cost of turnaround. The schedule cost is the part people omit and it is frequently the larger number — work you cannot bid because you cannot produce a plan in time, or a start date that slips while a submittal waits in someone else's queue.

The cost of producing in-house is a person's time plus software plus the training to make the time productive plus the rework when a submittal comes back. The rework line is the one new entrants underestimate. A company's first year of in-house plan production typically carries a rejection rate that falls sharply once the template library reflects what each agency actually accepts — which means the early economics look worse than the steady state, and abandoning too soon is a common and expensive mistake.

The break-even is mostly about repetition, not volume. Twenty highly varied plans a year is a harder in-house case than forty near-identical utility closures, because the second scenario amortises a template library and the first does not.

There is a middle path worth considering: produce routine work in-house against a reviewed template library, and buy design services for anything unusual or anything requiring a seal. Most companies that succeed at this end up here rather than at either pole, and it has the useful property of keeping an outside relationship warm for the jobs where you need it.

One more input: turnaround is a competitive weapon in this trade. Being able to answer "can you have a plan by Thursday" with yes wins work at a margin that is difficult to see in a spreadsheet, and it is often the real reason to bring the capability in-house. Our note on quoting traffic control jobs faster covers the adjacent version of the same advantage.

The part software comparisons skip: what happens after approval

Here is the failure mode that costs real money, and no drawing tool addresses it.

The plan is drawn. The plan is approved. The approved PDF lives in an email thread, or on the estimator's desktop, or in a folder somebody named after the customer. On the morning of the setup the foreman either has it or does not. If conditions differ from the drawing — a parked car, an unmarked driveway, a utility crew already occupying the shoulder — the crew adapts, correctly, and nothing about the adaptation gets recorded.

Six weeks later somebody asks what was actually set up on the 14th, and the honest answer is that nobody knows.

That gap is where the compliance exposure concentrates, and it is a records problem rather than a design problem. Three things close it:

The current approved plan is attached to the job, so the crew is building from the version that was approved rather than the version that was emailed first. Revision control matters here more than people expect — MDOT SHA's utility permit provisions, for instance, require plan modifications to be submitted in writing at least ten business days in advance for review and approval, which means multiple versions of a plan can be in circulation legitimately.

Field deviations are recorded at the time, with who authorized them. Our post on field changes to an approved traffic control plan covers the distinction between a change a foreman can make and one that has to go back for approval.

The setup is evidenced, with dated photographs from the driver's approach and a timestamped record of what was placed. This is the same daily ticket that supports billing, which is the argument for capturing it once and using it three ways.

That is the seam between plan production and operations, and it is where we have put the effort in Traffic OS — not in drawing the plan, but in making sure the approved one reaches the crew and the built one gets recorded. Our note on reading a traffic control plan in the field covers the crew-side skill that has to exist regardless of tooling.

Why the documentation half is worth the investment

The case for spending effort here rests on what the records are eventually for.

Two authorities can judge one field setup. The roadway agency judges it against the approved plan. OSHA judges it against the manual, which is incorporated by reference at 29 CFR Part 1926 Subpart G and enforced independently — an agency inspector's sign-off is not a defense on the worker-protection side. OSHA collects its guidance on a highway work zones topic page, and the construction standard at 29 CFR 1926.201(a) requires flagging to conform to Part 6.

And the underlying hazard is not abstract. The Work Zone Safety Information Clearinghouse records 850 work zone fatalities in 763 fatal crashes in 2024. FHWA reports 891 work zone fatalities in 2022 and 963 in 2021, with crash-type detail showing speeding a factor in 281 of 821 fatal crashes and rear-end collisions in 174 of them in 2022. On the worker side the same source records 94 highway construction occupational fatalities in 2022 and 108 in 2021, drawn from the Census of Fatal Occupational Injuries published by BLS.

Non-fatal incidents and property damage are far more numerous and appear in no national dataset. Whatever record exists of a given setup is the record you made.

A short buying checklist

If you have decided to produce plans in-house, the questions that separate a useful tool from a demo:

• Does it export in the format and sheet template your agencies require? Ask the agency, not the vendor.
• Where do the taper, buffer, and device-spacing rules come from, and can they be configured per agency? Including the definition of design speed.
• Can you build and version a library of your own reviewed templates? For a company doing repeat work this is worth more than the drawing engine.
• How does an approved plan reach the field? If the answer is "export a PDF and email it," you have bought half a solution.
• Who maintains the standard-sheet content, and how are agency revisions handled? Version drift is the quiet failure in this category.
• What does it cost per plan at your actual volume? Including the person's time, which usually dominates the license.

The unglamorous conclusion: for most traffic control companies the highest-return investment is not a better drawing tool. It is knowing each agency's standards cold, keeping a small library of templates those agencies have already accepted, and closing the gap between the approved plan and what the crew actually built. If you want to see the second half of that working against one of your own jobs, a demo is the fastest way to check it.