Most scheduling tools are built for general contractors. They’re Gantt charts: task A before task B, milestone by date, critical path highlighted in red. The PM moves the bars, the schedule updates, the crew follows.
That’s not how specialty sub scheduling works.
A specialty sub running three concurrent commercial jobs doesn’t have a sequencing problem. He has a labor allocation problem. His five crews are finite. The hospital job needs more electricians because the GC pushed the rough-in window two weeks earlier. The school renovation needs his best foreman because the inspector is coming Thursday. The grocery store is behind on trim-out and the GC is starting to call. All three jobs are running simultaneously. He can’t stop one to fix another. He can only decide which crew goes where, how many people each job gets, and when to rotate.
No Gantt chart solves that. The PM who figures it out is doing it on a whiteboard, in his head, and on phone calls with his foremen.
Here’s what that decision-making actually looks like, and what the PM needs to see to make it.
The Three Decisions in Specialty Sub Scheduling
GC scheduling is primarily a sequencing problem — what happens before what. Specialty sub scheduling is primarily a resource allocation problem — who goes where with how many people.
There are three recurring decisions:
1. Staffing level: How many bodies does each job need right now?
Every job has a phase, and every phase has a productivity rate. Electrical rough-in on a multi-floor commercial building moves at a predictable rate per crew of four — a certain number of circuits per day, a certain number of floors per week. If the job is behind, you can usually accelerate by adding crew. If it’s ahead, you can thin crew and redeploy.
The PM’s job is to know, at any given moment, which jobs are running at full production and which are either overstaffed (burning hours without accelerating completion) or understaffed (falling behind the GC’s window). That’s not a scheduling tool problem. It’s a visibility problem.
2. Crew composition: Which crew and which foreman go to which job?
Not all crews are the same. The foreman who runs the hospital job efficiently may be a nightmare on a remodel with tight quarters and an owner walking the site daily. The four-man crew that handles open-floor commercial rough-in doesn’t have the finesse for a high-end tenant improvement. The concrete sub who’s fast on elevated deck pours runs slow on flatwork.
Crew composition decisions are judgment calls. But they’re informed by performance data — which foreman closes out phases on time, which crew runs consistently under budget, which workers can be paired productively. Tracking time and task completions by crew and job gives the PM the history to make these calls from data, not instinct.
3. Rotation timing: When does crew move from one job to another?
The hardest decision. Moving crew too early leaves a job understaffed at a critical phase. Moving too late means the next job sits waiting for people who aren’t there yet.
Rotation timing is driven by phase completion, not by the calendar. The electrician crew doesn’t leave the school job when Friday comes — they leave when Floor 3 East rough-in is complete and Floor 3 West is started, the inspection gate is passed, and the trim-out crew is ready to take over. The right rotation signal is a task completion state, not a date.
Pull planning at the task level gives the foreman the tool to produce that signal — “Phase complete, crew can move” — at the right moment instead of the scheduled one.
How GC Schedule Changes Break Specialty Sub Scheduling
The biggest variable in specialty sub scheduling isn’t internal — it’s external. The GC’s schedule changes constantly. Deliveries push. Inspections fail. The structural crew runs two weeks behind on a floor and the electrical rough-in window closes before it was supposed to open.
When the GC changes the schedule, the specialty sub doesn’t just adjust one job. He adjusts the allocation across all his jobs simultaneously, because his labor pool is fixed.
Here’s what that looks like in practice. A three-job electrical sub is running:
- Hospital: Floors 4–6 rough-in, crew of six, on schedule
- School: Trim-out, crew of four, one week behind
- Grocery store: Rough-in complete, two workers on punch list
The GC on the hospital job calls Thursday afternoon: the concrete schedule slipped, Floors 4–5 aren’t ready for rough-in. The electrical window on those floors moves two weeks. The crew of six has nothing productive to do starting Monday.
The PM now has six people who are about to be idle on one job while the school job is behind. The right move is to pull four of the six to the school job to accelerate trim-out, keep two at the hospital on punch list prep, and re-sequence the rotation so the school finishes closer to when the hospital floor opens back up.
That reallocation happens in a phone call, a whiteboard update, and a conversation with the foremen. But the PM can only make that call quickly if he knows — immediately, not after two calls and a check of last week’s timesheet — how many hours the school trim-out has burned vs. budgeted, what’s left in the scope, and what the foreman needs to finish.
What the PM Needs to See to Make Staffing Decisions
Specialty sub scheduling runs on four pieces of information that the PM needs in near-real-time:
Hours by job, this week. Not last week’s payroll summary — this week’s hours by job as they clock in. If the hospital crew is logging hours on a floor that isn’t open for rough-in yet, something is wrong and the PM needs to know before it becomes a week of wasted labor.
Task completion state by zone. Which zones are done, which are in progress, which haven’t started. This tells the PM whether the foreman’s “we’re making good progress” translates to actual phase completion or just activity.
What’s coming up in the next two weeks. Phase changes, inspection gates, GC milestones that drive crew demand. The PM can’t allocate a crew to a new job if he doesn’t know when they’ll be needed back at the current one.
Foreman feedback — early, not after the fact. The foreman knows by Wednesday if the crew is short or the scope is going to slip. The PM finds out Friday when the timesheet comes in and it’s too late to make a staffing change for the current week. The communication loop between the foreman and the PM is what converts field reality into a PM decision fast enough to matter.
The Foreman’s Role in the Scheduling Equation
The PM makes the staffing allocation. The foreman executes it — and provides the feedback that makes the next allocation better.
The foreman’s scheduling input is the demand signal: “I need two more electricians on Floor 3 by Thursday or we miss the inspection window.” That signal has to reach the PM early enough to act on it, which means the foreman has to surface it before Thursday morning.
On commercial electrical rough-in, the foreman knows the zone completion rate by mid-week — he can see whether the crew is going to close out the floor in the timeframe the PM assumed. If he’s running short, the right time to say so is Tuesday, not Friday.
The foreman isn’t making the staffing decision — that’s the PM’s job. But he’s producing the information the PM needs to make it correctly. The scheduling system that works is one where the foreman’s task completions and hours are visible to the PM in real time, not summarized on a timesheet three days later. For how that plays out at the foreman level — daily task assignment, handling no-shows, sequencing within a zone — see construction crew management for specialty subcontractors.
What a Scheduling Tool Actually Needs to Do
Most scheduling tools are built around the Gantt chart. That’s the wrong tool for a specialty sub with multiple concurrent jobs.
What a specialty sub PM actually needs from a scheduling tool:
Headcount by job, today. Which jobs have crew on site and how many people. If a job shows zero hours on a day when crew should be there, the PM needs to know before noon.
Hours burned vs. estimated by phase. Not just total hours — hours by phase. If the hospital rough-in is 30% over budget on Floor 4, the PM needs to know whether to investigate or accept it before committing the same crew to Floor 5 at the same rate.
Task completion against the foreman’s pull plan. The foreman’s pull plan is the ground-level schedule. When task completions are logged in real time, the PM can see whether the crew is ahead or behind the pull plan without a phone call.
A simple way to see all jobs at once. Not one Gantt chart per project — a view across all active jobs that shows hours, completion state, and upcoming phase changes simultaneously. A specialty sub PM with five active jobs doesn’t open five separate project files. He needs a single view.
Running a Crew That’s Always Where It’s Supposed to Be
Specialty sub scheduling isn’t a software problem. It’s a visibility and communication problem. The PM who knows — in real time — which jobs are behind, which are ahead, which have crew sitting idle, and which are about to hit a phase change can make the staffing calls that keep his crews moving productively.
The PM who finds out on Friday, from a timesheet, is always a week late.
See how LogLoon handles scheduling and crew visibility for specialty contractors, or check the pricing — it’s on the website.