When a vendor's timeline slips, you shouldn't be the last to know

A vendor commits to a factory acceptance test in week 38. Three weeks later, on a Tuesday, their project manager mentions in passing that long-lead parts are running late. The date has actually moved to week 42 — but nobody told the portfolio. You find out at the next steering meeting, when the validation window is already at risk.

The problem isn't the slip. Vendor dates move; that's normal. The problem is the latency between the slip happening and the portfolio seeing it — and the fact that a single date change quietly invalidates a chain of downstream commitments nobody re-checked.

How STRUCTURA handles it

In STRUCTURA, a project doesn't carry one timeline — it carries several. Your execution plan and each vendor's schedule live on the same canvas in the schedule workshop. When a coordinator moves the vendor's FAT, the change is local to that vendor's timeline — and a cascade preview immediately shows which downstream milestones it pushes, before anything is committed.

The moment that date lands, the knock-on doesn't stay buried in one Gantt. If it puts a milestone or a validation window at risk, it surfaces as an escalation — owned, timed, and visible across the whole portfolio, not just inside that one project's schedule.

And you don't have to go looking. Coach John reads the change against everything else moving that week and writes it into the role-targeted summary for the people it actually affects: “A vendor FAT slipped four weeks; the Q3 validation window is now at risk; here's the one decision to make this week.” New this cycle, flagged as new — not lost in a report.

What changes

The slip still happens. But the gap between “it happened” and “the portfolio knows, with the knock-on quantified and a decision queued” collapses from weeks to the same week. That is the whole job of the tactical layer.