Most specialty subs operate on two schedules at the same time — and neither one tells the foreman what to do today.
The first schedule is the master schedule. The GC owns it, updates it in Procore or P6, and sends a two-week lookahead every Friday. It tells you when your trade is supposed to start, when it’s supposed to finish, and when the next milestone is. It does not tell your crew what to do on Tuesday.
The second schedule is the foreman’s schedule. It lives in his head or on a sticky note. He knows what still needs to happen before the rough-in inspection. He’s mentally sequencing the work based on where the crew left off yesterday and what sections of the building are ready to go. It works until it doesn’t — until someone is out sick, until a section isn’t ready, until the PM asks where they stand on Thursday’s inspection and the foreman has to stop and reconstruct the answer from memory.
Pull planning is the layer between these two. It’s not a replacement for the master schedule, and it’s not a replacement for the foreman’s expertise. It’s a structured way to take the GC’s milestone, work backwards to what the crew needs to complete each week and each day, and give the foreman a task list that comes from that logic — not from improvisation.
What Pull Planning Actually Is
Pull planning comes out of lean construction. The core principle is simple: instead of pushing work forward from where you are, you start from a fixed end point — an inspection gate, a milestone, a handoff to the next trade — and work backwards to figure out what has to be done by when.
The “pull” in pull planning is the end date pulling the work schedule toward it. The inspection gate on Thursday isn’t just a deadline. It’s the anchor that tells you exactly what has to be done by Wednesday, what has to be done by Tuesday, and what the crew needs to finish today.
For a specialty subcontractor, the logic runs like this:
The anchor: The rough-in inspection is scheduled for Thursday at 2 PM. The inspector needs to see complete rough-in in all areas of Floor 3 before he’ll sign off.
Working backwards: Complete rough-in means conduit run, wire pulled, boxes set, cover plates off. That’s three days of work if the crew is fully on it. Which means the floor-level work has to be done before end of day Wednesday.
What that means today: If it’s Monday morning and the crew is starting Floor 3 east wing, the foreman doesn’t just need to “work on Floor 3.” He needs to finish east wing today, west wing tomorrow, and the stairwell and mechanical room Wednesday. If east wing goes long, Thursday’s inspection is at risk — and that needs to surface Monday afternoon, not Thursday morning when the inspector is on the way.
That task-level translation from milestone to daily work — that’s pull planning.
The Three Layers Every Sub Needs
Specialty subcontractors need three layers of scheduling that connect to each other. Most have the first. Some have the second. Very few have the third.
Layer 1: The master schedule. The GC’s schedule, the two-week lookahead, the critical path. Your trade has a start date and an end date. You know roughly when each phase needs to be done. This is the input, not the plan.
Layer 2: The crew schedule. Who is on which job, on which day. If you’re running three jobs simultaneously, the crew schedule tells you which four guys are at the commercial job on Tuesday versus the school on Wednesday. This is workforce allocation. It doesn’t tell you what they’re doing when they get there.
Layer 3: The task schedule. What the crew is doing today, by area and activity, to hit the next inspection gate. This is the layer that actually drives daily production. It’s also the layer that most specialty subs don’t have — which is why the foreman is running it from memory.
Pull planning lives at Layer 3. The task schedule is the output. The inspection gate is the input. Working backwards from the gate to daily tasks is the process.
Building a Pull Plan for Your Next Phase
Here’s how to build a pull plan for a phase — using electrical rough-in as the example, because the inspection gate structure for electrical rough-in is typical of how specialty trade phases work.
Step 1: Identify the anchor
The anchor is the next gate — the point where your work has to be complete before something else can happen. For electrical rough-in, it’s the rough-in inspection. For plumbing, it’s the underground inspection or the rough-in inspection. For drywall, it’s the MEP inspection clearance that lets the hanging crew close the wall.
The anchor date comes from the GC’s schedule. It’s fixed. Your task plan flows back from it.
Step 2: Define what “complete” means at the anchor
This is the step most verbal schedule conversations skip. “Rough-in complete” means something specific: all conduit run, all wire pulled, all boxes set, all stub-outs labeled, all cover plates removed. If it means something different to the inspector than it does to the foreman, the inspection fails.
Write it down before you build the task plan. It becomes the definition of done for every area.
Step 3: Break the scope into areas
Floor, zone, wing, room — whatever the natural divisions are for your trade. The goal is to create tracking units that are small enough to measure daily progress against.
On a four-floor building with rough-in happening floor by floor, the areas might be: Floor 1 East, Floor 1 West, Floor 2 East, Floor 2 West. Each area has its own completion target before the inspection.
Step 4: Work backwards from the anchor
Starting from the inspection date, count back the number of days you need per area. If each floor takes two crew-days to rough-in and you have four floor areas, that’s eight crew-days of work. If you have four crew members, that’s two calendar days if everyone is on it — or four days if the crew splits.
Map the area completion targets to calendar dates. Floor 4 done by Tuesday. Floor 3 done by Monday. Floors 1 and 2 already done. That gives you the schedule.
Step 5: Give the foreman a daily task list
This is where the pull plan becomes operational. The foreman doesn’t need to see the full backwards calculation — he needs to know what his crew is completing today and in which area. A task list by area, with a clear completion definition for each, is the daily plan.
A task list the foreman can check off from his phone — and that you can see in real time — closes the loop between the pull plan and actual progress. When Floor 3 East is marked complete at 3 PM on Monday, you know the crew is on pace. When it’s not marked complete at end of day, you know before Tuesday morning that the inspection timeline has a problem.
What Changes When You Actually Do This
The most common objection to pull planning from specialty sub PMs is: “My foreman already knows what to do. I don’t need to tell him.” That’s usually true. Experienced foremen have the job in their head.
The problem isn’t what the foreman knows. It’s what the PM doesn’t know.
When the task plan lives in the foreman’s memory, the PM’s only visibility is the Friday call and the Wednesday “where are we?” text. If the crew got behind on Floor 3 East on Monday, that information travels to the PM on Wednesday — two days after there was still time to do something about it.
Progress tracked by area — marking tasks complete as they’re done, area by area — means the PM has visibility Monday at 3 PM, not Wednesday at noon. The foreman isn’t being second-guessed. He’s doing what he was going to do anyway. The PM is just no longer flying blind between Friday calls.
The other change is in conversations with the GC. When the super asks where you are relative to Thursday’s inspection, the answer is no longer “we’re making good progress” reconstructed from a phone call with the foreman. It’s Floor 4 complete, Floor 3 two-thirds done, on track for Thursday. That answer — specific, immediate, not assembled from memory — is what distinguishes a sub who has their operations under control from one who’s managing by feel.
The Scheduling Tool Problem
Most scheduling tools are built for the master schedule layer. Gantt charts, two-week lookaheads, milestone tracking — all Layer 1. Some crew scheduling tools handle Layer 2: who’s on which job on which day. Very few give specialty subs a practical Layer 3 tool: a task list by area that connects to the milestone and lets the foreman check things off in the field.
A scheduling and task management system built for specialty subs has to connect all three layers: the milestone from the GC’s schedule, the crew assignment for the day, and the task list the foreman is working off. Without that connection, you have a Gantt chart and a crew roster — and the foreman is still running the actual schedule from memory.
How specialty subs use scheduling tools in practice starts with understanding that the tool is only useful if the foreman uses it. A pull plan that lives in a spreadsheet on the PM’s laptop isn’t a pull plan. It’s a document. The task list has to be on the foreman’s phone, updated in real time, visible to the PM without a phone call.
Running a Job Where the Foreman’s Memory Isn’t the Schedule
Pull planning doesn’t replace the experienced foreman. It takes what’s in his head and makes it visible to everyone else.
The anchor is the inspection gate. The task list works back from it. The foreman marks progress in the field. The PM sees it in real time. When something is behind, it surfaces the same day — not two days later when the options are limited.
That’s the job that runs tight without constant status calls: foreman focused on the work, PM focused on the next gate, crew schedule and task list connected instead of disconnected.
See how LogLoon’s task management works for specialty sub scheduling, or check the pricing — it’s on the website.