How to turn GC milestones into your trade's working schedule

Clarify what the milestone actually means

A master schedule may say 'steel complete' or 'mechanical rough-in'. Ask what area, handoff, inspection, or access condition counts as complete. Confirm whether the date is contractual, a coordination target, or a tentative look-ahead. These distinctions affect how the trade plans and communicates risk.

Collect the latest drawings, scope boundaries, site sequence, and other trades' predecessors. A date without an agreed definition can appear achievable until the field team discovers it includes more work than assumed.

• Define the deliverable and area.
• Record the source and status of the date.
• Identify preceding and following trades.

Build the internal path backward

From the site milestone, trace installation, delivery, production, purchasing, and approvals. Use durations based on actual capacity and project-specific conditions. If the trade is field-only, replace shop steps with mobilization, layout, material staging, and inspection.

Separate work by area or release when it can happen independently. One building-wide bar hides the possibility that the first floor is ready while the roof is not. The internal plan can be more detailed than the GC's milestone without becoming a copy of the entire master schedule.

• Link each internal handoff to the external commitment.
• Split areas where readiness differs.
• Expose the decisions another party controls.

Reconcile and communicate

Compare the backward plan with today's status. If a required approval or purchase date has already passed, the milestone is unsupported. Raise the issue with a specific decision request and realistic options, such as phased release, resequencing, or a changed date.

Keep the GC-facing milestone and your current forecast aligned. Your internal schedule can carry more detail, but it should not quietly assume a different site start from the one being coordinated.

• Show the latest useful decision date.
• Explain the effect of an unresolved predecessor.
• Update both internal and shared dates after a decision.

Worked example

The GC requests curtain-wall installation on September 1. The glazing team needs field dimensions, approved shop drawings, fabrication, and delivery. Working backward reveals a July release date for fabrication. If field dimensions will not be available until August, the September milestone needs a different sequence or scope definition.

The trade might propose a phased measurement and release by elevation. That option must be checked against fabrication minimums and site access before being presented as a committed recovery.

• A master date can expose an impossible predecessor.
• Phasing is a decision with its own dependencies.

Use one agreed language for dates

Different teams may use 'start', 'ready', and 'complete' in different ways. Put the milestone definition in writing with area, quantity or scope, access condition, and acceptance point. If the GC schedule is revised, compare the new milestone to the prior commitment and confirm whether predecessors moved too.

A subcontractor's internal plan may have several dates behind one GC milestone. Share the few that require coordination: drawing release, material decision, area access, delivery, and installation. Do not overwhelm a coordination meeting with every shop activity, but do not conceal a critical handoff that another party controls.

When the internal path cannot support the GC date, bring options with assumptions. A phased sequence might protect the first area; acceleration might need paid overtime; a changed site date might be the honest answer. The schedule supports the decision but cannot approve it.

Before accepting the milestone

Confirm the path with the people responsible for drawings, materials, shop or field capacity, and site coordination. The aim is a defensible commitment, not a schedule that merely fits on paper.

• Is the completion definition clear?
• Are the required approvals and access dates plausible?
• Has shared capacity been checked?
• Does the team understand which assumptions remain open?

Common questions