The date can arrive without the document.

You apply for something that hasn't happened

The sequence starts with the contractor, and it starts early.

The application goes in up to a fortnight before the works will, in the contractor's own judgement, be complete and ready. So it is a forecast rather than a report: you are certifying an opinion about a state the works have yet to reach.

That framing matters for a reason that shows up later. An application made too early gets rejected and the clock restarts; an application made after completion has given away days that were available. The instrument rewards a forecast accurate to within about a week, which is a demand nobody states out loud.

And it collides with the phase it sits in. Predicting completion to within seven days requires knowing which of the outstanding items will close, which is the thing week 28 showed depends on who is available to inspect. You are forecasting a date set by other people's diaries.

What has to be true first

Taking over waits on a short list, and week 29 named the substance of it: the works complete and the tests passed, no-objection to the as-built records, no-objection to the manuals, and any required training actually delivered.

Two of those are document conditions carrying their own review periods, which is week 15's loop appearing at the last possible moment. A set of manuals still inside its review window is a set of manuals holding a certificate.

And the deeming that saves you elsewhere is available here too: a no-objection can be deemed as well as given. So the condition can be satisfied by a review period expiring, which is worth knowing when somebody says the manuals haven't been approved.

It is also a list with no partial credit. Four conditions, all required, and a certificate held by a training session that was scheduled and not delivered is held as firmly as one held by works that are unfinished.

Twenty-eight days, and what silence does

Once the application is in, the Engineer has four weeks to do one of two things: issue the certificate, or reject the application with reasons.

Do neither, and provided the substantive conditions are actually met, two things are deemed. Completion is deemed to have occurred on the fourteenth day after the application was received. And the certificate is deemed to have been issued.

The proviso is doing real work and it is worth being honest about it. Silence only produces the deeming where the conditions were genuinely satisfied — so this isn't a route around an incomplete works. It is a protection against a certificate being withheld from a works that qualified for one.

Read the arithmetic. The deemed completion date sits a fortnight after the application — two weeks before the deadline the Engineer had for answering. So an Engineer who says nothing hands you a better date than an Engineer who issues a certificate on day twenty-seven naming that day.

Which produces an incentive shaped unlike most in a construction contract: silence isn't neutral and it doesn't favour the party staying silent. It is worth knowing before you spend three weeks chasing a response.

It is worth being precise about what silence doesn't do. It can't manufacture a completion that didn't happen, and it gives no protection where a condition was genuinely unmet. What it protects against is a certificate withheld from works that qualified for one, which is a narrower thing and the thing that actually happens.

Everything hangs on the receipt date

If completion can be deemed fourteen days after an application was received, then the receipt date is load-bearing.

It sets the deemed date. It starts the four weeks. And it is the one fact in the sequence held by the other party — their inbox, their date stamp, their record of when the thing arrived.

Nothing about that is sinister. Receipt is a fact about the receiver, and it lives where they are. It is simply the point at which your entitlement rests on somebody else's filing.

Which is the eighth time on this track that something decisive has depended on a date somebody else holds. The remedy is the same as it has been each time: acknowledge it yourself, in writing, on the day.

The list is inside the certificate

The certificate doesn't merely record a date. It carries the outstanding work and defects with it, listed.

And the list is constrained. What may remain is minor work and defects that won't substantially affect the safe use of the works for their intended purpose — so the qualifying test is about use, exactly as the rejection thresholds in week 30 were.

That cuts both ways at the moment of certification. An item affecting safe use can't sit on the list, so it has to be finished before the certificate rather than after it. An item that doesn't affect safe use has a strong claim to belong on the list rather than to hold the certificate up.

So the test does work in both directions, and each party will find it pointing their way on different items on the same afternoon. That is the shape of the conversation at handover: not a dispute about standards, but the same question asked forty times about forty things.

Week 28 takes the list apart as a document. What matters here is that its contents are decided by a contractual test at the moment of handover, and both parties are arguing that test rather than arguing about workmanship.

System design

Row two is one line of administration standing behind two clocks. It has appeared on this track in seven other forms — the delegation notice, the release date, the access request, the date first known — and it is the same instrument every time: write down, on the day, a fact you will otherwise have to ask somebody else for.

Record	Produced by	Required quality	Verified against	Feeds
The application	You, before completion	Sent so that the date of receipt is provable by you	The state the works will reach	Both clocks that follow
Proof of receipt	You, on the day	Held on your file, not only in the other party’s system	Their acknowledgement, if given	The deemed date · the response period
Day fourteen and day twenty-eight	You, diarised on sending	Both dates, because one is a deeming and one is a deadline	The receipt date	Whether silence has become an outcome
The certificate, or the deeming	The Engineer, or the clock	Where deemed, the date written down, since no document announces it	The conditions that had to be met	Every consequence of the boundary
Safe-use argument per item	You, before applying	Written in advance, one line each, rather than assembled under refusal	The intended purpose of the works	What may stay on the list

Row five is the one people skip because it feels like preparing for a fight. It is the opposite: an argument written calmly in advance comes out shorter, and the short version is the one that gets read.

Practical insight

Send your application in a way that gives you your own proof of receipt, and record the date on your file the same day.

Everything downstream counts from your date: the four weeks the Engineer has, and the fourteenth day a deeming would land on. If the only record of receipt sits in their system, the two dates deciding your position are theirs to establish and yours to ask for.

Then diary both days. Your day fourteen, because it is the date a deeming would name and you want to be able to say so on the day rather than three weeks later. Your day twenty-eight, because that is where silence stops being an answer you are still waiting for and becomes the outcome.

And write down, before you apply, which items you expect on the certificate's list and why each of them doesn't affect safe use. Preparing that argument in advance takes an hour. Assembling it while somebody is refusing to certify is a different exercise entirely, conducted at the point of maximum pressure with the site already demobilising.

Key takeaways

• The certificate records the date the works were completed, so the date it names and the day it issues are two different things.
• The application goes in up to a fortnight before completion, on the contractor’s own judgement, so it is a forecast rather than a report.
• Applying too early invites rejection and a restarted clock; applying after completion gives away days that were available.
• Taking over waits on completion and tests passed, no-objection to as-built records and manuals, and training delivered.
• Two of those carry review periods, so a document still inside its window is a document holding a certificate.
• The Engineer has four weeks to issue the certificate or reject the application with reasons.
• Doing neither deems completion on the fourteenth day after the application was received, and deems the certificate issued.
• So the deemed date sits two weeks before the answering deadline, and silence produces a better date than a late issue.
• The receipt date sets both the deemed date and the four weeks, and it is held by the other party.
• The certificate carries the outstanding work and defects inside it, listed.
• What may be listed is limited to items not substantially affecting safe use for the intended purpose, so the qualifying test is about use rather than workmanship.

Records born here. The application, with proof of the date it was received · the fourteenth and twenty-eighth days, diarised · the certificate, or the record of a deeming and the date it fixed · the list attached to it · your safe-use argument for each listed item, written before applying · any rejection, with the reasons given.

What is coming next

All of that assumes one handover of one thing, at one moment. The contract itself provides for the alternative, which is a sign of how ordinary the alternative is.

An employer who needs part of an asset takes part of it, and a boundary that was designed to fall once falls several times instead — each time transferring a fraction of the works, a fraction of the risk, and a proportion of something that was never meant to be divided.