If your project is going to slip, you should hear about it in week two, not month five. The schedule we give you is the schedule the site actually runs to. If site conditions change, so does the plan you are working from.

The point of a project schedule is not to hang a date on the wall. The point is to give you enough warning to take a recovery decision while you still have options. Push the milestone. Add crew. Change the sequence. Renegotiate a vendor slot. Every one of these levers stops working the moment the schedule stops reflecting what is actually happening on site.
Our job is to keep the schedule honest, and to make sure you hear about a slip in the same week the site does, not the same month the deadline passes.
Almost every delayed project we have been called in to recover tripped on one of these. By the time we arrive, the recovery options are already narrower and more expensive.
Built to look good for the board deck. No allowance for rework, weather or vendor slippage. Everyone celebrates the timeline in week one, and quietly stops referring to it by week six.
A schedule exists, technically. Nobody updates it. By month three it bears no relationship to what is actually happening on site. Cost, procurement and staffing calls are then being made without a real baseline.
The tools (Master Programme, WBS, weekly reporting) are standard. Every serious PMC uses them. What actually changes the outcome for you is how often we walk the site, how honestly we report variance, and how quickly we bring recovery options when a milestone is at risk. We do not bury bad news, because burying it only makes it your problem later.
Each of these runs continuously through the project. Not a one-time exercise at kickoff, not a status slide once a quarter.
Not a status update once a month. A regular rhythm of documents that let you take time and cost decisions with real numbers.
Revised as conditions change on site, not a static document that gets outdated by week six.
Variance against baseline every week or fortnight, in real numbers. If a slip is coming, you see it early enough to act on it.
When a milestone is at risk, you get a clear set of options (push, resource up, resequence) with the cost and impact of each already worked out.
Cause and ownership documented for every slip. Useful when contract disputes come up, and useful when you plan the next project.
At project initiation, before you onboard the contractor.
The baseline schedule has to be in place to evaluate contractor bid programmes against it. Build the baseline first, evaluate bids second.