How to spot schedule risk before a milestone slips

Look beyond the finish date

A finish date alone says little about the health of a schedule. Check the path that supports it: approvals, purchasing, production, delivery, and access. The latest useful decision date for each predecessor is often a better early warning than the final installation date.

Float is the time an activity can slip without moving a linked milestone under the current assumptions. It is not a promise of free time. If durations, calendars, or constraints are wrong, the calculated float will be misleading.

• Track the next controlling decision.
• Review the assumptions behind available float.
• Separate committed milestones from internal targets.

Create practical risk signals

Choose a few signals the team can maintain: a predecessor past its decision date, a supplier date not acknowledged, an unconfirmed access window, or a crew conflict. Give each risk an owner, due date, and consequence. A color without an action is decoration.

A simple review can classify a milestone as supported, at risk, or blocked. Supported means its predecessors have credible dates. At risk means a decision or buffer is narrowing. Blocked means a required handoff has missed its useful date or cannot be confirmed.

• Define statuses in terms of evidence.
• Escalate by decision deadline, not only by severity.
• Check the same risk across all affected projects.

Keep a response path

For each at-risk item, identify an action that could change the outcome: obtain a release, confirm shipping, resequence an area, reserve capacity, or negotiate a date. Put that action in the schedule with an owner. If no action can recover the milestone, change the forecast and communicate it promptly.

Do not consume every buffer without discussion. A buffer may protect uncertainty elsewhere in the path, and an apparent recovery can create an impossible crew overlap.

• State what evidence would close the risk.
• Check the cost and capacity of an acceleration option.
• Update the forecast when recovery is no longer credible.

Worked example

A roofing package still shows a June installation start. Membrane delivery is forecast for the prior week, but the supplier has not acknowledged the purchase order. The installation date has not slipped yet, but the risk is real because the order confirmation deadline has passed.

The PM's next action is to obtain a committed ship date and test alternate sequencing or supply if needed. Waiting until the planned delivery day removes options.

• An unconfirmed supplier date is a risk, even before it is late.
• The useful escalation date comes before the site milestone.

Separate schedule risk from contractual responsibility

A risk flag says the planned path may fail; it does not determine who caused the condition or what relief a contract provides. Keep operational decisions and contract administration connected but distinct. The scheduler should identify the affected handoff and possible response while the responsible people handle notices and entitlement.

Float is sensitive to logic, calendars, and constraints. A task with ten days of apparent float may have no practical flexibility if the only crew slot is already reserved on another project. Conversely, a late non-controlling task may not move the final milestone. Use calculated float as a prompt to inspect the real work sequence.

A useful risk review focuses on dates where action can still change the outcome. Once the latest release date passes, the team should either accept a revised forecast or adopt a credible recovery path with resources and approvals.

Weekly risk check

Review the near-term path for each important milestone. A short list of actionable risks is better than a large register nobody updates.

• What must happen next?
• What is the latest useful decision date?
• Is the predecessor supported by evidence?
• What happens if it slips?
• Who acts now?

Common questions