An Australian organisation adopting NEC4 needs to consider how the contract will work with its own delivery arrangements. The NEC4 Engineering and Construction Contract (ECC) expects programmes to be kept current, early warnings given and the effects of change assessed as the project proceeds. Meeting those obligations depends on the quality of the project documents and the people making decisions.
In my experience, difficulties often arise when organisations adopt the contract but retain procedures and approval arrangements that prevent the team from using it properly. A submission can be technically ready for a decision while still waiting for an internal approval.
NEC4 procurement and main options
The contract form and main option should follow the procurement strategy, the information available at tender and the risks the parties can manage. Those choices also affect the work the Client and Contractor will need to do during delivery.
A priced contract does not resolve uncertainty in an incomplete design. If tenderers cannot establish the required work or its interfaces, they still have to decide what to allow in their prices and programmes. Describing the arrangement as lump sum does not settle the missing requirements.
A target contract needs a credible target and the resources to examine costs throughout the works. The fictional Ironbark Recycled Water Scheme in NEC4 Explained uses Option C. The team would therefore need to review cost records and forecasts while assessing changes to the target. Its Activity Schedule establishes the target; it is not the basis for periodic payment.
Design responsibilities need the same attention before tender. The ECC can accommodate Contractor design through the obligations stated in Scope, but the allocation must be clear before provisions on design liability are selected. The main and secondary options need to be read with the actual design requirements, rather than chosen independently of them.
Client preferences about liability or internal approvals should not be confused with changes required by Australian law. NEC4 does not have to be amended simply to make it work in Australia. Where a Client proposes an amendment, its commercial purpose and its effect on the contract’s management processes need to be understood.
Preparing NEC4 contract documents
The people pricing and planning the work should be able to establish what is required from the contract documents. If they need an explanation from someone who prepared the tender pack, that may indicate a requirement or interface that has not been recorded clearly enough.
Contract Data needs to be checked against the rest of the pack so that named roles, dates and response periods are consistent. Both parts must be completed, with accurate references to the documents and revisions that will form the contract. An otherwise clear specification can cause problems if the contract identifies a different version.
The operator, designers and construction team all have a contribution to make when preparing Scope. On Ironbark, the requirement to keep the treatment plant operating affects how the new works can be constructed and connected. Tenderers need usable information about access and operating constraints, while the operator needs to confirm that the proposed arrangements can be supported. The Scope also needs to identify design interfaces and the tests and records required to demonstrate Completion.
These operational requirements can usually be addressed in Scope without amending the conditions of contract. That does not make Scope an alternative place to change payment rights, liability or other contractual provisions.
Site Information needs a separate review. The team should establish what investigations have been undertaken and what information is being provided to tenderers, including its contractual status. Although that information matters when pricing and planning the work, a difference between it and the conditions encountered does not automatically establish entitlement. The relevant contractual tests still apply.
NEC4 amendments and Australian legislation
The contract needs to be reviewed against the legislation applicable to the project. NEC publishes Australian Y clauses addressing security of payment, but their suitability must be checked against the current law in the relevant jurisdiction and the contract being used.
Once the provisions are settled, the people administering the contract need the complete pack and a record of the amendments. Training on the standard form will not prepare them to apply a response period or assessment procedure that has been materially changed. The legal review and the implementation work therefore need to use the same contract.
Project Manager authority and approvals
The Project Manager needs sufficient time and support to carry out the role. That includes access to technical advice and commercial assessments, as well as a clear understanding of which decisions require the Client’s internal approval.
A design submission might need engineering input followed by a commercial decision. If the engineering review finishes promptly but the decision must wait for the next monthly committee meeting, the contractual response period may still be missed. The Client’s approval arrangements need to allow the Project Manager to respond in time, with an escalation route when a decision is delayed or the usual decision-maker is unavailable.
These arrangements should support the Project Manager’s contractual authority while preserving the Client’s necessary controls. Naming someone in Contract Data does not, by itself, establish how their decisions will be supported within the organisation.
The communication system needs to reflect those responsibilities. A document uploaded for discussion should not be mistaken for a contractual submission, and a notice should not sit in an inbox that nobody is monitoring. Before work starts, the team needs to know where communications are sent, who receives them and how responses are tracked.
Programme and commercial administration
Programme preparation and review need to be resourced as part of delivering the works. The planner requires input from the construction team, and the Project Manager needs access to the people who can assess the proposed sequence and interfaces. A programme submitted for acceptance should reflect the way the work is to be carried out.
On Ironbark, the operator’s contribution to planning the connections would need to be available while the programme is being prepared and reviewed. Leaving that discussion until the Contractor is ready to connect the new system could undermine a sequence that otherwise appears achievable. The programme review needs to test those dependencies while there is time to deal with them.
Early warning and project risk management should also fit together. The project needs arrangements for notifying matters, agreeing actions and following them through, without different teams maintaining competing records of the same issue. An early warning meeting should help people manage the problem, rather than add another reporting step before anyone can act.
Commercial records must support the selected option’s payment and cost assessments. Under C, D and E, the team needs to distinguish expenditure from Defined Cost and apply the Disallowed Cost provisions where relevant. Neither an overrun nor a cost query is, by itself, a contractual reason for disallowance.
Compensation event assessments require planning input as well as cost information. The people preparing and reviewing quotations need time to examine the effect on the works, including the appropriate use of forecast and actual cost. That work needs to take place as the project proceeds, with access to the records and people needed to complete it.
Contract administration and reporting
The reporting requirements in Scope create work for both the people preparing the information and those reviewing it. Before requiring another report, the Client should establish who will use it and what decision it supports. Information already available in a programme update or commercial forecast should not have to be recreated solely to fit a separate internal template.
The people and systems needed to meet the specified requirements also need to be included in the project budget. Where administration appears excessive, the first review should include the Scope and internal approval arrangements. Removing duplicated reporting may reduce the work involved, but the remaining arrangements must still meet the contract’s requirements.
NEC4 training and early project workshops
Initial training is the first step in preparing the team to administer NEC4. It should give them a working understanding of the selected contract and how its procedures affect their roles. Using the project’s own documents makes that training more useful, particularly where the contract has been amended or the Scope contains requirements that will affect day-to-day administration.
Before mobilisation, a start-up workshop can take a design submission through its intended review route, or test how an early warning would reach the people able to act on it. A compensation event example can establish whether the programme and cost records provide the information needed for assessment. The planner, commercial team, site team and Project Manager should work through these decisions together, resolving gaps in information or approval responsibilities before they delay delivery.
In the early stages of delivery, I prefer regular workshops that build on the initial training. The team can bring its first programme submissions, early warnings and compensation event quotations, and work through the questions arising from them. On Ironbark, that might include reviewing whether the programme properly allows for the treatment plant connections, or whether the records supporting an Option C payment assessment are sufficient. These are opportunities to apply the contract to work the team is already doing and correct misunderstandings before they become routine practice.
The workshops should involve the people preparing the information as well as those reviewing and deciding on it. They can be timed around the project’s early submissions and assessments, with their frequency adjusted as the team becomes more familiar with the contract. They should support the contractual processes, not become another approval stage or a reason to delay a notice or response.
