NewRFI Agent is now available: drawing and spec conflicts, found before tenderRead the announcement →

The Scope Gap Index  /  Division 01

Division 01 · General Requirements · Q3 2026

What Scope Agent flagged in general requirements scope packages

38 Division 01 packages across 20 projects, generated between 17 July and 30 September 2026 for Provision customers, ranked by how often each job got flagged. Model flags, checked by a person on fewer than one item in a hundred. Where to look, not proof.

38

Division 01 packages across 20 projects, 17 July to 30 September 2026

34

of 38 had at least one flag from Scope Agent

251

flags in total: 127 inferred, 124 coordination

49%

of flags were coordination flags, the closest to an even split of any division

Inferred means Scope Agent judged the job necessary and found no scope naming who does it. Coordination means it judged the job to sit between two trades. Neither is a confirmed omission on that project.

Ranked

Testing leads, in the package that belongs to the GC

Division 01 is the general contractor’s own package: general conditions, final cleaning, commissioning, surveying, the tower crane. Scope Agent flagged testing, inspection and certification in 18 of 38 packages, 15 of them as inferred. The spec requires the test, the general requirements say someone arranges it, and no trade is named. Temporary protection is second at 14. Everything below that sits at 12 or fewer, which is what you’d expect from a package that describes the job rather than a trade.

Job flaggedPackagesInferredCoordinationShare flagged
Testing, inspection and certification15 inferred · 9 coordination18 of 3815947%
Temporary protection13 inferred · 4 coordination14 of 3813437%
Anchors, embeds and connections6 inferred · 7 coordination12 of 386732%
Maintenance, warranty and spares11 inferred · 0 coordination11 of 3811029%
Sealants, flashing and waterproofing joints2 inferred · 10 coordination11 of 3821029%
Utility and service connections8 inferred · 6 coordination11 of 388629%
Blocking, backing and support1 inferred · 10 coordination10 of 3811026%
Cleaning8 inferred · 3 coordination10 of 388326%
Openings, cutting and patching1 inferred · 7 coordination8 of 381721%
Penetrations, sleeves and firestopping2 inferred · 6 coordination8 of 382621%
Removal, demolition and disposal6 inferred · 2 coordination8 of 386221%
Hoisting, lifting and delivery6 inferred · 2 coordination7 of 386218%
Tolerances, joints and trade interfaces3 inferred · 3 coordination5 of 383313%
Scaffolding, shoring and access1 inferred · 2 coordination3 of 38128%
Shop drawings and submittals1 inferred · 1 coordination2 of 38115%

“Inferred” and “coordination” count packages with that kind of flag, and a package can have both, so the two columns can add to more than the total. The generic supply-versus-install topic (20 of 38) is left out; see the method note.

Beyond the ranking

Three things the table doesn’t tell you

1. The split is almost even

Across all 1,290 packages, inferred flags outnumber coordination flags by three to two. General requirements come out at 127 inferred against 124 coordination, closer to even than any other division. A GC package names the boundaries between trades as often as it leaves a job unassigned, because drawing those boundaries is what the package is for.

2. Blocking and sealants are boundary flags here

Blocking drew ten flags, and all ten were coordination flags, with only one inferred. Sealants drew 11, ten of them coordination. The GC isn’t installing backing or caulk. The flag says the general requirements put a line between two trades and didn’t say which trade is on which side of it.

3. Sixteen of the 38 carry a label we couldn’t map

Sixteen packages carried a customer-specific label that doesn’t map to a standard trade, the largest share of any division on the Index. Sixteen more were labelled simply GC, three final cleaning, and one each commissioning, surveying and tower cranes. Read the ranking as a picture of the GC’s catch-all package, not of any one trade.

The items in detail

What each flag usually points at, and how to close it in the scope

The six jobs flagged most often, after the generic supply-versus-install topic. Check your own documents before assuming a flag is right.

Testing, inspection and certificationflagged in 18 of 38 packages

Usually points at third-party testing the spec requires and nobody carries: concrete cylinders, compaction, special inspections, the commissioning agent, the final air balance report. Fifteen of the 18 flags were inferred. Put every test the spec calls for in a schedule, name who orders it and who pays for a failed one.

Temporary protectionflagged in 14 of 38 packages

Protection of finished work, existing surfaces and adjacent property for the life of the job: the lobby floor, the elevator cab, the neighbour’s fence. Thirteen of the 14 flags were inferred. Say whether the GC’s general conditions carry it or each trade protects its own work, and for how long.

Anchors, embeds and connectionsflagged in 12 of 38 packages

In a GC package this is the tower crane base, the hoist tie-ins to the structure, and the temporary power and water connections. Six inferred, seven coordination. Name who designs the crane base, who casts it and who removes it.

Maintenance, warranty and sparesflagged in 11 of 38 packages

The warranty period, the close-out binder, attic stock and the maintenance of temporary systems. All 11 flags were inferred. State the warranty start date, who holds the master list of trade warranties and who chases the defects.

Sealants, flashing and waterproofing jointsflagged in 11 of 38 packages

Ten of the 11 flags were coordination flags: the general requirements describe a weather-tight building without saying which trade seals the joint between the window sub’s frame and the siding sub’s panel. Put the envelope boundaries in a matrix and attach it to every exterior scope.

Utility and service connectionsflagged in 11 of 38 packages

Temporary power, water and heat for the site, and the permanent connections the utility makes. Eight inferred, six coordination. Say who applies, who pays the utility’s charges and when the temporary service comes down.

Writing the package rather than checking it? The scope of work template covers the structure every subcontract needs, and the subcontractor scope examples show how the boundaries read when they’re written down.

Method

How we counted

38 scope packages classified to MasterFormat Division 01, generated by Scope Agent between 17 July and 30 September 2026 on 20 of the 24 projects in the quarter’s cohort. Sixteen carried the trade label GC, three final cleaning, and one each commissioning, construction surveying and tower cranes. Sixteen more carried a customer-specific label we couldn’t map to a standard trade; they’re counted here because the package itself was coded to the division. A package is one trade on one project, as it stood at quarter end. An item counts when Scope Agent flagged it as inferred or coordination. We grouped the items into sixteen topics by keyword, and one item can land in more than one topic.

38 packages on 20 projects clears our 20-package threshold for publishing a division, and one package moves a share by about three points, so treat the ranking as an order and the percentages loosely. The bigger caution is that Division 01 is a catch-all, and nearly half its packages carry a label we couldn’t map. These are Provision customers’ projects, and the numbers describe this sample only. A flag is Scope Agent’s judgment, checked by a person on fewer than one item in a hundred, so some flags will be wrong. We’ll update it every quarter.

See what Scope Agent flags in your own general requirements

Upload your drawings and specs. Scope Agent flags the inferred and coordination scope before the bid leaves your office, and your estimator decides what’s real.

Book a Demo