Plan backward from the installation date.

Define the site milestone

Write down the installation date, area, scope, and meaning of “ready.” A date for crew mobilization differs from a date when installation must be complete. Confirm whether the GC's date is committed, a coordination target, or provisional. Identify the party who controls site access and the predecessor trade whose work must be finished.

Do not treat a master-schedule bar as proof that your area will be available. Ask what condition must be met before your team can begin: layout accepted, supporting steel complete, inspection passed, or another specific handoff. Record the answer as a dated assumption until it is confirmed.

• What exactly must be installed or ready by the milestone?
• Which area or release does it cover?
• Who confirms that access and preceding work are ready?

Map the handoffs backward

Start at installation and list the activity immediately before it. That may be delivery, receiving, staging, or an inspection. Continue through production, material availability, approved drawings, and the earliest design or purchasing decisions. Connect only true prerequisites. If a portion of the work can proceed independently, give it a separate release path.

Use observable outcomes for milestones: “shop drawings approved for Area A” is clearer than “drawings.” An external approval needs an owner and a response target. A supplier lead time needs a defined start trigger, such as an acknowledged order following approved submittals.

• Separate submission, review, revision, and release when each can affect the date.
• Show shipping and receiving when fabrication completion is not enough for site use.
• Split areas or packages that can be released independently.

Calculate with real working time

Estimate each duration using the working calendar, team capacity, known supplier commitments, review allowance, and site restrictions. A two-week activity on a five-day calendar does not mean fourteen working days. Holidays, plant shutdowns, access windows, and crew commitments on other jobs can all change the result.

Work from the required milestone toward today to find the latest practical dates for each predecessor. Compare those dates with actual status. If the latest submission date has already passed, the schedule has found a conflict; it has not created extra time. Keep uncertain durations visible and test a range where the lead time has not been confirmed.

• Use the actual start trigger for supplier lead times.
• Check shared shop and field capacity across projects.
• Do not hide an unconfirmed expedite inside an optimistic duration.

Worked example: a steel package

Suppose the GC requests installation on Monday, June 15. The following is an illustrative sequence, not a standard lead-time promise. The dates would need to be calculated on the project's working calendar and confirmed with the detailer, supplier, shop, carrier, and field team.

If the backward pass says approved drawings are needed in late April but the package has not yet been submitted in early May, the installation commitment is unsupported. The team can test phased approval, a different production sequence, added capacity, or a revised site date. Each option needs an owner, cost check, and acceptance before it becomes the forecast.

Review and update the plan

Once the dates are credible, share the key handoffs with the people doing the work. Ask the shop what can actually start before full approval; ask the field what must be on site for the first installation area. Their answers often reveal a missing predecessor or an overly broad package.

When a date moves, update the changed event first and trace its effect through linked work. A late approval may delay production; late site access may instead create a storage or crew conflict. Do not move every task by the same number of days without checking the logic. Keep the former baseline and the current forecast distinguishable.

• Is the required site date confirmed or provisional?
• Can each key handoff be traced to the milestone it supports?
• Which latest useful decision date is closest?
• Do other jobs need the same shop or field capacity?
• Who must decide if the current path no longer works?