What Specifications Actually Protect on Your Project

On many construction projects, the outcomes an owner ends up living with are decided long before construction starts. And they are usually decided not in the drawings, which get most of the attention, but in the specification: the written document that defines what every product is and how it is meant to perform.

If you are an owner or a developer, the specification is one of the most consequential things your money buys, and one of the least understood. This is a plain guide to it — what it is, what it protects for you, where projects go wrong without it, and the short list of questions that let you hold your team to a real standard. You do not have to write a spec, or read one cover to cover, to benefit from knowing what it is supposed to do.

Much of what follows we worked through on the Arcfluence Podcast with two people who have spent their careers inside this document: Dave Stutzman and Steve Gantner of Conspectus, the nation’s largest independent specifications consulting firm, in the discipline since 1992. They are, in the best sense, teachers of the craft — Steve works the ideas out for college students, Dave draws on a nearly hundred-year-old text on writing specifications. We have leaned on their expertise throughout. The subject, though, is yours: what a good specification does for the person paying for the building.

What a specification actually is

Ask most people what an architect delivers and they will describe drawings — floor plans, elevations, the picture of the building. Drawings are only half of the work. The other half is the specification: the written document that says what every product is, how it is installed, what it is tested against, and how it is meant to perform. An architect has, by contract, two deliverables, and they do genuinely different jobs. The drawings carry the where — layout, quantities, sizes, and how the systems relate. The specification carries the what — the quality. The single line that captures the difference is one the specifiers return to often: you cannot draw performance. A plan can show where a wall goes; it cannot show how well that wall keeps out water, which product was chosen, or what test proves it was installed right. That lives in the spec.

It helps to make it concrete. Steve teaches the idea with a board game — you can buy Monopoly and hold the board and the pieces in your hands, but someone still had to write the instructions that make it a game. Dave prefers the recipe on the back of the cookie package: every ingredient, and every step to combine them. A specification is that recipe for a building. It names the products that go in and gives the instructions for putting them together. Framed that way, it stops being bureaucratic overhead and becomes the one place the finished quality — the thing you actually care about — is pinned down in writing.

What your specification protects — and it is mostly you

Here is the part that matters to an owner. The pieces of a project you naturally watch — the renderings, the layout, the way a room will feel — are not where quality, budget, and risk are actually won or lost. Those are decided in the documentation, and in who was in the room when the early calls were made. The specification is where the quality you are paying for gets written down and made enforceable, because the specification is a contract. It holds a builder to the standard that was promised even where a drawing is silent, and contractors do read it — the general contractor reads the parts that govern what they owe, and holds their subcontractors to the rest. This is not back-office paperwork that happens to concern you. It is an owner-facing protection that happens to look like paperwork.

Our co-founder Nick Karakaian put the stakes plainly at the top of the episode: the reason to care about specifications is not architectural housekeeping — it is the painful, expensive conversations they prevent on your project.

Protecting the budget works the same way, and earlier than most owners expect. Real value engineering is not the panicked cost-cutting that happens after a bid comes in high; it is a decision process that happens on paper, before the money is committed. Put the specifier who knows the products, the estimator who knows the costs, and a contractor who knows the install in the room while the design is still on the page, and a costlier product can be swapped for an equal one that meets the same criteria — vetted and approved before, as Steve put it, a nickel is spent in construction. The first question is always whether the substitution still meets the design criteria, not simply whether it is cheaper. Answered early, on paper, it protects both the budget and the intent. Answered late, under pressure, it usually protects neither.

That framing sounds like it is only about money, but the point behind it is not. Trying to save by cutting corners early does not make the cost disappear — you pay for it later, in the field, down the road, or in the expense of operating a building that was compromised to save a little up front. As our co-founder Nick Karakaian put it on the show, the real measure is the whole picture, not just this moment. A specification written with that whole picture in mind is protecting how a building performs and holds up over its life, not only the numbers on a budget today.

Where projects go wrong without one

The clearest way to see what a specification protects is to watch what happens when it is thin. The same failure modes recur, and none of them announce themselves until they are expensive.

The design intent gap. There is a distance between what an architect envisions early and what actually gets built, and it widens through round after round of budget-driven change until pieces of the original vision are simply gone. Our principal architect Paul Fatkins named the phenomenon on the show — the design intent gap — and the naming matters, because a gap you can name is one you can manage. The root cause is rarely the cutting itself; it is a lack of collaboration during design. When the intent is written down as its own deliverable, and the whole team — owner included — is in the room early, every later decision has a fixed standard to be measured against, rather than a slow erosion nobody quite tracked.

Deferred decisions. The single biggest source of breakdown on a project is time, and nothing burns it like a decision left open. Leave one item unresolved — the door hardware, say — and issue the project for construction “as is,” and you have guaranteed an addendum. An addendum is not free: contractors renegotiate with subcontractors who already bid the first set, or stop mid-bid and regroup. A choice that would have taken a day and a phone call at the right moment ripples into weeks at the wrong one.

Vagueness, paid for in RFIs. When a document does not answer a question clearly, the resolution is a Request for Information — an RFI — and RFIs are expensive. Dave cited an industry study putting the average near eight hundred RFIs on a single project, with architects reporting roughly eight hours to process each: something like three staff-years spent clarifying what better documentation would have settled up front. There is a newer wrinkle, too. AI now drafts RFIs that, as Steve put it, “know nothing” — which does not remove the obligation to document well so much as raise the cost of not doing it.

Underneath all three is a habit worth naming, because it is old. Dave read a line from a 1940s book on writing architect’s specifications by Goldwin Goldsmith, itself quoting a talk from 1918: the work, its author observed, is “approached by many with trepidation, by some with careless confidence of ignorance, and by a few with the studious determination to succeed.” A century on, it still sorts the field — and the lesson for an owner is not that anyone is foolish, but that it matters which of those postures writes your spec. Careless confidence of ignorance is the copy-paste specification: last project’s language pasted forward, nobody quite certain it fits this building. Its opposite is the earned confidence of a team that has documented what it actually knows about your project and can stand behind every line. That second kind of confidence is the one you want on your job — and you are entirely right to ask which one you are getting.

There is one more person a thin spec fails: the one who inherits the building. A project might take a year to design and build, or ten; someone then operates it for the next fifty. That person — the facility manager — is almost never in the early meetings, and they are the one left with every decision that made the building hard to run: the filter nobody can reach, the equipment that costs many times as much to operate. The people who should shape a specification are not only the designers. They are everyone who will pay for the building, operate it, and maintain it over its life.

Lessons to keep in mind

You do not have to become a spec-writer to get the benefit of one. You can ask. Three questions will tell you most of what you need to know about whether your documentation is working for you:

• Is the design intent written down? Not assumed — documented, so every later change can be measured against it.
• Is the estimator in the room during design? Not after the budget breaks — while choices can still be vetted on paper.
• Who is speaking for the people who will operate this building for the next fifty years?

One last myth worth putting down: that a good specification is a thick book. It is not — it is a complete one. Dave described writing the full architectural and structural spec for a two-story cancer infusion center, building enclosure and interior fit-out, in twenty-five pages, and fielding zero questions on it during construction. Complete and clear beats thick and boilerplate every time.

Asked for a single takeaway, the specifiers were almost boringly practical, which is the point. Document what you know when you know it, so you have something to judge future decisions against. And spend a little more time at the start to save far more at the end.

None of this is glamorous, and that is exactly why it is worth understanding. A firm that takes specifications seriously is protecting your interests in the places you cannot easily see — long before the first shovel, and long after the last rendering. The drawings show you the building you are hoping for. The specification is what makes the building you get match it.

Go deeper: the specifiers’ own show

If the craft of this document interests you, the people behind it are worth following. Dave and Steve go deeper on it every month on their own podcast, Deliberate Words — a genuinely good listen on where design and construction meet. You can learn more about their work, and get in touch with the firm, at conspectusinc.com.

This piece grew out of a full conversation with Dave Stutzman and Steve Gantner on the Arcfluence Podcast, where design impacts the way we live, work, and invest.

Related Articles

• Navigating the Permitting Maze — the compliance-and-documents side of getting a project approved, and the closest cousin to a good specification.
• Why General Contractors Are Essential to Construction Success — where the specification actually gets executed and enforced out in the field.
• Commercial Architecture: What to Know Before You Build — an owner’s-eye walk through the commercial build process, from permitting onward.