Extensions of time

Extensions of time, with the reasoning kept

An award is a number of weeks. What makes it defensible two years later is the sentence explaining how the number was reached, and that sentence is almost never written down.

Damages run from the revised completion date, not the original
Cap applied where the contract states one
Red warning where no certificate of non-completion has been issued

Start free for 30 days See the interactive demo

30 days free, no card.

Extensions of time: contract completion date, weeks awarded and revised completion date

Three weeks are awarded across EOT-01 and EOT-03, and only awarded weeks move the completion date the damages are counted from.

Where the extension stops the damages clock

The reason an extension matters in money is the completion date it moves.

Damages run against that date, and a week of extension is a week the employer can no longer deduct at the liquidated rate. QScope calculates damages from the completion date after any award, applies any cap, and refuses to let the figure stand while no certificate of non-completion is on the register.

Extensions of time

Time and money are different entitlements

A relevant event under clause 2.29 can carry an extension of time.

Thirteen relevant events, each flagged for whether it can carry money
A warning when loss and expense is claimed against an event that cannot carry it
Notice date, particulars date and award date held separately

An event with weeks claimed and awarded, and whether loss and expense is claimed

Exceptionally adverse weather is a Relevant Event but not a Relevant Matter: it relieves the contractor of damages and carries no money.

Extensions of time

Awarded is the only status that moves a date

A claim that has been notified but not decided extends nothing.

Revised completion date built from awarded weeks only
Contract completion date taken from start date and duration
Register prints as a document for issue with the assessment

An event rejected: no change to the completion date

EOT-02 claimed two weeks for adverse weather and was rejected, so none of it is applied to the completion date.

See it running before you sign up

Programme

Where the delay is visible before it is claimed

An extension of time is argued after the event.

Contract period taken from the project settings, not drawn by hand
Today marked, so the position is obvious without counting
Overrun past practical completion stated in weeks

Gantt programme against the contract period

QScope draws the works against the contract period with today marked, so the overrun that supports the claim is a matter of record rather than reconstruction.

Loss and expense

The money that some of these events carry

An extension of time buys relief from liquidated damages.

Prolongation, disruption, overheads and finance charges assessed head by head
Each head linked to the delay event it arises from
Warning where the event is a relevant event but not a relevant matter

Loss and expense heads linked to an extension of time event

Late information is a Relevant Matter, so the prolongation arising from EOT-03 is claimed as loss and expense. Adverse weather carries time only.

Every other function on the Extensions of time screen

5 functions the sections above do not cover, each as it works in the program.

Functions 1 to 3

01A client-side guest can read the extension of time register, and a guest with edit rights can add to it.

02Clause numbers appear next to the relevant event only where the contract form uses them, so no other form is quoted a JCT clause.

03The project settings show the completion date after extensions of time next to the contract date.

Functions 4 to 5

04Every delay event puts an EOT decision on the Contract Register, due twelve weeks after the particulars were received.

05Extension of time notices decided is one of the measures on the project health card.

Who it is for

One programme, four clocks running on it

You are applying

You claim the time before damages run

You notice delay, name the relevant event and claim the time before the damages clock does the arguing for you.

Applying for payment

the same measurement

You are certifying

You award the weeks and stop the clock

You assess the extension from the other chair, and the completion certificate you issue halves retention and stops the damages clock.

Certifying payment

You are doing both

Your delay is your own money waiting

You run the programme and the money together, and a completion date that slips moves the whole payment tail with it.

Doing both yourself

You are reporting

A late job is a loan running long

You track completion against the facility term, because a job that finishes late is a loan that runs longer than the model.

Recommending a drawdown

The client, the architect and the tenderer are not on this list. They are the people you let in on a link: they see the one document you sent them, answer it, and that answer is written into the record. No account, no licence, no charge, on every plan.

FAQs

The questions this page raises most often, answered without a sales pitch at the end.

No, and it should not. The assessment is a judgement made by a named person under the contract. QScope holds the dates, the claim, the award and the reasoning, and does the arithmetic that follows from your decision.

The list follows the JCT standard forms. Where you are working under an amended contract or a different form, the categories still work as a way of classifying the cause, and the clause numbering will differ.

It is cancelled and has to be reissued against the new completion date. QScope flags any damages calculation where no valid certificate is on the register.

Yes, and that is the point of linking them. The heads of claim live in the loss and expense register and each one points back at the event that caused it.

From the blog

The part nobody teaches you, written down

Three pieces from the same corner of a contract as this page, answered at length and without a sales pitch at the end.

Woman in a hard hat measuring a window with a tape and taking notes

Time & completion17/08/2026

The client says the work is defective and will not pay. Is it actually defective?

A defect is work that does not match the contract, and half the items on an angry snag list fail that test: they match the contract and not the client’s imagination. How to sort a defects schedule into its four real categories, and answer it without a war.

Read now

Worker in a hard hat checking a window frame with a level in a blockwork opening

Time & completion12/08/2026

Which delays entitle you to more time, and which do not?

The dividing line is simpler than the clause lists make it look: delay from the client’s side of the fence gives time, delay from yours does not, and neutral events give whatever the contract chose to give. Where weather really sits.

Read now

Two people in hard hats checking a window opening in a brick wall

Time & completion28/07/2026

A defect has appeared a year after handover. Am I still liable?

Almost certainly yes: the defects period ending did not end your responsibility, it ended a retention mechanism. How long liability really runs, six years on a signed contract, twelve on a deed, and how to respond to the call.

Read now

All 174 pieces

Keep reading

The three parts this page leans on

Completion and certificates Practical completion, making good and the final certificate, and their FIDIC equivalents: the Taking-Over Certificate and the Performance Certificate. See how it works Loss and expense Prolongation, disruption, overheads and finance assessed under JCT, or cost claimed with time under FIDIC Sub-Clause 20.1, each linked to its cause. See how it works Relevant events explained The dividing line is simpler than the clause lists make it look: delay from the client’s side of the fence gives time, delay from yours does not, and neutral events give whatever the contract chose to give. Where weather really sits. See how it works