Certified, and still not paid.

What the employer actually is

On a financed project — a concession, a PPP, a build-own-transfer — the entity signing the construction contract is a vehicle created for the purpose. It exists to hold the asset, service the debt and pass revenue back to its shareholders.

What matters for project controls is narrower than any of that. This employer doesn't have a treasury it can pay you from. Every payment comes from a drawdown against a facility, and every drawdown has conditions attached to it that were negotiated before the construction contract was signed and are not in it.

So the payment chain has a gate the contract doesn't describe. Everything Cost & Cash Week 17 says about the interim cycle still applies, with one extra step that can add weeks and is invisible from inside the contract.

The count reaches the lenders first

There is a reason a financed job is so often a single contract, and it runs straight back to the question this track opened with.

Lenders prefer the whole of the works under one fixed price, with one contractor answering for all of it. That is the structure their model is easiest to build on: one completion obligation, one party carrying the risk of the parts not fitting together, one place to look when they don't. Splitting the works into packages hands that risk back to the vehicle, and the vehicle is the thing the money was lent against.

Split structures are accepted, and more readily than they once were, but on a condition. The shareholders behind the vehicle undertake to put funds in above what they have already committed, if costs overrun or the vehicle can't service its debt before the works are finished. That undertaking is what closes the gap the packages opened.

And its size moves with the count. More packages means more boundaries nobody holds, which means more support the shareholders have to promise — which is why the number of contracts becomes one of the harder things to settle while the debt is being arranged, rather than a procurement preference somebody expressed.

That is worth carrying onto site for one reason. The interface risk this track has been describing is not invisible to everybody. It was priced once, in a negotiation that closed before anybody here was appointed, and the number that came out of it is why the job has the shape it has.

A second Engineer with no contract

The lenders appoint their own technical adviser. Their job is to protect the lenders' position: to confirm that the works are progressing as represented, that the money drawn matches value created, and that the asset will do what the financial model assumes.

That person has no authority over the contractor. They can't instruct, can't vary, can't determine. This is week 3 again in a different costume, with one difference that matters: the managing contractor there had authority in practice and none on paper, while this adviser has no authority in either sense and controls the money anyway.

They do it through certification of the drawdown rather than through the contract. Which means a request that would be an unreasonable demand if it came from the Engineer is, from them, simply a condition of the project being funded that month.

The reporting stream nobody priced

The immediate consequence lands on project controls and it lands as work.

The adviser reports to the lenders on their own cycle, to their own format, against the financial model rather than against the programme. They will want progress expressed in a way that maps to drawdown, evidence to a standard set by a credit committee rather than by an Engineer, and confirmation of things the construction contract doesn't require anybody to confirm.

None of that is in the tender. It is a second reporting obligation, to a second audience, with a second definition of what counts as progress — and by Reporting Week 20's standard it is a fifth document produced from a different extraction, which is exactly the condition under which numbers stop reconciling.

Two sets of milestones

The second consequence is slower and it catches people at the end.

The construction contract has completion, taking over, and whatever sectional dates were agreed. The financing agreement has its own: conditions for the final drawdown, a date by which the asset must be generating revenue, and tests the lenders require before the debt converts to its operating terms.

These are not the same dates and they don't have to be. A contractor can achieve completion under the contract and leave the vehicle unable to satisfy its lenders, or the reverse. The pressure that then arrives on the programme comes from a document nobody on the delivery side has read.

Which is why the useful question at the start is not what the completion date is. It is what the vehicle has to demonstrate, to whom, and by when — because that is the date the project is actually being run to.

What a planner does about it

Three things, and none of them requires access to the financing agreement itself.

Establish the drawdown cycle and put it in the cash flow. The gap between certification and payment is a working capital cost, and on this structure it is longer and less predictable than the contract implies.

Ask what the adviser needs and when, then produce it from the same extraction as everything else. The alternative is somebody assembling it separately each month, and two versions of the progress figure reaching two audiences.

And find out which financing milestones exist, even approximately. Not to manage them — they are not yours — but because they explain instructions that otherwise look arbitrary, and knowing why a date matters is what lets you argue about it.

System design

None of this needs the financing agreement. All of it can be assembled by asking the people who already have the answers.

Record	Produced by	Required quality	Verified against	Feeds
Drawdown calendar	Project controls	The date each month funds are released, not the contract period	The employer’s finance team	Cash flow · working capital
Adviser evidence list	Project controls	What they need and when, asked for rather than discovered	The adviser directly	The monthly extraction
Financing milestones	Project controls	Known approximately, even where the agreement is not shared	The employer	Why a date matters
One extraction, two audiences	Project controls	The adviser’s pack built from the same cut as the monthly report	The reporting calendar	Whether the two figures agree

The last row is the one that prevents the slower failure. An adviser’s pack assembled separately each month becomes a second version of the progress figure, reaching an audience with the power to stop the money, and neither audience knows the two documents differ.

Practical insight

Find out, for your own project, how long it takes between the Engineer certifying and the money reaching your account.

Compare that with the period the contract states. If they differ by more than a few days, ask what happens in the gap. On a financed structure there is a drawdown cycle in there, with a date each month that nothing in your contract mentions.

Then put that date in your own calendar next to the certification date. It costs you nothing, and it turns an unpredictable payment into a predictable one — which is the whole of what your treasury needs from you.

Key takeaways

• A vehicle employer has no money of its own. Every payment is a drawdown against a facility.
• The drawdown carries conditions negotiated before the construction contract and absent from it.
• The lenders' adviser can't instruct, vary or determine, and controls the money regardless.
• They exercise it through certification rather than through the contract, so their requests are funding conditions rather than instructions.
• They report on their own cycle, to their own format, against the financial model rather than the programme.
• That is a second reporting obligation to a second audience, produced from a second extraction unless somebody prevents it.
• Financing milestones are not contract milestones, and the pressure on the programme often comes from the first.
• Put the drawdown cycle in the cash flow. The gap between certification and payment is a real working capital cost.
• Lenders prefer one contract at a fixed price, because one party then carries the risk of the parts not fitting together.
• A split structure is accepted where the shareholders undertake to fund overruns before completion, and that undertaking grows with the number of packages.

Records born here. The drawdown calendar alongside the certification calendar · the adviser’s evidence requirements · the financing milestones, as far as they are knowable.

What is coming next

That is every party. From here the track turns to the physical work, and to the part of it that appears in nobody's scope until somebody has to build it.

Next week: the work in nobody's scope, and the gap between two risk registers.