The Standard Behind the Spec

Contributors: Aaron Denning (Senior Project Manager) and Ryan Gentry (Superintendent) with USE Construction.

Every institutional project comes with three sets of standards. The first is in the design documents. The second is the facility standards.  And the third isn’t written down anywhere. It lives in the facilities team that will be running the building long after the project closes out.

Reconciling those three sets of standards before the work reaches the field is one of the most consequential things a mechanical contractor can do on a long-term institutional project. The U.S. Engineering Construction team is navigating that challenge now on the Chemistry and Applied Mathematics Facility (CHAP), a project for the University of Colorado Boulder.

Multiple Owners, Multiple Timelines

Every owner cares about opening on schedule. For a commercial client, what matters most after that is getting revenue flowing. A university is planning for that same opening date, plus who will be maintaining the system for the next 50 to 70 years.

That difference in timeline produces a difference in standards. A university’s facilities preferences aren’t arbitrary; they’re built from decades of operating and maintaining buildings on that specific campus. A hospital system’s equipment preferences reflect hard-won knowledge about what holds up, what’s easy to source, and what its own technicians know how to fix at 2 a.m. Those standards existed before the drawings were ever issued, and they’ll still matter long after the project team has moved on.

Where the Standards Diverge

That tension between the drawn standard and the operational one tends to surface in a few recurring places.

Equipment is the most common. Institutions with large maintenance staff often prefer manufacturers already in their inventory, even when the design documents allow for others.  Standardizing on fewer manufacturers means fewer part numbers to stock, fewer manuals to train on, and faster repairs when something fails. On CHAP, that meant a different pump motor manufacturer than the plans specified, one with a longer lead time.

The drawings specified Baldor motors for the project’s pumps. CU’s unwritten standard called for WEG instead.

Catching it early let Superintendent Ryan Gentry procure the correct motors well ahead of the piping installation, turning what could have been a field conflict into a routine procurement decision.

Installation methods are another place conflicts appear. Facilities teams develop preferences for how a system goes in, based on which approaches have held up best in their own buildings. On CHAP’s snow-melt system, the drawings called for soldered joints on in-wall piping. CU’s inspectors asked U.S. Engineering to braze the line instead, a switch the team caught and built into the install sequence before it became rework.

Even a product name can carry a hidden standard. A product a campus maintenance team trusts can be discontinued or rebranded over the years while remaining functionally identical. Confirming that connection with the university keeps the right product on the job without an unnecessary substitution request or delay.

Knowing Which Conflicts Are Worth Pushing On

Catching conflict matters and knowing how hard to push for either the drawing or an operational revision matters just as much.

That judgment starts with understanding where a preference comes from. Some standards reflect consistency the facilities team has deliberately built into how it runs its buildings, a decision to limit variables across dozens of systems so that maintenance is predictable and training is replicable. Others come from experience: a standard exists because a different approach caused a real problem somewhere on campus in the past. A preference rooted in that kind of institutional memory carries more weight than one that’s simply habit, and it deserves a different response.

The second factor is what accommodation costs, in dollars and in schedule. A preference with a modest impact on a project this size is usually easy to accommodate. One that could run into the tens of thousands, or push back a commissioning date, is worth working through carefully with the design team and the owner together. Most of these situations land somewhere in the middle, with each party giving a little. On a campus that will need mechanical work for decades, a preserved relationship is worth far more than a battle won.

What Experience with an Owner Buys You

Each of these situations traces back to the same root: a standard that existed before the drawings were issued; built around a building the owner expects to still be running decades from now. Each conflict is cheapest to resolve at the same point in a project, before procurement and before installation, while it’s still just a conversation.

That’s true on CHAP, and it’s true anywhere an institutional owner will be living with a building long-term. The contractors who serve those owners best go beyond a close reading of the design documents. They listen to the owner with the same attention, treating the facilities team’s accumulated knowledge as a second specification, one worth understanding before the first conflict surfaces in the field.