Most subcontractor chasing is not a discipline problem. It is a scheduling problem that shows up as a phone problem. Subs no-show, run late or go quiet when they do not know what is expected of them and when. That information has to be in writing and far enough ahead to plan against. A rolling three-week lookahead fixes most of it. It goes out on the same day every week, and every line carries a named sub, a start date and a definition of “ready.” The chasing that remains is about insurance certificates, lien waivers and invoices. That needs its own calendar, not more calls.
Most advice filed under subcontractor management construction starts at the wrong end: scorecards, penalty clauses, approved-vendor lists. Those have their place. But they are tools for after a sub has already failed. The cheaper fix is upstream, in the document that tells subs when to show up.
Chasing is what happens when the date lives in someone's head
The superintendent knows framing finishes around the 14th, so drywall can start the 17th. The drywall sub heard “middle of the month” on a site walk three weeks ago. Nobody wrote it down. On the 15th the super calls to ask where they are. The sub has already committed that crew to another builder, who gave a firm date two weeks ago. From the builder's side, that is a sub who does not show up. From the sub's side, it is a builder who never gave a date.
A sub running crews for several general contractors allocates labor a week or two out, usually at the end of the week. Crews go to the builders whose dates arrive before that allocation happens and do not move without notice. Everyone else gets whoever is left, or a promise of “early next week.”
Look at what the chasing actually consists of. Calls asking whether the sub is coming. Calls asking whether they got the message. Calls asking when they will be done. Each one is a request for information that should already have been on paper.
What a lookahead has to say for a sub to plan against it
A lookahead is not the master schedule pasted into an email. A sub does not need 140 lines of Gantt bars. They need their own lines, the lines just before theirs and enough detail to commit a crew. Each line should carry:
- Activity and location — “Hang and tape, units 4–6, second floor,” not “drywall.”
- Sub and contact — one named company, and one named person who confirms.
- Start date and duration — a date, not “week of.” Duration in working days.
- Predecessor — the activity that must be finished first, and who owns it.
- Ready condition — what “ready” means on site: inspection passed, area swept, materials delivered and staged, temporary power on.
- Lead-time flags — anything the sub must order before the start date, with an order-by date.
- Status — confirmed, tentative or not yet sent.
Most lookaheads leave out the ready condition, and its absence causes the most wasted trips. A sub who arrives to find the insulation inspection has not happened loses a day of a crew. The next time that builder sends a date, the sub discounts it. Write down what must be true before they mobilize, and who is responsible for making it true.
Three weeks is the right window for most residential and light commercial work. Week one should be firm. Week two should be firm unless something upstream slips. Week three is a heads-up that lets subs order material and pencil in crews. Windows past four weeks tend to be fiction. Shorter ones arrive after the sub has already allocated labor.
Same day, every week, with a confirmation back
The rhythm matters more than the document. A lookahead that goes out on Tuesday some weeks and not at all in others trains subs to ignore it. One that goes out every Thursday by noon becomes the thing they plan against.
- Monday to Wednesday: the super records actual progress against the schedule — what finished, what slipped and why. Daily logs are the source, not memory.
- Wednesday: the schedule is updated from that progress, and downstream dates move. Any sub whose date moved inside week one gets a phone call that day, before the document goes out.
- Thursday morning: the lookahead goes to every sub with a line in the next three weeks. Each sub sees their own lines and the predecessor lines.
- Thursday to Friday: each sub confirms their week-one and week-two lines in writing. A reply email is enough. “Confirmed, crew of four, Tuesday” is enough.
- Friday afternoon: anyone who has not confirmed gets one call. This is the only chasing call of the week, and it is about a specific line and date.
Step four turns a broadcast into an agreement. Without it, the lookahead is just another message the sub may or may not have read. With it, the builder knows by Friday which lines are at risk for next week. Otherwise the first sign is an empty site at 7:30 on Monday.
Step two comes with a rule: a date change inside the firm window never arrives by document alone. Say framing slips three days and the drywall start moves. The drywall sub hears it by phone first, then sees it confirmed in Thursday's issue. Subs forgive slips. They do not forgive finding out from a spreadsheet.
When a date moves by phone and nobody writes it down, there is no record of who knew what and when. That matters the day a sub back-charges for a remobilization. It also matters the day the builder wants to back-charge a sub for holding up three trades. Disputes like these turn on contemporaneous records. A dated lookahead and a written confirmation are that record. A call log is not.
What a lookahead does not fix
A good lookahead stops the chasing about dates. It does not stop all of it, and pretending otherwise just moves the problem somewhere less visible.
- Paperwork — certificates of insurance expire, and lien waivers have to be collected with every payment. Whether a waiver is conditional or unconditional decides whether the builder is actually protected; see how construction lien waivers work. Track these on a separate list with expiry and due dates, reviewed weekly, not tied to the schedule.
- Scope disputes — the subcontract or scope letter may be vague about who does blocking, who hauls debris or who patches after the electrician. If so, a clear date just means the argument happens on time. Fix the scope document at award.
- Drawings — subs working from an old revision show up on time and build the wrong thing. That is a document control problem, and the fix is a naming rule, enforced.
- An overextended sub — some subs confirm everything and show up for half of it. Two missed confirmed dates is information. A lookahead makes the pattern visible; it does not change the sub.
That last one is the honest limit. A lookahead removes the excuse of not knowing. What is left after that is a performance conversation. It is a much shorter conversation when there is a dated, confirmed line to point at.
Where BuilderSolve fits, and where it does not
This routine involves two kinds of work, and BuilderSolve offers both. The scheduling side is software. In the work planner, the schedule is built from the estimate, so each line already maps to a scope. It can be viewed as a Gantt chart, a calendar or a table. Daily logs feed actual progress into it. When something slips, the AI assistant drafts the schedule shift, and a person approves or rejects it before anything moves. Crew management shows who is booked where, so conflicts surface before Thursday's issue rather than on site on Monday.
The other side is labor. Every week, somebody has to update the schedule on Wednesday, issue the lookahead on Thursday and collect confirmations on Friday. On most small builders' jobs, that somebody is the super, at 9 p.m. Running lookaheads, RFIs and contracts is part of what the BuilderSolve operations and admin team does. It is priced against the coordinator role it replaces.
There are limits worth knowing. Purchase orders are in development and not shipped, so subcontract scopes and POs live outside the platform for now. The assistant does not send anything to a sub on its own — it drafts, and a person decides. QuickBooks stays the book of record for what subs are paid; the platform reads from it and does not write back.
What to do this week
Pick one active job — the one generating the most phone calls about subs — and run the routine on it alone.
- List every sub activity in the next three weeks with a start date, a duration and a ready condition. If a date cannot be written down, that is the first problem to solve.
- Send it on Thursday to every sub on the list, and ask each one to reply confirming their lines.
- On Friday afternoon, call only the subs who have not confirmed.
- Repeat on the same day next week, with changes marked.
After three or four weeks, the calls on that job will be about specific problems — a failed inspection, a late delivery — instead of whether anyone is coming. Then roll it out to the next job.
Common questions
what is a 3 week lookahead schedule in construction
A three-week lookahead is a rolling short-range schedule listing every activity starting in the next 21 days. It is updated and reissued weekly. Each line should name the sub, the start date, the duration, the predecessor and what “ready” means on site. Week one is firm, week two is firm unless something slips and week three is a heads-up for ordering material and booking crews.
how to get subcontractors to show up on time
Give them a firm date in writing before they allocate crews, usually a week or two out. Issue a lookahead on the same day every week, and ask each sub to confirm their lines in writing. Tell them about any date change by phone first. Most no-shows trace back to a date that was spoken but never written, or that moved without notice.
how often should you send a lookahead to subcontractors
Weekly, on the same day, every week. Thursday works well because it lands before most subs allocate crews for the following week. Consistency matters more than the format. A lookahead that arrives on different days, or skips weeks, teaches subs to ignore it, and the phone calls come back.
should subcontractors confirm the schedule in writing
Yes. A written confirmation of week-one and week-two dates turns a sent schedule into an agreement. A one-line reply email is enough. It tells the builder by Friday which lines are at risk. It also creates a dated record if a back-charge or delay dispute comes up later. A phone call alone leaves no record of what was agreed.
does BuilderSolve track subcontractor purchase orders
Not yet. Purchase orders are in development and not shipped, so subcontract scopes and POs live outside the platform for now. BuilderSolve does handle scheduling built from the estimate, daily logs, change orders with an audit trail and budget vs. actual. QuickBooks stays the book of record for sub payments, and the platform reads from it one way.