Visit Website →
← Back to blog

Defensible Signal Warrant Study: U.S. Playbook for Nine MUTCD Warrants

September 26, 2026
Defensible Signal Warrant Study: U.S. Playbook for Nine MUTCD Warrants

A signal warrant study is an engineering study, grounded in MUTCD Chapter 4C and any state supplements, that documents whether traffic, pedestrian, or safety conditions meet one or more of the nine warrants. Meeting a warrant is a screening result, not an approval. The final product is a signed engineering recommendation weighing alternatives, safety, and operations, submitted under the agency's own forms and review process. Confirm the controlling MUTCD edition and local supplement before a single count begins.

TL;DR:

  • Meeting a MUTCD warrant only prompts a closer review; actual installation requires a comprehensive engineering judgment considering safety, operations, and alternatives.
  • Accurate data collection includes multi-day volume counts, crash history, pedestrian gaps, and turning movements, with clear differentiation between observed and forecast traffic.
  • Warrant 1 and Warrant 3 are most commonly checked first, but Warrant 3 demands careful interpretation to avoid misapplication for short demand spikes.
  • Crash data should be at least 12 months old, and signals based solely on crash history need supporting evidence of correctable crash types and prior trials of measures.
  • Proper documentation of the study scope, geometry, traffic counts, crash summaries, and final recommendation is essential for a defendable and review-ready submission.
Urban Planning Pros
Plan Land Decisions With More Clarity
Urban Planning Pros evaluates property documents, zoning constraints, and market direction to help landowners and developers make informed decisions.
Explore Urban Planning Pros

Table of Contents

What Are the Nine MUTCD Signal Warrants?

Every signal warrant study starts with the same question: which of the nine screening tests actually apply to this intersection? The MUTCD sets these out as minimum thresholds, and each one targets a different failure mode at an intersection, from raw volume to crash history to network coordination.

Here is the short version of each:

  • Warrant 1, Eight-Hour Vehicular Volume: screens for sustained traffic demand across two conditions, minimum volume and interruption of continuous traffic.
  • Warrant 2, Four-Hour Vehicular Volume: plots four representative hours against a volume curve to catch moderate, steady demand that Warrant 1 might miss.
  • Warrant 3, Peak Hour: targets short, intense demand spikes, like a single dominant commuting hour, that don't sustain across eight or four hours.
  • Warrant 4, Pedestrian Volume: screens for pedestrian crossing demand and inadequate gaps in vehicular traffic.
  • Warrant 5, School Crossing: applies specifically to established school crossings with documented student volumes.
  • Warrant 6, Coordinated Signal System: justifies a new signal on progression or platooning grounds within an existing corridor.
  • Warrant 7, Crash Experience: looks at crash history correctable by signal control, paired with a minimum volume showing exposure.
  • Warrant 8, Roadway Network: justifies a signal based on the intersection's role in a broader street network, even without meeting other volume thresholds.
  • Warrant 9, Intersection Near a Grade Crossing: applies narrowly where rail crossing proximity is the dominant safety concern.

Federal MUTCD adoption sets the floor, but many states, including several across the Urban Planning Pros service area, layer on supplements, district-level review forms, or modified thresholds. Missouri's Engineering Policy Guide is one example of a state manual that adds operational detail on top of the federal chapter, including right-turn inclusion guidance. None of the nine warrants function as a mandate on their own. Satisfying a threshold simply means the intersection has earned a closer look, and the TTI guidance on conducting warrant analysis treats that closer look, not the raw numbers, as the real engineering work.

How Do You Structure a Defensible Data Package?

A warrant worksheet is only as good as the data behind it, and reviewers can tell within minutes whether a count package was rushed. The workflow below reflects how a defensible study typically comes together, drawing on the phased approach TTI's guidelines recommend and the practical checklist municipal traffic studies commonly follow.

  1. Confirm authority and scope. Identify which agency controls the intersection, which MUTCD edition and state supplement governs, and what forms the reviewing agency expects.
  2. Document geometry and context. Record lane configuration, median presence, channelization, sight lines, and posted speed before counting anything.
  3. Select counting windows. Choose representative days (typically Tuesday through Thursday, non-holiday) and confirm the peak periods actually reflect normal demand.
  4. Collect turning-movement counts. Break volumes into 15-minute intervals to build the 8 highest hours needed for Warrant 1 and the peak-hour data needed for Warrant 3.
  5. Layer in pedestrian counts, crash records, and operational observations. Pull at minimum 12 months of crash history, and log queue lengths, delay, and any sight-distance obstructions.
  6. Assemble and cross-check the package. Verify that hourly totals, pedestrian counts, and crash summaries are internally consistent before running the warrant worksheets.

Sites under active development complicate this. When a signal request is tied to projected trips from a project not yet built, the study needs to separate observed background traffic from forecast site traffic, with growth rates and pass-by assumptions documented explicitly rather than buried in a spreadsheet. The MUTCD's own guidance on signal needs studies requires that a signal installed on projected volumes get re-evaluated within a year of installation, confirming the projection actually materialized, except where Warrant 8 independently justifies the signal on network grounds.

Pro Tip: Pull crash data before you schedule your traffic counts. If the crash history is thin or the types aren't signal-correctable, you may be able to skip a full eight-hour count push and focus resources on the warrants that actually have a shot.

Warrant 1: How Does Eight-Hour Volume Counting Work?

Warrant 1 has two conditions. Condition A sets a minimum vehicular volume threshold across eight hours, aimed at intersections with heavy traffic on both approaches. Condition B, interruption of continuous traffic, targets a different problem: a minor street struggling to break into major-street flow, even if total volumes are lower.

Warrant 1: How Does Eight-Hour Volume Counting Work? — overview diagram

Both conditions rely on selecting the correct 8 highest hours from a full day of counts, not simply the morning and evening peaks by default. Where the intersection sits in a rural area or a small, isolated community, or where the 85th-percentile speed on the major street exceeds 40 mph, the MUTCD allows reduced thresholds, commonly applied at 70% for Condition A and 56% for Condition B columns.

Common mistakes worth avoiding:

  • Using only peak-hour data and assuming it represents all 8 hours.
  • Forgetting to check whether the speed or population exception applies before defaulting to the full-volume columns.
  • Mixing raw approach counts with adjusted counts inconsistently across the two conditions.

Warrant 2: How Do You Plot Four-Hour Volumes Correctly?

Warrant 2 works by plotting, for each of four representative hours, the total major-street volume (both approaches) against the higher-volume minor-street approach. Each hour becomes a single point, and if enough points fall above the applicable curve in the MUTCD, the warrant is met.

Which curve applies depends on lane configuration on each approach, and the same speed and population exceptions from Warrant 1 apply here too, shifting the curve downward.

  • Start with a quick hourly screen using existing or short-duration counts to see whether any hours are close to the curve.
  • If several hours look borderline, invest in a full multi-hour count before drawing conclusions.
  • Match the lane-combination curve to actual approach lanes, not the design lanes shown on old plans.

Warrant 3: When Does Peak Hour Delay Justify a Signal?

Warrant 3 exists for intersections where demand spikes hard for a single hour and nowhere else, a pattern that a shift change, a school dismissal wave, or a single dominant employer can create. It has two paths.

Category A measures stopped-time delay on the minor-street approach, paired with a minor-street volume floor, both of which must be met within the same peak hour. Category B is a plotted test, similar in structure to Warrant 2 but restricted to a single hour rather than four.

  • Category A requires both the delay threshold and the volume floor in the same hour, not averaged across the day.
  • Category B uses the same lane-combination curves as Warrant 2, scaled for one hour.
  • Where a signal is justified only under Warrant 3, agencies often recommend flashing operation outside the peak period rather than full-time fixed-time control.

Pro Tip: Warrant 3 is the one practitioners misuse most often. It's built for unusual, short-duration demand, not as a shortcut around the eight-hour or four-hour tests when those don't quite pencil out.

Warrant 4: How Do Pedestrian Counts and Gaps Work?

Warrant 4 screens for pedestrian crossing demand against inadequate gaps in traffic, using both a four-hour threshold and a one-hour threshold as alternate paths to satisfaction. The gap side of the test looks at whether fewer than 60 adequate gaps per hour exist in the traffic stream during the study period.

  • Count pedestrians separately for each crossing direction, and where a median or refuge island exists, treat each half of the crossing as its own gap analysis.
  • The warrant generally does not apply within roughly 300 feet of an existing signalized intersection, since pedestrians there have another crossing option.
  • Field observers should log gap counts concurrently with pedestrian counts, not as a separate follow-up visit, since traffic patterns shift day to day.

Warrant 5: How Do You Document a School Crossing Study?

Warrant 5 is the most schedule-sensitive of the nine. It requires at least 20 students during the highest crossing hour, compared against available gaps relative to the number of minutes in that period, following the same gap-adequacy logic as Warrant 4 but scoped to school arrival and dismissal windows.

  • Coordinate directly with the school to confirm bell times and any variation by grade level or bus schedule.
  • Document actual student counts by direction, not enrollment figures, since not every student crosses at the study location.
  • Note existing crossing guard coverage, since agencies weigh current supervision when deciding whether a signal changes the safety picture meaningfully.

Agencies commonly request an appendix showing the school's daily schedule alongside the count sheets, since reviewers want to confirm the observation window actually captured peak crossing demand rather than a quiet period.

Warrant 6: When Does Signal Coordination Justify a New Signal?

Warrant 6 differs from the others because it isn't about the intersection in isolation. It justifies a new signal when adding it maintains platooning and progression along an already-coordinated corridor, typically where uncontrolled gaps in an otherwise signalized system disrupt travel-time consistency.

  • The case for Warrant 6 usually starts with a corridor-level timing analysis showing where platoons currently break down.
  • Engineers should model how the proposed signal's cycle length and offset would integrate with adjacent signals, not just how it performs standalone.
  • Documentation should include existing coordination timing plans and the projected timing plan with the new signal inserted.

Because this warrant affects every signal in the coordinated group, agencies typically want to see mitigation for any progression loss at neighboring intersections before signing off.

Warrant 7: What Crash History Actually Supports a Signal?

Warrant 7 requires five or more reported crashes in a 12-month period, of types that a signal could reasonably correct, such as angle collisions or left-turn conflicts, combined with a minimum volume showing adequate exposure and a documented trial of less restrictive measures.

Not every crash counts. Rear-end collisions, for instance, often signal that a corridor already has too much stop-and-go, and adding a signal can sometimes increase rather than reduce them.

The City of Anna, Texas warrant study is a useful real-world illustration here: the intersection met the Peak Hour warrant, yet the engineering recommendation still came back against installation, because the crash pattern and progression impacts didn't support it. Crash counts alone, especially over a single year, can be distorted by regression to the mean, a handful of crashes clustering in one period. This is why prediction models or empirical-Bayes methods are increasingly used to separate a genuine safety problem from statistical noise.

  • Confirm crash types are signal-correctable before counting them toward the threshold.
  • Cross-check exposure, since five crashes at a low-volume approach mean something different than five crashes at a high-volume one.
  • Document any prior trial of signing, striping, or enforcement changes and their measured effect before relying on the crash warrant alone.

Warrant 8: How Do You Justify a Signal on Network Grounds?

Warrant 8 applies where the intersection's role in a broader roadway network justifies control, independent of the standalone volume tests. It requires a combined vehicular volume of at least 1,000 vehicles per hour during the peak, tested across five hours of an average day, and it's the warrant most often invoked for intersections tied to sites still under development.

  • Confirm the 1,000 vph threshold applies to the combined approach volumes during the peak hour, not a daily average.
  • Document five-year traffic projections with explicit growth rate, background traffic, and pass-by trip assumptions spelled out for reviewers, following the same forecast-documentation discipline the MUTCD calls for.
  • Flag clearly whether the analysis relies on non-normal-day traffic patterns, since Warrant 8 explicitly accounts for those.

If a signal goes in based on projected volumes under Warrant 8, most agencies still expect a follow-up traffic study within a year of opening to confirm the projection held.

Warrant 9: When Is Grade Crossing Proximity the Deciding Factor?

Warrant 9 is narrow by design. It applies where an intersection's proximity to a railroad grade crossing is the principal safety concern, not simply one factor among several. Before relying on this warrant, the study needs to show that other alternatives, additional pavement width, revised stop control, or channelization, were considered and found inadequate.

  • Document train frequency, typical dwell time on the crossing, and any history of vehicles queuing across the tracks.
  • Include sight-distance measurements between the intersection and the crossing, and contact notes from coordination with the railroad operator.
  • Present any trial period results, such as temporary signing or restriped stop bars, and explain why they didn't resolve the queuing risk.

Railroad coordination adds a layer most other warrants don't require, so build in extra lead time for that outreach.

How Do You Turn Warrant Results Into a Defensible Recommendation?

Meeting a warrant answers one question. Recommending a signal answers a different one: does installing it actually improve safety and operations at this location, on balance? That second question is where the real engineering judgment lives, and it's where reviewers spend most of their attention.

  1. List the non-signal alternatives first. All-way stop control, roundabouts, access management, added turn lanes, or revised signing frequently address the same problem without the maintenance burden and rear-end crash risk a signal can introduce.
  2. Weigh the negative signal impacts. New signals commonly shift crash patterns from angle to rear-end, add queuing on the minor approach during off-peak hours, and can disrupt progression on an otherwise coordinated corridor.
  3. Propose mitigation for whichever trade-offs you accept. If progression loss is unavoidable, document the retiming plan for adjacent signals. If rear-end risk is a concern, address approach sight distance and advance warning.
  4. Write the recommendation to stand alone. A reviewer should be able to read the signed recommendation without cross-referencing the raw worksheets to understand why the engineer reached that conclusion.

The Anna, Texas example is instructive again here: meeting Warrant 3 was not treated as the end of the analysis. The final call weighed progression and safety trade-offs against the marginal benefit of installation, and the recommendation went the other way. That is exactly the kind of judgment a defensible signal warrant study needs to show its work on, not bury.

What Belongs in the Final Agency Submittal?

A complete submittal package needs to hold up on its own if a different engineer picks it up years later. At minimum, agencies expect:

  • A location sketch showing the intersection in context, including nearby signals, schools, and rail crossings.
  • A condition diagram documenting lane geometry, channelization, and posted speeds.
  • Turning-movement tables broken into 15-minute intervals for each counted period.
  • Pedestrian count worksheets, including gap-adequacy calculations where relevant.
  • A crash summary table and collision diagram covering at least 12 months.
  • Completed warrant worksheets for every warrant screened, met or not.
  • A signed engineering recommendation summarizing the findings and the final call.

Many states require their own forms on top of this, similar to district-level warrant sheets used in Missouri's Engineering Policy Guide, so confirm local requirements before assembling appendices. Retain the underlying count sheets and field notes for the period your agency's records policy requires, since reviewer comments sometimes arrive months after submittal and reference raw data, not just the summary tables.

What Practical Mistakes Slow Down Warrant Study Approval?

Small errors in count interpretation cause more rework than any warrant threshold ever will. Right-turn volumes are the most common culprit: whether to count a free-flowing right turn on a channelized approach the same as a signal-controlled right turn changes warrant outcomes materially, and research on right-turn volume adjustment shows this isn't a minor rounding issue. Some agencies apply a percentage reduction to right turns on exclusive lanes with adequate acceleration distance; others exclude them from the warrant count entirely when a free-right condition exists.

Comparison of right-turn lane configurations

Development-related studies bring a second common trap: mixing observed counts with forecast trips without labeling which is which. Keep them in separate columns, with growth rate and trip-generation assumptions documented in an appendix, not folded into the raw count sheet.

Pro Tip: Before submitting, run a quick QA pass on your own worksheets: confirm the sampling hours actually match a normal weekday, check that count equipment was calibrated or spot-checked against manual counts, and make sure every appendix a reviewer might ask for is already attached rather than promised in the narrative.

Our Approach to Signal Warrant Studies

A signal warrant study should start by confirming jurisdiction, building a complete data package, and testing alternatives before recommending a signal. Our feasibility and surveying teams support the geometry and condition documentation that warrant worksheets depend on. A consultant earns its fee when a project's traffic picture is still forming, background growth, pass-by assumptions, phased build-out, and an agency-led study makes more sense once conditions are stable and the count window is straightforward.

— Jeremy Wenger

Let Urban Planning Pros Handle the Data Package

A signal warrant study lives or dies on the quality of its underlying data, and that's precisely where most projects lose time. A defensible warrant analysis typically includes feasibility work that separates observed conditions from projected demand, topographic survey for accurate condition diagrams, and technical documentation designed to withstand agency review.

Urban Planning Pros

For a site still moving through zoning or entitlement, the traffic picture is rarely stable enough for a straightforward count-and-plot exercise. That's where our feasibility services fit: we help document the growth assumptions, pass-by rates, and phasing details a warrant study's projection section needs to hold up under review. Pair that with topographic and existing conditions survey work for the geometry appendix, and your engineer of record has a complete package instead of a partial one. Visit our services page to scope a warrant study support engagement, or start with a feasibility conversation if your site's future traffic volumes are still an open question.

Sources

FAQ

What Is the Difference Between a Warrant and a Signal Recommendation?

A warrant is a screening threshold defined in MUTCD Chapter 4C; meeting one flags the intersection for further study. A signal recommendation is the engineer's final judgment call, weighing alternatives and operational trade-offs, which can go against installation even when a warrant is met.

Which Warrant Is Most Commonly Met in Practice?

Warrant 1 (Eight-Hour Vehicular Volume) and Warrant 3 (Peak Hour) tend to be checked first because they rely on standard turning-movement counts most agencies already collect. Warrant 3 is also the one most often misapplied to demand patterns that don't actually qualify as short-duration spikes.

Do You Need All Twelve Months of Crash Data Before Starting?

Warrant 7 requires a minimum of 12 months of crash history, and most agencies expect the most recent complete year rather than a partial or outdated period. Starting the crash pull early, before scheduling traffic counts, helps determine whether that warrant is even worth pursuing.

Can a Consultant Complete a Signal Warrant Study Instead of the Agency?

Yes, many agencies accept warrant studies prepared by a qualified consulting engineer, provided the final recommendation carries a signed engineering seal and follows the local submittal format. Urban Planning Pros supports the feasibility, survey, and documentation phases of these studies through its services, particularly for development-related sites where projected traffic needs careful documentation.

What Happens if No Warrant Is Met?

If no warrant is satisfied, the standard recommendation is against signal installation, often paired with alternative suggestions like signing, striping, or minor geometric changes. Some agencies will revisit the study after a set period if development or traffic patterns change materially.