How to write a traffic control plan for a small paving crew

Last updated 2026-07-11

What exactly is a traffic control plan and does your crew legally need one?

A traffic control plan is the written document that tells your crew, inspectors, and local traffic engineers exactly how you'll keep moving vehicles away from workers in a roadway work zone. It spells out sign placement, cone tapers, flagger positions, arrow board use, and what happens when something goes sideways.

Do you legally need one? Almost certainly. OSHA's construction standard at 29 CFR 1926.200 through 1926.203 requires employers to provide traffic control devices that conform to the Manual on Uniform Traffic Control Devices (MUTCD), published by the Federal Highway Administration ^[1]. MUTCD Part 6 covers temporary traffic control for highway work zones, and that's where most of the practical rules live ^[2]. Past OSHA, most state DOTs and cities want an approved TCP on file before they'll issue a permit for work that touches a travel lane.

Paving a private parking lot? A short internal TCP still makes sense even when nobody requires you to submit one. If a worker gets struck, the first question an OSHA compliance officer asks is whether you had a plan. "No" makes everything that follows worse.

Here's the good news. A TCP for a two-to-four person crew paving a residential street or commercial lot does not need 40 pages. A clear site diagram, a device list, flagger assignments, and a daily check log usually satisfies both OSHA and a local permit office.

What standards and regulations govern work zone traffic control?

Three layers of rules hit most small paving contractors in the United States: OSHA, the federal MUTCD (plus any state version), and your local permit ordinance. Learn the MUTCD first, because everything else points back to it.

OSHA 29 CFR 1926.200-203 requires that every traffic control device at a construction site meets the MUTCD. The standard says devices must be "reflectorized" and positioned so workers aren't exposed to unnecessary traffic hazard ^[1]. OSHA doesn't write its own cone-spacing tables. It points straight at the MUTCD, which is why the MUTCD is non-negotiable reading.

FHWA's MUTCD Part 6 is the technical bible. The 11th Edition (finalized December 2023, compliance phased through 2026) sets device warrants, sign sequences, taper formulas, and flagger requirements ^[2]. If your state runs its own MUTCD supplement, that supplement controls wherever it's stricter than the federal version. California, New York, and Texas keep their own versions, so pull up your state DOT's site before you assume the federal book applies.

Your state DOT and city likely stack their own permit rules on top. Plenty of cities require a TCP stamped by a licensed engineer for work on a collector or arterial road. For residential streets and parking lots, a contractor-prepared TCP is usually fine as long as it cites the MUTCD correctly.

Work on any federally funded roadway and you also have to check 23 CFR 630 Subpart J, which sets federal program requirements for work zone safety ^[3].

Governing Document	Who Issues It	What It Controls
29 CFR 1926.200-203	OSHA	Device compliance, employer duties
MUTCD Part 6 (11th Ed.)	FHWA	Technical device specs, taper formulas, flagger rules
State MUTCD Supplement	State DOT	State-specific additions/modifications
23 CFR 630 Subpart J	FHWA	Federal-aid highway work zone programs
Local permit ordinance	City/County	Submission requirements, timing restrictions

What are the required components of a traffic control plan?

A defensible TCP for a small paving crew needs six components. Skip any one and you've left a gap an OSHA inspector or a plaintiff's attorney will find.

1. Project description and scope. One paragraph: the work, the location (address, highway number, milepost), estimated duration, and hours of operation. Be specific. "Paving overlay, 200 linear feet of Main Street from Oak Ave to Elm Ave, 7 a.m. to 4 p.m., Monday through Friday, roughly two weeks" is the right level of detail.

2. Site diagram. A to-scale or clearly dimensioned sketch showing road geometry, the work zone, and every device. Draw it by hand or mark up a Google Maps printout. Label the advance warning area, the transition (taper), the buffer space, the work space, and the termination area. Those are the five work zone components MUTCD Part 6C defines ^[2].

3. Device schedule. A table listing every device: type (sign, cone, drum, arrow board), quantity, mounting height, retroreflectivity rating, and spacing. MUTCD Table 6C-2 gives minimum device spacing by posted speed for lane closures. At 30 mph, cone spacing in the taper is 20 feet. At 45 mph it's 40 feet ^[2].

4. Flagger assignments. Name (or role) of each flagger, their ATSSA or state-equivalent training card number, their exact position in the diagram, and how flaggers communicate (radios, hand signals). OSHA 29 CFR 1926.201(a) says flaggers must be trained and use MUTCD hand-signaling procedures ^[1].

5. Contingency procedures. What happens if the arrow board dies? If a flagger gets hurt mid-shift? If a driver blows past your controls into the work zone? One page on these scenarios proves to an inspector you actually thought the plan through.

6. Daily inspection log. A simple form where the crew lead initials that every device is in place, working, and correctly positioned before work starts. Date, time, initials, any deficiency noted and corrected. That log is your proof of ongoing compliance.

How do you design the work zone layout and calculate taper lengths?

Work zone geometry is where most small contractor TCPs fall apart. The math isn't hard. You just have to actually do it instead of eyeballing it.

The MUTCD defines a standard lane closure sequence: advance warning signs, then a transition taper where traffic merges, then a longitudinal buffer space, then the work space, then a downstream taper to close it out ^[2]. Each zone carries a minimum length tied to posted speed and lane width.

The taper length formula in MUTCD Part 6C for speeds at or above 45 mph is L = WS²/60, where W is lane width in feet and S is posted speed in mph. Below 45 mph, it's L = WS/60 ^[2]. For a 12-foot lane on a 35-mph street: L = (12 × 35) / 60 = 7 feet. That's absurdly short, and the MUTCD sets a 100-foot minimum for any taper on a two-lane road, so you'd run 100 feet. On a 45-mph road with a 12-foot lane: L = (12 × 45²) / 60 = 405 feet. That's a real distance you have to account for in device placement.

Advance warning sign spacing is a separate calculation from taper length. MUTCD Table 6C-1 gives three distances for each sign in the "Road Work Ahead" sequence: roughly 100 feet apart in urban low-speed settings, up to 1,500 feet apart on high-speed rural roads ^[2]. Read the table. Don't guess.

The buffer space matters too. A longitudinal buffer of 20 to 80 feet (speed-dependent) sits between the taper end and your work area, giving space for a vehicle that slips past the taper. No worker stands in that buffer. Ever.

Draw the full geometry on your site diagram before you count a single device. You can't fill out the device schedule accurately until you know the distances.

What are the flagger requirements under OSHA and the MUTCD?

Flaggers are the most visible piece of any small crew TCP, and they carry real legal weight. OSHA 29 CFR 1926.201(a) says flaggers must be trained for their duties ^[1]. MUTCD Section 6E sets the performance rules: a STOP/SLOW paddle meeting retroreflectivity specs, a Class 2 or Class 3 high-visibility garment meeting ANSI/ISEA 107, and a position with adequate sight distance in both directions ^[2].

Training is a real requirement, not a checkbox. Most states recognize training from the American Traffic Safety Services Association (ATSSA), but several require state-specific certification. California requires a flagger card through a Cal/OSHA-approved program, for example. Keep copies of every training card in your TCP file.

A few things TCPs routinely leave out. Flaggers need written instructions for a driver who refuses to stop. They need the hand and radio signals they'll use to coordinate at opposite ends of the zone. And they need a defined break and relief rotation so nobody stands in a live lane for four hours without relief. Put all of that in the contingency and assignment sections.

High-visibility garments cover more than flaggers. Every worker in the right-of-way needs one. The federal rule at 23 CFR 634 requires all workers on federal-aid highway projects to wear ANSI/ISEA 107 Class 2 or Class 3 vests ^[3]. Even on non-federal roads, OSHA's general duty clause makes a Class 2 vest the practical floor for anyone inside the roadway.

For more on documenting the training itself, see our guide to osha training.

What equipment does a small paving crew's TCP need to specify?

Your device schedule should be specific enough that a new hire or a sub could set up the work zone from your TCP alone, with zero questions. If it isn't, it's not done.

At a minimum, a small paving crew TCP lists:

Signs. The standard MUTCD advance warning sequence for a lane closure opens with "Road Work Ahead" (W20-1), then directional signs for the closure type. Signs run 48 x 48 inches on most state routes and expressways; 36 x 36 inches is acceptable in some low-speed urban settings. Check your state supplement. Signs are diamond orange with black legend, retroreflective to MUTCD minimums ^[2].

Channelizing devices. Cones (28 inches tall minimum for most work, 36 inches in zones over 45 mph), drums (36 inches), or tubular markers depending on the application. Pull quantity and spacing straight from your taper calculation.

Arrow boards. Any lane closure where traffic passes the work space should carry a Type C arrow board (48 x 96 inches minimum) ^[2]. A trailer-mounted board rents for roughly $150 to $350 per week depending on your market; buying one runs $2,000 to $6,000. Do regular roadway work and owning one pays off inside a season.

Temporary pavement markings. If your work wipes out existing lane markings, the TCP has to address temporary markings or delineators. Removing stop bars or crosswalk lines without replacing them is a liability waiting to happen.

Portable changeable message signs (PCMS). Not always required for small crews, but some cities want them for night work or when a closure runs more than a block. Flag it in your permit inquiry before you write the TCP.

How do night paving jobs change the traffic control plan?

Night work raises the stakes on everything in the TCP. Retroreflectivity requirements climb, sight distances shrink, and OSHA's general duty clause gets easier for an inspector to invoke when workers are poorly lit.

The MUTCD requires every channelizing device in a night work zone to carry retroreflective collars or stripes meeting minimum retroreflectivity values (measured in mcd/m²/lux). Plain orange cones with no retroreflective banding are not compliant after dark ^[2].

Work zone lighting is addressed in MUTCD Section 6F and in ANSI/IES RP-8, the roadway lighting standard. The practical requirement: workers in the work space have to be visible to approaching drivers from far enough away for a safe stop at the posted speed. On a 35-mph road, stopping sight distance is roughly 250 feet, so workers must be lit well enough to be seen at that distance ^[2].

Your nighttime addendum should name lighting towers and their positions, the generator location (set so exhaust doesn't blow into the work space), extra signage or flashing lights, and the reduced work zone speed many jurisdictions require at night. Some cities also require a nighttime traffic control engineer review they skip during the day.

Fatigue bites harder at night. Your TCP should set explicit flagger relief intervals of no more than two hours for night shifts.

What documentation do you need to keep, and for how long?

Keep your TCP, daily inspection logs, and flagger cards for the life of the project plus at least three years. OSHA's recordkeeping rule at 29 CFR 1904 requires a five-year retention for the OSHA 300 injury log ^[4]. The TCP itself isn't a 1904 record, but it becomes your primary defense document after a worker injury or a citation, so treat it like one.

Here's the full file to hold. The signed, dated TCP. Every daily inspection log. Flagger training certificates. Any permit or municipal approval letters. Any mid-project change orders that modified the TCP, signed and dated. Photos of the setup from the first day and from any day you changed the layout. Many attorneys push for five years of retention rather than three.

If OSHA inspects and you can't produce a current TCP and recent inspection logs, you're looking at a serious citation under 29 CFR 1926.200. Willful violations run up to $161,323 per violation as of 2024 ^[5]. Serious violations reach $16,131 per violation ^[5]. A few weeks of daily log signatures is cheap insurance against that.

For the wider written-program structure your TCP sits inside, see our osha training resources and the SafetyFolio guide on written programs.

How do you handle TCP requirements when working for a general contractor or DOT?

Working as a sub under a general contractor (GC) or directly on a DOT contract changes the TCP picture. The GC or DOT may run a project-level TCP for the whole site, but you still need a plan specific to your immediate operation, and it has to line up with theirs.

On a DOT contract, the TCP is usually a contract deliverable that a traffic engineering reviewer signs off on before work starts. Mid-project changes need a formal revision and re-approval, which can eat days. Build that lead time into your schedule.

The GC relationship is trickier. Under OSHA's multi-employer citation policy, a GC can be cited for a sub's TCP violation even when the GC didn't create the hazard, because the GC has a duty to control the site ^[6]. So GCs often demand that subs submit their TCP for review. Take the review seriously. A GC-required change beats a shared citation every time.

If your crew is the "controlling employer" under that policy, meaning you set up and control the work zone where other trades also work, you carry extra responsibility to monitor everyone's compliance in that zone ^[6].

For crews that pick up GC work regularly, keeping a pre-written, MUTCD-compliant template for your common scenarios (single-lane road closure, parking lot with adjacent traffic, residential curb-and-gutter) saves real time on every bid.

Can you use a template, or does every TCP need to be written from scratch?

Use a template. For a small crew it's the right call, not a shortcut. The MUTCD itself publishes standard work zone drawings for common setups, like single-lane two-way traffic control, that you can adapt directly ^[2]. FHWA's Work Zone Safety site and most state DOTs publish free standard plan sheets for typical closures, detours, and flagging operations.

The catch: the template has to match the actual site. A template with the wrong taper length for your speed, or a device count that doesn't fit your road geometry, is worse than no template because it builds a false sense of compliance.

Here's the workflow that works. Build one solid template for each of your three or four most common configurations, then fill in the project fields (address, dates, measured distances, device counts) before each job. That project version gets dated, signed by the competent person, and filed with the job.

SafetyFolio's safety program generator produces a base TCP and work zone safety program in about 15 minutes for contractors who answer a few questions about how they work. You still adapt the site diagram and device counts yourself, but the written structure and required elements come pre-built to OSHA and MUTCD standards.

If your work puts crews near traffic often enough that incident report situations come up, building a TCP template is one of the highest-return moves you can make on both injuries and post-incident liability.

What are the most common TCP violations OSHA cites for paving crews?

Struck-by hazards drive most work zone trouble, and small crews get cited over paperwork more than physical setup. Get the zone right and still get cited if the TCP doesn't document what you did.

BLS data makes the risk concrete. In 2022, struck-by incidents caused 302 construction worker deaths, the second-leading cause of construction fatalities after falls ^[7]. Road work zones are among the highest-risk places for a struck-by event.

The citation categories that come up over and over:

No TCP at all. Common for crews who figure a few cones and one sign covers it.

Devices that miss MUTCD specs. Cones under 28 inches, signs with faded retroreflectivity, arrow boards too small for the road.

Wrong taper lengths. Almost always too short, because the contractor eyeballed it instead of running the formula.

Untrained flagger. A crew member handed a STOP/SLOW paddle with no documented training. OSHA 29 CFR 1926.201(a) requires training. No card, citation ^[1].

Missing high-visibility garments. Workers in the roadway without a Class 2 or Class 3 vest.

No daily inspection. Devices set up on day one and never re-checked.

The thread running through all of it is cutting corners on paper. Write it down. Every day.

How long does it take to write a TCP, and who should write it?

A competent person with the MUTCD nearby can produce a compliant TCP for a common setup, like a single-lane closure on a 35-mph residential street, in two to four hours the first time. Once you've got a template for that configuration, adapting it for the next job takes 30 to 60 minutes.

Who qualifies? OSHA defines a "competent person" as someone who can spot hazardous conditions and has the authority to correct them ^[1]. For traffic control, that person also needs working knowledge of MUTCD Part 6. No engineering degree required. Plenty of experienced foremen with ATSSA Traffic Control Technician (TCT) certification or equivalent state training clear the bar.

For major arterials, highways, or larger projects, some states require a licensed professional engineer to stamp the TCP. California requires a registered traffic engineer (or a civil engineer with traffic credentials) for any TCP on a state highway. Check your state DOT before you assume a contractor-prepared plan is enough.

OSHA's 10-hour and 30-hour construction courses (see our guide to osha 30) cover work zone hazard recognition but don't replace MUTCD-specific traffic control training. A crew lead with both has a stronger claim to competent-person status. If your crew wants a deeper credential, the osha 30 training course is a solid starting point on the regulatory framework.

Frequently asked questions

Is a traffic control plan required for paving a private parking lot?

OSHA standards apply to worker safety whether the lot is private or public, so you still need controls protecting your crew from vehicle hazards under 29 CFR 1926.200. A written TCP makes sense for any job where moving traffic, including customers, can reach workers. Local rules vary, but if the lot borders a public road, a permit is likely required, which usually means a submitted TCP.

What is the difference between a traffic control plan and a traffic management plan?

The terms often get used interchangeably, but some DOTs split them. A traffic control plan (TCP) is the site-specific document covering device placement and work zone layout. A traffic management plan (TMP) is broader and may include detour routing, public notification, and coordination with emergency services. A small paving crew needs a TCP; a full TMP is usually required only on major highway projects.

How many cones does a typical single-lane residential road closure need?

It depends on taper length and spacing, which the MUTCD sets by speed. On a 25-mph street with a 12-foot lane, the formula gives L = (12 × 25) / 60 = 5 feet, but the MUTCD minimum is 100 feet. At 20-foot cone spacing in the taper, that's five cones for the taper alone. Add cones along the work space at 20 to 40-foot intervals. A typical 200-foot residential closure might use 15 to 25 cones total.

Does OSHA require a specific flagger certification?

OSHA 29 CFR 1926.201(a) requires flaggers to be trained but doesn't name a specific certification. ATSSA certification is the most widely recognized, and many state DOTs require it or an equivalent state-issued card. Some states, including California, mandate state-specific training. Keep copies of flagger training certificates in your TCP file; OSHA may ask for them during an inspection.

Can one flagger handle a two-way lane closure alone?

No. A single-lane, two-way operation needs a flagger at each end so drivers on both approaches get controlled alternating passage. MUTCD Part 6E and plain sense both require two. One flagger can't hold sight distance in both directions at once. If you can't staff two, you need a different method such as a temporary signal or a full road closure.

What happens if OSHA inspects and you don't have a TCP?

An inspector can cite you under 29 CFR 1926.200 for failing to provide traffic control devices that meet MUTCD standards. A serious violation carries a penalty up to $16,131 per violation as of 2024. Beyond the fine, the missing TCP badly weakens your position in any workers' comp or liability claim if a worker is struck. OSHA can also issue a willful violation, up to $161,323, if the inspector finds you knew controls were required and ignored them.

Does the MUTCD 11th Edition change anything for small paving contractors?

FHWA finalized the 11th Edition in December 2023 with a phased timeline; states have until late 2025 or 2026 depending on the provision. Changes relevant to paving crews include updated retroreflectivity requirements, revised device color and size standards, and new pedestrian access provisions in work zones. Check your state DOT's adoption timeline, because state supplements can delay when 11th Edition provisions take effect locally.

How do you write a TCP for a paving job on a state highway vs. a local road?

State highway work almost always requires a TCP submitted to and approved by the state DOT before the permit issues, and many states require a licensed engineer's stamp. Local road TCPs are usually contractor-prepared and reviewed by public works or the road commissioner. Both must meet the MUTCD, but submission process, review timeline, and engineering requirements differ. Contact your state DOT permit office early; lead time on a state highway can run two to four weeks.

What high-visibility vest class do paving workers need?

Workers in active roadway zones on federal-aid highways must wear ANSI/ISEA 107 Class 2 or Class 3 garments, per 23 CFR 634. Class 2 provides at least 775 square inches of background material and 201 square inches of retroreflective material. Class 3 provides more coverage and is required in higher-speed or lower-visibility conditions. Flaggers, who face oncoming traffic directly, should wear Class 3. Most state DOTs apply the same rule even on non-federal roads.

How often should you update or revise a traffic control plan during a project?

Any time the physical work zone changes, update the TCP before the new setup goes live. That covers extending the closure, moving the taper, adding night work, or shifting flagger positions. Date and sign every revision. A TCP that describes day one accurately but not day ten is not a valid compliance document. Your daily inspection log should note any deviation and whether the TCP was updated to match.

Are there free resources to help write a traffic control plan?

Yes. FHWA's Work Zone Safety website (ops.fhwa.dot.gov) publishes standard TCP drawings for common configurations. Most state DOTs publish their own standard plan sheets, often free to download. ATSSA sells work zone design guides. The MUTCD itself is free at mutcd.fhwa.dot.gov. For crews who want a pre-structured written program around the TCP, SafetyFolio's safety program generator builds a base program in about 15 minutes that you then adapt to site specifics.

What is a Type C arrow board and when is it required?

A Type C arrow board is the largest category under the MUTCD, at least 48 by 96 inches, and is required for lane closures on high-speed roadways (generally 45 mph and above). Smaller Type A boards (at least 24 by 48 inches) are acceptable in low-speed, low-volume settings. Most state DOTs require a Type C for any single-lane closure on a state route regardless of speed. Your device schedule must specify board type, size, and placement.

Does a paving crew need a TCP for milling only, without paving?

Yes. Milling creates the same struck-by hazards as paving, and the layout requirements are identical. OSHA 29 CFR 1926.200 applies to any construction activity that exposes workers to traffic. The milling machine is itself a hazard to pedestrians and cyclists when it runs near sidewalks or bike lanes. Your TCP should address pedestrian and cyclist access routes around the zone as well as vehicle lane control.

Sources

1. OSHA, 29 CFR 1926 Subpart G (Signs, Signals, and Barricades), 29 CFR 1926.200-203: OSHA requires traffic control devices at construction sites to conform to the MUTCD; flaggers must be trained under 29 CFR 1926.201(a)
2. FHWA, Manual on Uniform Traffic Control Devices (MUTCD) Part 6, 11th Edition: MUTCD Part 6 sets work zone component definitions, taper length formulas, advance warning sign spacing tables (Table 6C-1), device spacing tables (Table 6C-2), arrow board size requirements, and retroreflectivity requirements for night work
3. FHWA, Work Zone Safety Program (23 CFR 630 Subpart J and 23 CFR 634): Federal-aid highway work zone rules at 23 CFR 630 Subpart J and 23 CFR 634 set program requirements and require ANSI/ISEA 107 Class 2 or Class 3 high-visibility garments for workers
4. OSHA, 29 CFR 1904 Recording and Reporting Occupational Injuries and Illnesses: OSHA 29 CFR 1904 requires employers to retain OSHA 300 logs for five years
5. OSHA, Penalties page: As of 2024, OSHA serious violations carry penalties up to $16,131 per violation; willful violations carry penalties up to $161,323 per violation
6. OSHA, Multi-Employer Citation Policy (CPL 02-00-124): Under OSHA's multi-employer citation policy, a controlling employer can be cited for hazards created by a subcontractor on a shared worksite
7. BLS, National Census of Fatal Occupational Injuries in 2022 (CFOI): BLS CFOI 2022 data shows struck-by incidents caused 302 construction worker fatalities, the second-leading cause of construction deaths after falls
8. FHWA, Work Zone Safety Program (ops.fhwa.dot.gov): FHWA Work Zone Safety website publishes standard TCP drawings and traffic control plan templates for common work zone configurations
9. ATSSA, Traffic Control Technician (TCT) Training Program: ATSSA provides the Traffic Control Technician certification recognized by most state DOTs as meeting MUTCD flagger and traffic control training requirements