Works Information vs Scope

Works Information is the NEC3 term for the documents and instructions that describe what the Contractor provides and any constraints on how. NEC4 ECC calls the same thing the Scope. The rename changes the word much more than the idea, but the term is central to entitlement, so it needs care.

For NEC3, the definition is at 11.2(19) of the ECC. For the edition generally, see the NEC4 contracts guide. Our glossary has separate pages on Works Information and the Scope.

What stayed the same

• Purpose. It specifies and describes the work, and states any constraints on how it is done.
• Where it comes from. It's in the documents named in the Contract Data, or in an instruction given under the contract.
• Its link to Defects. A Defect is measured against it.
• Its link to change. An instruction changing it is normally a compensation event under 60.1(1).
• Its separation from Site Information. Site Information describes the Site, not the work.

What is different

Point	NEC3 ECC	NEC4 ECC
Word	Works Information	Scope
Subcontract equivalent	Subcontract Works Information	Subcontract Scope
Programme	Less dependent on it for the form of a programme	Sets the form of a programme issued for acceptance (31.2)
Payment	Not relevant to the form of an application	Sets the form of the Contractor's application (50.2)
Quality	No quality management clause	Sets the requirements for the quality management system (clause 40)
Communications	Not relevant to timing	Can name a system that decides when a communication takes effect (13.2)
Contractor's proposals	No clause	Clause 16 proposes changes to the Scope

So NEC4 expects more from the document. A Scope carried over from an NEC3 job might have nothing on these points, leaving the contract's references with nothing to rely on.

Why the term matters so much

Here's a fictional example. A Scope for an office fit-out specifies a particular floor finish. Later, the Client's team decides a different finish looks better, and the Project Manager tells the Contractor to use it.

Question	Answer
Is it a change to the Scope?	Yes, because the document specified something else
Is it a compensation event?	Yes, under 60.1(1), unless it falls within the clause's exceptions
What if the drawing and specification conflicted beforehand?	An ambiguity. The Project Manager resolves it under 17.1, and the effect may be assessed under 63.10 in the Contractor's favour if the Client's document caused it
What if the instruction was only verbal?	It needs recording, because communications need a form people can read, copy and keep on record (13.1)

This is why good document control matters. If you can't show what the Scope said on the date of the instruction, it's harder to show that something changed.

What a good Scope or Works Information contains

• A clear description and specification of the work, with drawing and document lists showing revisions.
• Any constraints: working hours, sequencing, access limits, people on site, other contractors.
• Who designs what.
• Tests and inspections, and who does each of them.
• The form of programmes and applications (NEC4).
• Quality requirements (NEC4).
• Any procedures, such as procurement, on which Disallowed Cost might later turn.
• Anything the Client or Others will provide, and when.

What people get wrong

• Writing obligations into the Scope as if they were contract terms. Clauses that change liabilities or the conditions belong in Z clauses. Hiding them in the Scope invites a dispute, and may not have the effect intended.
• Mixing Site Information into it. A ground report in the wrong volume can blur a physical conditions argument under 60.1(12).
• Using "or equal" and "as required" loosely. Vague wording leads to ambiguity, and to arguments about the Contractor's design.
• Tender-stage leftovers. Unresolved tender queries and old drawings cause trouble. State exactly what forms the document at the Contract Date.
• Using the old word in NEC4 documents. See NEC4 terminology changes for a list of terms to update.

Other forms

Names vary across the suite, so don't assume one word applies everywhere. The NEC3 PSC already used "Scope", for instance, and the NEC4 Supply Short Contract's index points "Goods Information" to the Scope.

Related guides

• NEC4 Contracts: A Complete Guide
• Employer vs Client in NEC
• The History of NEC Contracts
• The NEC3 Risk Register
• NEC3 Risk Reduction Meetings

This guide is general information in our own words, not legal advice. Your contract and its Contract Data always govern. NEC, NEC3 and NEC4 are trade marks of Thomas Telford Ltd; Contract Status is not affiliated with or endorsed by NEC.