The winner read it most favourably.

The pack that was priced isn't the pack that was issued

An enquiry goes out. Bidders read it and start asking questions, because the documents are never complete and the questions are the mechanism for closing the gaps.

Each answer goes to everybody, as an addendum. Which is procedurally correct and has a consequence: the document set being priced changes while it is being priced, and the later changes land in the weeks when there is no capacity left to work through them properly.

So the tender that was submitted is the base documents plus a stack of addenda, some of which moved something material. Reconstructing that exact set afterwards is the single most useful piece of archaeology available to a delivery team, and it becomes harder every month.

There's a second-order effect worth naming. A question is asked because one bidder spotted something, and the answer goes to everybody — so the process converts one firm's diligence into information for its competitors. What it doesn't convert is the reasoning: the answer arrives without the question's context, and a bidder who wasn't looking at that part of the works reads a sentence with no idea what it was protecting against.

The document that changes everything, read last

A standard form isn't used as printed. It is amended, and the amendments live in the Particular Conditions.

The contract law literature is direct about what this means for a bidder: the Particular Conditions are where the standard terms get changed, and a contractor has to be alert to those changes throughout the tender period, because employers' advisers use exactly that instrument to move the balance.

Consider what that asks. The risk allocation you will live inside for three years — who carries the ground, what a notice period is, whether a claim survives a late notice — is set in a document that arrives with the pack and gets read while a bid is being priced against a deadline. Contract Week 2 takes apart what those amendments do. What matters here is when they were read, and by whom.

And the amendments that matter most are the ones that read as housekeeping. A changed word in a notice provision doesn't look like a risk transfer on a Tuesday afternoon three days before submission. It looks like tidying. It becomes a risk transfer eighteen months later, on the first occasion somebody serves a notice a day late.

What lowest price selects for

Where price is the criterion, the process selects the lowest number, and the lowest number is produced by whichever combination of efficiency, appetite and optimism happens to go furthest.

Public procurement systems know this and provide a remedy: a tender can be rejected as abnormally low. The remedy is harder to use than it looks. Where the law doesn't define the term precisely, a competitor challenging an award has to demonstrate that the winner couldn't perform at that price without loss — which requires access to the winner's books, and the winner is under no obligation to open them.

The contract law literature records a case where a motorway package was won at a price far below the employer's own expectation, wasn't rejected, and ended with the contractor abandoning the site and leaving subcontractors unpaid. The re-let packages cost more than the bid that had originally lost.

That outcome is the extreme form. The ordinary form of the same mechanism is a job that completes, at a margin thin enough that every unforeseen problem has to become a claim, because there is no room to absorb it.

What was actually accepted

Award isn't one event either. There is a Letter of Acceptance, and the interesting question is what it accepted.

Bids arrive with qualifications — assumptions the bidder wrote down, exclusions, clarifications of its own. Some of those get accepted, some get negotiated away, and some are simply not mentioned again. A negotiation between the lowest bid and award can change scope, programme or terms after the price was set against different ones.

Bid qualifications have a particular way of disappearing. A bidder writes down an assumption because it's doing the honest thing — stating what its price rests on. If the employer neither accepts nor rejects it, the qualification sits in a covering letter that may or may not be a contract document, and whether it is one depends on the order of precedence.

The result is a contract whose documents have an order of precedence, and whose meaning depends on which version of which document sits where in that order. That is the first thing to establish on day one and it is Contract Week 1's subject, not this one. The lifecycle observation is narrower: the answer was produced by a process nobody documented as a process.

What survives into delivery

Almost nothing.

The estimator's build-up stays inside the bidding organisation and is treated as commercially sensitive within it. The reasoning behind each resolved ambiguity was never written down, because there was no document asking for it. The evaluation record belongs to the employer. What crosses into delivery is the contract, the accepted price, and a programme.

Which closes the phase on the same note it opened. Week 1 followed a decision through six hands and found the reasoning stripped at each one. Phase A is that pattern at the scale of a whole front end: five stages, each producing a conclusion, each discarding what produced it, and a delivery team inheriting the last conclusion with none of the four before it.

System design

The last row doesn't exist as a document anywhere in this industry, which is why it is in the table. Every other row is a record somebody already keeps; the interpretation list is one that could be kept, costs a conversation, and answers a question that will be asked repeatedly for the next three years.

Record	Produced by	Required quality	Verified against	Feeds
Invitation to tender	The Employer, at issue	Dated, with the document list it was issued against	The delivery strategy it serves	Everything priced afterwards
Query register and addenda	The tender process, continuously	Every addendum numbered and dated, so the priced set is reconstructible	The questions that produced them	What the price actually covers
Particular Conditions	The Employer’s advisers	Changes to the standard form visible as changes, not reprinted silently	The general conditions they amend	Risk allocation for the whole job
Bid qualifications	The bidder, with its price	Each one tracked to accepted, negotiated away, or unanswered	The Letter of Acceptance	What the contract actually says
Interpretation list	Your estimator, in ten minutes	Names each document the bidder had to read one way rather than another	The tender documents themselves	Where arguments will arise

Row two carries the phase’s recurring quality requirement in its final form. Not the documents — the order and the dates. A list of addenda tells you what was issued. Their sequence tells you what could realistically have been priced.

Practical insight

In your first month, reconstruct the tender pack as it was actually priced, and date it.

You want the base documents, then every addendum in issue order, then the query register that generated them. Your own estimating team has all of it and will hand it over while the job is new and nobody is defending anything. Ask in month nine and the same request is read as the opening of an internal argument.

Then do one pass with a specific question in mind: which addenda arrived in the final fortnight? Those are the ones that were absorbed rather than priced, and they are where your exposure concentrates. Mark them.

Finally, ask your estimator one question and write the answer down: which parts of the documents did you have to interpret? You will get three or four items, delivered in about ten minutes, and they are the map of where this contract will generate arguments. Nobody else on your project will ever be in a position to produce that list again.

Key takeaways

• Where documents admit of more than one reading, the winning bid is by construction the most favourable reading of them.
• That set of interpretations becomes the delivery team's budget, and it was made by people who won't deliver against it.
• The pack that was priced is the base documents plus every addendum, and the late addenda land when there is no capacity to price them.
• Standard forms are amended in the Particular Conditions, and a bidder has to catch those changes while pricing against a deadline.
• The risk allocation you live inside for years is therefore read once, quickly, by an estimator rather than by a delivery team.
• Selecting on lowest price selects for whichever mixture of efficiency, appetite and optimism goes furthest.
• The power to reject an abnormally low tender exists, and the burden of proof requires access to the winner's books.
• The extreme outcome is abandonment and a costlier re-let; the ordinary one is a margin too thin to absorb anything, so every problem becomes a claim.
• Award can change scope or terms after the price was set against different ones, and bid qualifications may be accepted, negotiated away, or never mentioned again.
• Nothing about how the ambiguities were resolved crosses into delivery, because no document ever asked.

Records born here. The invitation to tender and its issue date · the query register · every addendum, in order, with the date it landed · the Particular Conditions · the bid qualifications and which of them survived · the evaluation record · the Letter of Acceptance and what it accepted.

What is coming next

Phase A ends here, at a signature. Everything in it was done by people you won't meet, in documents you will mostly not read, and it is now the ground your job stands on.

What follows is the part nobody writes down, because it is too ordinary to seem like a subject and too fast to record while it is happening. Somebody arrives on a Monday with a laptop and a contract, and by Friday has to know things that took the front end four years to decide.