This guide reviews 60 concepts related to ATSSA’s Traffic Control Supervisor (TCS) training course, spanning plan decisions, devices, road-user protection, field inspection, nighttime work, and supervision. Use it as a study aid; field decisions should follow the applicable approved plan and responsible authority.
TTC foundations and human factors
1. Treat movement and protection as paired objectives
Temporary traffic control (TTC) is not merely a way to keep vehicles moving. Its primary function is to guide road users through or around a work area while protecting road users, workers, incident responders, and equipment. Safety and efficient traffic flow both matter, alongside efficient completion of the work. Use these purposes as the starting point for reviewing any proposed setup.
Worked example: A resurfacing crew closes a lane, but the proposed arrangement gives drivers no clear route through the work. The supervisor identifies both movement and protection as objectives, then seeks a plan that guides users while protecting the crew and equipment.
Mistake to avoid: Focusing only on traffic delay misses the safety purpose; focusing only on the work crew can leave road users without a safe, understandable route.
References: FHWA MUTCD 11th edition Revision 1, December 2025: complete Part 6
2. Include every road user in the initial review
TTC planning includes motorists, bicyclists, pedestrians, and people with disabilities. It can also need to preserve transit operations and access to properties or utilities. Identify who uses the site and what access they need before settling on devices or a traffic pattern. The MUTCD treats safe, accessible passage for all road users as part of TTC planning, not as an optional afterthought.
Worked example: A sidewalk closure is proposed beside a lane shift. The reviewer adds pedestrian access and an accessible route to the issues that must be resolved, rather than treating the vehicle path as the whole plan.
Mistake to avoid: A vehicle-only review overlooks people who walk, cycle, or need accessible passage, and can produce a plan that does not serve the full roadway context.
References: FHWA MUTCD 11th edition Revision 1, December 2025: complete Part 6; FHWA MUTCD11th edition Revision1, December2025: Part1: General
3. Select TTC for the actual site
No single set of TTC devices suits every project. Device needs depend on factors such as highway type, road-user conditions, work duration, physical constraints, and how close the work is to traffic. Apply a typical application as a starting reference, then compare its assumptions with the actual site. Engineering judgment is needed because conditions vary between projects and may change during work.
Worked example: The same contractor proposes the same device layout for a low-speed local street and a high-speed divided highway. The supervisor rejects the assumption that one arrangement fits both and requests a site-specific review.
Mistake to avoid: Copying a familiar layout without checking its assumptions can leave important site risks or road-user needs unaddressed.
References: FHWA MUTCD 11th edition Revision 1, December 2025: complete Part 6
4. Balance project efficiency with safety and access
TTC planning must consider safety, accessibility, road-user flow, and the efficient completion of work together. The MUTCD identifies safety for road users and workers as a high-priority planning element, while also recognizing the need to complete construction and maintenance efficiently. When objectives conflict, identify the competing effects and use the site plan and authorized decision process to resolve them rather than assuming one objective cancels the others.
Worked example: A lane closure would shorten the workday but create a queue that blocks an access point. The supervisor weighs the safety and flow effects and asks whether timing or traffic management can reduce that conflict.
Mistake to avoid: Treating schedule or traffic flow as the only measure of a good plan can conceal unacceptable risks to workers or road users.
References: FHWA MUTCD 11th edition Revision 1, December 2025: complete Part 6
5. Recognize the limits of your decision authority
The MUTCD assigns certain implementation decisions to an engineer or an individual under an engineer’s supervision with suitable experience and expertise. It also distinguishes engineering judgment from an engineering study. A supervisor should recognize when a field choice is outside their authority or expertise and route it to the proper decision-maker. This is a practical boundary, not a reason to ignore an urgent safety concern.
Worked example: A supervisor is asked to approve a device decision that requires engineering judgment. The supervisor checks who has the required expertise and refers the decision to an engineer or a person working under appropriate engineering supervision.
Mistake to avoid: Assuming that a supervisory title alone grants authority to make every engineering decision can lead to an unsupported or unauthorized change.
References: FHWA MUTCD11th edition Revision1, December2025: Part1: General
6. Brief the team before occupation and control changes
A TTC plan should be prepared in a level of detail appropriate to the project’s complexity and understood by responsible parties before the site is occupied. Changes should be approved by an official knowledgeable in proper TTC practices. A supervisor can use a pre-work briefing to establish what the plan requires, identify questions, and make sure that a field suggestion is not mistaken for an approved revision.
Worked example: Before a crew occupies a site, the supervisor finds that the field team has not seen the plan. The supervisor arranges a briefing and clarifies that a proposed plan change needs approval from a knowledgeable official.
Mistake to avoid: Starting work before the responsible parties understand the plan invites inconsistent setup; treating an unapproved field change as authorized bypasses the stated approval process.
References: FHWA MUTCD 11th edition Revision 1, December 2025: complete Part 6
7. Make the reason to slow down perceptible
The MUTCD says TTC design should assume drivers will reduce speed only when they clearly perceive a need to do so. This human-factors principle makes the clarity and timing of warnings important. When reviewing a layout, ask whether road users can recognize the upcoming condition early enough to respond, rather than relying on a posted lower speed alone to produce a change in behavior.
Worked example: Drivers approach a work area at nearly normal speed because the restriction is not apparent. The team improves the warning and path guidance so the need to adjust is perceptible before drivers reach the change.
Mistake to avoid: Relying on a lower speed limit without a clearly perceived need can fail to produce the intended driver response.
References: FHWA MUTCD 11th edition Revision 1, December 2025: complete Part 6
8. Avoid abrupt changes in the road-user path
Frequent, abrupt geometric changes—such as sudden lane narrowing, dropped lanes, or transitions requiring rapid maneuvers—should be avoided. They make the path through the work area harder to anticipate. During plan review, trace the driver’s path from approach to work area and check whether the proposed changes ask for a quick or confusing sequence of movements.
Worked example: A draft shifts traffic twice in quick succession and narrows a lane abruptly. The reviewer identifies the rapid maneuvers and asks the designer to reconsider the sequence before the plan is implemented.
Mistake to avoid: Keeping the work area compact at the cost of abrupt transitions can demand rapid maneuvers that the MUTCD advises avoiding.
References: FHWA MUTCD 11th edition Revision 1, December 2025: complete Part 6
9. Plan for queues beyond the standard warning area
Reduced roadway capacity can create a stopped or slow-moving queue that extends beyond the usual advance-warning signs. Queue length should be assessed during plan design. If the anticipated queue reaches beyond the warning area, the plan may need adjusted sign spacing or quantity, more conspicuous devices, or other measures to provide warning farther upstream. Treat the queue as a planning condition, not merely a delay observed after setup.
Worked example: A planned closure is expected to create a queue longer than the warning area shown in the draft. The reviewer calls for queue assessment and considers extending or strengthening upstream warnings before approving the setup.
Mistake to avoid: Assuming that the usual warning locations will always reach the back of a queue can leave approaching drivers with too little notice.
References: FHWA MUTCD 11th edition Revision 1, December 2025: complete Part 6
10. Match responsibilities to TTC training
People whose actions affect TTC safety should receive training suited to the decisions their roles require. The MUTCD says only people trained in proper TTC practices and familiar with the relevant principles should supervise selecting, placing, and maintaining TTC devices. Supervisors should match responsibilities to training and provide clear oversight, especially when field conditions call for a judgment beyond routine installation.
Worked example: A less experienced worker is assigned to maintain TTC devices while the supervisor is away. The supervisor checks the worker’s training and assigns device decisions and maintenance supervision to appropriately trained personnel.
Mistake to avoid: Assigning device-selection or maintenance oversight to someone without suitable training ignores the MUTCD’s stated qualification principle.
References: FHWA MUTCD 11th edition Revision 1, December 2025: complete Part 6
TTC plans and project decisions
11. Build the plan review around site conditions
A TTC plan should reflect the actual project variables. The MUTCD identifies work location, highway type, geometry, alignment, intersections, interchanges, traffic volume and mix, vehicle mix, and speed among the factors affecting TTC needs. In urban areas, vulnerable road users and access activity may be especially significant. Make the site conditions explicit in review so a plan is not evaluated as if it were for a different roadway.
Worked example: A two-lane urban street has bus stops, frequent driveways, and a high pedestrian presence. The plan reviewer lists these conditions, along with traffic volume and work location, before judging whether the proposed application fits.
Mistake to avoid: Reviewing only the drawing’s lane arrangement can miss user mix, access, or geometry that changes the TTC needs.
References: FHWA MUTCD 11th edition Revision 1, December 2025: complete Part 6
12. Scale plan detail to project complexity
Plan detail should correspond to the complexity of the project or incident. A plan must still be understood by the responsible parties before occupation; simplicity does not mean leaving key decisions ambiguous. The TCS course description emphasizes interpreting plans and specifications and implementing them in the field. In practice, review whether the drawing and its supporting notes communicate the needed setup for this particular operation.
Worked example: A short, straightforward shoulder operation needs a simpler plan than a complex urban closure. In both cases, the responsible team receives enough detail to understand the devices and the intended traffic movement before occupying the site.
Mistake to avoid: Using excessive detail can obscure a simple setup, but omitting essential decisions from a complex plan leaves crews to invent the arrangement.
References: A student receiving less than 80% on the final exam can take a make-up exam for an additional fee. Contact customerservice@atssa.com for more information.; FHWA MUTCD 11th edition Revision 1, December 2025: complete Part 6
13. Use typical applications as references, not templates
MUTCD typical applications illustrate common TTC situations; they do not cover every conceivable work condition. Selecting one requires understanding the site, and the application should be altered when needed to fit local conditions. Use the typical application to identify a relevant starting pattern, then compare its assumptions with the project’s geometry, user mix, and operating conditions before adopting it.
Worked example: A familiar typical application shows a lane closure, but the project also has an unusual driveway conflict. The supervisor uses the application as a reference and requests a site-specific adjustment rather than treating the figure as a complete design.
Mistake to avoid: Treating a typical application as a complete answer can preserve its common-case assumptions even when the site does not meet them.
References: FHWA MUTCD 11th edition Revision 1, December 2025: complete Part 6
14. Adapt device layouts within the stated options
The MUTCD allows devices to supplement those shown in a typical application. It also permits increasing sign spacing and taper lengths to provide additional time or space for driver response, and permits deleting devices identified as optional. Use these provisions to fit the application to site conditions; do not infer that every pictured device is mandatory or that optional devices should always be removed.
Worked example: A selected typical application has an advance-warning arrangement that does not reach a predicted queue. The plan reviewer considers adding devices and increasing warning spacing to suit the conditions, rather than copying the figure unchanged.
Mistake to avoid: Copying every optional detail regardless of need—or deleting it without checking the conditions—confuses a typical illustration with a site-specific decision.
References: FHWA MUTCD 11th edition Revision 1, December 2025: complete Part 6
15. Recognize the legal authority behind traffic controls
The MUTCD says adequate statutory authority should exist for implementing and enforcing needed road-user regulations, parking controls, speed zoning, and traffic-incident management. A supervisor should confirm that proposed controls follow the authority and process applicable to the roadway; a field team cannot create legal authority by choosing a device or posting a restriction.
Worked example: A project proposes restricting parking and lowering a speed limit on a road under agency jurisdiction. The supervisor checks the agency’s authority and approval process before treating either change as authorized.
Mistake to avoid: Assuming a traffic-control plan alone creates legal authority for a restriction can lead to controls the responsible jurisdiction has not authorized.
References: FHWA MUTCD 11th edition Revision 1, December 2025: complete Part 6
16. Keep routine speed-limit reductions limited
Reduced speed zoning should be avoided as much as practical, and any reduced limit should be limited to the portion where conditions or restrictions justify it. The MUTCD says a TTC plan should be designed for a reduction of no more than 10 mph where possible. Calculate the difference from the normal speed limit, then verify that the reduced zone corresponds to the restrictive conditions rather than applying a lower limit throughout the project by default.
Worked example: The normal posted speed is 55 mph, and the draft proposes 45 mph through a restricted portion. The proposed change is 10 mph, within the MUTCD’s stated design target when a reduced limit is used; the reviewer still checks whether the restriction warrants it.
Mistake to avoid: Applying a reduced limit over the whole zone without a site need ignores the guidance to restrict it to the portion with restrictive conditions.
References: FHWA MUTCD 11th edition Revision 1, December 2025: complete Part 6
17. Support a necessary reduction greater than 10 mph
A reduction greater than 10 mph should be used only when restrictive features require it. When it is justified, the MUTCD calls for additional driver notification, a stepped-down speed limit in advance of the lowest-speed point, and additional TTC warning devices. These conditions matter together: a large reduction should not appear suddenly at the restriction or be used without the stated supporting warnings.
Worked example: A restrictive feature makes a 15 mph reduction necessary. The plan steps the limit down before the lowest-speed location and adds driver notification and warning devices; the reviewer confirms that the larger reduction is tied to that feature.
Mistake to avoid: Posting a large reduction without restrictive justification or advance notification fails to preserve the conditions specified for that exception.
References: FHWA MUTCD 11th edition Revision 1, December 2025: complete Part 6
18. Choose work timing for the full operating context
Where work permits, lane closures on high-volume streets and highways should be scheduled during off-peak hours. Night work can help when daytime strategies do not balance safety, traffic, community effects, and constructability, but its advantages depend on reduced traffic and the ability to set up and remove the pattern easily each night. Decide based on the actual operation, not on the assumption that night work is automatically safer or easier.
Worked example: A high-volume street closure is scheduled during the busiest period even though the work can be moved. The project team checks off-peak scheduling; if considering night work, it also verifies that the pattern can be set up and removed and the roadway restored for daytime traffic.
Mistake to avoid: Moving work to night solely to reduce congestion ignores visibility, speed, setup, restoration, and other night-work concerns.
References: FHWA MUTCD 11th edition Revision 1, December 2025: complete Part 6
19. Consider demand management when capacity falls
The MUTCD recommends trying to reduce demand to match the capacity available under a lane closure and encouraging alternative routes. For high-volume roads and freeways, it also recommends evaluating selected entrance-ramp closures or signed diversion routes. These are planning options, not automatic requirements; assess expected traffic and the effect on the surrounding network before selecting them.
Worked example: A freeway lane closure is forecast to exceed available capacity. The team evaluates alternative routes and whether selected entrance ramps or access points should close, then checks that any diversion is included in the plan.
Mistake to avoid: Treating a lane closure as an isolated site decision can overlook demand that exceeds capacity and creates a queue.
References: FHWA MUTCD 11th edition Revision 1, December 2025: complete Part 6
20. Coordinate project interfaces before work starts
TTC planning may need early coordination with officials responsible for affected cross streets and with transit, other highway agencies, emergency services, utilities, schools, trucking groups, or rail organizations. The affected partners depend on the project. Identify interfaces before the work begins, and resolve access or operating conflicts through the responsible parties rather than assuming the contractor’s plan alone addresses them.
Worked example: A road project affects a transit stop, a utility access point, and a nearby cross street. The supervisor identifies each affected party early and coordinates how the plan will maintain access or communicate a change.
Mistake to avoid: Late coordination can reveal access or operational conflicts only after the traffic pattern is in place, when changes are harder to manage.
References: FHWA MUTCD 11th edition Revision 1, December 2025: complete Part 6
Device selection, messages, and visibility
21. Preserve uniformity in device meaning and use
Uniform traffic control devices help road users recognize and understand messages, reducing the time needed to perceive and respond. Uniformity also supports consistent interpretation by road users and enforcement personnel. When selecting or replacing a device, use the applicable standard design and consistent application. A familiar message loses effectiveness if similar situations are treated in visibly different ways without a justified basis.
Worked example: Two crews use different-looking signs for the same warning in comparable situations. The supervisor checks the standard device and restores consistent use, so users can recognize the message without interpreting a novel design.
Mistake to avoid: Using a nonstandard variation for convenience can make a familiar message harder to recognize and weaken consistency.
References: FHWA MUTCD11th edition Revision1, December2025: Part1: General
22. Make messages clear and readable in context
Device design should combine clear meaning with adequate legibility and response time. The MUTCD describes size, shape, color, message simplicity, placement, and legibility as factors that work together to communicate effectively and command respect. Review the message from the road user’s perspective: can it be recognized, read, and acted on in the available approach space? A technically present sign is not useful if its message is unclear.
Worked example: A draft sign carries several long instructions in small text. The reviewer simplifies the message and checks that its size and placement give approaching road users a reasonable chance to read and respond.
Mistake to avoid: Adding detail without considering legibility or response time can make a sign harder to use, not more informative.
References: FHWA MUTCD11th edition Revision1, December2025: Part1: General
23. Check visibility from the approaching user’s view
Traffic control devices should be positioned so road users have adequate time to respond, in both day and night conditions. Placement and operation should also be consistent and uniform. Inspect devices from the direction and path users actually take, rather than judging them only from beside the post. If visibility or response opportunity is inadequate, correct the placement through the applicable plan and approval process.
Worked example: A sign is legible when viewed from directly in front but is partly hidden on the actual approach. The field reviewer checks the approach view in the relevant lighting conditions and requests a placement correction.
Mistake to avoid: A sign’s presence at the worksite does not establish that it can be seen early enough from the approach.
References: FHWA MUTCD11th edition Revision1, December2025: Part1: General
24. Choose devices for roadway, duration, and exposure
Device selection depends on the road, user conditions, work duration, physical constraints, and proximity of the activity to road users. The MUTCD notes that needs on low-volume or special-purpose roads can sometimes be minimal, especially for shorter and lower-speed work, while other settings require different treatment. Use these factors to assess what the site needs; do not infer a universal device count from duration alone.
Worked example: A temporary shoulder operation on a low-speed road is compared with a high-speed, high-volume closure. The reviewer selects devices for each condition instead of assuming that the same set is suitable for both.
Mistake to avoid: Choosing devices only by habit or work duration can leave the setup unsuited to speed, traffic, or the work’s closeness to users.
References: FHWA MUTCD 11th edition Revision 1, December 2025: complete Part 6
25. Use complementary devices to guide the path
The MUTCD identifies pavement markings, signing, and crashworthy, detectable channelizing devices as means of channelizing road users. They guide the path through the TTC zone as a system. In reviewing a setup, check whether the chosen combination makes the intended route understandable and whether the devices meet the relevant requirements for the application; one isolated device may not provide continuous guidance.
Worked example: A proposed channelized path relies on a single warning sign but gives no visible guidance through the changed roadway. The reviewer considers coordinated signing, markings, and detectable crashworthy channelizing devices for the site.
Mistake to avoid: Relying on one device to convey the entire route can leave users without clear, continuous channelization.
References: FHWA MUTCD 11th edition Revision 1, December 2025: complete Part 6
26. Use changeable messages for actionable traffic information
Portable changeable message signs are particularly useful for unexpected situations, including significant queues or delays and changes in alignment or surface. Their purpose is to give information that helps road users decide before reaching the point where action is required. Their messages must be traffic-operation, regulatory, warning, or guidance information; the MUTCD prohibits their use for advertising.
Worked example: A closure will create a substantial delay that is not obvious before drivers reach the decision point. The plan uses a portable changeable message sign to communicate the unexpected condition in time for drivers to choose a response.
Mistake to avoid: A message that is vague, unrelated to traffic, or delivered after the needed decision point does not serve the device’s stated purpose.
References: FHWA MUTCD 11th edition Revision 1, December 2025: complete Part 6
27. Match warning-light type to its intended use
The MUTCD distinguishes warning-light uses: Type A low-intensity flashing lights warn during nighttime; Type B high-intensity flashing lights can warn in daytime and nighttime; Types C and D steady-burn lights may delineate the traveled-way edge at night. When Types C or D delineate a curve, they should be on devices outside the curve, not inside it. Match the light type to the purpose and setting.
Worked example: A team needs a nighttime delineation light, not a warning intended for daytime use. It selects a steady-burn type for the intended nighttime function and checks that curve delineation is on the outside of the curve.
Mistake to avoid: Treating all warning lights as interchangeable ignores their distinct time-of-day uses and the curve-placement guidance.
References: FHWA MUTCD 11th edition Revision 1, December 2025: complete Part 6
28. Understand the limits of temporary lane separators
Temporary lane separators can channelize users or divide traffic lanes, but they are not substitutes for positive protection. The MUTCD requires their attached channelizing devices to be retroreflectorized for nighttime visibility. Their base also has specified dimensions and sloping sides to facilitate emergency-vehicle crossover. When reviewing this device, distinguish its channelizing role from that of a temporary traffic barrier.
Worked example: A plan uses temporary lane separators to divide opposing flows. The inspector checks that their attached channelizing devices are retroreflectorized so the arrangement remains visible at night.
Mistake to avoid: Calling a lane separator worker protection confuses channelization with a device that provides positive protection.
References: FHWA MUTCD 11th edition Revision 1, December 2025: complete Part 6
29. Keep temporary messages traffic-related
Portable changeable message signs are limited to traffic operational, regulatory, warning, and guidance information; they are not for advertising. This is a content boundary, even when the sign is already useful for a closure or delay. Review each displayed message for relevance to road-user decisions and ensure that promotional material does not compete with the TTC information.
Worked example: A project message board includes a sponsor logo and a promotional slogan alongside a closure warning. The reviewer removes the unrelated content and keeps the sign focused on the traffic condition and action information.
Mistake to avoid: Adding advertising to a TTC message sign violates the stated restriction and can distract from road-user information.
References: FHWA MUTCD 11th edition Revision 1, December 2025: complete Part 6
30. Prevent conflicting proceed indications with red/yellow-lens AFADs
For red/yellow-lens AFADs controlling a one-lane, two-way TTC zone, the MUTCD requires safeguards to prevent a flashing circular yellow indication from being actuated at both ends simultaneously. Review the safeguards for this specific setup; this condition should not be generalized to every type of AFAD.
Worked example: A paving operation uses red/yellow-lens AFADs at both ends of a one-lane section. During plan review, the supervisor confirms safeguards prevent simultaneous flashing-yellow indications.
Mistake to avoid: Applying this specific safeguard as a general rule for every AFAD overlooks the one-lane, two-way context stated in the MUTCD.
References: FHWA MUTCD 11th edition Revision 1, December 2025: complete Part 6
Protecting pedestrians, workers, and flaggers
31. Maintain accessible pedestrian passage
TTC planning should preserve access and passage for pedestrians, including people with disabilities, as well as bicyclists. When an existing pedestrian facility is disrupted, the temporary facility needs accessibility features consistent with those in the existing facility. Assess pedestrian movement as part of the plan and check the completed path for continuity, not merely whether signs announce the closure.
Worked example: A roadwork plan closes the existing walkway. The supervisor checks for a continuous accessible pedestrian route or an alternate route, and includes people with disabilities in that review rather than checking vehicle movements alone.
Mistake to avoid: A sign announcing a sidewalk closure is not a substitute for the accessible route or alternate route the situation requires.
References: FHWA MUTCD 11th edition Revision 1, December 2025: complete Part 6; FHWA MUTCD11th edition Revision1, December2025: Part1: General
32. Provide an alternate when closing a pedestrian route
When pedestrian routes are closed, alternate pedestrian routes shall be provided. If facilities are disrupted, closed, or relocated, the temporary facilities shall be detectable and include accessibility features consistent with those of the existing facility. The reviewer should check both the route’s existence and its usability. A closure plan is incomplete if it identifies the obstruction but does not address pedestrian passage.
Worked example: A construction activity blocks the only pedestrian route along a block. The plan provides a signed alternate pedestrian route, then the reviewer verifies that the route is available before the closure takes effect.
Mistake to avoid: Closing a route first and expecting pedestrians to find their own way leaves the required alternate passage unresolved.
References: FHWA MUTCD 11th edition Revision 1, December 2025: complete Part 6
33. Check the full pedestrian path surface
Temporary pedestrian facilities should have a smooth, continuous hard surface throughout. The MUTCD guidance warns against curbs or abrupt changes in grade or terrain that can cause tripping or create barriers for people with disabilities. Inspect the full length of the route, including transitions, rather than checking only its central section. Continuity and surface quality matter at each connection.
Worked example: The temporary path contains an abrupt grade change and loose, uneven ground. The site reviewer requests a smooth, continuous hard surface and removes the abrupt change before the route is treated as ready for use.
Mistake to avoid: Inspecting only the route’s main segment can miss a hazardous or inaccessible transition at its ends.
References: FHWA MUTCD 11th edition Revision 1, December 2025: complete Part 6
34. Direct necessary crossings at suitable locations
Pedestrians should be separated from both work activity and vehicle traffic where possible. If an acceptable route that avoids crossing the roadway cannot be provided, they should be directed with advance signing to cross to the opposite side. In high-volume urban or suburban areas, the MUTCD guidance places such signs at intersections rather than midblock, where a worksite could prompt unsafe crossing behavior.
Worked example: There is no acceptable pedestrian path that avoids crossing the roadway near a worksite. The plan directs pedestrians to an appropriate crossing; in a high-volume urban area, the signs are located at intersections rather than midblock.
Mistake to avoid: Placing a detour sign midblock in a high-volume area can encourage pedestrians to skirt the site or cross midblock.
References: FHWA MUTCD 11th edition Revision 1, December 2025: complete Part 6
35. Maintain both kinds of access to affected transit stops
When work affects or relocates a transit stop, the MUTCD states that both pedestrian and vehicular access to the affected or relocated stop shall be provided. Review the route pedestrians use to reach the stop and the access transit vehicles need to serve it; preserving only one connection does not meet this stated requirement.
Worked example: A project relocates a stop beyond a temporary lane closure. The supervisor checks that a usable pedestrian route reaches the stop and that transit vehicles can access the relocated stopping point.
Mistake to avoid: Saying access should merely be considered weakens the MUTCD requirement that both pedestrian and vehicular access shall be provided.
References: FHWA MUTCD 11th edition Revision 1, December 2025: complete Part 6
36. Keep work movements off pedestrian routes
Movement of work vehicles and equipment across designated pedestrian paths should be minimized and, when necessary, controlled by flaggers or other TTC. Staging or stopping equipment beside the path should be avoided because it encourages workers and materials to cross it. Plan site access to reduce conflicts instead of treating the pedestrian route as a convenient work-vehicle staging area.
Worked example: A work vehicle must cross a temporary pedestrian path to enter the worksite. The supervisor limits crossings, arranges control when a crossing is necessary, and keeps vehicles and materials from being staged along the path.
Mistake to avoid: Routine equipment crossings or roadside staging can undermine separation and prompt pedestrians to make unsafe movements.
References: FHWA MUTCD 11th edition Revision 1, December 2025: complete Part 6
37. Plan activity-area vehicle movements to limit backing
Operations within and around the work space should be planned to minimize backing maneuvers by construction vehicles and equipment. The MUTCD gives reducing run-over and back-over crash risk as the reason. A supervisor can examine the intended circulation and staging plan, identify avoidable reversals, and coordinate a safer movement pattern before the operation begins.
Worked example: A job involves backing trucks near workers in the activity area. The supervisor reviews vehicle entry and exit movements and arranges the operation to reduce backing where practical, lowering exposure to run-over and back-over conflicts.
Mistake to avoid: Treating backing as unavoidable without reviewing the operation misses a stated way to reduce run-over and back-over risk.
References: FHWA MUTCD 11th edition Revision 1, December 2025: complete Part 6
38. Place equipment and materials to reduce roadside exposure
Workers’ private vehicles, equipment, materials, and debris should be stored in a way that reduces the probability of being struck by a run-off-the-road vehicle. Where practical, unencumbered roadside recovery areas should be provided. Review staging as part of worker and road-user protection; the work space is not automatically a safe storage location simply because it is inside the project limits.
Worked example: A crew proposes storing materials and private vehicles between the work space and an exposed roadside edge. The supervisor relocates the staging area to reduce the chance that a run-off-road vehicle will strike them.
Mistake to avoid: Using an exposed recovery area as a storage area can increase the consequences of a vehicle leaving the roadway.
References: FHWA MUTCD 11th edition Revision 1, December 2025: complete Part 6
39. Consider positive protection when exposure is elevated
Positive protection should be considered where it offers strong safety potential, including work with no worker escape route, long-term stationary work, anticipated speeds of at least 45 mph especially with high volumes, work close to open lanes, or overnight roadside hazards. If temporary barriers are used to channelize traffic, they require supplemental delineation, markings, or channelizing devices for visibility; barriers and end treatments must be crashworthy.
Worked example: A long-duration bridge operation leaves workers close to live traffic with little room to escape. The project team evaluates temporary traffic barriers as positive protection and checks that any selected barrier is crashworthy and visible.
Mistake to avoid: Treating ordinary channelizing devices as equivalent to a crashworthy barrier leaves workers without the protection the site may warrant.
References: FHWA MUTCD 11th edition Revision 1, December 2025: complete Part 6
40. Control nighttime visibility, glare, and shadows
Night work reduces visibility even when traffic is lighter, and speeds may be higher. Floodlights should illuminate work areas and equipment crossings while minimizing glare to approaching users, flaggers, and workers. Check lighting by observing or driving through from each approach after setup and periodically. Lighting should make a worker identifiable as a person, and flagger stations should be illuminated at night except in emergencies.
Worked example: A night shift uses floodlights near an approach and has a flagger station. The team drives through the area from both directions to check glare and shadows, adjusts the lights, and illuminates the flagger station.
Mistake to avoid: Brightening a work area without checking glare can impair approaching users; leaving a flagger station unlit conflicts with the stated nighttime provision.
References: FHWA MUTCD 11th edition Revision 1, December 2025: complete Part 6
Field implementation, inspection, and correction
41. Compare the installation with the approved plan
The TCS course trains people to interpret plans and specifications and implement them in the field. MUTCD guidance says the plan should be understood by responsible parties before occupation and changes approved by a knowledgeable official. A practical first field check is therefore to compare the actual installation with the plan, identify differences, and route them through the proper approval process.
Worked example: Before the shift, the supervisor places the approved plan beside the field arrangement and checks whether the installed pattern matches its details. A discrepancy is raised for resolution instead of being accepted because the crew has already started work.
Mistake to avoid: Assuming that a visible setup is acceptable because it is already installed substitutes custom for plan compliance and approval.
References: A student receiving less than 80% on the final exam can take a make-up exam for an additional fee. Contact customerservice@atssa.com for more information.; FHWA MUTCD 11th edition Revision 1, December 2025: complete Part 6
42. Coordinate opposing movements in a one-lane, two-way operation
When both directions must use one lane, their movements shall be coordinated. MUTCD guidance calls for a flagger at each end in typical cases, with one designated coordinator and a means of communication; any manual coordination signals should not be mistaken for flagging signals. A single flagger is an option only when the section is short enough for that person to see end to end and maintain control.
Worked example: On a supervised one-lane, two-way closure, a crest blocks each flagger’s view of the other end. The team assigns a flagger to each end and a coordinator. Using their agreed radio check, the coordinator confirms the previous movement has cleared before authorizing the opposing movement.
Mistake to avoid: Releasing opposing traffic by a timer or assumption, without coordination, can send vehicles into the same restricted lane from both ends.
References: CurrentFHWA MUTCD11th editionRevision1: completeChapter 6D Flagger Control; CurrentFHWA MUTCD11th editionRevision1: completeChapter 6E One-Lane Two-Way Traffic Control
43. Verify required pavement-marking alignment
For long-term stationary TTC zones, the MUTCD says existing pavement markings shall be maintained as specified, and pavement markings shall match the alignment in place at both ends of the zone. Markings shall also be placed along the entire length of a paved detour or temporary roadway before it opens to road users. Inspect the full alignment and tie-ins before traffic is shifted.
Worked example: Before opening a temporary roadway on a long-term project, an inspector checks that its markings extend throughout the route and match the alignments where traffic enters and leaves it.
Mistake to avoid: Describing the required alignment as something markings merely should achieve downgrades a MUTCD Standard expressed with shall.
References: FHWA MUTCD 11th edition Revision 1, December 2025: complete Part 6
44. Remove markings that conflict with the current route
For long-term stationary operations, pavement markings in the temporary traveled way that are no longer applicable should be removed or obliterated as soon as practical. The method should remove the non-applicable material while minimizing pavement scarring. Inspect the traveled way for markings that conflict with the current pattern, rather than assuming that new markings alone will make obsolete ones harmless.
Worked example: The temporary alignment has changed, but old markings still direct drivers into the closed lane. For a long-term operation, the project removes or obliterates markings that no longer apply and minimizes pavement scarring during removal.
Mistake to avoid: Leaving obsolete markings visible can undermine the temporary path even if the new alignment is marked correctly.
References: FHWA MUTCD 11th edition Revision 1, December 2025: complete Part 6
45. Inspect function as well as physical condition
The MUTCD distinguishes functional maintenance—deciding whether devices need to change for current traffic conditions—from physical maintenance that preserves legibility, visibility, mounting, and function. A field inspection should ask both whether the device works physically and whether it remains appropriate. A sound post and clean face do not prove that the device is still the right one for the current operation.
Worked example: A device still stands upright, but its message is hard to read and it no longer fits current traffic conditions. The reviewer flags both physical maintenance and whether the device needs a functional change.
Mistake to avoid: Checking only for breakage misses a device that is readable but no longer appropriate for the traffic conditions.
References: FHWA MUTCD11th edition Revision1, December2025: Part1: General
46. Remove devices when their purpose ends
Unnecessary traffic control devices should be removed. The MUTCD explicitly cautions that a device’s good physical condition is not a reason to delay a needed removal or change. Include the end of the operation in the field check: determine whether each device is still needed for the current traffic condition and remove or change devices that no longer serve it.
Worked example: A completed activity leaves warning signs in place although the road has returned to its ordinary pattern. The supervisor arranges their removal instead of keeping them because they remain in good condition.
Mistake to avoid: Leaving a serviceable but unnecessary device in place can create inconsistent or misleading control.
References: FHWA MUTCD11th edition Revision1, December2025: Part1: General
47. Account for setup and removal exposure
Short-duration work can make setup and removal take longer than the task itself, and workers face hazards during both. The MUTCD says simplified procedures may be warranted after considering these effects, but safety should not be compromised merely because work moves frequently. Base simplification on the operation and site, not on a blanket rule to use fewer devices for short work.
Worked example: A short task takes less time than setting up and removing its TTC pattern, exposing the crew during both operations. The supervisor evaluates a simplified procedure but keeps the safety controls necessary for the site.
Mistake to avoid: Reducing controls solely because the task is brief ignores the explicit caution not to compromise safety.
References: FHWA MUTCD 11th edition Revision 1, December 2025: complete Part 6
48. Keep mobile controls effective as work moves
Short-duration and mobile operations may need devices with greater mobility, including signs on vehicles. The MUTCD allows simplified procedures in some short-duration cases and says fewer devices may be offset by more dominant vehicle warnings. It also cautions that mobile or short work is not a reason by itself to compromise safety. Reassess the control as the work location changes.
Worked example: A mobile crew frequently relocates for brief repairs. The supervisor considers a more visible warning vehicle or other dominant device, while retaining controls needed for each location instead of stripping the setup down automatically.
Mistake to avoid: Applying one reduced device package at every stop ignores changing locations and the requirement to preserve safety.
References: FHWA MUTCD 11th edition Revision 1, December 2025: complete Part 6
49. Distinguish merging tapers from longitudinal buffer spaces
A merging taper requires at least L, calculated using the applicable Table 6B-4 formula and speed basis; at 45 mph or more, L = W × S. A buffer is a separate lateral or longitudinal separation area that may provide recovery space. Table 6B-2 stopping-sight-distance values may be used to determine longitudinal buffer length, but do not make every buffer a fixed length. Work activity and storage of equipment, vehicles, or material should not occur in a buffer.
Worked example: For a supervised design review, assume an anticipated operating speed of 50 mph and a 12-foot offset for a merging taper. Since 50 mph is at least 45 mph, L = 12 ft × 50 = 600 ft, so the merging taper should be at least 600 ft. Separately, Table 6B-2 lists 425 ft at 50 mph as a value that may be used to determine a longitudinal buffer; it is not the taper calculation or a universal buffer requirement.
Mistake to avoid: Using the shifting-taper fraction for a merge, or treating the buffer as space for workers or stored equipment, confuses distinct functions and geometry.
References: CurrentFHWA MUTCD11th editionRevision1: completeChapter 6B Temporary Traffic Control Elements
50. Inspect crash cushions and promptly address damage
Crash cushions must be crashworthy and designed for their intended application. The MUTCD says they shall be periodically inspected to verify that they have not been hit or damaged; damaged crash cushions shall be promptly repaired or replaced to maintain crashworthiness. Include their condition in ongoing field checks and ensure damage is addressed before relying on them for protection.
Worked example: During a routine inspection of a work-zone approach, a supervisor finds a crash cushion with visible impact damage and arranges prompt repair or replacement before accepting it as serviceable.
Mistake to avoid: Assuming a crash cushion remains effective because it is still in place overlooks the required inspection and prompt response to damage.
References: FHWA MUTCD 11th edition Revision 1, December 2025: complete Part 6
Supervision, authority, and coordination
51. Identify the authority responsible for the roadway
The MUTCD assigns responsibility for TTC plans and devices to the public body or official with jurisdiction over the roadway, or to the owner of a site roadway open to public travel. A supervisor should identify the responsible authority when a decision exceeds the crew’s role. This distinction helps prevent a contractor’s field preference from being mistaken for the jurisdiction’s approved direction.
Worked example: A proposed device decision has regulatory implications and the field team is unsure who may authorize it. The supervisor refers the issue to the public body or official responsible for guiding road users on that facility.
Mistake to avoid: Assuming that the work crew alone controls traffic-device decisions can ignore the jurisdictional responsibility stated in the MUTCD.
References: FHWA MUTCD 11th edition Revision 1, December 2025: complete Part 6
52. Separate technical advice from agency implementation
MUTCD decisions that require implementation are to be made by an engineer or someone under an engineer’s supervision with appropriate experience and expertise, using engineering judgment or study as required. The Manual also explains that the agency having jurisdiction makes the final decision to implement an engineering-based solution after consultation. Keep technical development, advice, and final agency implementation distinct.
Worked example: An unusual site condition does not fit a standard device application. The supervisor gathers the relevant facts and refers the decision to an engineer or appropriately supervised person, while the agency retains its role in deciding whether to implement the solution.
Mistake to avoid: Treating an engineering recommendation as automatic field authorization confuses the roles described in the MUTCD.
References: FHWA MUTCD11th edition Revision1, December2025: Part1: General
53. Check applicable adoption and compliance provisions
The MUTCD contains provisions for adoption and compliance, including that new or reconstructed devices installed after the relevant effective date or state adoption must comply as specified. Existing noncompliant devices are addressed through systematic upgrading, subject to the Manual’s provisions. Because adoption and applicability depend on the facility and circumstances, a supervisor should consult the governing agency requirements instead of inventing a universal date or rule.
Worked example: A supervisor is asked whether a new edition automatically changes every existing device immediately. The supervisor checks the applicable adoption and compliance provisions rather than announcing a blanket deadline unsupported by the project information.
Mistake to avoid: Applying a single assumed compliance date to every facility can misstate the adoption and transition rules.
References: FHWA MUTCD11th edition Revision1, December2025: Part1: General
54. Check the approach-lane condition before using an AFAD
Automated Flagger Assistance Devices (AFADs) allow a flagger to be positioned out of the traffic lane and are remotely operated. The MUTCD says they shall be used only where there is one lane of approaching traffic in the direction to be controlled. They may be appropriate for short- or intermediate-term activities, with examples including bridge maintenance, haul-road crossings, and pavement patching.
Worked example: A one-lane operation uses an automated flagger assistance device. Before accepting the proposal, the supervisor verifies that there is only one lane of approaching traffic in the direction being controlled.
Mistake to avoid: Assuming an AFAD is suitable for multiple approaching lanes conflicts with the stated single-lane limitation.
References: FHWA MUTCD 11th edition Revision 1, December 2025: complete Part 6
55. Include AFAD location lighting in night plans
When an AFAD is used at night, its location shall be illuminated in accordance with the cited MUTCD provision. An AFAD controls road users; it does not remove the need to verify the overall TTC arrangement or the suitability of the site. Review the time of operation and illumination as part of the selection, and do not assume that remote operation makes nighttime visibility irrelevant.
Worked example: An AFAD is proposed for a nighttime operation. The supervisor confirms that the location will be illuminated and checks that the planned arrangement follows the device’s operating requirements.
Mistake to avoid: Planning only for the device’s remote operation overlooks the explicit nighttime illumination condition.
References: FHWA MUTCD 11th edition Revision 1, December 2025: complete Part 6
56. Use qualified personnel for incident traffic control
For incidents, if manual traffic control is needed, the MUTCD guidance calls for qualified flaggers or uniformed law-enforcement officers. Interagency planning can support timely establishment, maintenance, and removal of diversions. The supervisor should coordinate the control method with responders and protect the traffic flow through the scene rather than assuming that any available person can perform flagging.
Worked example: A traffic incident requires manual control while a lane diversion is established. The team assigns qualified flaggers or uniformed law-enforcement officers and coordinates device deployment with the agencies responding to the incident.
Mistake to avoid: Assigning manual control to an unqualified person ignores the stated qualification guidance and can create inconsistent directions.
References: FHWA MUTCD 11th edition Revision 1, December 2025: complete Part 6
57. Weigh both advantages and risks of night work
Night work can reduce congestion and business impacts, but its advantages normally depend on reduced traffic and easy nightly setup and removal. It also brings reduced visibility, often higher speeds when traffic is lighter, and potential impaired, fatigued, or drowsy drivers. Consider the advantages alongside safety, productivity, social, economic, and environmental effects before deciding that night work is preferable.
Worked example: A project is moved to night to reduce congestion. The manager compares that benefit with reduced visibility and potentially higher speeds, and confirms the work can be completed and the road restored for higher daytime traffic.
Mistake to avoid: Equating lower traffic volume with lower overall risk ignores the visibility and speed concerns identified for night operations.
References: FHWA MUTCD 11th edition Revision 1, December 2025: complete Part 6
58. Coordinate agencies and communicate route changes
Early coordination with affected agencies and services can reduce unusual or conflicting road-user situations. The MUTCD also notes that public information about the work, schedule, effects, and alternate routes can reduce the number of users traveling through a TTC zone. In suitable settings, intelligent transportation systems can support monitoring, warnings, traveler information, and traffic management.
Worked example: A project’s diversion affects several agencies, while the closure creates a queue. The supervisor initiates coordination and supports clear public information about the work, timing, effects, and alternate routes.
Mistake to avoid: Keeping the public and affected agencies uninformed can leave travelers unprepared and increase avoidable conflicts or demand at the worksite.
References: FHWA MUTCD 11th edition Revision 1, December 2025: complete Part 6
59. Distinguish course completion from certification
ATSSA’s course description identifies a written final exam and says a passing result earns an attendance certificate. ATSSA’s Model Training Specifications separately describe certification criteria, including an independent certification body. These are distinct statements: course completion and certification are not interchangeable, and the model specification should not be presented as a universal state rule.
Worked example: A candidate completes the course’s written exam and receives the course attendance certificate described in the course information. They do not treat that result alone as proof of certification under every jurisdiction’s rules.
Mistake to avoid: Calling an attendance certificate a universal professional certification misstates what the supplied course description establishes.
References: ATSSA Model Training Specifications; A student receiving less than 80% on the final exam can take a make-up exam for an additional fee. Contact customerservice@atssa.com for more information.
60. Resolve field discrepancies through a clear decision path
A useful supervisory response links observation, plan, risk, authority, and communication. Compare the site with the understood plan, consider effects on all road users and workers, and route a proposed plan change to a knowledgeable official for approval. Once resolved, make sure responsible parties understand the direction before relying on the revised setup. This approach applies the course’s emphasis on implementation and deficiency correction without assuming authority the supervisor may not hold.
Worked example: A field discrepancy affects a pedestrian route and an advance warning sign. The supervisor compares the setup with the plan, identifies the safety and access effects, assigns the issue to the appropriate decision-maker, and ensures the responsible crew receives the approved direction.
Mistake to avoid: Changing the setup informally and failing to communicate the approved direction can leave the crew working from conflicting versions of the plan.
References: ATSSA Model Training Specifications; A student receiving less than 80% on the final exam can take a make-up exam for an additional fee. Contact customerservice@atssa.com for more information.; FHWA MUTCD 11th edition Revision 1, December 2025: complete Part 6
Sources
Source check:
- Featured Roadway Safety Training Courses | ATSSA
- ATSSA Model Training Specifications
- A student receiving less than 80% on the final exam can take a make-up exam for an additional fee. Contact customerservice@atssa.com for more information.
- FHWA MUTCD 11th edition Revision 1, December 2025: complete Part 6
- FHWA MUTCD11th edition Revision1, December2025: Part1: General
- CurrentFHWA MUTCD11th editionRevision1: completeChapter 6B Temporary Traffic Control Elements
- CurrentFHWA MUTCD11th editionRevision1: completeChapter 6C Pedestrian and Worker Safety
- CurrentFHWA MUTCD11th editionRevision1: completeChapter 6D Flagger Control
- CurrentFHWA MUTCD11th editionRevision1: completeChapter 6E One-Lane Two-Way Traffic Control