How to Read Construction Specifications — For Builders (Part 2: The Written Half of the Contract)

Part 1 of this series covered the drawings — how a construction drawing set is put together, how the title block works, how to chase a callout, and why you never scale off a print. Drawings are half of a contract. This post is about the other half: the specifications.

If you only read the drawings, you'll build the wrong project. Not because the drawings lie, but because they can't say everything. A drawing shows where a wall is and how many doors go in it. The specification tells you what the wall is made of, to what standard, and how you have to prove it. Miss the specs and your takeoff is short, your submittals are wrong, and your closeout is a fight.

This piece is a builder-audience primer on reading specifications the way an estimator or project manager should — how they're structured, where the quiet money lives, and a repeatable routine you can apply to any project. Public work is the reference here because that's where MODRN lives, but the same discipline applies everywhere.

What specifications actually are

The specifications — usually just called "the specs" — are the written portion of the contract documents. Where the drawings are graphic, the specs are prose. They spell out the materials, the products, the workmanship standards, the tests and inspections, and the administrative obligations of the job. On public work, they carry as much scope as the drawings, and usually more of the obligations that a bidder doesn't see coming.

Modern American construction specs are organized under a system published by the Construction Specifications Institute (CSI), known as MasterFormat. MasterFormat divides the work of a project into numbered divisions and sections. A section covers a specific piece of scope — say, "Section 09 65 00 Resilient Flooring" — and every section on every project uses the same numbering and the same internal structure. Once you know the map, you can find your way around any set of specs.

The high-level divisions run roughly: Division 00 (procurement and contracting requirements — the front-end forms, bid documents, contract), Division 01 (general requirements — everything that applies to the whole job), then Divisions 02–14 (site work through equipment), followed by 21–28 (fire suppression, plumbing, HVAC, electrical, low-voltage, communications, security), and 31–35 (earthwork, exterior improvements, utilities, transportation, waterway/marine). Not every project uses every division; the ones it does use appear in a table of contents at the front of the spec book.

The three-part section — the pattern that repeats

Every technical specification section (Divisions 02 through 49) follows the same three-part outline. Once you can navigate it, you can read any section. The three parts are:

Part 1 — General. The administrative and reference layer. This is where you find what's included in the section ("Summary"), what's specified elsewhere ("Related Sections"), reference standards (ASTM, ANSI, ACI, UL, and so on), submittal requirements, quality assurance provisions, mock-up requirements, delivery/storage/handling, warranty terms, and field conditions. Part 1 is where the money hides — a single "Submit product data, samples, mock-ups, and manufacturer certifications" bullet can add days of PM labor to your bid.

Part 2 — Products. The materials themselves. Manufacturers, model numbers, materials of construction, finishes, colors, performance criteria, and accepted product substitutions. Part 2 is what most people think "specs" means — the actual material call-outs. It's usually the shortest of the three parts, and it's the part your buyers and estimators will pull numbers out of first.

Part 3 — Execution. How the work gets installed. Preparation, examination of substrates, installation methods, tolerances, coordination with other trades, field quality control, tests, and closeout obligations for the section (cleaning, adjusting, protecting, demonstrating). If Part 2 tells you what, Part 3 tells you how and how you'll be judged.

That's the whole pattern. Section 09 65 00 Resilient Flooring, Section 05 12 00 Structural Steel Framing, Section 23 09 23 Direct-Digital Control System for HVAC — different scope, same three-part shape. Learn the shape and every spec section becomes readable.

Division 01 — the sneaky expensive division

If you learn nothing else about specs, learn to read Division 01. General Requirements is where the project-wide obligations live — the ones that apply to every section, every trade, and every day of the job.

A representative Division 01 table of contents runs through: summary of work, work restrictions, alternates and allowances, unit prices, contract modification procedures, payment procedures, project management and coordination, construction schedule requirements, RFI procedures, submittal procedures, quality requirements, temporary facilities and controls, common product requirements, execution requirements, cutting and patching, cleaning, closeout procedures, project record documents, operation and maintenance data, warranties, and demonstration and training.

Read that list slowly. Every one of those sections is scope. Some of it is scope you have to carry as cost (temporary facilities, cleaning, closeout documentation), some of it is scope you have to staff (submittals, RFI management, schedule updates), some of it dictates how you get paid (payment procedures, retainage, lien waivers). On public work, Division 01 is where the difference between a profitable bid and a stressed-out one is often decided.

Habit worth building: on every new project, read Division 01 end to end before you start pricing anything. It's typically 40–80 pages. It reads slower than a novel but pays for itself the first time you catch an allowance you were about to double-count or a submittal requirement your team was about to underestimate.

How to read a spec section quickly

Nobody reads every spec section cover to cover on a competitive bid — the schedule doesn't allow it. What experienced estimators do instead is read each section in a disciplined order. When you open a technical section for a scope you're pricing:

1. Read the Summary and Related Sections first. Know what's in the section and what's specifically NOT in it. "Related Sections" tells you where adjacent scope lives so you don't double-count or drop something.
2. Scan the reference standards. Some standards are routine; some (a specific ACI mix design, an ASTM test method that requires third-party inspection) carry cost. Note them for your estimate.
3. Read submittal requirements carefully. Product data, shop drawings, samples, mock-ups, and certifications each take real time. On public work, submittals are also the first place a job stalls.
4. Read the Products part. Get your materials list and check the substitution language — some specs allow "or equal," some don't, some require a formal substitution request 10 or more days before bid.
5. Read the Execution part. Pay particular attention to preparation (what the substrate has to be before you start), tolerances, and field quality control — anything that means an inspector, a test, or a rework risk.
6. Read the closeout obligations in that section. Warranties, spare parts, attic stock, cleaning, training. Small line items, real costs — and easy to miss.

Done well, this takes twenty to thirty minutes for a substantial section. Done badly (i.e., skimmed), it takes five minutes and costs you the job.

Where specs and drawings collide

Drawings and specs are supposed to agree. They frequently don't. When they conflict, the contract has to pick a winner — and every set of contract documents publishes an order of precedence that says which document governs when they disagree.

On most projects, the precedence hierarchy is spelled out either in Division 01 (General Requirements) or in the front-end contract documents in Division 00. As a general pattern, addenda take precedence over the original documents, the specifications generally govern over the drawings for material and quality questions, and the drawings generally govern for dimensions and locations. Schedules published on the drawings — door, finish, hardware, window — usually govern the count for their type. Larger-scale views govern over smaller-scale ones, and specific notes govern over general ones. But do not memorize this list — memorize where to find the actual clause on your project. Every project publishes its own precedence rules, and they can vary.

The practical takeaway is simple: when you spot a conflict, don't guess. Log it, ask an RFI, and carry a bid clarification stating your assumption if the answer doesn't come back before bid. Silent guessing is the fastest way to eat a change order after award.

Where scope quietly lives in the specs

Certain kinds of scope live almost entirely in the specs and almost never on the drawings. Read these areas twice on any new project:

• Submittals. Product data, shop drawings, samples, mock-ups, and manufacturer certifications. Zero of this shows up as a line on a plan. All of it takes PM time and often outside consultant fees.
• Quality assurance and testing. Independent inspections, laboratory tests, and manufacturer field oversight. Sometimes the contractor pays; sometimes the owner does — the spec tells you which.
• Mock-ups. Full-size trial assemblies (masonry walls, curtain-wall corners, roofing terminations) required before production installation. Real cost, real schedule impact.
• Temporary facilities and controls. Site fencing, sidewalk sheds, dust partitions, temporary utilities, security. Priced in Division 01, easily forgotten by the trades.
• Cleaning and closeout. Progressive cleaning, final cleaning, punch-list, warranty, O&M data, as-builts, spare parts, training. A separate scope by itself, spread across every technical section and Division 01.
• Warranty extensions. Roofing, waterproofing, and specialty systems often carry extended manufacturer warranties that need to be priced into the bid, not assumed as standard.

A repeatable spec-reading routine

On any new set of contract documents, once the drawings have been read (see Part 1), the disciplined pass through the specifications runs:

1. Read the specification table of contents. Confirm every division and section listed. Note anything missing that you'd expect to see.
2. Read Division 00 quickly. Instructions to bidders, contract form, and the precedence-of-documents clause. This tells you who wins when drawings and specs disagree.
3. Read Division 01 end to end. Every project-wide obligation. Price the cost items (temporary facilities, cleaning, closeout) and staff the process items (submittals, RFIs, schedule updates).
4. Read every technical section that touches your trades. Follow the six-step per-section routine above.
5. Skim the technical sections that don't touch your trades. Boundary conflicts — where your scope hands off to another trade — hide in adjacent sections.
6. Read every addendum, twice. Addenda change scope. Missed addenda are the classic public-bid mistake.
7. Reconcile with the drawings. Every scope item you priced from a spec section should have a corresponding location on the drawings, and vice versa. Where they don't match, log the conflict and either RFI it or clarify in your bid.

This is the same discipline described in Part 1 for drawings, extended to the written side. Together, drawings and specs are the whole contract. Read them together, and your bid reflects the actual scope. Read one without the other, and you're guessing.

The bottom line

Specifications are half the contract. Learning to read them fluently — MasterFormat divisions, the three-part section, Division 01, the precedence rules, and the places scope hides quietly — is the same kind of durable, career-long skill as reading drawings. Neither is glamorous. Both separate the estimators who consistently protect margin from the ones who chase it.

Start with any spec book you have access to. Read the table of contents. Read Division 01. Read one technical section from top to bottom. You'll be surprised how quickly the pattern becomes obvious — and how much scope you find that a fast read would have missed.

MODRN runs preconstruction, estimating, and contract administration on NYC and NYS public work. Disciplined spec reading is baked into how we bid and how we build. If your firm wants a second set of experienced eyes on a public bid — or a partner who reads the whole contract, not just the pretty pictures — get in touch or see what we do.

This article is provided for general informational and educational purposes and reflects standard construction-documentation conventions. Exact spec formatting, precedence clauses, and section requirements vary by project and by owner — always defer to the actual contract documents for the job you're on.

Featured image: Construction workers on-site (Santa Clara, CA, 2020). Photo by Daniel Mekis via Wikimedia Commons, CC BY 4.0. Used unmodified.