Nobody is the Engineer.

The assumption nobody stated

Read back through the tracks and the same picture sits behind all of them. One employer. One contract. One contractor with the whole of the works. One Engineer administering it. One programme that covers everything being built.

It was never argued for, because it didn't need to be. It is the shape the standard forms are written around, the shape the textbooks use, and the shape that lets a method be taught without a page of qualifications attached to it. Every technique in six tracks quietly depends on it.

That is not a flaw in what came before. Teaching the single-contract case first is the only sensible order — you can't explain what happens when a definition has nowhere to live before explaining the definition. But the assumption has been doing work all along, and it has never been named.

What actually rests on it

Four things, and they are worth separating because they fail differently.

Entitlement assumes an address. A notice is served on somebody with the authority to receive it and the duty to act. Where that role is split across firms, or held by a company with no contractual relationship to you, the mechanism from Contract Week 3 doesn't simply become harder. It has nowhere to attach.

The critical path assumes work. Schedule Week 13 computes float across a network of activities you control or subcontract. On a job where the long-lead equipment is bought by the employer under a separate order, the driving path runs through a contract you can't see and a supplier you can't chase.

Risk registers assume a scope. Risk Week 3 breaks risk down within the works. Break risk down within a scope and the gaps between scopes are exactly what the structure excludes. On a multi-package job that is where an expensive item can sit, and no register is shaped to hold it.

A number assumes an owner. Reporting Week 1 made that the foundation of a whole track. When the record you would check against belongs to another company, on their cut-off, in their coding, the reconciliation is no longer a conversation down the corridor.

Concurrency, and where the definition lives

One example is worth following all the way through, because it shows that this is not a matter of degree.

Claims Week 16 established that the standard forms don't define concurrency. The definition is left to the Particular Conditions, which is uncomfortable but workable: two parties, one contract, and a document where the meaning can be written down and agreed.

Now take the same argument onto a job with six packages and no head contract. There is no single document to hold the definition, and the two delays being argued about may sit under two contracts with different wording and different tests. The technique is entirely correct and there is nowhere to apply it.

That is the difference between a harder version of a problem and a different problem.

Same job, different shape

The example running through six tracks has been a single lump-sum contract. It stays. What changes from here is how it was bought.

Instead of one contractor holding the works, the employer lets it as packages: civil, mechanical, electrical, and the long-lead equipment ordered directly. A managing contractor coordinates them and employs none of them. Same scope, same quantities, same money. A different diagram.

Keeping the job is deliberate. The alternative is a second case study, and then every figure has to be traced twice. What is being examined here is not a bigger project. It is the same project under a structure that removes the single point every method has been leaning on.

What this track is, and is not

It is not a catalogue of delivery models. Knowing what the letters in EPCM stand for changes nothing about a Tuesday. Each model appears only where it breaks something specific, and the definition arrives as a consequence rather than as a lesson.

It doesn't re-teach a method. Float stays in Schedule, concurrency in Claims, cost accounting in Cost & Cash, and where a number comes from in Reporting. This track marks the edges and hands the technique back with a link every time.

What is left is the part that only exists at the joins: who can instruct whom, which work belongs to nobody, whose programme the critical path runs through, and who owns a figure that two organisations both produce correctly.

System design

Before any technique, one page that doesn't exist on most multi-contract jobs: who the parties are, who may instruct each of them, and where a notice goes.

Record	Produced by	Required quality	Verified against	Feeds
Contract map	Project controls	Every party the employer holds a contract with, not just yours	The employer’s contract register	Notices · interface register
Instruction authority	Contracts or commercial	Contractual or conventional, stated for each party	The contracts themselves	Who an instruction is valid from
Notice address	Contracts	One named recipient per party you can be delayed by	Each contract’s notice clause	Entitlement · delay events
Package scope boundary	Engineering with each party	Where one scope ends and the next begins, in writing	Drawings and the bills	Interface register · risk

The second row is the one that causes arguments. Authority on these jobs can be conventional rather than contractual — everybody does what the managing contractor says because that is how the site runs, not because a clause says so. Writing down which it is, party by party, is an hour of work and it decides what happens the first time an instruction is disputed.

Practical insight

Take your own project and answer three questions in writing. They take ten minutes and most people can't finish them.

How many separate contracts exist on the site — not subcontracts under yours, but contracts the employer holds directly? Who has the authority to instruct each of those parties, and is that authority contractual or conventional? And if a delay were caused to you by one of them tomorrow, who would you serve the notice on?

If the third question has a clean answer, this track will be a description of other people's projects and worth reading anyway. If it doesn't, the sixteen weeks after this one are about the job you are already on.

Key takeaways

• Six tracks assumed one employer, one contract, one contractor, one Engineer, one programme. None of them said so.
• Teaching that case first is correct. It only becomes a problem when it is mistaken for the general case.
• Entitlement assumes an address for the notice. Split the role across firms and the mechanism has nowhere to attach.
• The critical path assumes the work is yours. It can run through an order placed by somebody else.
• Risk registers cover what goes wrong inside a scope. The expensive items sit between two.
• A number assumes an owner you can reach. Across companies, the corroborating record belongs to somebody else.
• Concurrency is the clearest case: the definition lives in the Particular Conditions, and with no head contract there are none.
• The case study doesn't change. The same job is re-let as packages, so no figure moves.

Records born here. The contract map · the list of parties and who may instruct each · the notice address for every party you can be delayed by.

What is coming next

If the shape matters this much, the first question is how a job comes to have the shape it has. That decision is made before anybody is appointed, by people the project team never meets.

Next week: how many contracts are there — the axis that decides more than the payment mechanism, and the one nobody teaches.