Conemap
Requirements/Arizona

Maricopa County (MCDOT) traffic control plan requirements

MCDOT uses two different submittal forms — one for MCDOT projects and one for permit work. Submitting on the wrong form is an automatic rejection. The MCDOT MAG Supplement and the MCDOT Traffic Control Manual govern where they differ from the federal MUTCD.

Check a plan against these rulesWhere to submit

Published requirements

Transcribed from Maricopa County (MCDOT)'s own published document. Each entry cites where it came from and when it was last checked.

  • The contractor shall maintain a twelve (12) foot lane width unless otherwise approved by the MCDOT Engineer.

    12 ft

    Maricopa County MCDOT TCP Submittal Form, General Note 6 · Verified 2026-08-25

  • A minimum of two (2) working days are required for all traffic control plan reviews. The MCDOT MAG Supplement Section 401.4.1 allows up to ten (10) working days for TCP review.

    2 days

    Maricopa County MCDOT TCP Submittal Form, General Note 1 · Verified 2026-08-25

  • All advance warning signs shall be 48" x 48", on spring stands, with flags, lights, and ballasted unless otherwise approved by the MCDOT Engineer.

    48 text

    Maricopa County MCDOT TCP Submittal Form, General Note 4 · Verified 2026-08-25

  • All traffic control devices shall be NCHRP 350 or AASHTO MASH compliant.

    Maricopa County MCDOT TCP Submittal Form, General Note 3 · Verified 2026-08-25

  • Traffic control flaggers shall be certified, properly equipped, and use Stop/Slow paddles (not flags). Flag person signs shall be removed or turned away from traffic when flaggers are not present.

    Maricopa County MCDOT TCP Submittal Form, General Note 13 · Verified 2026-08-25

  • Uniformed, off-duty officers shall be required when working within three hundred feet (300’) of signalized intersections.

    300 ft

    Maricopa County MCDOT TCP Submittal Form, General Note 12 · Verified 2026-08-25

  • The plan shall include a detailed site plan showing existing signing, striping, posted speed limits, road names, required devices, tapers, pedestrian walkways, bike lanes, driveways and access points, parking, construction fences, jurisdictional boundaries, phase of work, true north, and all dimensions. There shall be a legend.

    Maricopa County MCDOT TCP Submittal Form, General Note 14 · Verified 2026-08-25

Source

https://www.maricopa.gov/DocumentCenter/View/39195/Traffic-Control-Plan-Submittal---ConstructionMaintenance-PDF

Agencies revise these documents without notice. If something here is out of date, tell us at hello@conemap.com and it will be corrected. Report a discrepancy.

Taper length for a Maricopa County (MCDOT) work zone

Taper geometry is federal — it comes from MUTCD 11th Edition Tables 6B-3 and 6B-4 wherever you are. What Maricopa County (MCDOT) adds is the checklist above.

Posted speed limit, off-peak 85th-percentile speed prior to work starting, or anticipated operating speed.

ft

How far traffic is moved sideways — usually the width of the closed lane.

Open this in the plan builder

Merging taper length

245ft

L = W × S² ÷ 60 = 12 × 35² ÷ 60 = 245.0 ft

MUTCD 11th Ed, Tables 6B-3 and 6B-4 — at least L

Plan view

8 devices at 35 ft
245 ft12′

Length is to scale; the lateral offset is exaggerated so the taper is legible.

All taper types at these conditions

MUTCD 11th Ed, Table 6B-3

Merging taper

at least L

245 ft

Shifting taper

at least 0.5 L

125 ft

Shoulder taper

at least 0.33 L

85 ft

One-lane, two-way traffic taper

50 ft min, 100 ft max

50 ft

Downstream taper

50 ft min, 100 ft max

50 ft

Channelizing devices

MUTCD 11th Ed, Section 6K.01

Maximum spacing in this taper

1 × 35 mph

35 ft

Devices required

One at each end, evenly spaced between

8

Table 6B-3 states these lengths as minimums. Longer tapers are not automatically better — MUTCD Section 6B.08 notes that extended tapers tend to encourage sluggish operation and delay lane changes, particularly in urban areas with short blocks or frequent driveways.