Synthetic worked example
Illustrative case study: reviewing a late steel delivery
An illustrative review of a late steel delivery through dependent activities, float and milestones, separating schedule questions from contractual notice and entitlement.
ILLUSTRATIVE SCENARIO. All project records are invented. This is not an actual delay, service-executed analysis or extension-of-time entitlement. It is not contractual or legal advice.
The problem: a new delivery date does not quantify impact
Imagine a supplier reporting a late steel shipment. The project manager asks whether a concrete pour and the next contractual milestone will slip. Shipment delay cannot simply be equated with project delay: available stock, alternative work or other constraints may change the effect.
What records does the reviewer need?
The planner records the data date, accepted programme revision and actual progress update. The delivery event is linked to affected activities, followed by a review of logic, calendars, constraints and resources. Float cannot be inferred from an activity list without accepted logic.
- Procurement records, correspondence, required quantity and stock actually available.
- Programme revision, update date and actual progress of affected activities.
- Design approvals, inspection, labour, plant and independent work constraints.
- The contract and relevant correspondence if the question becomes contractual.
How does the team use the planning workflow?
The planning service overview helps organise inputs and programme-review questions. In this example, the planner traces activities from delivery to the relevant milestone, compares the need date with the delivery date, then reviews logic and float in the working programme.
Any generated suggestion requires a qualified planner to review the actual programme before adoption. This scenario does not claim that CAIS rescheduled a real project, established its critical path or automatically read a supplier system.
Compare mitigation options with their conditions
The team records each option, the evidence needed and the human decision before changing the plan.
| Option | Check first | Limit of the conclusion |
|---|---|---|
| Use available stock | Quantity, specification, location and approvals | Stock existence does not establish suitability |
| Resequence available work | Access, resources, logic and safety | A revised sequence needs a workable delivery plan |
| Investigate another supplier | Approval, lead time, cost and purchase conditions | An option is not a supply commitment or proven saving |
Separate time impact from responsibility and entitlement
A possible programme impact does not establish responsibility or automatically prove entitlement to extra time or money. A specialist reviews the actual contract, notice, correspondence, contemporary records and any concurrent delays under an appropriate method.
The educational output is a list of activities, evidence and options needing decisions, with contractual questions kept distinct. This example contains no calculated delay duration, mitigation percentage or established claim outcome. Real project documents and workflows remain authenticated.