How to manage several subcontractor project schedules at once

Start with one dependable view

A subcontractor can have ten active jobs and ten apparently healthy schedules while the same detailer, shop bay, or field crew is promised to several of them. The first step is to list each job's next external commitment alongside the internal handoff that makes it possible. Keep the list short enough to review every week.

For each project, capture the required site date, the next approval or release, the status of long-lead materials, the production window, the planned delivery, and the person responsible for the next action. Mark dates as confirmed or provisional. A date copied from an old email should not look as reliable as a written commitment.

• Show the next milestone and its predecessor together.
• Record the owner of the next decision, not just the task owner.
• Separate confirmed dates from assumptions.

Compare capacity before accepting another date

Look across jobs for shared people and equipment. A shop crew can perform one sequence at a time even if individual project plans each appear possible. Rough capacity bands are enough to reveal a collision: committed, tentatively reserved, or available. Refine only the weeks where demand exceeds capacity.

When two jobs compete, do not silently slide one schedule. Identify which commitment has less flexibility, whether work can be resequenced, and who can authorize the trade-off. The portfolio view should make that decision visible to the PMs who own both jobs.

• Flag weeks with overlapping fabrication or installation peaks.
• Keep a separate list of unapproved assumptions.
• Name the decision-maker for any capacity conflict.

Run a short weekly review

Review the next four to six weeks, then look farther out for procurement and drawing approvals. Ask what changed since the last review, what is due before the next review, and which milestone is now unsupported. Update the underlying project plan after the meeting so the portfolio summary and detailed schedules agree.

A useful meeting produces decisions: request an approval, release a purchase order, reserve a crew, or notify the GC of a conflict. If the discussion only reports percentages complete, the schedule is not yet helping the team plan.

• Sort by the next action date, not project name.
• Escalate a late predecessor before its successor slips.
• Record a new date and owner when a commitment changes.

Worked example

Three jobs need the same installation crew in the second week of May. Job A has a confirmed access date, Job B has a tentative GC look-ahead, and Job C has approved drawings but materials are not due until midweek. The apparent three-way clash is not three equal commitments. Confirm B's access, check C's delivery, then reserve the crew against the dates that can actually be met.

If the crew cannot cover the resulting overlap, discuss a split sequence, an additional crew, or a revised start date while there is still time to act. The decision and its effect belong in each job's schedule.

• Do not treat a tentative look-ahead as a firm booking.
• Use material readiness to test the feasibility of a crew reservation.

Decide what belongs in the portfolio view

The cross-project view is a coordination layer, not a substitute for every job's detailed plan. It should carry dates that change decisions: the next external commitment, the latest approval or purchase release, a capacity reservation, and a blocker. Keep quantities, drawing revisions, and detailed installation tasks in the job schedule unless they affect another project.

Choose a consistent unit for shared capacity. A crew-week or shop-bay-week may be sufficient for early planning; hours by individual may be necessary only at the next-two-week level. Avoid false precision. A rough, honest capacity forecast is more useful than a detailed grid built on unconfirmed site dates.

When a new job arrives, place its proposed shop and field windows beside committed work before accepting a target. If the overlap is unavoidable, price and approve the additional capacity or negotiate sequence before it becomes an invisible burden on the team.

Common traps and a final check

A portfolio dashboard can become a reporting exercise if it duplicates detailed schedules without exposing risk. Keep it tied to real handoffs. Before sharing, check whether someone could tell which commitment is threatened, why, and what decision is needed. If not, simplify the view or add the missing dependency.

• Is the next external milestone current?
• Is its critical predecessor visible?
• Is the date confirmed or assumed?
• Who owns the next decision?

Common questions