Delay deems something, in both directions.

The test has a six-week lead

Before any of that, the tests have to be programmed, and the notice period is longer than the horizon anybody is planning at.

A detailed test programme — when each test will run and what it needs — goes to the Engineer more than six weeks before the contractor intends to start testing. The Engineer may review it and comment.

Which makes the test a planning object with a lead time longer than any look-ahead on the project. By the time a four-week window shows the tests approaching, the document that permits them was due a fortnight ago.

And the programme has to say what each test needs, which forces a set of questions early: who witnesses, what has to be energised, what the acceptance criteria are, and which of them are measurable. Answering those six weeks out is the point of the obligation. Answering them on the day is what happens instead.

Same shape as week 20's scaffold: a genuine predecessor, with a duration, that no programme has a line for — discovered when somebody tries to start the thing it precedes.

The documents come first, not alongside

Last week established that working is one of three conditions. The ordering is sharper than that.

The obligation to carry out the tests is expressed as following the submission of as-built records and the operation and maintenance manuals, where those are required. The documents aren't a parallel workstream that has to finish by the same date. They sit in front of the test.

So a set of manuals that is three weeks late doesn't delay handover by three weeks. It delays the start of a test programme whose own notice period is six, and the arithmetic compounds from there.

Which puts a document nobody watches on the critical path of the thing everybody watches. The manuals were somebody's administrative task in month twenty; they are the gate in month thirty.

Which puts an unusual instruction on the document controller. The manuals aren't a closeout task to be cleared before handover; they are on the critical path of the test that permits handover, and they need the attention that implies six weeks before anybody wants to test anything.

If you delay: the results bind you anyway

Suppose the tests are held up by the contractor. The Engineer can require them within twenty-one days of a notice, and the contractor picks the days inside that window, giving at least a week's warning of which ones.

Note what the contractor keeps: the choice of day. Three weeks with the choice inside it is a genuine accommodation, and it exists because a test needs conditions rather than just a diary slot.

Miss it, and after a second notice the employer's own people may run the tests. The contractor is entitled to attend and watch. The results come back within four weeks.

And here is the part that matters. Whether or not the contractor turns up, the tests count as having been carried out in their presence, and the results stand as accurate.

That isn't a penalty for absence. It removes the argument that absence would otherwise create — but it also means the evidentiary position gets fixed by a test you may have had no part in. The window is three weeks long and it closes.

If they delay: the boundary arrives without the test

The mirror is at least as consequential and far less known.

Where the contractor is prevented from testing for more than a fortnight — continuous, or added up across several periods — by the employer's people or by something the employer is responsible for, the contractor gives notice of the prevention. Taking over is then treated as having happened on the date the tests would otherwise have finished, and the certificate follows immediately.

Everything week 27 listed as flowing from that date then flows: damages stop, the defects period starts, care passes. On a date fixed by a test that hasn't been run.

The tests still have to happen — afterwards, as soon as practicable and before the defects period expires, on dates the Engineer notices in advance. But they now happen inside somebody else's building, which is the visitor problem from week 27 arriving through a different door.

Failing, and what failing entitles them to

A failed test can be repeated, on the same terms, at either party's request, and a repeat counts as the test itself rather than as something lesser.

Fail the repeat and the Engineer acquires options rather than a single remedy: order further repetition, or reject the works where the failure deprives the employer of substantially the whole benefit of them, or reject a section that can't serve its intended purpose.

The thresholds are worth reading carefully, because they are high and they are stated in terms of use rather than compliance. A works that fails a test but still does what it was built for sits in a different position from one that doesn't.

That distinction is where the argument lands. Rejection is reserved for failures that take away substantially the whole benefit, or that stop a section serving its purpose — which are questions about consequence rather than about whether a number came in under a limit. The test produces the number. Somebody still has to argue about what the number means.

And the repetition has no stated limit. A test can be ordered again, and again, which is a cost with no ceiling attached to it — the contractor bears the retesting and the works remain unhanded-over throughout, so the pressure of an unresolved test grows in two directions at once.

System design

Row three is the one that has to be started before anybody knows whether it will matter. A count of prevented days is worth nothing until the total crosses a fortnight, and it can't be assembled retrospectively, so it has to begin on the first day and most of the time it will be wasted effort.

Record	Produced by	Required quality	Verified against	Feeds
Detailed test programme	You, six weeks ahead	Timing and resources per test, submitted as an obligation not a courtesy	The requirements it tests against	Whether testing may start at all
Notice of test days	You, a week ahead	Names the days chosen inside the window, in writing	The window it sits in	Whether the window was met
Prevented-days count	You, daily, from day one	One line per day, recorded at the time rather than reconstructed	What prevented it, named	Whether a deemed taking over is available
Test results and attendance	Whoever ran the test	Records who was present, since presence may be deemed regardless	The test programme it followed	Pass, retest, or rejection
The deeming, where one occurred	Neither party — the clock	The date it fixed, written down, because no document announces it	The event that triggered it	Every consequence of the boundary

Row five is the second entry in this dictionary produced by nobody. A deeming happens by the passage of time and issues no document, so the only way its date exists as a record is if somebody writes it down when the period runs out.

Practical insight

Put three dates in your programme as activities, not as notes.

The submission of your test programme, six weeks before you intend to test. The submission of as-built records and manuals, in front of that. And your own seven-day notice of the actual test days. All three are contractual obligations with lead times, and none of them appears on a construction programme unless somebody puts it there.

Then set one alarm. The moment anything prevents you testing — access refused, a system not energised, the employer's people unavailable — start counting days and record each one. You need the total to exceed a fortnight before the prevention entitles you to anything, and the days are countable only if somebody counted them at the time.

That record costs you a line a day and it is the difference between an entitlement and a recollection. Nobody reconstructs prevented days from a diary eight months later, which is exactly when you will want them.

Key takeaways

• Delay by either party triggers a deeming, and the two are mirror images of each other.
• Both are triggered by delay rather than by fault, and each transfers something that can't be recovered afterwards.
• A detailed test programme is due more than six weeks before testing starts, so the test has a lead time longer than any look-ahead.
• That makes it a real predecessor with a duration and no line on the programme, like the scaffold in week 20.
• As-built records and manuals sit in front of the tests rather than beside them, so a late manual delays a six-week notice period rather than a date.
• If the contractor delays, the Engineer can require the tests within twenty-one days, with the contractor choosing days and giving a week’s notice.
• Miss that window and the employer’s people may run the tests after a second notice, with the contractor entitled to attend.
• Attendance is deemed either way and the results stand as accurate, so the evidentiary position is fixed by a test you may not have been part of.
• If the employer prevents testing for more than a fortnight, taking over is deemed on the date the tests would have finished, and the certificate issues at once.
• The tests then happen afterwards, inside a building the employer holds, before the defects period expires.
• A failed test can be repeated on the same terms; failing the repeat gives the Engineer options, and the rejection thresholds are stated in terms of use rather than compliance.

Records born here. The detailed test programme, with its submission date · the Engineer’s comments on it · your notice of the test days · the count of days you were prevented from testing, kept daily · the test results, and who was present · each retest and what was repeated · the deeming, where one occurred, and the date it fixed.

What is coming next

Whichever route the tests take, they end in a certificate, and that certificate is a date.

It is the most consequential date on the project, and it can be issued late, disputed, or deemed rather than given. What comes next is what the document actually says, what it doesn't say, and what changes hands the moment it bears a date.