A small builder running five concurrent residential projects is also running a scheduling problem with twenty moving parts. Each trade has its own crew size, its own backlog, its own definition of “ready,” and its own way of communicating. The discipline of getting the right sub on the right site on the right day, week after week, is what separates a builder who delivers on time from one who is forever a draw behind.
The hardest part is that scheduling is not a one-time exercise. It is a continuous negotiation against a moving baseline. Framing slips three days because of weather, which pushes MEP rough into a week the electrician already committed elsewhere, which pushes insulation out, which collides with the drywall crew the builder fought to lock in two months ago. A small builder who treats scheduling as a static gantt chart drawn at project start finds the chart out of date by the second week.
The rolling four-week look-ahead
The working unit of subcontractor scheduling is the rolling four-week look-ahead, refreshed weekly. The first week is committed: subs have been confirmed, materials are staged, the work will happen unless a force-majeure event intervenes. The second week is firm: subs have been notified, the date is on their calendar, but small adjustments are still possible. The third week is planned: the dates are penciled and the subs know they are queued. The fourth week is provisional: the order of operations is set but the days are flexible.
Every Friday afternoon, the builder rolls the window forward. Week one drops off because it is done or rescheduled. Weeks two through four shift up. A new week four enters the picture. The look-ahead is then circulated by Monday morning so each sub sees their own commitments and the trades immediately before and after them on the sequence. This rhythm is what gives the builder room to recover from a slip without burning a sub’s good will.
Date commitment vs. date window
Not every sub gets a hard date. The decision of when to commit a date and when to commit a window depends on how predictable the predecessor work is.
Foundation, framing, and dry-in are usually committed as windows because they depend on weather, inspector availability, and the cascading slips that weather causes. The builder tells the framer that framing starts the week of May 18 and confirms the actual day on the prior Wednesday. MEP rough, insulation, drywall, and finish trades typically get hard dates because the predecessor is a clean inspection event rather than a weather-dependent outdoor task. The electrician is told to be on site Tuesday May 26 at 8 a.m., full stop, with the understanding that if MEP rough fails inspection, the electrician’s hard date moves but the next hard date is firm.
Hard dates are scarce currency. A builder who burns through hard-date commitments by chronically rescheduling them ends up with subs who quietly deprioritize the builder’s work. Window commitments preserve the relationship for as long as the builder confirms the actual day with enough notice for the sub to plan their week.
The framer-finishing-late cascade
On a residential build, the single most common schedule failure is the framer running long. The framer was committed to a window of May 11 through May 22. The crew gets pulled to a different project on May 14. They return short-handed and finish on May 26 instead of May 22. Four days late on framing is not a four-day project slip. It is a four-day push of every trade behind it, but the trades behind the framer were not committed to a window, they were committed to a date.
The builder now has three bad options. Push every downstream trade four days and accept that the build delivers a week late. Try to compress some downstream trade to absorb the slip, knowing that compression usually means quality risk. Or split the framer’s late finish work into a punch list and bring the electrician in on the original date for the rooms that are framed, with a return visit for the rooms that are not.
The third option is what experienced small builders default to, because it preserves the downstream commitments and the relationship with the electrician. It costs the electrician a return trip, which the builder absorbs in margin or negotiates as a small additional charge, but it keeps the build on its published delivery date.
Sequencing rules that do not bend
A builder running multiple projects develops a set of sequencing rules that function as hard constraints. Violating them creates rework, failed inspections, or quality problems that show up months later. The core residential rules apply on every project regardless of the schedule pressure.
| Predecessor | Successor | Why |
|---|---|---|
| Electrical rough | Insulation | Wires must be run before walls are filled |
| MEP rough inspection passed | Insulation | Inspector must see the rough before it is buried |
| Insulation | Drywall hang | Wall cavity must be sealed before being closed |
| Drywall finish | Paint | Mud must be sanded smooth before primer |
| Cabinet install | Countertop template | Boxes must be set before fabricator measures |
| Tile | Plumbing trim | Tile substrate must be set before fixtures attach |
These are not preferences. A builder who lets the insulator beat the electrician on site by even one day is paying for the insulation twice, once to install it and once to tear it back out so the electrician can finish their runs. Sequencing rules are the bedrock the rest of the schedule sits on.
What to do when a sub does not show
The no-show is the operational test. The plumber was on the schedule for Tuesday morning. Tuesday morning arrives, the plumber does not, and the phone is going to voicemail. The builder has three responses, in order.
First, call once and text once, then move on. A small builder cannot afford to burn a half day chasing a sub who is already unavailable. The follow-through matters but it does not happen in real time on Tuesday morning. Second, work the rest of the day around the gap. If the plumber was supposed to do the rough on the upstairs bath, push that to later in the week and use the superintendent’s presence for something else productive on site. Third, by Tuesday afternoon, the builder needs to know whether this is a one-day delay or a relationship problem. A plumber who responds at 4 p.m. with a legitimate reason gets rescheduled. A plumber who does not respond by end of day Tuesday is being replaced for this scope.
The bench depth matters here. A builder with one plumber for every project is exposed to that plumber’s schedule, health, and reliability. A builder with a primary plumber and a known backup who runs maybe one in eight projects has options when the no-show happens. The backup does not have to be cheaper or better. It has to exist and know the builder.
Communication cadence
The confirm cadence is what reduces no-shows in the first place. Each sub gets three touchpoints before the day they are due on site. Seven days out, a confirmation that the date still holds, with any changes to scope or access. Forty-eight hours out, a reminder with the address, the gate code, and the contact for the day. Day-of, a short text by 7 a.m. confirming the sub is on the way.
The seven-day touchpoint matters most because it is when a sub will tell the builder if a problem is brewing. The plumber is double-booked, the framer is running over on another job, the HVAC crew is one person down. None of these problems get resolved at the forty-eight hour mark when the alternatives are already booked. They get resolved seven days out when there is room to shuffle. Builders who skip the seven-day check find out about the conflict on the morning the work was supposed to start.
Penalty clauses that work and ones that do not
Penalty clauses for sub no-shows or late finishes are easy to write and hard to enforce. A clause that withholds $500 per day of unjustified delay reads well in the contract and almost never gets collected, because invoking it ends the relationship and the builder still has a half-finished job that needs the sub back.
The clauses that actually shape behavior are smaller and more immediate. A scheduling deposit, refunded when the sub completes the work on schedule, is more effective than a delay penalty. A back-charge for the cost of returning a downstream trade because of an upstream slip is enforceable because it is documented at the time the back-charge happens. A reduction in retainage release timing tied to schedule performance is enforceable because the funds are already held.
The clauses that fail are the ones that require the builder to invoice the sub for damages the sub disputes. By the time that argument lands in small claims court, the builder has already absorbed the cost. The remedies that work are the ones the builder applies unilaterally from funds the builder already controls.
The 926 Stratford schedule, in practice
On the 926 Stratford build (1,784 SF, $430,250 contract), the rolling four-week look-ahead at the start of MEP rough looks like this. Week one is committed: HVAC rough Monday and Tuesday, electrical rough Wednesday through Friday, plumbing rough running parallel with electrical. Week two is firm: MEP rough inspection scheduled Tuesday morning, with the inspector confirmed seven days prior. Week three is planned: insulation crew arrives Wednesday assuming the rough inspection clears, with Thursday and Friday as buffer. Week four is provisional: drywall hang starts Monday, with the order of rooms depending on how the insulation week ran.
The builder running this schedule has confirmed the electrician seven days prior, the HVAC sub seven days prior, and the inspector seven days prior. The forty-eight hour confirmations go out Sunday afternoon. The day-of texts go out at 7 a.m. on each work day. Three hours of phone work spread across the week prevents the half-day fire drills that consume builders who run reactive.
How BuilderGrid handles subcontractor scheduling
BuilderGrid runs the rolling four-week look-ahead as a live document per project, with sequencing rules enforced as hard constraints so that downstream trades cannot be scheduled before their predecessors clear. Confirm cadences fire automatically at seven days, forty-eight hours, and day-of, with the responses recorded against the sub’s reliability score over time. When a slip occurs, the cascade engine recalculates the downstream impact and flags the trades that need to be re-confirmed against new dates. The builder running five concurrent projects sees one consolidated calendar across all five rather than juggling five separate schedules.