The update should tell you something.
Monthly schedule updates that record what actually happened, show what it did to the finish date and say what to do about it. Same data date, same day, every month, in plain English.
How updates bury the slip.
Eighty percent for three months
Activities parked at 80 percent complete while the field falls behind. The finish date holds on paper and nowhere else.
Logic edited in the dark
A tie deleted here, a duration cut there. Each update looks fine alone, but the critical path is no longer the schedule you approved.
Float eaten quietly
Total float to the key milestone drops every month and nobody reports it. Then one late delivery turns a buffer into a delay.
How we update.
- 01
Status from the field
Actual starts, finishes and remaining durations are confirmed with superintendents and daily reports, never copied forward from last month.
- 02
Hold the data date
One cutoff, one data date, one submittal day. A steady rhythm is what makes month-to-month comparison mean anything.
- 03
Compare file to file
Every logic, duration, calendar and constraint change is checked against the prior XER and flagged if it moved the finish.
- 04
Explain the driving path
A short narrative on what drives completion now, how float moved and why. Written for an owner, not for another scheduler.
- 05
Hand the field a look-ahead
A two to three week look-ahead pulled from the updated schedule, so crews work to the same plan the owner is reading.
What you walk away with.
Scoped to your project. Native files and plain-English outputs that stay yours when we leave.
The statused P6 or Microsoft Project file, with actual dates and remaining durations confirmed against field records.
What moved, why it moved, what drives the finish and which decisions are needed from leadership this month.
Every logic, duration and constraint change from the previous update, listed and explained, ready for any later dispute.
Total float to each key milestone month over month, so erosion shows up long before a date is missed.
A short-interval plan for the field, drawn from the same updated schedule the owner receives.
Rebuilt by night, flying by morning.
An 11,000 foot runway rebuilt in night closures, delivered CM/GC over 30 months. Each update measured float to every reopening, so the airport committed closures to airlines on real dates. Every morning, the first flight left on time.
- $260M
- Capital value
- 11,000 ft
- Runway rebuilt
- 30
- Months, CM/GC
Straight answers to fair questions.
Can you review the contractor’s updates instead of doing them?
Yes. Many owners have us check each contractor submittal against the field, test the logic changes and write the owner’s narrative.
How quickly do we get the update?
We agree a fixed day each month, usually a few business days after the data date, and we hold to it.
What if our update shows we are already late?
Then you know now, not in six months. We show you what drives the slip and what it would take to win time back through Recovery Planning.
Send the schedule. See reality early.
Share the project, the latest schedule and the date you are protecting. A senior project controls lead replies within one business day.