Spec Management

Division 00 & 01 Red Flags to Catch Before You Bid

The eight most expensive red flags hiding in Division 00 and Division 01 of construction specs — what standard looks like, what it costs if missed, and what to do.

Mike Lapeter
Founder, DeadFront.AI
18 min read

Before you bid any project, read Division 00 (Procurement and Contracting Requirements) and Division 01 (General Requirements) looking for eight specific red flags: liquidated damages clauses, no-damages-for-delay language, unusual retainage terms, short submittal turnaround requirements, non-standard warranty durations, restrictive substitution clauses, unusual labeling or identification requirements, and coordination-drawing burdens. These two divisions don't describe any physical work, which is exactly why estimators skim them — and exactly where owners bury the terms that turn a profitable bid into a loss. For each red flag you find, you have three moves: submit an RFI before bid, qualify your bid, or price the risk in.

Table of Contents

Why Do Division 00 and 01 Hide the Most Expensive Mistakes?

In CSI MasterFormat, Division 00 covers bidding requirements, contract forms, and conditions of the contract. Division 01 covers general requirements — submittals, quality control, temporary facilities, closeout. Neither one tells you what to build.

That's the trap. Estimators under bid-week pressure go straight to their trade divisions — 26 if you're electrical, 23 if you're mechanical — because that's where the takeoff lives. Division 00 and 01 look like boilerplate, and 90% of the time they are. The other 10% is where an owner's attorney or a burned public agency inserted something non-standard: a $10,000/day LD clause, 10% retainage held to final completion, a two-year warranty on everything.

Boilerplate is dangerous precisely because it usually is boilerplate. When 47 pages read exactly like the last ten projects, your eyes stop registering the one paragraph that doesn't. In a typical 1,000-page spec set we see 15 to 40 requirements that deviate from standard practice, and 2 to 5 serious enough to need an RFI or change-order conversation before bid day. Most cluster in Divisions 00 and 01 or in the Part 1 (General) articles of the trade sections.

Quick Reference: The 8 Red Flags

Red FlagStandardRed Flag VersionExposure If Missed
Liquidated damagesRealistic daily rate to substantial completionHigh rates, interim-milestone LDs, LDs plus actual damagesDaily bleed that can exceed your margin in weeks
No-damages-for-delayTime extension AND compensation for owner delayTime extension only, regardless of causeYou eat the cost of the owner's own delays
Retainage5–10%, reduced at 50%, released at substantial completion10% to final completion; withheld on stored materialsMonths of cash tied up after your work is done
Submittal turnaroundReasonable windows; stated review timeEverything due days after NTP; long reviews, no schedule reliefProcurement delays charged to you
Warranty duration1-year correction period; manufacturer terms2–5 year blanket warranties; extended labor warrantiesUnpriced liability years after closeout
Substitutions"Or equal" with defined procedureNo substitutions, or bid-period-only requestsSole-source pricing and lead times
Labeling/identificationConduit labeled at terminationsLabels at fixed intervals along entire runs; custom taggingUncarried labor — real example: $600k+
Coordination drawingsGC leads composite coordinationFull BIM/composite drawings per sub; sign-off before fabricationUncarried modeling cost; schedule hostage to other trades

1. Liquidated Damages Clauses

Where it hides: Division 00 — Agreement form, Supplementary Conditions, sometimes the Instructions to Bidders. Cross-referenced in Division 01 schedule sections.

What standard looks like: LDs are legitimate and common on public work: a daily amount that's a genuine pre-estimate of the owner's delay cost, running from the contract completion date until substantial completion.

What a red flag looks like:

  • Daily amounts far out of proportion to project size
  • LDs assessed on interim milestones, not just final completion
  • LDs plus the owner reserving the right to actual damages (double-dipping language)
  • LD periods running to final completion rather than substantial completion, so punch list and closeout paperwork accrue damages

What it costs you if missed: LDs are the cleanest money an owner ever collects — no proof of harm required, deducted straight from your pay applications. At $5,000/day, a three-week delay is $105,000. If your bid carried 8% margin on a $1.5M contract, that's most of it gone.

What to do: You usually can't RFI an LD clause away, but you can RFI ambiguity — which milestones carry LDs, whether the trigger is substantial or final completion. Then price it: test schedule realism against the exposure and carry contingency or acceleration cost. On negotiated work, ask for a cap or mutual delay-damages provision.

2. No-Damages-for-Delay Clauses

Where it hides: Division 00 — General or Supplementary Conditions, usually in the article covering delays and time extensions.

What standard looks like: If the owner delays you — late access, slow decisions, design errors — you get a time extension and compensation for extended overhead and standby costs.

What a red flag looks like: Language stating a time extension is your "sole and exclusive remedy" for delay, regardless of cause. Some versions carve out narrow exceptions (active interference, bad faith); the aggressive ones don't.

What it costs you if missed: Everything time costs you: extended general conditions, supervision, equipment rental, escalation, and a crew stuck on a stalled job. On a six-month owner-caused delay, that's easily six figures for a mid-size sub — and the clause says you eat it.

What to do: Flag it in your go/no-go decision; some contractors simply won't bid unrestricted no-damages-for-delay work. If you bid, price the schedule risk realistically, and document delays obsessively from day one — many jurisdictions won't enforce the clause against active owner interference, but only if your records are airtight.

3. Unusual Retainage Terms

Where it hides: Division 00 — Agreement and payment articles; sometimes restated in Division 01 payment procedures (Section 01 29 00).

What standard looks like: 5–10% retainage depending on the state and market, commonly reduced or halted at 50% completion, released at substantial completion. Many states cap retainage on public work by statute.

What a red flag looks like:

  • 10% held on everything, all the way to final completion — including closeout paperwork that depends on other parties
  • Retainage withheld on stored materials you've already paid vendors for
  • Release contingent on events you don't control (owner's financing, other primes' completion)
  • No reduction as the job progresses

What it costs you if missed: Cash. If you're an early-finishing trade — sitewide rough-in, underground utilities — you can be functionally complete for a year while 10% of your contract value sits with the owner. On a $2M contract that's $200,000 of working capital financing someone else's project, and the carrying cost wasn't in your bid.

What to do: RFI whether retainage reduces at 50% and whether stored materials are exempt. Price the carrying cost of your expected retainage timeline into overhead. On public work, check your state's retainage statute — specs sometimes demand more than the law allows, and a pre-bid RFI citing the statute usually fixes it.

4. Onerous Submittal Turnaround Requirements

Where it hides: Division 01 — Submittal Procedures (Section 01 33 00), plus each trade section's Part 1 submittal article.

What standard looks like: A submittal schedule developed after award, reasonable preparation windows, and a stated architect/engineer review period (commonly around two weeks) with resubmittal procedures.

What a red flag looks like:

  • All submittals due within a short fixed window after Notice to Proceed — 15 or 30 days for the entire job
  • Long engineer review periods (30+ days) with explicit language that review time is not grounds for a time extension
  • Unlimited resubmittal cycles with the clock restarting each time, at your schedule risk
  • PE-stamped submittals required on items that normally don't need them

What it costs you if missed: Submittal turnaround is a schedule clause wearing paperwork clothing. If you can't get gear submittals approved, you can't release switchgear — and on today's lead times, a 60-day submittal cycle on long-lead equipment can push energization by months. Combine this with the LD clause from item 1 and the paperwork delay becomes a liquidated damages bill.

What to do: Build the submittal schedule during the bid, not after: count the submittals, map the long-lead items, and test whether the required turnaround is physically possible. RFI anything ambiguous about review durations. This is one place DeadFront helps directly — it auto-builds a submittal log from the spec set with CSI section, submittal type, and long-lead flags, exportable to Excel, so you can sanity-check the burden before bid day instead of discovering it after award.

5. Non-Standard Warranty Durations

Where it hides: Division 01 — Closeout/Warranties (Section 01 78 36 or similar), plus warranty articles buried in individual trade sections. Check both — they often conflict.

What standard looks like: A one-year correction period from substantial completion (the AIA A201 pattern), plus manufacturers' standard product warranties passed through. Certain systems (roofing, for example) customarily carry longer manufacturer warranties.

What a red flag looks like:

  • Blanket two- to five-year contractor warranties on all work
  • Extended labor warranties riding on top of manufacturer material warranties — the manufacturer ships you a part in year four, and you send a crew for free
  • Warranty periods that restart on repaired work
  • Warranty start tied to final acceptance rather than substantial completion, on a project where final acceptance drifts

What it costs you if missed: A tail of unpriced liability. Warranty callbacks in year three come out of that year's overhead, long after the job closed. Extended labor warranties on equipment-heavy systems are the expensive version — labor is usually the biggest cost of a warranty call, and manufacturers never cover it.

What to do: Search every occurrence of "warranty" and "guarantee" across the spec set and reconcile Division 01 against the trade sections. RFI conflicts (they're common). Price extended warranties explicitly — an allowance per year of extended coverage on affected systems — rather than hoping the phone doesn't ring.

6. Restrictive Substitution Clauses

Where it hides: Division 00 — Instructions to Bidders (substitutions during procurement), and Division 01 — Substitution Procedures (Section 01 25 00).

What standard looks like: Products specified with named manufacturers plus "or equal" language, and a defined procedure for proposing substitutions with reasonable documentation.

What a red flag looks like:

  • "No substitutions will be considered" — period
  • Substitution requests accepted only during bidding, with a deadline days before bids are due, then closed forever
  • Approval standards so subjective ("sole discretion of the architect") that "or equal" is meaningless in practice
  • Single-manufacturer specs with no "or equal" on long-lead or volatile-price items

What it costs you if missed: You're sole-sourced. The named vendor knows it, and post-award pricing behaves accordingly. Worse is the lead-time trap: if the sole specified switchgear line quotes 40 weeks after award and substitutions are closed, you own the schedule consequence — see red flags 1 and 2 again.

What to do: During the bid, get quotes on the actual specified products, not your usual equivalents. If a specified item has a lead-time or price problem, use the pre-bid substitution window or RFI process while it's open — after award is too late. If you bid an alternate manufacturer anyway, qualify your bid explicitly, knowing many public owners will treat that as non-responsive.

7. Unusual Labeling and Identification Requirements

Where it hides: Division 01 identification sections, and Part 3 (Execution) of trade sections — for electrical, Section 26 05 53 (Identification for Electrical Systems).

What standard looks like: Industry-standard identification: conduit and raceway labeled at terminations and points of origin, panel schedules typed, circuits identified at devices, cable tagged at pulls and terminations.

What a red flag looks like: Identification at fixed intervals along entire runs, custom owner tagging schemes with engraved plates, color-coding systems beyond code requirements, or labeling formats requiring owner-furnished asset numbers you won't have until closeout.

What it costs you if missed: Here's the real one. A contractor bid a data center where the spec required conduit labeling every 30 feet along the run — not just at start and termination, the industry standard their estimate assumed. Across more than a million feet of conduit, that single sentence meant tens of thousands of additional labels, the labor to install them, and rework on completed runs. Final damage: a $600k+ loss and a multi-week delay. Nobody carried it because nobody expected a labeling paragraph to be worth reading closely.

What to do: This class of deviation — a standard-sounding requirement with one non-standard parameter — is the hardest to catch by skimming, because the paragraph looks exactly like every other identification spec you've read. Read the execution articles at full attention, or use a tool built for this: DeadFront's risk-scored extraction flags requirements that deviate from standard practice, with a rationale and a citation that highlights the exact sentence in the PDF. The 30-foot labeling requirement is precisely the kind of item that surfaces at the top of the high-risk list. If you find one manually, quantify it (labels × labor) and either price it or RFI to confirm intent — sometimes it's a copy-paste error from another project, and an answer of "terminations only" just saved you the money.

8. Coordination-Drawing Burdens

Where it hides: Division 01 — Project Management and Coordination (Section 01 31 00), sometimes with BIM requirements in a separate Division 01 section or an exhibit.

What standard looks like: Each contractor coordinates its own work; the GC or CM leads composite coordination where trades overlap, with reasonable participation from subs.

What a red flag looks like:

  • Each subcontractor required to produce full composite coordination drawings or a discipline BIM model to a specified LOD
  • No fabrication or installation permitted until coordination drawings are signed off by every trade — your schedule is now hostage to the slowest participant
  • Mandatory weekly coordination meetings for the project duration, modeling software mandates, clash-resolution obligations with no compensation mechanism

What it costs you if missed: Two costs. The direct one: modeling and coordination-drawing production is real scope — detailer time, software, meetings — that can run tens of thousands of dollars on a mid-size project and is invisible in a takeoff. The schedule one: a sign-off-before-fabrication clause converts another trade's slow modeling into your procurement delay, and (red flag 2 again) you may have no delay-damages remedy.

What to do: Price the coordination effort as its own line item. RFI the sign-off mechanics: what happens when another trade is late, and does the milestone schedule carry float for coordination? If the burden is genuinely disproportionate for your scope, raise it pre-bid; owners sometimes scale the requirement back when someone actually asks.

RFI, Qualify, or Price It In?

Every red flag resolves into one of three moves, and picking the right one is most of the skill:

MoveWhen to Use ItWatch Out For
Pre-bid RFIThe requirement is ambiguous, conflicts with another section, or looks like a copy-paste errorRFI deadlines in the Instructions to Bidders — often a week or more before bid day. Miss the window and this option is gone.
Qualify the bidThe risk is real, priced poorly by everyone, and you want the job on adjusted termsOn public hard-bid work, qualifications can make you non-responsive. Mostly a negotiated-work tool.
Price it inThe requirement is clear and enforceable — LDs, retainage carry, extended warranties, labeling scopePricing risk only works if you found the risk. The $600k labeling miss wasn't a pricing failure; it was a detection failure.

The common thread: all three moves happen before bids are due. After award your leverage is gone, and the RFI becomes a change-order fight you'll probably lose.

That's the honest case for reading these divisions line by line on every pursuit — and for automating the first pass. DeadFront ingests the full bid set and surfaces the non-standard provisions with risk scores and PDF citations in minutes, so your senior estimator spends their limited hours judging the 2–5 items that matter instead of re-reading 80 pages of boilerplate to find them. If you're comparing tools in this space, our DeadFront vs Document Crunch comparison covers how spec-focused analysis differs from contract-only review.

FAQs

What's the difference between Division 00 and Division 01?

Division 00 contains the bidding documents and legal framework: instructions to bidders, bid forms, agreement, bonds, and general/supplementary conditions. Division 01 contains the administrative rules for executing the work: submittals, quality control, coordination, closeout. Contract-risk clauses (LDs, delay damages, retainage) live mostly in Division 00; process burdens (submittals, coordination drawings, warranties, identification standards) live mostly in Division 01. Review both — plus the Part 1 articles of your trade sections.

How long does a proper Division 00/01 review take?

Manually, plan on 2–4 hours for an experienced estimator on a typical bid set — front-end documents are usually 50–150 pages, and the review is reading for deviation, not skimming. With AI-assisted extraction, the first pass takes minutes and the estimator's time shifts to evaluating the flagged items.

Are liquidated damages clauses enforceable?

Generally yes, when the amount is a reasonable pre-estimate of the owner's delay cost rather than a penalty. Courts in most U.S. jurisdictions enforce them without requiring the owner to prove actual damages. Treat any LD clause as fully enforceable when you price the bid; arguing unenforceability after the fact is expensive and uncertain.

Do Division 01 requirements override the trade sections?

Division 01 applies to all work and is read together with each trade section. When they conflict — a one-year warranty in the trade section and a two-year warranty in Division 01, say — most general conditions include an order-of-precedence clause, and many state the more stringent requirement governs. Don't guess: RFI the conflict before bid so every bidder prices the same obligation.

What should I do if I find a red flag after the RFI deadline has passed?

Your options narrow to pricing it or passing on the bid. Price the requirement as written — assume the worst reasonable interpretation — and note it in your bid file so the project team knows the exposure on day one. On negotiated procurements you may still raise it in scope review; on public hard-bid work, the number you submit has to carry it.

Can AI really catch these red flags reliably?

This is the problem AI handles well: comparing every provision in a large document set against standard practice and flagging deviations with citations back to the source text. DeadFront typically surfaces 15–40 non-standard requirements per 1,000-page spec set, each risk-scored with a linked PDF highlight so a human can verify in seconds. It doesn't replace estimator judgment on what to do about a flag — but it makes detection fast and consistent instead of dependent on whoever had time to read the front end that week.

Bottom Line

Division 00 and 01 are where bids are lost before the takeoff even starts. The eight red flags — liquidated damages, no-damages-for-delay, retainage terms, submittal turnaround, warranty durations, substitution restrictions, identification requirements, and coordination burdens — share one trait: they look like boilerplate until they cost you six figures. Read them on every pursuit, use the pre-bid RFI window while you have leverage, and price what you can't change.

If you'd rather not bet the bid on a manual read of 150 pages of front-end documents, DeadFront does the first pass for you: upload the bid set, get a risk-scored list of every non-standard provision with citations into the source PDF, plus a one-page bid brief and an auto-built submittal log. Try the interactive demo, check out pricing (Pro is $1,000/month with a 30-day risk-free pilot), or book a 15-minute walkthrough and bring your ugliest spec set.

Ready to catch million-dollar mistakes?

See how DeadFront.AI automates specification review and prevents costly errors.