Review the delivery interfaces
Before the work
Are access, work boundaries and prerequisite approvals reflected in the submitted plan?
Keep in the review: Baseline, phasing narrative, agreed calendars and a record of assumptions needing confirmation.
At the handoff
Has a change in one package moved a dependency or affected the next planned work window?
Keep in the review: Prior and current updates, the changed logic, supporting correspondence and a reviewer disposition.
Into service
Which testing, documentation or acceptance activities remain in the path to the intended milestone?
Keep in the review: Milestone logic, outstanding submissions and the named parties responsible for closing each item.
Experience behind the practice
LaGuardia fuel transmission
CPM scheduling, baseline review, monthly updates, change-order evaluation, and time-impact analysis for the fuel transmission project.
- Developed and maintained CPM schedules
- Reviewed baseline and monthly updates
- Evaluated change orders and time impacts
Prior advisory work; not a Kairos software deployment or customer endorsement.
A useful next read
Time-impact analysis — Frame the event, schedule context and assumptions.
Monthly update review — Separate reported movement from its explanation.
Review memorandum example — Follow a fictional finding through to a clear request.
Make the first review count
Choose one phase or interface and bring two schedule versions with their narratives. Use demonstration data first, then agree any permitted project information and review boundaries.