Terms that do real work in Part 7 but lack definitions in Part 1 or Part 7 — creating discretionary gaps that jurisdictions use to avoid compliance.
| Notes | Term | Where used | Type | Regulatory Language (May/Shall/Should) |
Count | In context | Problem | Advocacy Implication | Source / Verification |
|---|---|---|---|---|---|---|---|---|---|
| "special pedestrian conditions" | 7A.01 DE 7A.04 scope statement |
Scope | SHALLDE 7A.04: "Signs... shall be installed" |
The term is undefined yet load-bearing: it single-handedly scopes the entire applicability of Part 7, so its vagueness propagates into every downstream provision. | Broad enough to encompass any school-proximate hazard; no definitional floor for jurisdictions to narrow it. DE 7A.04 makes this a Standard — applies regardless of formal zone designation. | SOURCED DE MUTCD Rev 3 (2018) DE 7A.04 — term present and load-bearing. Confirm exact section and absence of definition in Part 1 glossary. | |||
| "school areas" | Part 7 title 7A.01 |
Scope | GUIDANCE7A.01: "Schools are considered" (no imperative) |
The term is undefined, while the narrower "school zone" (Part 1 §211) is defined but only takes effect upon formal designation — leaving the broader "school area" with no operative meaning. | Jurisdiction could argue Part 7 applies only in formally designated zones, not the broader area. Counter: DE 7A.04 Standard applies Part 7 wherever special pedestrian conditions exist. | INDIRECT Referenced in MUTCD literature — confirm exact section in DE MUTCD Rev 3. Confirm "school zone" is defined in Part 1 §211 and "school areas" is not. | |||
| "school serving elementary to high school students" | 7A.02 ¶01 | Scope | GUIDANCE7A.02: "Schools serving... should have" (Guidance) |
The phrase is ambiguous: it excludes pre-K, lets multi-site programs fall through the cracks, and rests on a definition of "school" (Part 1 §210) that punts to state authority — producing state-by-state variation. | State-by-state variation in what schools are covered. Pre-K explicitly excluded from planning obligation. | INDIRECT Referenced in MUTCD literature — confirm exact section in DE MUTCD Rev 3. Confirm pre-K exclusion and Part 1 §210 definition language. | |||
| "uniformity" | 7A.02 ¶01 | Slippery | PRINCIPLEPreamble: "uniformity in application" |
"Uniformity" is never defined as a standalone term; the MUTCD preamble only gestures at it as "treating similar situations similarly," leaving no operative test a jurisdiction must meet. | Inconsistent treatment across similar schools (e.g., WPPE vs. lower-minority schools with zone designations) is a uniformity argument and potential Title VI evidence. | UNVERIFIED Confirm term is absent from all relevant DE standards. Confirm preamble language — exact wording matters for advocacy use. | |||
| "systematic manner" | 7A.02 ¶02 | Slippery | SHOULD7A.02: "should be prepared... in a systematic manner" |
There is no process standard and no floor for what counts as "systematic," so almost any cursory effort — even a one-page sketch — can be self-certified as compliant. | A one-page sketch could technically qualify. Jurisdiction can self-certify compliance. | INDIRECT Referenced in MUTCD literature — confirm exact section in DE MUTCD Rev 3. Confirm no process standard is defined anywhere in the document. | |||
| "established school walk routes" | 7A.02 ¶02 | Circular | SHOULD7A.02: "should include... established school walk routes" |
The term is undefined and circular: a plan cannot reference walk routes that were never formally established, yet routes are never established because no plan is ever made. | The circularity is the problem. Breaking the loop requires formal establishment act — typically via the route plan itself. | INDIRECT Referenced in MUTCD literature — confirm exact section in DE MUTCD Rev 3. Confirm no definition of "establish" or "established" appears in Part 1 or Part 7 glossary. | |||
| "established school crossings" | 7A.02 ¶02 | Circular | SHOULD7A.02: "should include... established school crossings" |
This carries the same circularity as walk routes: a crossing must be formally established before the plan can cite it, yet nothing in Part 7 triggers that establishment. | No crossings formally established at WPPE — downstream sign Standards cannot activate. | INDIRECT Referenced in MUTCD literature — confirm exact section in DE MUTCD Rev 3. Confirm no definition of "established school crossing" appears in Part 1 or Part 7. | |||
| "established" / "establish" (the act, as modifier) | 7A.02 ¶02 modifier on "walk routes" & "school crossings" |
Circular | SHOULD7A.02: "should include... established school walk routes / crossings" |
The MUTCD never defines what act "establishes" a walk route or crossing, who performs it, or how it is recorded — yet "established" is the precondition that activates multiple downstream Standards (e.g., the 7B.11 advance-assembly Standard). | Because the establishing act is undefined, a jurisdiction can claim nothing is "established" and so no Standard is triggered; conversely, advocates can argue the school traffic control plan itself is the establishing act, breaking the circularity. This single modifier is the linchpin of the whole circular chain. | UNVERIFIED Confirm term is absent from all relevant DE standards. This is the central structural claim of Table 1 — must be verified in DE MUTCD Rev 3 Part 1 glossary and Part 7 before advocacy use. | |||
| "as applicable" | 7A.02 ¶03 (bicycles) | Slippery | SHOULD7A.02 ¶03: "should include... as applicable" |
This undefined qualifier further weakens an already Guidance-level bicycle provision, giving a jurisdiction an opening to treat cyclists as never "applicable." | Jurisdiction can invoke this to ignore cyclists entirely. Cyclist sidewalk regulation is outside MUTCD scope — set by state/local law. | INDIRECT Referenced in MUTCD literature — confirm exact section in DE MUTCD Rev 3. Confirm no definition of "applicable" or applicability test appears in the document. | |||
| "related to" (four factors) | 7A.02 ¶04 | Slippery | SHOULD7A.02 ¶04: "selection should be related to" |
No defined relationship links the four factors (volume, speed, width, age) to device selection — there is no formula and no minimum floor, only discretion. | Pure discretion. But if jurisdiction hasn't assessed all four factors, it hasn't met even Guidance. TMCs have no speed data — speed factor cannot be assessed from TMC data alone. | INDIRECT Referenced in MUTCD literature — confirm exact section in DE MUTCD Rev 3. Confirm the four factors are listed there and no formula or minimum is provided. | |||
| "school traffic control plan" | 7A.02 ¶05 | Missing | SHOULD7A.02 ¶05: "should develop" |
The plan is undefined: the MUTCD specifies no required contents, format, update cycle, or responsible party, so it can be empty and still technically exist. | Plan can be empty and still technically exist. But its absence is a documented failure — FOIA-able. | UNVERIFIED Confirm term is absent from all relevant DE standards. Confirm no required contents or format are defined in DE MUTCD Rev 3. FOIA Christina SD and City of Newark for any existing plan. | |||
| "adequate gap" / "sufficient gap" | 7A.02 ¶07 | Slippery | SHOULD7A.02 ¶07: "sufficient gaps... should be considered" |
The two terms are used interchangeably with no minimum gap standard and no age-differentiated standard, even though a 6-year-old and a 16-year-old cross at very different speeds. | Jurisdiction self-defines adequacy. Need gap study methodology — DE MUTCD references Traffic Control Devices Handbook. | INDIRECT Referenced in MUTCD literature — confirm exact section in DE MUTCD Rev 3. Confirm no minimum gap duration or age-differentiated standard is defined in the section. | |||
| "frequency" of gaps | 7A.02 ¶07 | Slippery | SHOULD7A.02 ¶07: "frequency of adequate gaps should be determined" |
No minimum frequency standard is given, so even a single adequate gap per hour could be characterized as "frequent." | One gap per hour could technically be "frequent." Platoon release from Elkton signal suppresses actual gap frequency — not captured by standard count data. | INDIRECT Referenced in MUTCD literature — confirm exact section in DE MUTCD Rev 3. Confirm no minimum frequency standard is defined anywhere in Part 7. | |||
| "excessive" delay | 7A.02 ¶07 | Slippery | SHOULD7A.02 ¶07: "excessive delay should be considered" |
No threshold defines "excessive," leaving the trigger for this obligation entirely to engineering discretion. | Entirely at engineering discretion. No objective trigger for the "needs to be considered" obligation. | INDIRECT Referenced in MUTCD literature — confirm exact section in DE MUTCD Rev 3. Confirm no threshold or objective measure is defined for "excessive delay." | |||
| "impatient" / "endanger themselves" | 7A.02 ¶07 | Slippery | DESCRIPTOR7A.02 ¶07: "impatient pedestrians may endanger" |
The language frames the hazard as a child's behavioral failure rather than an infrastructure failure, shifting causation — and blame — onto children. | Matters in litigation, politics, and engineering documentation. Advocates should reframe gap hazards as infrastructure failures. This language can be used to shift blame to children. | SOURCED DE MUTCD Rev 3 (2018) — confirm exact section and quoted language in 7A.02 ¶07. Wording is central to the advocacy reframing argument. | |||
| "crossing demand" | 7A.02 ¶07 | Missing | SHOULD7A.02 ¶07: "crossing demand should be evaluated" |
No methodology is provided for measuring or documenting crossing demand, so a jurisdiction can claim demand is unknown without ever studying it. | Jurisdictions can claim demand is unknown without study. WPPE community count addresses this — creates documented crossing demand data. | UNVERIFIED Confirm term is absent from all relevant DE standards. Confirm no methodology is defined in DE MUTCD Rev 3 for measuring crossing demand. | |||
| "adequate sidewalks or other pedestrian walkways" | 7A.02 ¶09 Factor A (DE Factor A) | Slippery | SHOULD7A.02 ¶09: "availability of adequate sidewalks should be considered" |
No width, condition, continuity, or ADA-compliance standard is specified for what makes a sidewalk "adequate," so the jurisdiction self-defines it. | Jurisdiction self-defines adequacy. If indirect route itself lacks adequate sidewalks, the detour solution fails on its own terms — a direct WPPE leverage point. PROWAG (2023) sets standards for new/altered sidewalks. | INDIRECT Referenced in MUTCD literature — confirm exact section in DE MUTCD Rev 3. Confirm DE Factor A language and confirm no width or condition standard is defined in the section. | |||
| "feasibility" | 7A.02 ¶09 | Slippery | SHOULD7A.02 ¶09: "feasibility of... should be reviewed" |
No methodology is provided for determining "feasibility," making it a pure judgment call by the reviewing engineer. | Pure judgment call. Delaware adds Factors E (crossing guard presence) and F (unexpected location) — use these to raise the bar on feasibility determination. | SOURCED DE MUTCD Rev 3 (2018) — confirm exact section for Factors E and F (crossing guard; unexpected location). These are DE-specific additions — confirm they appear in DE MUTCD Rev 3 and not in federal MUTCD. | |||
| "adequate visibility" | 7C.02 ¶03 | Slippery | SHOULD7C.02 ¶03: "adequate visibility should be provided" |
Part 7 specifies no sight-distance standard for "adequate visibility," though 4C.06 ¶06B offers a 100-ft reference for signal placement that can be borrowed as a benchmark. | Funeral home parking at WPPE Location 4 demonstrably reduces visibility below stopping sight distance — documents the inadequacy even without a defined threshold. | INDIRECT Referenced in MUTCD literature — confirm exact section in DE MUTCD Rev 3. Confirm 4C.06 ¶06B 100-ft reference and confirm it applies in the DE version. WPPE sight-line condition: verify via site visit and photographs. | |||
| "school crosswalk" | 7B.11 ¶02 (trigger for Standard) | Circular | SHALL7B.11 ¶02: "advance assembly shall be installed" |
The term is undefined in the DE MUTCD; an unmarked crossing may not qualify, and it requires a prior act of establishment before the 7B.11 Standard can attach. | None of WPPE's crossings are formally established. Until established, the 7B.11 Standard (advance assembly shall be installed) cannot activate. | UNVERIFIED Confirm term is absent from all relevant DE standards. Confirm "school crosswalk" is not defined in DE MUTCD Rev 3 Part 1 or Part 7, and confirm the 7B.11 Standard is correctly quoted. |
Key: Scope undefined scope term · Circular depends on undefined prior act · Slippery defined but unmeasurable/discretionary · Missing no definition anywhere in MUTCD
Confirmed from text diff of deldot-mutcd-part7-school.pdf vs federal 11th Ed. Rows marked INDIRECT or UNVERIFIED above that are now confirmable:
| Term (Table 1 row) | DE Section confirmed | Was | Now | Confirmed text / note |
|---|---|---|---|---|
| "related to" (four factors) | DE 7A.01 §08 | INDIRECT | SOURCED | "The type(s) of school area traffic control devices used…should be related to the volume and speed of vehicular traffic, street width, and the number and age of the students using the crossing." Four factors confirmed; no formula or minimum defined. |
| "school traffic control plan" | DE 7A.01 §09 | UNVERIFIED | SOURCED | "School area traffic control devices should be included in a school traffic control plan." — Guidance. No required contents, format, or responsible party defined. Plan can be empty and technically compliant. |
| "adequate gap" / "sufficient gap" | DE 7A.03 §01–02 | INDIRECT | SOURCED | DE added dedicated section 7A.03. Methodology punted to "Traffic Control Devices Handbook." No minimum gap duration or age-differentiated standard defined. "Impatient" language confirmed in 7A.03 framing. |
| "feasibility" (Factors E & F) | DE 7A.02 §03E–F (DE Revision) | SOURCED | SOURCED ✓ | Factors E (crossing guard presence) and F (unexpected location) confirmed as DE-specific additions not in federal text. Confirmed: federal 11th Ed. does not include these factors in equivalent provision. ⚠ REGRESSION WARNING (2026-06-14): DE MUTCD 2026 §7A.02 ¶09 lists only Factors A–D — Factors E and F are removed. If DE MUTCD 2026 is formally adopted, the crossing guard and unexpected-location arguments are no longer embedded in the MUTCD. Cite Rev 3 for advocacy based on existing conditions; demand explanation if 2026 version is cited against this argument. |
| "school serving elementary to high school students" | DE 7A.01 §06 | INDIRECT | SOURCED | "A school route plan for each school serving elementary to high school students should be prepared…" Confirmed in DE 7A.01 §06. Pre-K exclusion confirmed; no definition of "school" in Part 7. |
| "established school crossings" | DE 7A.02 title + body | INDIRECT | SOURCED | DE section title is "School Routes and Established School Crossings" — term load-bearing in section title and body. No definition of what constitutes the act of establishment. Circularity confirmed. |
| "school crosswalk" (trigger for 7B.11 Standard) | DE 7B.11 §02, §05 | UNVERIFIED | SOURCED | 7B.11 Standard confirmed: "shall be installed" at school crosswalk. DE §05 (DE Revision) adds in-street sign option requiring DelDOT Traffic approval. Term "school crosswalk" still undefined in Part 7. |
Each row is a regulatory double-bind: a planner who wants to act is blocked not by discretion but by the structure of the rules themselves. These are the leverage points for advocacy — the system should not be able to point to itself as the reason nothing was done.
| Bind | Federal requirement | DE rule that blocks action | WPPE consequence |
|---|---|---|---|
| Circular establishment lock | 7B.11 SHALL: advance assembly required at "school crosswalk." 7B.12 SHALL: crossing assembly at "established school crossing." | Neither document defines what act establishes a crossing or who is authorized to do it. DE 7A.02 title uses the term as a given without defining the process. | No WPPE crossing is formally established → no SHALL provisions activate → agency can defer indefinitely without violating any rule. The undefined act is the escape hatch. |
| Speed law chicken-and-egg | Federal: "Reduced speed limit signs… included solely for standardizing signing… not an endorsement of mandatory reduced speed zones." (Support) | DE 7A.01 §10A (DE Revision, Standard): "speed limit in school zones shall be 20 mph where 20 mph regulatory signs are posted." Law activates only where signs exist. Signs require engineering study + DelDOT approval. | No signs → no law. Law would require signs only if signs already exist. Engineering study required to install signs → no study has been done → §4169 never activates at WPPE. |
| DelDOT approval gate loop | Federal has no approval gate for in-street signs, beacons, or speed limit signs. | DE adds SHALL gates: in-street signs (7B.12 §09), S3-1-DE (7B.13 §03), speed limit beacons (7B.15 §19), flashing beacons (7B.18 §01–02) — all require DelDOT Traffic approval + some require ROW agreement signed by sponsoring entity. | Community cannot self-install. School cannot self-install. City must petition DelDOT. DelDOT is both the standard-setter and the sole approver. Advocacy must go through and get approval from the same agency being petitioned. |
| Stop control exclusion | Federal 7B.12 ¶03: "School Crossing assembly shall not be installed on approaches controlled by a STOP or YIELD sign." | DE 7B.12 confirms this prohibition. DE 7B.12 §03A (DE Revision) says assembly should be at marked crosswalks on established route — but only for non-stop-controlled approaches. | If WPPE Locations 1–3 have stop-controlled approaches (unverified), the crossing assembly standard is prohibited on those approaches. Most meaningful controls may be excluded by the intersection control that's already there. |
| Post-Jan-2026 adoption limbo | FHWA Final Rule: January 18, 2026 deadline for Delaware to adopt MUTCD 11th Ed. — this deadline is now PAST (today: 2026-06-14). 11th Ed. has different section structure, updated school area provisions. DE MUTCD 2026 is labeled PENDING APPROVAL on the deldot.gov MUTCD index page (primary source, verified 2026-06-14) — retains 2009-era base structure, does NOT adopt 11th Ed. | DE is operating past the FHWA compliance deadline with a 2009-era standard (Rev 3) as the formally adopted governing document. DE MUTCD 2026 is labeled PENDING APPROVAL on deldot.gov — not formally adopted, no effective date, no adoption notice in Delaware Register of Regulations. FHWA compliance status of DE is unknown — FOIA FHWA and DelDOT for any correspondence. Further: DE MUTCD 2026 removes Factors E&F, sign codes S3-1-DE / S5-1-DE / S5-3-DE, §7B.18 beacon warrant, and §4169 integration — all advocacy strengths. The proposed 2026 text is a regression even if adopted. | Planners cannot confidently cite DE MUTCD sections as durable in either direction: Rev 3 is post-deadline; 2026 draft is not formally adopted. Creates legitimate uncertainty that agencies use to delay action. Counter: federal 11th Ed. Standards are already in effect as of Jan 18, 2026. Advocates can argue the federal standard applies by default where DE has failed to adopt. |
→ See also Table 9 — Federal vs. Delaware Diff for full section-by-section comparison. Source PDFs: MUTCD 11th Ed. Part 7 · DelDOT MUTCD Part 7