Project Contract Lab

Scenario: the Contractor will install a modern heating, ventilation and air-conditioning (HVAC) system in a new office building. “State of the art” expresses an ambition, but does not by itself give a measurable acceptance criterion.

Connection: NEC4 uses Scope for requirements and constraints. This overview and the specification in card 2 belong to that same Scope; they are not two independent contractual definitions.

What must the system do, and what evidence will show that it does it?

NEC: terminology changes in NEC4 works contracts.

Scenario: maintain 68–72°F (about 20–22°C), with separate controls for each floor and a minimum stated efficiency of 18 SEER. These are the original example’s fictional requirements, not a recommended HVAC specification.

Connection: in NEC4 this is Scope; Works Information is the older NEC3 terminology. A real specification would also need an appropriate rating standard, test conditions, operating limits and evidence. “Year-round” alone leaves those conditions unclear.

Could two people interpret the temperature or efficiency requirement differently?

NEC: Works Information becomes Scope.

Scenario: plan installation in weeks 12–15 and testing and commissioning in week 16. The original five-week window includes one week for commissioning.

Connection: the accepted programme supports coordination and assessment of change. Updating it to show a delay does not by itself change the contractual Completion Date; that is a separate contractual process.

Which preceding delivery, access or design decision makes the week-12 start possible?

NEC: the accepted programme and additional time.

Scenario: the Contractor learns that the specified unit has a ten-week lead time which could delay installation. Raise the matter promptly so the team can consider earlier ordering, sequencing or another unit.

Connection: NEC4 ECC early warnings sit in clause 15. They bring potential effects on price, time or performance into joint risk management. Giving an early warning does not itself create a compensation event or a payment entitlement.

What action might avoid the delay before anyone assesses its contractual consequences?

NEC4 guidance mapping, clause 15.1; NEC: early warnings and compensation events are distinct (2017 article uses earlier clause numbering).

Scenario: the Project Manager instructs an upgrade to the Client’s specified HVAC requirements. Assume it is a genuine change to the Client’s Scope, not correction of the Contractor’s non-compliant design.

Connection: a qualifying instruction to change Scope is a compensation event, subject to exceptions. Notification, quotation, assessment and implementation still matter. Its assessed effect may concern time, money, both or neither; it is not simply the difference between two catalogue prices.

What changes in installation, commissioning and planned Completion as well as purchase cost?

NEC: introduction to compensation events; NEC: Scope-change exceptions.

Scenario: the fictional activity schedule allocates £150,000 of an initial £1,000,000 total to one HVAC installation-and-testing activity. That is 15% by our assumption; NEC does not prescribe a 15% HVAC milestone.

Connection: under Option A, Price for Work Done to Date (PWDD) uses prices for completed activities or groups of activities. Assume this single activity satisfies the contract’s completion test. Part-progress alone does not earn a fraction of that activity’s price.

This activity’s PWDD contribution: £0

This illustration excludes other activities, compensation-event adjustments, retention, tax, prior payments and other amounts due. £150,000 is a contribution to PWDD, not an assessed net payment or permission to invoice.

NEC: Option A pricing and completed activities.

Scenario: testing shows that a zone cannot achieve the temperature range under the agreed test conditions. If the works do not comply with the Scope, that can constitute a Defect; a problem caused by operation outside those conditions is not automatically the same thing.

Connection: NEC4 defines Defects by compliance with Scope and, for Contractor-designed work, relevant law and accepted design. The Contractor and Supervisor have notification duties. The defects date and a notified defect’s correction period are distinct; the Contractor’s obligation to correct is not created only by a notification.

Which requirement failed, how was it tested, and which notification and correction provisions apply?

NEC: defining, notifying and correcting defects.