The schedule and the contract are supposed to be the same story told two ways. On most jobs, they aren't. The contract lives in a binder — or worse, an email thread — that nobody opens until there's money on the table, and the look-ahead gets built from field reality and a superintendent's gut. That gap is where the ugly change-order fights live. It's where a sub shows up to do work he swears isn't his, where retention gets held on the wrong percentage, where a warranty claim lands on you two years later because nobody tracked when the clock started.
Tying subcontractor management to contract terms isn't paperwork for its own sake. It's how you keep the weekly plan honest — how you make sure the work you're scheduling is work someone is actually obligated and paid to do, in the sequence the deal assumed. Here's how the two fit together on a real job, and where they usually come apart.
Scope Is the First Thing You Verify, Not the Last
Most scheduling problems that look like coordination problems are really scope problems. You've got drywall and the framer arguing over backing for the grab bars. You've got the fire-stopping caulk that the drywaller assumed was in the mechanical scope and the mechanical sub assumed was in fire protection. Nobody's lying — the scope was never nailed down, and now it's a hole in your wall on the day of the inspection.
Before you drop an activity into a look-ahead, you should be able to answer one question: whose contract covers this, exactly? Read the exclusions, not just the inclusions. Subcontract exclusions are where the real scope lives — "excludes cutting and patching," "excludes temporary heat," "excludes final clean." Those three lines will cost you a week each if you find them on the day the work is due.
The practical move is to walk the scope gaps room by room before the trades hit that area, not project-wide in a conference room. Overlaps are annoying but cheap — two subs both think they own it, you point at the contract, done. Gaps are the killers, because a gap becomes a change order, and a change order becomes a schedule delay. When you're building the plan, treat any activity you can't tie cleanly to one subcontract as a red flag to resolve now, not a note to circle back to.
The Contract Date and the Look-Ahead Have to Reconcile
Every subcontract has a duration baked into it, even if it's only implied by the number of crews the sub priced. When your three- or four-week look-ahead assumes a pace that sub can't hit with the manpower he bid, you have a contract problem dressed up as a scheduling problem — and the sub knows it even if you don't.
Run this check early: take the contracted man-hours or the bid crew size, lay it against the durations your weekly work plan needs, and see if the math closes. If your plan needs the electrician to rough-in a floor a week and he priced two crews that can do a floor every ten days, you're going to be short before you start. Better to have that conversation at buyout than at week six when you're leaning on him to "catch up" work he was never staffed to do.
A few rules of thumb that keep schedule and contract from drifting apart:
- Milestone dates in the schedule should trace to a contract obligation or a downstream trade's start — not a date you picked because it felt right. If you can't say why a date matters, the sub won't respect it.
- Build a buffer between adjacent trades where an inspection or a cleanup sits — frame-to-rough-in usually wants a day or two for the framer to clean up and the inspector to sign off before the walls fill with pipe and wire. That buffer is yours; don't let a tight contract date eat it.
- When the contract fixes a completion date and your realistic sequence blows past it, that's a formal conversation and probably a change — not something you quietly absorb by compressing everyone downstream.
This is exactly where good look-ahead software earns its keep. When the weekly plan is visual and location-based, a pace mismatch shows up as a wall you can't build fast enough — you see it three weeks out instead of feeling it the Monday it's already late. Tools like LookAheadWall are built so trade-flow sequences and durations are in front of you while you plan, which makes the reconciliation against contract durations a normal part of the routine instead of a fire drill.
Payment Terms Belong in the Schedule, Because Subs Schedule Around Cash
Here's something the office side often misses: subs sequence their crews around getting paid, not around your critical path. A sub who's carrying you on a slow-pay job will move his best crew to whoever cuts checks on time, and he'll do it without telling you. Your beautiful look-ahead means nothing if the manpower quietly walked.
The contract's payment terms — retention percentage, billing cycle cutoff, pay-when-paid clauses — are schedule inputs whether you treat them that way or not. Tie your progress tracking to the payment milestones so that when a sub completes a floor, the billing actually reflects it and the check moves. Nothing keeps a crew on your job like a pay app that goes through clean and on time. And know your retention terms cold: a sub who thinks he's getting 5% held and finds out at closeout it was 10% will fight you on the last item on the punch list out of pure spite.
Change Orders: Keep the Extra Work Visible and Separate
The single most common way jobs lose money on changes isn't the price of the change — it's that the extra work gets absorbed into the base scope in the field and never billed. A sub does the added work because your foreman told him to, and three months later there's no paper, no signed change, and an argument nobody can win from memory.
Discipline here is simple and unglamorous: no changed work goes into the weekly plan as if it were base scope. When a change order adds activities, they get tracked as change-order work with a reference back to the contract they modify. That way the relationship stays legible — this activity exists because of this change, which modified this original scope. When the number gets big enough to need higher approval, the contract value usually tells you the threshold; respect it, because a foreman approving a $40,000 change on a handshake is how principals end up eating it.
Keep the documentation as you go, not at the reckoning. Daily logs, dated photos, the email where the owner's rep said "yeah, do it" — that's the record that settles a change dispute. Reconstructing it after the fact never works, and everyone remembers the version that favors them.
Insurance, Certifications, and the Compliance Trap
You can't schedule a sub whose certificate of insurance lapsed last week. Well — you can, and plenty of superintendents do, right up until someone gets hurt and the carrier walks away because the additional-insured endorsement was never in place. The contract specifies the coverage; the field has to actually verify the certificate matches before the crew is on the schedule.
Same logic for certifications tied to specific work — the welder's cert, the flagger's card, the confined-space qualification. If an activity legally requires a qualified person and you schedule it against a crew that doesn't have that person, you've built a plan that can't legally execute. Catch that when you're staffing the look-ahead, not when the inspector asks for the paper. A quick habit that saves grief: flag any activity with a certification requirement so it can't go active until the qualification is confirmed on file.
Closeout and Warranty Start Long Before You Think
Closeout is a scheduled activity, and treating it like one is the difference between a clean final payment and a sub who's disappeared with three items on the punch list and your retention in the wind. Every subcontract has its own closeout requirements — as-builts, O&M manuals, lien waivers, warranty letters, attic stock. Pull those requirements out of each contract and put them on the look-ahead as real activities with dates, because the sub's motivation to finish paperwork evaporates the day he pulls his last crew.
Tie the final retention release to that closeout list being complete. It's the only leverage you have left at the end, and it works. Chase the lien waivers before you cut the last check, never after.
Warranty is the one that bites long after everyone's forgotten the job. The warranty clock usually starts at substantial completion, sometimes at the sub's own completion — and the notification procedure in the contract dictates how you have to file a claim to keep it valid. Capture those dates and terms when you close the contract out, while the paper is in front of you. Two years later when the roof leaks, you want to know in five minutes whether it's covered and how to notice the sub, not spend a week digging through a binder to find out the window to claim closed last month.
Make the Two Systems Talk
None of this requires a mountain of software. It requires that the person building the weekly plan can see the contract terms that constrain it — scope, duration, payment, compliance, closeout — instead of scheduling in a vacuum and colliding with the contract in the field. When your short-interval schedule and your subcontracts tell the same story, the arguments get shorter, the changes get billed, and the subs trust that the plan reflects the deal they signed.
The superintendents who run smooth jobs aren't the ones with the fattest contract binders. They're the ones who read the exclusions before the trade shows up, who staff the look-ahead against real contracted capacity, and who never let extra work slip into the base scope unbilled. Get the schedule and the contract pointing the same direction, and most of the fights you're used to having simply stop happening.