Which Spec Governs?

Every estimator in public or commercial work knows the moment: a bid requires knowing the embedment, bedding, testing, and backfill requirements for a water-line installation, and the answer is somewhere in — city standard specifications, the city's standard details, the adopted plumbing code, public-works requirements, the water utility's own standards, possibly DOT specs, the project plans, the project manual, the geotech report, two addenda, and whatever the owner's requirements PDF says.

Twelve documents. Written by different authors, in different decades, revised on different schedules. They overlap, and where they overlap, they disagree.

The naive framing of this problem is "finding city specs," as if it were a search problem. The actual problem is a governance problem, and it has five layers:

• Which jurisdiction controls — city, county, utility district, state DOT, or several at once.
• Which version applies — the spec current today, or the one in force at bid date.
• What is incorporated by reference — the innocuous sentence that imports an entire ASTM or AWWA standard.
• Whether the plans override or supplement the standard specifications — and whether an addendum quietly changed the answer.
• Which document wins a conflict — the order-of-precedence clause everyone reads for the first time during a dispute.

What getting it wrong costs

Wrong answers here do not fail loudly at bid time. They fail as rejected submittals, failed inspections, redone work, and back-charges — the rework that already averages around 5 percent of project cost industry-wide, concentrated exactly where documentation is ambiguous. FMI and Autodesk's research on bad data — inaccurate, incomplete, or untimely information — priced the global damage at $1.85 trillion in a single year. Specification ambiguity is bad data with a stamp on it.

And the institutional defense is thinning. The estimator who "just knows" that this city always requires the stricter bedding detail is part of the same retiring cohort carrying the safety folklore out the door.

Jurisdictional intelligence

The architecture is the one this series built for safety last week, pointed at a domain with more documents and sharper edges — a controlled library plus a retrieval layer that must show its work:

The library: the specifications, standard details, adopted codes, utility standards, and DOT sections that actually govern your markets — plus, per project, the plans, manual, geotech report, addenda, and owner requirements. Every document tagged: jurisdiction, effective date, revision, what it applies to. Version tracking is not a feature here; it is the point. When a city revises its standard details, the system should know — and say — which of your active projects bid under the old ones.

The retrieval contract: every answer arrives with jurisdiction, document, revision, exact section or detail number, a concise statement of the requirement, any known conflicting documents, whether the source is direct or inferred — and whether engineer, inspector, PM, or estimator review is required before anyone acts.

The workflows that pay for it: extracting requirements during bid review; comparing project plans against standard details; building submittal and mobilization checklists from the governing set; surfacing testing and inspection requirements before the inspector does; alerting when a source document changes; and — the quiet one — drafting the RFI when the controlling requirement is genuinely ambiguous, with the conflicting sections cited side by side. Ambiguity found at bid time is a question; ambiguity found at inspection time is an invoice.

The water-line question, answered properly

Run the opening example through the system. The estimator asks about embedment, bedding, testing, and backfill. A safe system does not return a paragraph of confident prose. It identifies the project's jurisdiction; searches the approved document set; locates the applicable spec sections and details; identifies the incorporated standards; notes the conflict between the city detail and the utility standard; cites every source; and prepares a summary for the estimator's review — with a drafted RFI attached, because in this case the two documents genuinely disagree.

That last behavior is the whole philosophy in miniature, and it gets next week's post to itself: in regulated construction, an answer without a source is not an answer. It is a liability.