A permit or consent is late: who carries the risk under NEC?

NEC has no clause on permits. See how the Scope and the Accepted Programme decide whether a late permit is a compensation event.

Compensation events and changeScenario3 min read

On this page
  1. The short answer
  2. What to do, step by step
  3. What to record
  4. What not to do
  5. When to get help
  6. Example
  7. Related guides

You cannot start work because a consent, licence, street works permit or possession has not arrived. Whether you or the Client carries that delay depends on who was supposed to obtain it.

The short answer

NEC has no permit clause, so the delay is the Client's risk only if it fits a listed compensation event. Two documents usually settle it: the Scope (who was to apply) and the Accepted Programme (what date it showed). Warn now whoever you think is responsible, and notify if you may have an event. The references here are NEC4 ECC and match NEC3 unless stated.

What to do, step by step

  1. Give an early warning today (clause 15.1, 16.1 in NEC3). If you could have warned and didn't, a later event can be assessed as if you had.
  2. Search for who holds the job. Look in the Scope, the Contract Data and any Z clauses for permit, consent, licence and approval.
  3. Find the permit date on the Accepted Programme as it stood when the delay began.
  4. Notify if you may have an event. You have eight weeks from awareness (clause 61.3), and you can notify on the expected delay without waiting for the permit.
  5. Gather evidence (below) and write your position against the table.
Who was to obtain it, and what went wrong Likely route
Client provides it, and it arrives after the Accepted Programme date Clause 60.1(3). Harder to show if the programme has no date
You obtain it, your application was late or incomplete Your risk, no event
You obtain it, the authority takes longer than the programme showed after a proper application Possibly clause 60.1(5), but arguable
You obtain it for your own design and the authority won't approve it Your risk (clause 27.1)
Nobody named, documents conflict Notify under clause 17.1 and the Project Manager says how it is resolved
Permit refused for something neither side could prevent Narrow chance under clause 60.1(19)
Client changes what is being built and a new permit is needed Instruction, clause 60.1(1), permit time in the assessment

What to record

  • Scope extract on who applies
  • The application, its date and proof it was complete
  • The authority's stated or published turnaround and your correspondence
  • Early warnings and meeting records
  • The Accepted Programme current at the time

What not to do

  • Do not assume a public authority counts as the Client. Ask whether the Client's own department is acting, or a separate statutory body, because a separate body falls under Others.
  • Do not put a hopeful permit date on your programme. A date you knew was too short weakens your claim and may give the Project Manager a reason not to accept the programme.
  • Do not leave the permit line off the programme. Clauses 60.1(3) and 60.1(5) both measure delay against times shown on it, and clause 31.2 expects the programme to show dates you need things.

When to get help

Bring in a commercial manager if responsibility is unclear, and a planner to set the permit and a realistic lead time on the programme. If the authority is part of a public Client, take advice on the structure.

Example

A streetworks connection for a new water main on Option A. The Scope says the Client's consultant obtains the environmental consent. The Accepted Programme shows it by 10 March. It arrives on 21 April, six weeks late, and the connection is on the critical path. This is a thing the Client was to provide arriving after the programmed date. You warned on 12 March and notified before the eight weeks ran out. Costs and dates are invented. Had the Scope made you apply, the answer would have been very different.

This guide is general information, not legal advice. Check it against your contract.

Was this useful?