An EPC schedule is a negotiating document before it is a management tool. Reading it as an owner means testing what it hides, not admiring what it shows.
Test the logic, not the dates
Dates are outputs. The questions that matter live in the network: are engineering deliverables actually linked to the procurement packages they enable? Does construction logic respect crew and workface constraints, or is it a bar chart wearing a schedule’s clothes? A programme with soft logic can absorb months of slippage before anything turns red.
Ask who owns the float
Total float belongs to the project — but contract language often lets the contractor consume it first. Before accepting a baseline, an owner should know exactly how much float sits on each critical and near-critical path, and what the contract says about who may use it.
Distrust early engineering progress
Engineering percent-complete is the easiest number on the project to inflate. Insist on deliverable-based measurement — documents issued at defined maturity, counted against a fixed register — and reconcile it monthly against procurement’s need dates.
Watch the resource histogram
If the schedule requires a peak workforce the site cannot house, or a design office to triple in a quarter, the dates are fiction regardless of the logic. The histogram is where optimism goes to hide.
An owner who applies these four tests at baseline — and re-applies them at every update — turns the schedule back into what it should be: an early-warning system.