Rung 2. On that same job.

Several teams, one plan.

We join up the planning they already do.

One plan they all update, and one progress story. We will name which file is master and what each party must supply.

How the job runs

A short fact-find: who plans, in which file, on what cycle, and where the dates already disagree. Then we build or rationalise the master schedule and the rules. Then we sit in the update cycle for an agreed number of periods. Then we leave the procedure, and a person on your side who has been coached on it.

Workshops are part of the job. A single .xer emailed over the fence is not this product.

When it is the right rung

When the pain is people and interfaces. Owner and contractor, or engineering, procurement, construction, and commissioning, each with a program. It is not a fancier version of a project schedule. We do not propose it in a first meeting by default. It follows a health check or a monthly cycle that has shown the other plans do not match.

Not in this offer

• A model that tries to hold scope, cost, risk, contracts, and earned value for its own sake.
• A promise that every contract updates in one click, or that a scenario appears in under an hour.