Division 01 — General Requirements — is the spec section everyone acknowledges and almost no one reads carefully. It sits at the front of the project manual. It runs anywhere from 40 to 150 pages. And it contains clauses that can swing your margin by hundreds of thousands of dollars.
Liquidated damages. Coordination-of-trades requirements. Insurance minimums that exceed your existing coverage. Scheduling submission timelines with non-compliance penalties. These are not buried in the technical specs. They are right there in Division 01, waiting for an estimator who is too busy to read them.
The average construction dispute in North America was worth $60.1M in 2024, according to the Arcadis Global Construction Disputes Report. "Errors and omissions in contract documents" has repeatedly ranked as the #1 dispute cause in North America across the years Arcadis has tracked. Division 01 is the document layer where those omissions most often originate — because it is the layer where scope, schedule, and risk allocation intersect.
This guide is for GC estimators and pre-construction teams who want a systematic approach to finding construction risk in Division 01 specs before bid day.
Not every clause in Division 01 carries the same weight. Some sections are administrative boilerplate. Others are loaded with financial exposure. Here are the eight you need to review on every project.
This section defines the project scope and, critically, what is excluded. Read it against the drawings. Owner-furnished equipment, phasing restrictions, and access limitations often appear here without making it into the drawings or the sub scopes.
Watch for language like "work not included" or "owner-supplied." If the spec says the owner supplies equipment but does not say who is responsible for connections, installation, or startup, that gap lands on the GC. Write it into your sub scopes explicitly or it disappears.
This section covers access limitations, occupied facility requirements, noise ordinances, and construction hours. These directly affect your schedule and your sub pricing.
A hospital project with night-work restrictions is a different job than one without them. If your mechanical sub priced an eight-hour day and the restriction limits work to four hours in certain areas, your buyout conversation gets expensive. Catch it here, not at buyout.
Substitution rights can meaningfully affect your ability to recover on material costs. Some owners lock in specified products with no substitution allowed. Others allow substitutions only within a narrow window — sometimes as short as ten days from contract award.
If you have priced an alternate product and the substitution window closes before you complete buyout, you have a problem. Note the window date. Build it into your buyout schedule.
This is where the change order process lives. It defines notice periods, required documentation, and approval chains. Most GCs read this once during contract review and never flag it to the field team.
The risk: if your project requires written notice within 48 hours of a potential change and your superintendent logs it on day five, you have likely waived your right to claim. That is a contractual trap, and it is in Division 01. Get the notice requirements into your project startup checklist.
Scheduling requirements vary enormously between owners and project types. Some require a simple bar chart updated monthly. Others require a fully resource-loaded CPM schedule with a two-week look-ahead submitted every Friday by noon.
If your estimating budget included one scheduler at $120/hour for two days a month, and the spec requires a dedicated scheduling resource submitting weekly, you have underbid the project before you have broken ground. Check the schedule submission requirements and the recovery schedule provisions.
This is the miscellaneous-metals scatter problem applied to Division 01. Temporary hoarding, site fencing, security, fire watches, dust control, temporary heat, temporary utilities — all of it costs money and all of it is often listed here without a clear owner/GC split.
On a recent project reviewed through Provision's scope of work template methodology, a team identified that the spec required a full-time fire watch during hot-work operations but had not priced any labour for it. The cost to self-perform was $38,000 over the project schedule. That is a recoverable cost — but only if you catch it at bid.
Storage, handling, and protection requirements for materials often live here. This is where the $10,000 glulam beam problem originates: a project team took delivery of mass-timber components, stored them on site without protection, and sustained weather damage — because no clause in the spec required material protection and no one had written it into the scope.
Read the product requirements section against your lay-down plan. If the spec requires climate-controlled storage for certain finishes, that is a cost. If it is silent and the drawings show sensitive materials, flag it as a risk item and get a clarification in writing before bid day.
Closeout requirements affect your schedule float and your final payment. Extended warranty periods, commissioning requirements, operations and maintenance manual standards, and as-built drawing submissions can each add weeks to your project closeout timeline.
If the spec requires 90-day commissioning on mechanical systems and your schedule shows substantial completion at week 48, your actual contract end is closer to week 60. That affects your bonding, your staff commitment, and your holdback release. Read it before you price the job.
Knowing where the risk lives is half the problem. The other half is understanding why experienced teams miss it repeatedly.
Division 01 risk review gets deferred to the legal or contracts team. But by the time the contract is in front of counsel, the bid is already in. You have committed to a number that did not account for the $45,000 in temporary utilities or the weekly CPM requirement. Contract review at that stage is damage control, not prevention.
The pre-bid scope review checkpoint — one of the Eight Habits from the Scope Gap Playbook — is the right moment to flag Division 01 issues. That is before the number leaves your building.
It rarely is. Owners customise Division 01. Design teams swap spec sections. Supplementary conditions override standard language. A liquidated damages clause that was $1,000 per day on last year's job might be $5,000 per day on this one. Copy-pasting your risk register from a previous project is how you miss it.
An Estimating Manager at a Canadian ICI GC put it plainly: "If you miss anything, they'll bill it." Division 01 is where that billing finds its legal footing.
The spec comes in 20 days before bid day. Division 01 gets a skim on day one and is not touched again. Questions get submitted too late to get answers. Addenda that modify Division 01 get processed for technical sections and the administrative changes get missed.
One Pre-Construction Lead at a Top-ENR Canadian GC described this as the point where risk stops being discoverable: "Pre-con is working in the scope sheet world and project management is working in the scopes of work." When those two worlds do not sync before bid day, Division 01 costs land in field budgets with no recovery path.
Use this checklist on every project. Assign it to a specific person — not "the team." Someone owns it or no one does.
Liquidated damages (LDs) are sometimes in the contract. But they are often in Division 01 as well — and the two documents do not always match. The contract might reference a daily LD rate. Division 01 might define the milestone events that trigger it, or list exceptions the contract does not carry.
Read both. Compare the LD rate, the trigger events, and any caps or carve-outs. A $2,000-per-day LD with a 90-day cap is a manageable risk. A $5,000-per-day LD with no cap and a milestone tied to a design-incomplete area of the project is a different conversation.
If the spec is silent on LD caps, ask the question during the bid period. That question — and the owner's answer — becomes part of your risk record.
Division 01 typically includes insurance and bonding requirements. These are often higher than your standard policy limits. If the spec requires $10M commercial general liability and your base policy is $5M, the cost of the umbrella extension is a real number. It belongs in your bid.
Check the additional insured requirements as well. Some owners require every sub and sub-sub to name the owner, the construction manager, and the design team. Coordinating that across a 40-trade project takes time and sometimes money. Flag it at bid. Write it into your sub scope cover letter.
Reading 150 pages of Division 01 on a tight bid timeline is not realistic for most pre-construction teams. The pressure to get drawings out to subs and get numbers back takes priority. Division 01 review gets compressed to one person, 30 minutes, and a mental flagging system that relies entirely on their experience.
That is where purpose-built construction AI changes the workflow. Risk Review reads the full project set — drawings, specs, and contract documents together — and flags risk items cited to the exact clause, section, and page. Across more than 100,000 documents processed and over 1,000,000 risks identified, it catches the kinds of exposures that a busy estimator under bid-day pressure will miss.
The result: an 80% reduction in contract and spec review time, with every flagged item traceable to its source. That is not a replacement for judgment. It is a way to make sure your judgment gets applied to the right clauses — not the ones that happen to be visible in a 30-minute skim.
For teams running multiple pursuits at once, Chat Agent lets you query the spec set directly. Ask "What are the liquidated damages terms?" or "What are the insurance requirements for subs?" and get a cited answer in under 20 seconds. No more digging through a 2,000-page project manual to find the one clause that matters.
If you want to see how this works on a live project set, book a demo and bring your own spec book.
Division 01 risk does not stay in Division 01. A coordination-of-trades requirement in Section 01 31 00 affects how you write your mechanical and electrical scopes. A temporary-utilities obligation in Section 01 50 00 affects what you put in your concrete sub's scope. A closeout requirement in Section 01 77 00 affects your finishes sub's contract terms.
This is why the subcontract language chapter of the Scope Gap Playbook treats Division 01 as the connective tissue between the contract and the trade scopes. The GCs with the tightest buyout — and the fewest change orders — are the ones who systematically transfer Division 01 obligations into sub scope packages, not the ones who rely on "as per plans and specs."
A Director of Pre-Construction at a Mid-Market Southeast GC described the gap directly: "Pre-con is working in the scope sheet world and project management is working in the scopes of work." Division 01 is the document that should bridge those two worlds. When it does not get read carefully, the gap opens — and it gets filled by change orders.
For general contractors building out a more systematic pre-construction process, the Provision platform for GCs covers the full document set: drawings, specs, contracts, RFIs, and addenda — all in one place, all cited to source.
Division 01 — General Requirements — is the first division of the project manual under the CSI MasterFormat structure. It covers administrative and procedural requirements that apply to the entire project: scheduling, temporary facilities, substitution procedures, change order processes, insurance requirements, and closeout. It applies across all trades, not just one.
Division 01 contains financial and operational obligations that rarely show up in the drawings: liquidated damages rates, insurance minimums, notice periods for change orders, and scheduling submission requirements. If these are missed at bid, they become costs the GC absorbs without recovery. They are contract commitments, not scope assumptions.
The change order notice period is consistently the most overlooked. Some specs require written notice within 24 to 72 hours of a potential change event. If the field team does not know this requirement, they miss the window. The right to claim the cost may be waived — even when the scope change is legitimate and the cost is real.
Division 01 should be reviewed at bid kickoff, not during contract execution. The obligations it contains affect how you price general conditions, what you write into sub scope packages, and how you structure your schedule. Deferring it to contract review means the number is already locked before the risk is understood.
The contract typically states the LD rate. Division 01 often defines the triggering milestone events and any applicable caps or carve-outs. The two documents do not always align. Read both and compare the trigger events, the daily rate, and whether any cap applies. Where they conflict, raise a clarification in writing during the bid period.
Yes — purpose-built construction AI like Risk Review reads the full project set and flags risk items cited to the exact clause and page. It covers contract and spec documents including Division 01, reducing review time by 80%. It does not replace estimator judgment, but it ensures the right clauses get reviewed — not just the ones that happen to be visible in a quick skim.
Division 01 obligations — coordination requirements, temporary facility responsibilities, insurance minimums — need to flow into trade-specific scope packages. If a coordination-of-trades requirement stays in the GC's Division 01 notes and never makes it into the mechanical scope, the sub has no obligation. That gap costs money at buyout or in the field. Systematic scope package generation is the fix.
Risk Review flags every liquidated damages clause, insurance requirement, and notice period — cited to the exact page.
See Risk ReviewMore Articles
