The provision that changed how American highway agencies choose their projects is a sentence about money, not about pavement. Under 23 CFR 515.15, a state that has not developed and implemented a compliant asset management plan sees the maximum federal share for National Highway Performance Program projects cut to 65 percent for that fiscal year. For an agency accustomed to 80 or 90 percent federal participation, that is a reduction of a scale no engineering argument can survive.

Everything downstream sits under that penalty. Condition indices, deterioration models, treatment triggers and programming documents are all real engineering, and they are also the paper trail that keeps the federal share intact. A rebuild list is the output of both purposes at once.

Four measurements, two reporting deadlines

Federal law does not ask states what condition their roads are in. It asks for specific numbers, collected specific ways, on a fixed calendar.

Under 23 CFR 490.311, every state reports four condition metrics for each pavement section on the National Highway System: International Roughness Index, rutting, faulting and cracking percent. Alongside those go three inventory items, through lanes, surface type and structure type. Interstate metrics are due to the Highway Performance Monitoring System no later than April 15 each year, non-Interstate National Highway System metrics by June 15. The instruments are specified too. Roughness data must come from an inertial profiler meeting AASHTO M328-14 and be collected under AASHTO R57-14, and estimating roughness from samples of the mainline is expressly not permitted.

What the resulting picture can show has built-in blind spots. Sections coded as bridges drop out before any pavement measure is computed, and unpaved or otherwise surfaced sections drop out with them. Missing, invalid or unresolved sections are capped at 5 percent of total lane miles, and each uncollected section must be coded with a reason. Every state also has to run a Data Quality Management Program approved by FHWA.

The rating rule is deliberately asymmetric

The thresholds in 23 CFR 490.313 convert those measurements into Good, Fair and Poor, and the combination rule is the part that decides what the national numbers mean.

Asphalt and jointed concrete pavement carry three ratings: roughness, cracking, and rutting or faulting. A section of either reaches overall Good only when every one of the three ratings comes back Good, and it drops to overall Poor once at least two of the three read Poor. Continuously reinforced concrete carries only two ratings, roughness and cracking. It reaches overall Good only when both come back Good, and it drops to overall Poor only when both are Poor. Everything in between, on either kind of pavement, is Fair. Good is hard to earn and Poor is hard to fall into, and the rule is written that way on purpose.

The consequence for interpretation is easy to miss. When a state publishes a low Poor percentage it is reporting the near-absence of pavement that has failed several ways at once. It is not reporting the presence of good pavement, and the two claims often get conflated in press coverage of state condition figures. The distinction between a threshold that flags multi-mode failure and a threshold that flags a candidate for work is developed in how long a modern highway should last.

What the agency measures is not what the agency reports

The index most state and local agencies actually run their programs on does not appear in the federal rule at all. FHWA’s own research report on serviceability computation says so directly: many agencies do not collect present serviceability ratings on their pavement segments and instead use the Pavement Condition Index or other indices computed from measured surface distresses in their pavement management systems.

The Pavement Condition Index was developed in the late 1970s by the U.S. Army Corps of Engineers. It runs from 0 to 100, with 100 a perfect score, and it is computed by taking deduct values that vary with distress type, severity and density, then applying an adjustment that depends on the total deduct value and the number of deducts. ASTM International adopted the calculation method in 2000 from the PAVER asphalt and concrete distress manuals; the 2016 revision, D6433-16, covers 20 distresses for asphalt surfaces and 19 for portland cement concrete.

FHWA then states the point that matters for interpretation: that standard is not required under FHWA regulations, and the definition and manner of computing the index vary across agencies. On one narrow slice of the network, regulation 490.309(b)(2)(iii) permits a state to convert another condition-assessment method to present serviceability rating provided it satisfies FHWA that the conversion produces equivalent ratings, but that allowance reaches only sub-40-mph mainline on the non-Interstate National Highway System. It has nothing to do with how Interstate condition is measured, and the report tabulates which distresses a widely used California variant leaves out of its calculation altogether.

The real limit on cross-state comparison sits outside that narrow allowance. Most agencies run their own programs on the Pavement Condition Index or a state-specific variant, an index the federal rule does not require, does not define uniformly and does not touch at all: it is built, weighted and applied however each agency’s pavement management system was configured. That unstandardized internal layer, not the speed-limited conversion clause in Part 490, is why a state’s internal ranking of candidate projects rarely maps cleanly onto its federally reported percentages. The condition rating machinery for structures runs on an entirely separate system, described in how bridges are inspected and rated.

The plan that has to commit to something

The asset management plan required by 23 U.S.C. 119(e) and 23 CFR Part 515 is where an agency’s engineering judgment becomes a document FHWA can audit.

Part 515.9 fixes the minimum contents: asset management objectives, measures and targets for asset condition, a summary description of National Highway System pavement and bridge condition regardless of who owns it, performance gap identification, life-cycle planning, risk management analysis, a financial plan and investment strategies. The plan covers at least a 10-year period, its financial plan identifies annual costs over at least 10 years, and the state must resubmit its plan development processes for a new FHWA certification at least every 4 years. Part 515 fixes that cycle for the processes; it sets no comparable fixed interval for revising the plan itself.

Part 515.7 does more work than its length suggests. Life-cycle planning happens at the network level rather than project by project, which is what makes preservation of good pavement compete against reconstruction of bad pavement on comparable terms. And, in the regulatory text itself rather than an accompanying guidance document, the rule says that as a state builds its life-cycle planning process it should account for future changes in demand and for current and future environmental conditions including extreme weather events, climate change and seismic activity, on the grounds that these affect whole-of-life costs. The recommendation sits inside the rule’s own text. Climate is inside the asset management rule, not adjacent to it, and the design implications appear in extreme heat and roads.

Then there is the compliance test, which is unusually concrete for a planning regulation. FHWA considers the best evidence that a plan has been implemented to be that, for the 12 months preceding its consistency determination, the state’s funding allocations are reasonably consistent with the plan’s investment strategies, taking into account the alignment between actual and planned investment across initial construction, maintenance, preservation, rehabilitation and reconstruction. In other words, FHWA checks whether the money went where the plan said it would, by work type. The regulation then allows a finding of implementation despite deviation, where the state shows the deviation was necessary because of extenuating circumstances beyond its reasonable control. That clause is the pressure valve, and it is where the argument between engineering and politics is actually settled.

The federal floor almost never binds

There is a hard minimum condition requirement. Under 23 CFR 490.315, carrying out 23 U.S.C. 119(f)(1), the percentage of Interstate lane miles in Poor condition must not exceed 5.0 percent, with a single named exception: Alaska’s ceiling is 10.0 percent. Regulation 490.317 sets the consequence. A state out of compliance must, the next fiscal year, obligate from its National Highway Performance Program apportionment at least what it received under the old Interstate Maintenance program in fiscal 2009, escalating 2 percent a year, and shift 10 percent of that same 2009 figure into the apportionment out of Surface Transportation Program funds.

What the states report sits nowhere near it. FHWA’s national table of Interstate pavement condition, which currently runs from 2018 through 2022, lists 52 jurisdictions. For 2022, exactly one exceeded the 5.0 percent Poor limit: Puerto Rico, at 11.9 percent. The next highest values were Hawaii at 4.0 percent, Colorado at 3.2 and Louisiana at 3.2. The median across reporting jurisdictions was 0.4 percent.

The Good column tells a completely different story. In the same year and the same table, percent Good ranged from Hawaii at 14.7 to South Dakota at 83.8, with a median of 64.5. One column is compressed against zero across nearly every state; the other spans nearly seventy points.

The conclusion follows directly, and it is the single most useful thing to know about how rebuild decisions get made. The federal minimum condition rule is not what drives programming in almost any state, because almost no state is anywhere near it. What varies enormously, and what agencies actually manage against, is the Good-to-Fair boundary, where the choice is between preserving a road that still works and rebuilding one that has slipped. Preservation timing and reconstruction thresholds are decided against a state’s own targets, not against the federal floor, which is why a national Poor percentage explains so little about the projects that turn up across the highways section.

The table carries one more thing worth noticing, which is a data observation rather than a condition one: Michigan’s entries for 2020 through 2022 read NULL in both columns. Missing years in a five-year national series are a reminder that these percentages are administrative outputs with reporting histories, not readings taken off an instrument.

Where the ranking meets the map

An engineering ranking is not a program. The document that commits money is the statewide transportation improvement program, and 23 CFR 450.218 governs it. How a selected candidate then becomes a buildable contract is set out in how highway construction projects are planned.

A program covers at least four years and is updated at least every four, though a governor may elect a shorter cycle. Each metropolitan planning organization’s own program goes in without change once it has been approved by the organization and the governor. The whole thing must be fiscally constrained, and projects in any of the first four years may be advanced in place of one another under the project selection rules. Everything has to be consistent with a long-range statewide plan carrying a minimum 20-year forecast period. FHWA and FTA will not withdraw a finding of fiscal constraint if a revenue source later disappears, but they will not act on an amended program that fails to reflect the change either.

The omission in the regulation is the operative part. Nothing requires a state to program pavement projects in condition order. What is required is that the money be demonstrably available, that the metropolitan programs be incorporated intact, that the plan and the spending pattern match by work type, and that the reported condition stay above a floor almost everyone clears. Those are all auditable. Priority sequence is not.

That is the honest shape of the tension. Condition data narrow the field to a defensible set of candidates and the asset management plan constrains the mix of work types. Within those constraints, which of two comparable candidates goes first is decided by geography, by legislative delegations, by construction sequencing, by which corridor already has right of way, and by which project can be let when the money lands. Every one of those is defensible on the record. What an agency cannot truthfully claim is that the condition index chose.