2.2 Plans vs. Specifications & Order of Precedence (FP-24, Special Provisions, Standard/Supplemental Specifications)

If plans show where, specifications explain how: what materials are acceptable, what methods and workmanship are required, and how the work is measured and paid. A concrete pavement plan sheet might show a slab's location, thickness, and jointing layout — but it is the specification that tells the inspector the concrete must meet a stated compressive-strength class, be placed within a stated air-content range, and be measured for payment by the square yard of accepted pavement. Neither document stands alone; a complete contract requires both, and an inspector must read them together.

Plans vs. Specifications

Plans are graphic: dimensions, geometry, elevations, quantities, and locations, drawn to scale. Specifications are written: material requirements, construction methods, acceptable tolerances, testing frequency, and the basis of measurement and payment for each pay item. A specification section for concrete pavement, for instance, describes the required mix design, curing method, and joint-sawing timing in words; the plan sheet for the same pavement shows where the joints go and how thick the slab is at each point. Reading only one document gives an incomplete picture of what the contract actually requires.

The FP-24 Standard Specifications

Effective with the April 27, 2026 relaunch, NICET HCI exams became open-reference, and candidates may bring a bound, secured copy of FP-24 — the Federal Highway Administration's Standard Specifications for Construction of Roads and Bridges on Federal Highway Projects — into the testing center at every level (Level I candidates may additionally bring the MUTCD 11th Edition (2023)). FP-24 replaced the prior FP-14 edition and organizes requirements into divisions covering general requirements, project requirements, earthwork, earth retaining systems and slopes, aggregate and base courses, asphalt pavements and surface treatments, rigid pavements, bridge construction, incidental construction, and materials. Many state DOTs maintain their own standard specification books built around a comparable division structure and the same order-of-precedence logic described below; FP-24 is simply the shared reference NICET has designated across all four HCI levels.

Order of Precedence: What Governs When Documents Conflict

Every set of contract documents includes an order-of-precedence (sometimes called a "control of work") clause that tells the inspector and the contractor which document wins when two documents disagree. The general pattern used by FP-24-based and most state DOT contracts runs from most specific and most current down to most general:

1. Addenda (issued before contract award) and executed change orders / supplemental agreements (issued after award) — the most current instructions, because they were written specifically to correct or update the original documents
2. Special provisions — modifications written specifically for this project that add to, revise, or supersede standard specification language
3. Supplemental specifications — agency-wide updates issued between full editions of the standard specification book
4. Standard specifications (such as FP-24, or a state DOT's own standard spec book) — the general requirements that apply to every project using that book
5. Standard drawings and contract plans

Federal construction contracts also codify a related principle directly: under Federal Acquisition Regulation clause 52.236-21, "in case of difference between drawings and specifications, the specifications shall govern." Highway agencies build on that same idea — a written requirement is more reliable than a graphic interpretation — while layering in the special-provision and supplemental-specification tiers above, because highway contracts routinely modify a shared standard specification book for project-specific conditions that a general clause does not anticipate on its own.

The pattern to remember: the more specific and more current a document is to this project, the higher it ranks. A special provision written for this contract overrides a standard specification that was written to apply generally across every project in the book, and a supplemental specification updates the standard specification until the next full edition is published. When an inspector finds a conflict between a special provision and the standard specifications, the special provision governs — not simply because it is newer, but because it was deliberately written to supersede the general requirement for this specific job.

Written Dimensions Govern Over Scaled Dimensions

A parallel precedence rule applies within the plans themselves: a written (figured) dimension printed on a sheet always governs over a dimension obtained by scaling the drawing with a ruler. Reproduction, printing, and PDF scaling can all distort a sheet's true scale by a small percentage — enough to matter on a rebar cover dimension or a pipe slope, even where the difference looks negligible on a full roadway alignment. An inspector who needs a dimension that is not explicitly labeled should request clarification through the engineer rather than scale it and treat the result as contractual.

Reading the Hierarchy in the Field

In practice, an inspector rarely resolves a conflict by consulting all five tiers of the hierarchy from scratch. Most day-to-day answers come from the special provisions and the plans, because those are the documents written specifically for the project in front of the inspector. The standard specifications and any supplemental specifications matter most when the special provisions and plans are silent on a point — they fill the gaps rather than override the project-specific documents. Knowing the hierarchy matters most at the moment of conflict: when two documents genuinely disagree, the inspector needs to know immediately which one controls, document the conflict, and route it to the engineer rather than guess.