Eight habits of GCs whose scopes hold up

Drawings-first, not boilerplate-first

The first habit is also the most consistently violated. The best teams start every scope from the drawings of the current project; they refuse to copy the previous job's scope sheet into the new project and edit from there. The reason is operational, not philosophical.

Templates have a role — but only as a checklist of items to confirm against the current drawings, not as a starting body of text. A Pre-Construction Lead at a Top-ENR Canadian GC frames it as “process of elimination instead of trying to create it. Because I'll never know. I'm not a mass timber expert. I'm not a door expert.” A checklist of 80-plus line items per trade lets him be “95% confident” he caught everything in four hours.

Specific document references, not generic incorporation

Every clause in a great scope of work points to the document where the work is defined. Sheet number. Detail callout. Spec section. Addendum number and date. The reasons for this are belt-and-suspenders.

• It collapses the time to resolve a field dispute from days (junior PM hunts through 1,200 pages) to minutes (junior PM opens to the cited sheet).
• It survives the addendum cycle. When drawing A2.04 is reissued, the team knows every scope clause that referenced it.
• It eliminates the “we didn't see it on our set” dispute. The set is named.

An Owner at a Small/Mid-Market Quebec GC: “We go into the mechanical drawings. Changes in ductwork require blocking of through-wall openings in demising walls where ducts are removed. We'll highlight those to the drywall contractor who would never look at the mechanical drawings, would never pick this stuff up.” Every cross-discipline scope item is cited.

Front-load the buyout conversations

Scope gaps surface no matter what; the question is whether they surface during the bid window, when the GC has leverage, or after award, when the GC has none. The best teams treat the scope sheet as a tool for forcing ambiguity to the surface before the bid closes — not as a passive document mailed alongside the drawings.

• Pre-bid phone calls to shortlisted subs. “We will call them ahead of time — ‘do you have R1? Do you have R2? Do you have the flashings?’ And they might be like, ‘oh, we have flashings up to this point but not this point’” (Pre-Con Lead, Top-ENR Canadian GC).
• Yes/no checklist scopes returned signed. “We used to do more of a written scope. People would submit a bid and may or may not make markups, and later on there can be arguments. That's why we switched to the checklist — because you've done that, there's no question” (Director of Pre-Construction at a Mid-Market Canadian Self-Perform GC).
• Time-stamped internal interpretation calls. When language is ambiguous, the estimator adds a documented allowance, writes the assumption into an internal email, and uses that record to negotiate with the owner later. “It's pretty easy to say it's excluded if it's time-stamped” (Director of Pre-Construction at a Mid-Market US GC).

Templates as a floor, not a ceiling

Nearly every well-run team we spoke with maintains a master scope library by trade. The library is built from lessons learned — items missed on previous jobs, recurring trade exclusions, gaps that bit the team once and were not allowed to bite a second time. A Senior PM/Estimator at a Mid-Market Canadian GC describes it: “We've got a library of master scope of work lists for each trade division. That's been made up of things that we've come up with over the years, lessons learned, things that were missed that we don't want to miss again. We copy it into the job and then edit it, customize it to match the drawings and the specs.”

The discipline is in the editing. A generic inferred-scope laundry list, applied to a project it doesn't fit, is worse than no template at all. A PM at a Canadian ICI GC: “One thing to just have all these kind of catch-all statements, but if they don't even apply, it doesn't add much weight to the job.” Subs learn to ignore boilerplate the second they spot an item that obviously doesn't apply. The library is a starting point; the project-specific edit is the work.

The pre-bid walk is a scoping tool, not a courtesy

The walk is where coordination scope is discovered. The skinniest scope sheets we saw all had one thing in common: their authors had walked the building, read the geotech, and called the architect with three specific questions before they wrote a line. Two patterns repeat.

• Read the geotech before the drawings. A PM at a Mid-Market Self-Perform GC: “Sometimes it's buried in there. There's usually a lot of juicy information in those geotechs that we need to kind of ferret out.” Compaction percentages, lift requirements, bearing assumptions — most of it lives in the geotech report and never makes the drawings.
• Index the drawing set page-by-page — do not trust the cover sheet. “Architects will often put the drawing list on the cover, but it's extremely rare that it actually matches what's in the set. I've actually had projects where they were trying to hold us contractually to revision 2 which had all this extra landscaping stuff on it when really all we had was revision 1” (Senior Estimator at a Mid-Market Canadian ICI GC).

Sub-specific tailoring — sophistication matters

A scope written for an MEP sub does not read like a scope written for a flooring sub. A Director of Pre-Construction at a Mid-Market Canadian Self-Perform GC: “There's the general and there's the detail. Mechanical or electrical subcontractors are highly sophisticated. When you're dealing with the flooring guy, he just lays down floor. The things you need to say and specify are different.”

The implication is operational. A standard scope template treated as one-size-fits-all will be too thin for the trades that need detail (MEP, curtainwall, elevators) and too thick for the trades that don't (flooring, painting, basic finishes). The estimators who manage this best calibrate the level of detail to the bid-package risk.

Clarifications, not just exclusions

Exclusions are defensive language: “we are not responsible for X.” Clarifications are affirmative language: “this contractor is responsible for X, including Y.” Affirmative language does more work on three fronts: it survives boilerplate exclusions sent back by the sub, it prevents two trades from both excluding the same line, and it gives the field super a clear basis for resolving a dispute on the spot.

A Senior Estimator at a Mid-Market Canadian ICI GC: “We do not incorporate those lead letters into the contracts. Ultimately the lead letter or the quote gets set aside and what's written on that scope of work becomes the Bible for the job.” Lead-letter exclusions only survive if they get migrated into the scope sheet itself.

The pre-issue scope review checkpoint

Every well-run team described some form of structured pre-issue review — a checkpoint with a named owner, completed before the bid invitation goes out. The form varies; the discipline is the same.

• Two senior reviewers, page by page. “When the two of us review subcontracts, we go through them top to bottom, page by page. Make sure it's structured properly, everything is in the right order, and drill into the trade-specific scope of work” (VP of Operations at a Top-ENR Canadian GC).
• PM sign-off before contract issue. “The people who are building the job are always going to need to sign off on this” (Construction Manager at a Top-ENR Canadian GC). Pre-con may write the scope; the PM who has to live with it for two years has to bless it.
• 100% coverage check by elimination. Assign every captured line item to a sub. Whatever remains unassigned is the gap list. This single discipline catches more orphan scope than any template review.