Reading a tender: the clauses that shape execution

A tender document is usually read for scope and price first. For the team that will execute it, the more useful read is for the clauses that constrain method, because those decide the programme long before the bar chart is drawn.

Measurement and payment terms come first. Whether work is measured on completion, on milestones, or on a running-account basis changes cash flow, and cash flow changes how procurement and subcontracting are structured. The billing breakdown is effectively a work-breakdown structure imposed by the contract.

Time-related clauses come next: the completion period, any sectional completion or milestone dates, the extension-of-time mechanism, and the notice requirements attached to it. Sectional dates often matter more than the headline completion date because they fix the sequence.

Then the quality and testing regime — the specification, the referenced codes, the hold points that require the engineer's presence, and the consequences of a failed test. A specification that demands third-party testing or long cube-strength waits has a direct programme cost that has to be planned in.

Finally, site constraints written into the contract: working hours, traffic management obligations, environmental conditions, utility coordination, and access or possession limits. These are the clauses that most often turn a straightforward scope into a staged, method-driven one.

Reading in this order turns a tender from a document to be priced into a project to be planned. The estimate is better for it, and so is the first month on site.