There is no freeze. There are documents.

Engineering produces a list before it produces a design

The first thing a design organisation makes isn't a drawing. It is a list of the drawings and documents it is going to make, with a discipline against each and a planned issue date.

That list is the real object of control for this phase. It is divided by discipline — civil, structural, mechanical, electrical, process — and each discipline works to its own logic and its own sequence while depending on outputs from the others. A structural drawing waits on a mechanical load; the mechanical load waits on a vendor who hasn't been appointed.

Which means engineering progress is countable in a way construction progress isn't. A document is issued or it isn't. There is no partly issued, no judgement, no percentage anybody has to defend. That property makes the deliverable list the single most reliable measurement available in the early months, and it goes unused as one, because a list of documents doesn't look like progress the way a foundation does.

The gate, and how it actually works

Take the design-and-build conditions, where the mechanism is written out most fully, and follow one document through it.

A document goes to the Engineer with a notice saying the contractor considers it ready and compliant. The Engineer then has a review period — not more than 21 days unless the requirements say otherwise — counted from receipt.

If the Engineer says nothing within that period, no-objection is deemed to have been given. And construction of the part covered by that document may not begin until no-objection exists — given or deemed, the contract treats them alike.

So there is your freeze, and it has no date. It is one document reaching a state, then another, then another, each unlocking a small piece of the work.

Two consequences follow from that shape. The design is never frozen as a whole, so asking whether it is frozen has no answer — the answerable question is which parts are, and that question has a list behind it. And because each release is small, nobody experiences the freeze happening, which is why teams argue about whether the design is stable while the evidence sits in a register nobody is reading as a schedule.

The deeming has a condition attached

The silence provision looks like a safety net and is a narrower one than it reads.

Deemed no-objection applies only if every document the submitted one relies on has also been given, or been deemed to have been given, no-objection. A document standing on a document that is still under review doesn't get the benefit of the clock.

Read that as an operational fact and it is a chain reaction with the arrow pointing the wrong way. One document held at the bottom of a stack quietly suspends the deeming for everything above it, and the suspension is invisible — nothing arrives to tell you it has happened. You discover it when you try to start work on a part whose document you believed was through.

The second lap

If the Engineer objects, three things happen together and the third is the one that matters.

The contractor revises the document. It is resubmitted, and the review period runs again from the date the Engineer receives it — not from where it left off. And there is no entitlement to an extension of time for any delay caused by that revision, that resubmission, or the review that follows.

So a document that goes round twice has consumed six weeks of calendar, and the contract has already decided whose six weeks they were.

The planning consequence is sharp. A programme that allows one review period per document is a programme assuming every submission succeeds first time. That assumption is unmarked, uncontroversial and load-bearing — which puts it in exactly the category week 13 asked you to write down.

And it is worth noticing which way the incentive runs. The party who decides whether a document goes round again isn't the party who pays for the lap. That is a defensible allocation, since the objection is supposed to mean the document was non-compliant. It also means the cost of a marginal objection falls entirely on the side that can't make it.

What this makes the deliverable list

Put those mechanisms together — the clock, the deeming, the condition on the deeming, the restart — and the list stops being an administrative register.

Each row on it is a small gate with a clock, a dependency on rows beneath it, and a failure mode that costs three weeks and is charged to you. The list isn't a record of engineering output. It is the schedule of when the site is allowed to start things.

Which is why the strongest thing a delivery team can do in this phase has nothing to do with design. It is to know, for every document it depends on, which lap it is on and what it is standing on.

That is a reporting question rather than an engineering one, and it is answerable by somebody with no design training at all. Nothing in it requires an opinion about whether a drawing is any good. It requires two dates and a number.

System design

Row four is the strangest entry in this dictionary so far, because the producer may be nobody. A deemed no-objection is a permission created by the passage of time, and it arrives with no document attached — so the only way it exists as a record is if somebody writes the date down when the period expires.

Record	Produced by	Required quality	Verified against	Feeds
Deliverable list	Engineering, before any drawing	By discipline, with what each document releases on site	The scope it has to cover	When site may start each part
Contractor’s notice	The contractor, with each submission	States compliance, or the extent of non-compliance, in writing	The requirements it answers	The start of the review period
Review register	You, one row per document	Carries the lap number, not only the issue date	The responses actually received	Which delays are already yours
Notice of no-objection	The Engineer, or the clock	Recorded with its date, including where it was deemed rather than given	The review period it ran against	Permission to start construction
Reliance map	You, once, in an afternoon	Names what each document stands on, so a suspension is visible	The documents themselves	Whether the deeming applies at all

Row three is where the lap number lives, and it is the difference between knowing a document is late and knowing whose lateness it is. Both facts are available on the same day, and only one of them has a column anywhere to be recorded in.

Practical insight

Keep your own review register. Not a document register — the document controller has one of those and it records issue rather than outcome.

One row per document your work depends on. Date you submitted it. Date of the response, or blank. Outcome: no-objection, no-objection with comments, or objection. And a lap number, starting at one.

Two columns then do work nothing else on the project does. Your lap number shows which documents are consuming time the contract has already charged to you, and it shows it while your second lap is running rather than afterwards. The blank response dates show which review periods are about to expire into deemed no-objection — worth noticing on the day, because it is a permission to start work that arrives silently.

Then add one column and populate it once: what each document relies on. It costs you a tedious afternoon and it is the only way you will see a suspension coming rather than discovering it at a work face with a crew standing in front of you.

Key takeaways

• No standard form contains a design freeze, and none of them names one.
• What exists is a gate operating one document at a time, so the freeze happens distributed across hundreds of small events.
• Engineering produces a deliverable list before it produces a design, and the list is the real object of control in this phase.
• A document is issued or it isn't, so engineering progress is countable in a way construction progress isn't.
• Under the design-and-build conditions the review period isn't more than 21 days from receipt of the document and the contractor’s notice.
• Silence is deemed no-objection, and construction of the part covered may not start until no-objection exists.
• The deeming applies only if every document the submitted one relies on has also been given, or deemed given, no-objection.
• So one held document silently suspends the clock for everything standing on it, and nothing arrives to say so.
• On an objection the review period restarts from receipt of the revision, and there is no entitlement to an extension of time for it.
• A programme allowing one review period per document assumes every submission succeeds first time, which is an unmarked load-bearing assumption.
• The deliverable list is therefore the schedule of when site is permitted to start things, not a record of engineering output.

Records born here. The deliverable list, by discipline · the contractor’s notice accompanying each submission · the review register, with lap numbers · each notice of no-objection, or the date one was deemed · the reliance map showing what each document stands on · the objections and their stated reasons.

What is coming next

A dimension on one of those documents becomes a purchase. Somebody takes it off a drawing, writes it into a requisition, and a sequence begins that ends with something arriving on a lorry.

That sequence has its own clocks, its own approvals and its own way of failing, and it runs in parallel with the one just described while depending on it. What comes next is the path from a line on a drawing to an order with a delivery date against it.