When the Rules Move: Change-in-Law Protection for Transition Assets

1 The financing decision when compliance changes

A project board assessing a new legal obligation has to approve a compliant response and establish who can fund it on the required dates. The financial question is whether the executed agreements supply an enforceable, collectible payment mechanism that covers the allocated impact. A contractual claim, an approved compensation amount and cash received into the project account describe different states. The distinction matters when construction invoices or debt payments fall due before a claim is settled.

This paper develops a linked decision method for an operating power or water asset. It connects the legal reference position, the efficient technical response, the eligible cost calculation and the dated funding account. Its original contribution is the reconciliation between compensation economics and interim liquidity. The worked case shows how identical compensation totals and annual debt coverage can accompany different funding requirements. It also separates the capital expenditure necessary for compliance from the operating cash used in a deliberately defined debt-coverage ratio.

The analysis draws on verified official contract guidance and selected procurement sources. Its recommendations are proposed controls for transaction preparation. They establish no compensation entitlement for a Gulf jurisdiction or a particular power and water purchase agreement. The legal examples are bounded comparisons; domestic law, procurement category, contractual wording and lender documents require separate project review. No private contract, completed claim or actual lender offer is represented as evidence.

For the numerical analysis, legal qualification and the specified payment terms are expressly assumed. This permits a reproducible examination of funding consequences without pretending to resolve an actual dispute. A project-specific assessment should replace every hypothetical input with dated contract, engineering and financial evidence. If entitlement or collection remains unresolved, the funding decision should preserve that uncertainty explicitly. Booking the full claim as an immediate receipt would erase the problem the board needs to manage.

2 The legal baseline and the eligible event

World Bank contractual guidance identifies the definition of law, reference date, foreseeability and risk allocation as drafting choices. Its sample approaches include broad allocation and differentiated treatment of general and discriminatory changes [1]. The accompanying checklist asks whether regulations, binding interpretations and technical standards belong within the agreed definition [2]. These sources support a contract-review agenda. They do not supply missing terms in an executed agreement.

The proposed baseline record therefore contains the instrument relied upon, its version, publication date, commencement date and precise project obligation. A published consultation might inform pricing risk without imposing a present compliance duty. An enacted measure with deferred commencement raises a different question. An authority's request for enhanced output may use a variation procedure even when a policy objective motivated the request. Classification should follow the operative document and the contractual definition rather than the label used in an email.

Consider a hypothetical desalination project that priced one discharge specification and later receives a binding new permit condition. The eligibility analysis would first establish the old condition, the regulator's authority, the new condition's effective date and the project company's existing undertakings. Counsel would then test whether the agreed definition includes that permit change. A technical adviser would identify the equipment or operating adjustment needed for compliance. The cost estimate follows those conclusions. A larger invoice alone establishes neither a legal change nor causal eligibility.

The baseline also needs a record of expenditure already committed for the same purpose. If a scheduled replacement would have installed compliant equipment anyway, the additional claim should expose that overlap. Keeping the original lifecycle plan alongside the new design gives the parties a basis for comparing the relevant counterfactual. The proposed method records uncertainty as a specific unresolved issue, such as the prior permit interpretation or a disputed reference date, with its effect on the calculation. It avoids a general disclaimer that leaves the disputed amount hidden.

Table 1. Proposed legal-baseline evidence

Author-proposed evidence record; no legal conclusion or completed project review is represented.

3 Classification and foreseeability in the contract

The historical December 2012 PF2 draft distinguishes discriminatory, specific and general changes, with different treatment across construction and service periods and capital and noncapital costs [3]. The publication is a useful example of differentiated drafting. It is historical UK standardisation, and its terminology should not be transplanted into another agreement as a statement of present law. A project can use similar words with materially different exclusions or payment consequences.

The proposed classification schedule treats each definition as a separate test. A measure directed at a named project might fit a discriminatory definition. A rule applying to a defined service sector could meet a specific-change definition. Economy-wide taxation may fall within a general-change category. Whether any category receives relief remains a further question. The schedule should reproduce the relevant contract cross-reference, the identified event and the reason for the classification, with counsel's confirmation before the amount is approved.

Foreseeability also needs a specified observer and date. A contractor's ability to foresee a measure when submitting its bid is a different enquiry from a contracting authority's foreseeability test under a procurement-modification rule. The reference material may include a draft, an announced commencement timetable or a technical standard already incorporated into the output specification. The paper does not assume that every public discussion is a priced obligation. It recommends recording what the agreed test requires and which contemporaneous materials bear on that test.

This distinction affects bid discipline. A bidder could knowingly accept an emerging requirement in exchange for an agreed price or a specific adjustment formula. A later claim should then reconcile that accepted allocation. Conversely, an excluded future obligation should appear in the qualifications and negotiated contract rather than remaining an undocumented model assumption. For operating assets acquired after financial close, the buyer should review the inherited reference record; the acquisition date does not automatically reset the original project's legal baseline.

Table 2. Classification without assumed entitlement

Original review prompts informed by sources 1-3; actual wording and governing law control.

4 Contractual compensation and permission to amend

Two questions require separate answers: does the contract support relief, and may the authority implement the proposed amendment through the applicable public-law process? Article 72 of Directive 2014/24/EU contains several modification routes, including defined review clauses and a route for circumstances unforeseeable to a diligent authority. The latter includes conditions about the contract's nature and a 50% price-increase limit [4]. The appropriate route and all of its conditions matter; an unexpected legal event alone does not establish permission.

Utilities require particular care. Article 89 of the separately inspected Directive 2014/25/EU text uses its own modification provisions [5]. A diligence memo should identify the procurement regime and contracting-entity category before citing a numerical cap. Copying a public-procurement rule into a utility analysis can change the conclusion. The precise current statutory wording and territorial application should be confirmed for the transaction; the paper's comparison is a source-bounded explanation of why regime identification matters.

Current Cabinet Office guidance describes the Procurement Act 2023 modification grounds and explicitly excludes utilities contracts from the 50% limits discussed for unforeseen circumstances and materialisation of a known risk [6]. Its transitional guidance says procurements and contracts begun under the previous legislation continue under that legislation, including the relevant previous modification rules [7]. These official guidance sources are cited as guidance. They should not be used to infer that every existing UK utility contract has migrated to a single new regime.

The proposed approval memo separates the contractual sum, legal route, competent approver, budget authority and required notices. A draft tariff addendum might be commercially agreed before any of those approvals is complete. Until the conditions for effectiveness are satisfied, the cash model should distinguish proposed relief from an enforceable payment and from actual receipt. This permits the board to approve necessary safety measures while retaining a clear list of unresolved funding and amendment conditions.

Table 3. Separate approval enquiries

Author-proposed transaction process. Procurement sources 4-7 have regime-specific conditions.

5 Comparing efficient compliance options

The illustrative engineering choice compares two assumed solutions that deliver the same required compliance and service life. Option A requires capital 30, an outage-related CFADS loss 18 in year one and additional annual operating cost 3. Option B requires capital 40, outage loss 6 in year one and annual operating cost 1. All amounts are hypothetical USD millions. Equal technical performance is a modelling premise; no equipment, plant design or regulatory acceptance is verified.

Using a ten-year evaluation horizon and an 8% effective annual discount rate, capital is paid at time zero, outage loss at the end of year one and operating cost at each yearend. Discounted incremental cost equals capital plus discounted outage loss plus the present value of the operating annuity. Option A's higher ongoing cost and longer outage must therefore be evaluated alongside its lower initial capital. The calculation excludes residual value, tax, inflation, construction financing, replacement cost and service-quality differences. Any of those inputs could alter an actual decision.

The table and first figure report results generated from these stated inputs. The method supplies a reason for procuring a more expensive initial solution when its complete cost is lower under the agreed technical and financial assumptions. It does not make higher capital expenditure inherently efficient. Engineering evidence must establish that both options satisfy the mandatory obligation, and procurement evidence must support their costs. A proposed compensation mechanism that reimburses only the cheapest invoice could otherwise favour an option with a larger lifetime burden.

The same comparison exposes the allocation issue. The public authority and project company may use different discount rates or bear different portions of outage and operating cost. Their private rankings can diverge even when total project cost is measurable. A negotiated selection should disclose those effects and the approved evaluation basis. The example's Option A is retained for the liquidity diagnostic to demonstrate a concentrated compliance event; its use there is not a recommendation to choose it over Option B.

Table 4. Ten-year discounted compliance alternatives

Hypothetical USD millions; 8% effective annual rate; operating costs paid at each yearend. Equal technical performance is assumed, not verified.

Option B has lower discounted cost by USD 14.53 million. Its maximum additional capital at equal cost is USD 24.53 million, giving total B capital of USD 54.53 million. These figures use the separate time-zero appraisal boundary and cannot be substituted into the monthly funding schedule.

Author calculations from the expressly hypothetical ten-year options; no engineering feasibility or compensation assumed.

6 Measuring incremental cost and offsets

The proposed claim calculation begins with the compliant solution and a documented counterfactual. Capital invoices are separated from recurring operating cost and the cash consequences of an approved outage. Every amount is attached to a period and evidence source. This permits the parties to distinguish a necessary compliance item from an optional upgrade, an existing maintenance obligation or a cost caused by unrelated delay. An approved amount should remain traceable to that record after procurement and completion.

For a separate hypothetical claim bridge, begin with gross compliance expenditure 40. Deduct 6 for planned lifecycle work displaced by the retrofit,2 for an assumed grant and 1 for a supplier rebate. Net eligible capital is 31. A single capital deductible 3 gives public capital relief 28. These offsets are distinct in the example; their overlap is excluded by assumption. The cash schedule still contains the gross invoice and actual grant and rebate receipts. Deducting an offset from eligibility does not establish that its cash arrives before the contractor must pay.

The bridge should also record benefits that are measurable only later. Energy savings could reduce future operating costs, while a changed disposal method could increase them. The historical PF2 draft discusses mitigation and saved maintenance [3]. Here, the proposed practice is to measure the supported increment once and disclose the timing and uncertainty of each benefit. A speculative carbon-credit sale should not silently reduce an approved claim. Its eligibility, ownership, contract treatment and realised proceeds require their own evidence.

The principal liquidity case uses a simpler net incremental capital amount 30 and public compensation 27 after its own once-only deductible 3. The separate 40-to 28 bridge illustrates an accounting reconciliation and is never added to that case. Keeping these boundaries explicit protects replication. An analyst combining both illustrative capital amounts would create a fictional programme cost that no scenario actually assumes. The paper consequently gives each calculation a stated purpose, units and relationship to the other exhibits.

Table 5. Separate illustrative capital-claim bridge

Hypothetical USD millions. Offsets are distinct by assumption. This separate illustration is excluded from the main 30-capital liquidity case.

Author-created separate claim example; offset eligibility and collection dates remain transaction-specific.

7 Deductibles and triggers produce different amounts

A materiality provision may operate as a deductible, a threshold that activates full recovery, a sharing percentage or an aggregate cap. Its label is insufficient to determine its arithmetic. Under an assumed deductible 3, an eligible capital amount 2 receives no public payment and an amount 4 receives 1. Under an assumed trigger 3 with full recovery above it, the same amount 4 receives 4. The table displays both hypothetical rules across several amounts so that their discontinuity is visible before drafting is finalised.

Aggregation introduces further choices. A contract might combine events during a year, during the project term or only when they arise from the same instrument. If eligible costs 2 and 2 are assessed separately against a deductible 3, both payments are zero. If the two amounts form one eligible aggregate, compensation is 1. Those outcomes follow the specified examples only. The actual drafting must establish the unit of aggregation, whether favourable effects net against adverse effects and how amendments or settlement amounts affect the remaining balance.

The main case assumes a capital deductible 3 applied once to the 30 capital amount. It assumes no second deductible on the separate 21 operating and outage compensation. That treatment should be stated in the payment schedule; otherwise a reader could apply the 3 again or assume that the entire 51 qualifies without any private contribution. The resulting total public compensation 48 leaves an incremental private burden 3 before omitted financing and tax costs.

Procurement and financing should use the same threshold interpretation as the contract administration team. A cost forecast may move across a trigger after tender prices are received. A claimed amount may then decline at final audit. The recommended record preserves the estimate, approval, advance and actual-cost calculation separately. It permits a subsequent refund or balance payment to be identified without treating a provisional estimate as the final economic result.

Table 6. Deductible compared with a full-recovery trigger

Hypothetical USD millions. Trigger payment is full recovery only when eligible cost exceeds 3. Actual wording may choose other rules.

8 Defining the monthly funding case

The integrated case models one operating asset for twelve months. Baseline CFADS is 7.50 each month, already after baseline tax and lifecycle costs, giving 90 annually. Debt service is stipulated at 5 each month, giving 60 annually. Opening unrestricted cash is 12 and a separate debt-service reserve is 15. Incremental compliance capital 10 is paid in each of months one, two and three. Additional operating cost is 0.25 monthly. Outage losses reduce CFADS by 6 in each of months two, three and four. Those losses are direct CFADS reductions and receive no second revenue deduction.

The assumed contract awards capital compensation 27 after the single deductible 3 and operating/outage compensation 21. The latter is received in month twelve. The comparison changes only the capital receipt date: month one or month nine. A third adverse case assumes no compensation is received within the twelve-month horizon. Legal entitlement, public approval and actual collection are assumed for the first two paths solely for calculation; the adverse path illustrates the cash consequence when those expected receipts are absent.

Within each monthly bucket, receipts arrive before the stated payments. Cash first pays incremental operating effects and compliance capital. An uncommitted support requirement cures any shortfall at that stage. Debt service then uses remaining cash, a permitted reserve draw and additional required support if needed. After service, surplus cash restores the reserve to 15 before refunding outstanding support. No distribution, tax on compensation, funding interest, reserve interest or facility fee is included. Support refunds assume no lender, covenant or subordination restriction.

These conventions are deliberately exposed. The calculation assumes support arrives whenever needed; it does not establish an available facility or sponsor commitment. Without the required support, the shown obligations cannot all be paid. Monthly buckets also leave intramonth timing unresolved. An implementation model should replace them with invoice and payment dates, draw conditions and account restrictions. The useful output is a quantified funding request, with the assumptions requiring confirmation listed beside it.

Table 7. Main monthly case assumptions

All values hypothetical USD millions. No capital or operating/outage receipts occur in the no-compensation alternative.

9 Annual coverage and dated liquidity

Before operating and outage compensation, annual CFADS in the case is 90 less 3 less 18, or 69. Dividing by annual debt service 60 gives 1.15 x. When the full 21 operating/outage receipt is included in the expressly assumed cash-coverage numerator, annual coverage becomes 1.50 x. Capital compensation and required support are excluded from that numerator. These are annual analytical ratios. They are not reported minimum covenant ratios, and they do not establish how an actual facility defines additional capex or compensation.

Both capital-payment alternatives receive the same 48 compensation over the year. They therefore share the same annual coverage calculation and overall cash bridge. Their interim cash, reserve balances and support requirements differ because three early capital invoices and the outage occur before the late public receipt. The complete monthly tables show where an annual model loses that distinction. The figures then identify the highest required support balance and the lowest reserve balance without assigning an unsupported probability to collection.

The compensation receivable should remain outside the cash account until its receipt date. A board might have a legally approved claim while the cash still depends on budget processing or satisfaction of evidence conditions. Those circumstances require their own actual facts. For this hypothetical diagnostic, moving the capital receipt from month one to month nine is enough to expose the timing exposure. A positive annual ratio cannot fund a payment in a month whose unrestricted cash and permitted reserve are inadequate.

The support amounts shown are principal requirements under a zero-cost assumption. A lender model must add interest, fees and draw eligibility if support is financed. It must also distinguish the construction-compliance facility from the reserve account. A reserve restricted to debt service cannot be treated as unrestricted capital funding merely because it is included in the project's bank balances. The model's payment order makes that boundary explicit and permits the result to be checked against actual account controls.

Table 8. Coverage and funding consequences

Hypothetical USD millions except ratios; required support is assumed available solely to compute funded balances. Actual covenant ratios are unverified.

The delayed-capital path requires support of 4.50 in month two and 8.75 in month three, a peak 13.25. It draws 13.75 from the reserve, which reaches 1.25. Monthnine restores the reserve and refunds support under the stipulated permissions. The uncompensated path ends with 9.00 still owed to support providers. It cannot be described as independently funded.

Author calculations from the 12-month model; nonnegative balances depend on otherwise uncommitted support arriving when required.

Author calculations; reserve draw, restoration and refund rights are expressly assumed. Monthly timing omits intramonth payment order.

10 Replication of each monthly payment path

The next three schedules expose all twelve monthly states. Each begins with opening cash, operating CFADS and cash compensation. Compliance capital is paid before debt; the reserve pays only the stipulated debt-service deficit. Surplus then restores the reserve and refunds support after full restoration. Amounts shown are rounded; unrounded rows and annual conservation checks were independently recalculated.

The compensated annual bridge is 12 +90 -3 -18 +27 +21 -30 -60 =39. The uncompensated path also includes support advanced 13.25 and refunded 4.25, yielding closing cash 0 and support owed 9. Transfers between cash and reserves do not change total project funds. An undrawn compensation claim is excluded from these cash bridges. The assumed funding requirements need an actual commitment before implementation.

Table 9. Capital month 1 monthly funding

Hypothetical USD millions. Base CFADS 7.50, operating cost 0.25 and debt service 5 occur monthly; outage loss 6 occurs in months 2-4. Reserve replenishment precedes support refund.

Table 10. Capital month 9 monthly funding

Hypothetical USD millions. Base CFADS 7.50, operating cost 0.25 and debt service 5 occur monthly; outage loss 6 occurs in months 2-4. Reserve replenishment precedes support refund.

Table 11. No compensation monthly funding

Hypothetical USD millions. Base CFADS 7.50, operating cost 0.25 and debt service 5 occur monthly; outage loss 6 occurs in months 2-4. Reserve replenishment precedes support refund.

11 Periodic coverage and the required cash-flow restoration

An annual ratio can conceal a weak measurement period even when every annual receipt arrives. Under the model definition, the first quarter contains base CFADS 22.50, incremental operating cost 0.75 and outage losses 12. Cash CFADS is therefore 9.75 against debt service 15, giving 0.65 x. The second quarter has the remaining outage loss 6 and coverage 1.05 x. The fourth quarter receives all 21 operating compensation, raising its ratio to 2.85 x. These are analytical quarterly calculations using the hypothetical monthly data; they do not identify the measurement period or cure rules of an actual loan.

The timing of the operating receipt therefore affects the period in which coverage is restored. Capital compensation, reserve transfers and support remain excluded from the chosen numerator. They can fund a payment under the assumed permissions while leaving a low coverage ratio unchanged. A project team should ask whether the actual covenant uses cash, accruals, a rolling historical period or a forecast measure, and how extraordinary compensation is treated. An approval letter for relief supplies none of those terms. The underlying facility definition must be read before a calculated ratio is described as compliance.

A separate annual restoration calculation starts with uncompensated cash CFADS 69 and service 60. At a stipulated target 1.25 x, the numerator would need 75, requiring an additional 6. A 1.30 x target needs 78, requiring 9. A 1.50 x target needs 90, requiring 21. These gaps specify arithmetic amounts for the chosen annual definition. They do not establish a tariff entitlement, an available operating subsidy or a permitted covenant cure. A public contribution allocated exclusively to capital cannot simply be recategorised as operating CFADS to close the ratio.

The outage loss 18 is concentrated in the first year. Incremental operating cost 3 is assumed recurring in the separate ten-year appraisal. A relief package that addresses only the first-year annual shortfall may leave later operating impacts unresolved. Conversely, repeating the full outage allowance every year would overstate the modelled effect. An amendment should state the payment period and the cost component each receipt addresses, with actual performance evidence for any continuing adjustment. The illustrative operating compensation 21 restores the specified first-year annual numerator only.

The funding diagnostic has no minimum operating-cash buffer. A closing cash balance of zero therefore means the stated payments can be made under the support assumptions, with no further operating cushion. If an actual project requires minimum unrestricted cash, the schedule should retain that buffer before support refunds and recalculate peak funding. The current result should not be promoted as a ready-to-execute treasury plan. It identifies the additional evidence and model rules that distinguish payment sufficiency, covenant compliance and the liquidity retained for continuing operations.

Table 12. Analytical quarterly cash coverage in the delayed case

Hypothetical USD millions except ratios. Operating compensation 21 is collected in quarter 4. These are not verified covenant measurements.

Table 13. Separate annual numerator needed for assumed coverage targets

Hypothetical USD millions except ratios. The targets are assumptions, not lender terms; no actual cure or tariff right is established.

12 Delay changes compensation value and funding cost

A separately calculated timing comparison discounts the same 27 capital payment at an 8% effective annual rate. Payment at monthm has present value 27 divided by 1.08 raised to m/12. The table compares several dates and states the month one benchmark. Its value difference reflects time only; there is no assumed default probability, litigation outcome, currency movement or recoverable financing charge. A delayed nominally identical payment can therefore leave different economic value even before financing charges are added.

The contractual financing calculation requires a different basis. It should use the actual incremental balance drawn, the agreed eligible rate, the dates on which funds are outstanding and the applicable interest convention. For illustration, a separate constant bridge balance 27 outstanding for eight months costs 1.44 under an 8% simple annual rate. This balance is an assumption for that diagnostic, and it is not the support profile generated by the monthly case. Mixing its interest with the main case would overstate or misstate the funding requirement.

Whether any such charge is compensable depends on the contract and approval. A public payment schedule may include financing within a tariff adjustment, exclude it, reimburse demonstrated borrowing or offer a capital advance. The paper supplies no universal reimbursement rule. The proposed negotiation record identifies the funding source, permitted rate and evidence required for each requested component, then reconciles the approved amount to the dated project accounts.

Public affordability also changes with payment form. A lump sum, an annuity and an availability-payment adjustment have different budget profiles and collection risks. Equal present value under one selected rate does not establish identical lender acceptance or public value. The executed amendment needs a funding source and effective payment terms. Until those terms are verified, the project model should retain a sensitivity for receipt delay and partial collection, with required support shown as an unresolved requirement.

Table 14. Timing value of identical capital compensation

Separate hypothetical USD millions; 8% effective annual discounting. No collection-default probability or eligible financing charge is included.

Table 15. Separate constant-balance bridge-cost illustration

Hypothetical USD millions except rates/months. Constant 27 balance is separate from the variable support schedule. Compensation entitlement and funding availability are unverified.

Author calculations at an assumed 8% effective annual rate; no actual receivable valuation or recoverable interest conclusion.

13 Actual cost and the settlement balance

An advance based on an estimate requires a defined reconciliation when actual expenditure is known. The separate true-up example starts with an advance 27. Audited gross cost 32 is reduced by lifecycle overlap 2 and an assumed eligible grant 1, giving net eligible capital 29. Applying the once-only deductible 3 gives final entitlement 26. The advance exceeds that illustrative entitlement by 1. The calculation therefore identifies a refund 1, without assuming when it is payable or whether a contractual set-off is permitted.

A complete settlement record would explain each variance from the approved estimate. It would separate price, quantity, timing, scope and excluded betterment. The technical record should confirm which delivered items satisfied the qualifying compliance requirement. The finance record should show amounts paid, amounts accrued, available rebates and duplicate receipts. A supplier invoice is evidence of a charge; its relationship to the qualifying obligation remains a separate eligibility judgement.

Timing affects the practical settlement. A project may have paid 32 of gross invoices while a promised grant 1 remains uncollected. Reducing entitlement for the grant then exposes a liquidity assumption. The parties could agree to reconcile eligible grants only when received, provide a contingent true-up or allocate collection risk expressly. The paper recommends making that choice visible. It does not prescribe an enforceable solution without knowing the contract, approval conditions and public funding rules.

The true-up also needs a closed relationship with operating compensation. Recurring savings observed after the retrofit should be tested against the operating allowance rather than deducted indiscriminately from capital. An outage credit should use the agreed service and payment treatment. A settlement that resolves capital alone should identify any remaining operating or performance questions. The board then has a bounded record of what is final, what remains provisional and which cash movements still require funding.

Table 16. Separate actual-cost true-up

Hypothetical USD millions. No refund due date or permitted set-off is assumed; not a change to the main monthly case.

14 Evidence boundaries and applicability

The inspected official material supports the analytical distinction between contract design and public approval. The EPEC 2026 guide includes treatment of contract variations and the implications of modifications [8]. The UAE Ministry of Finance announcement describes the federal PPP law's scope and identifies exclusions [9]. That announcement establishes a scope question for federal projects; it is not a verified clause giving an emirate utility or a project elsewhere in the GCC compensation for legal change.

IFC's published 2012 Performance Standards are directed towards clients and address environmental and social risk management. Its current webpage also records an update to the Sustainability Framework [10]. A project's financing documents must establish the standards it has agreed to follow. A voluntary financing commitment, a later lender request and a binding domestic obligation can have different allocation consequences. The paper uses that distinction as a diligence question, with no assumption that a lender standard automatically creates purchaser reimbursement.

The numerical results concern a deliberately fictional asset. They provide no estimate of the prevalence of qualifying events, compensation collection, actual tariff increases or returns in a particular market. No probability weights have been invented. The model does not price legal uncertainty, public counterparty default, tax leakage or technical underperformance. Its integrated cash result is conditional on the displayed payment order, reserve permissions and availability of otherwise uncommitted support.

Those limits still permit specific work to be commissioned. Counsel can establish the baseline and eligibility; engineers can compare compliant options; the commercial team can substantiate incremental costs; treasury can test dated funding and draw terms. The recommended board decision states the accepted solution, provisional or final relief, public and lender approvals and the funding source for every payment date. Where an input is missing, the model should name it and show its consequence. That record supplies a usable basis for negotiation without presenting an incomplete claim as cash already available.

15 Follow the obligation through the contract chain

A proposed compliance programme should begin with the document that creates the obligation and the contract through which each party seeks payment or time. Consider an illustrative water project whose operator proposes additional treatment equipment following a revised water specification. The project company would need to establish whether the requirement arises from an applicable legal instrument, an amended permit, a purchaser instruction or an obligation already contained in the operating contract. That classification remains a matter for the actual documents and qualified review. Each possible route can lead to a different approval process, financial calculation and allocation of responsibility.

The next step is to trace the same event through the offtake, construction and operating agreements. The review should compare the relevant baseline dates, covered obligations, notification steps and available remedies. Suppose the operating contractor requests reimbursement immediately, while the project company's offtake claim remains subject to verification and later payment. The resulting timing gap belongs in the project cash forecast even if the substantive claims eventually match. Another possible gap concerns scope: a construction contractor may price an upgraded design that includes discretionary improvements, while the purchaser considers only the minimum qualifying compliance work. Passing a supplier invoice upstream would leave that difference unexplained.

For the illustrative project, the contract manager should prepare an event-specific reconciliation showing the requested treatment at each interface. A useful entry would identify which party buys the equipment, who accepts its performance and who bears the cost of an unsuccessful retrofit. An operating contractor's proposed outage should also be compared with the offtake performance regime. Any requested adjustment to output or availability needs its own documented basis. Relief from a supplier obligation cannot be assumed to change the purchaser's rights, and an upstream approval cannot be treated as a signed downstream variation.

The financing review should then examine the proposed response against the actual consent provisions. Additional borrowing, changed project payments, reserve use or altered security may require decisions under the financing documents. The amendment pack should identify these requirements precisely and state which remain outstanding. If a supplier needs an advance before approvals are complete, the sponsor should present a funded interim proposal with defined spending authority. Treating an expected compensation claim as immediately available cash would conceal the execution gap. The recommended approval sequence connects the purchase commitment to both a lawful compliance route and an identified source of money.

Table 17. Proposed contract-interface reconciliation

Author-proposed checklist; illustrative gaps are not reported conditions at an actual project.

16 Establish causation before selecting the compliance package

The proposed quantum analysis should reconstruct the position that would have existed without the claimed event. That counterfactual needs the asset's actual condition and existing obligations at the relevant date. In the water example, treatment equipment already due for replacement should remain visible in the original maintenance plan. A new specification could change the replacement's capacity, timing or operating cost. The claim analysis would identify those changes separately. Charging the entire new installation to the event would require evidence explaining why the original replacement expenditure no longer forms part of the comparison.

Causation also needs a technical bridge from the requirement to the selected response. The engineer should explain the measured gap in current performance, the necessary operating outcome and the options capable of achieving it. The procurement brief should use that outcome consistently across bidders. Where proposals differ in energy consumption, consumables or maintenance requirements, the financial comparison should include those differences over the proposed operating period. A cheaper purchase price could produce a different whole-life result. The recommendation should show the assumptions governing that comparison and identify costs whose timing or amount remains uncertain.

Efficient procurement can be tested through a documented comparison of feasible responses. For example, the team could assess an equipment retrofit, a revised operating configuration and a staged installation if each is technically permissible. The comparison should explain why rejected options fail the service requirement, exceed the deadline or impose unacceptable dependencies. A single-source proposal requires an explanation grounded in the available equipment, access or timing evidence. It should retain an independent price or scope challenge where practicable. Procurement efficiency is a proposed review criterion here; the extent to which it affects entitlement depends on the applicable agreement.

Delay requires the same event-level analysis. A programme should distinguish time needed for the compliance design from an existing maintenance outage, supplier delay or unrelated access constraint. The scheduler should show which activity determines the completion date and how the proposed work changes it. The cost model should then use that particular delay period, with an explanation of any overlap with lost output or additional operating expense. If the selected package also improves efficiency, the analysis should record that benefit and the proposed treatment of it. The decision record can then address an identified incremental consequence rather than an undifferentiated project overrun.

17 Define carbon, water, localisation and digital boundaries

Different compliance topics require different units of analysis. For a hypothetical carbon obligation, the starting point would be the entity and activity covered by the instrument under review. The project team should identify the measured quantity that creates the cost and the period to which it belongs. A supplier's increased price needs a separate explanation of how that price relates to the claimed obligation. Existing tariff recovery, contractual credits or other compensation should be reconciled in the same period. This structure tests a proposed claim without presuming that a carbon measure exists or applies to any particular project.

For water, the review should distinguish the incoming resource, delivered product and discharged stream. A tighter product specification could require a different response from a changed abstraction permission or discharge condition. The technical case should identify the point of measurement and the consequences for output, energy use and waste handling. If a purchaser requests quality exceeding the verified requirement, the incremental enhancement should receive its own scope and approval decision. Combining required compliance and purchaser preference in one equipment package makes the cost allocation difficult to reproduce.

A localisation assessment should similarly identify the exact obligation being claimed: a workforce condition, sourcing restriction or specified procurement outcome. The proposed counterfactual should use the sourcing plan actually available to the project at the baseline. A comparison with an unavailable supplier or an expired price would give a weak measure of incremental cost. Changes in delivery time, qualification testing and warranty support should be recorded alongside purchase price. Any improvement in local servicing or reduction in logistics exposure should also be considered where evidenced. The analysis should avoid assuming that a preference, tender commitment and binding legal requirement have identical consequences.

Digital controls introduce another boundary. A request to replace an unsupported control system, restrict remote access or validate an automated decision could arise from an existing maintenance duty, a new binding requirement, a purchaser instruction or a financing condition. The claim file should establish the actual source. For an AI-assisted monitoring tool, the proposed compliance scope should identify the decisions affected, the evidence retained and the responsible human review. For cybersecurity work, the equipment and access interfaces should be specified sufficiently to price implementation and test acceptance. Neither a vendor's product announcement nor a general technology concern establishes contractual compensation by itself.

18 Test public affordability alongside the proposed amendment

A public purchaser considering a change request needs a dated expenditure and service proposal. The project's requested economic adjustment should be translated into the purchaser's payment obligations under each proposed delivery route. An immediate contribution, a tariff adjustment and a milestone reimbursement create different cash schedules. Their comparison should disclose the discount basis, payment timing and treatment of performance deductions. A present-value comparison can inform that decision, but the approval also needs to identify which payments fit within available authority and funding. This paper assumes no particular public budgeting power or amendment permission.

The recommended affordability assessment should include the service consequence of postponement. If a retrofit must be installed during an available outage, the team should explain the implications of missing that opportunity using the technical programme. The authority can then compare an early funded intervention with later alternatives on stated assumptions. Any temporary operating arrangement should have its own technical and legal review. Continuing the original payment schedule during an unresolved claim does not establish that the proposed compliance work can be financed. The project and purchaser should identify that gap before either treats the response as executable.

The amendment should describe what the purchaser receives for the agreed adjustment. For the illustrative treatment upgrade, this would include the accepted operating specification, testing arrangements and responsibility for correcting deficient performance. The payment terms should connect to verifiable milestones or another expressly agreed measure. A requested extension of the project term needs a separate assessment of the service, revenue and residual obligations introduced by that extension. It should not enter the model as a costless funding source. The authority should receive the resulting affordability profile and the reasons for preferring that package over the alternatives reviewed.

Approval should also address the consequences of lower realised cost or a changed requirement. A proposed amendment could define a reconciliation date and the records used to calculate any adjustment. Its treatment of savings, overruns and abandoned work should be explicit. If the public contribution covers only specified costs, the project must identify how excluded costs are funded. Where the parties disagree about entitlement, an interim arrangement could preserve their stated positions while funding an agreed limited scope, subject to legal review. The signed document should distinguish that interim payment from final settlement of the wider claim.

19 Build the notice file around evidence that can be reconciled

The notice process should follow the actual agreement's requirements. A recommended initial file would identify the event, the potentially affected obligation and the evidence currently available. The contract team should confirm the recipient, service method and required timing from the governing document. An early estimate should identify its provisional status and the missing information needed to refine it. The notice should avoid presenting a contractor's untested proposal as an approved compliance cost. It can instead explain the immediate decision required, such as permission to investigate an option or undertake narrowly defined urgent work.

Subsequent submissions should retain a clear relationship to that initial file. A revised estimate needs a bridge explaining which quantities, prices or programme assumptions changed. The claim owner should maintain the original submission and the evidence supporting each revision. For example, an equipment estimate replaced by a firm bid should identify changed scope, exclusions and payment timing. A delay claim should refer to the corresponding programme update. This history allows the purchaser and independent reviewer to distinguish better information about the same event from additional work requiring a separate decision.

The recommended cost record should connect approved scope to commitments, invoices, payment evidence and accepted delivery. An invoice alone establishes neither efficient procurement nor the technical necessity of the expenditure. The reviewer should be able to trace the purchased item to the compliance design and explain its allocation where it also serves another project purpose. Provisional amounts, disputed charges and unpaid commitments should retain distinct statuses. The financial model should apply the selected cash timing consistently. Treating every approved estimate as an immediate payment would distort both liquidity requirements and any financing-cost calculation.

A true-up should close those specific differences. The parties should compare the agreed estimate with the completed scope, actual eligible payments and verified operating consequences over the agreed observation period. Equipment that fails acceptance may require retention, remediation or another response under the signed terms. A continuing operating-cost adjustment should use the agreed measurement basis and identify any later review. The final record should explain remaining uncertainty and unresolved amounts. Closing the installation workstream does not itself resolve a disputed allocation or establish the performance of the modified plant over its remaining life.

20 Resolve disputed liquidity through a decision with a funded fallback

An unresolved compensation claim should enter the liquidity analysis through a stated collection scenario. The model should distinguish the requested amount, any admitted amount and money already received. The first unpaid construction or operating obligation then becomes visible against actual available cash. A proposed bridge requires its own committed amount, draw conditions, cost and repayment route. If repayment depends on claim proceeds, the downside should include a delayed or reduced recovery. The paper assumes no automatic lender obligation to fund that gap and no automatic right to suspend service while it remains unresolved.

The recommended lender case should compare the proposed compliance programme with the project's ability to continue meeting debt and operating payments. Any reserve draw should be matched to its permitted use and replenishment requirement. A covenant breach, an unpaid liability and a forecast cash deficit should be reported separately, because they describe different conditions. If the sponsor offers support, the decision file should identify its amount, enforceable documentation and availability before the relevant payment date. An expression of willingness can support negotiations; it should remain outside committed liquidity until the required evidence exists.

Where compliance appears technically infeasible or financing remains unavailable, the project should obtain advice on the actual contractual alternatives. A termination analysis would need the relevant trigger, process, compensation basis and continuity obligations for the specific agreement. The financial comparison should account for the time required to reach that outcome and the cash needed during the intervening period. It should also identify unresolved claims and the treatment of incomplete work. Assigning a single assumed recovery percentage would conceal these dependencies. Any illustrative recovery case should therefore expose its inputs and avoid presenting them as a contractual entitlement.

The final decision memorandum should select an executable next action. It should state the compliance scope being authorised, the amount being committed, the funding available and the questions reserved for later determination. For a conditional approval, it should identify what must be satisfied before the next irreversible commitment. The fallback should specify the decision date at which unavailable funding or unresolved technical evidence requires reconsideration. This produces a practical account of what the parties can do now, what remains disputed and how the proposed response changes service, cash requirements and retained obligations.

Table 18. Decision record for the next commitment

Original recommended decision record; no completed approval or mandate is claimed.

21 Reproducibility and limitations

The monthly calculations were independently reproduced across 36 rows with zero unrounded cash-plus-reserve conservation residuals. The schedules and figures use the same inputs; there is no fitted market series or undisclosed probability. Displayed rounding can produce minor apparent differences in totals. Original paragraph development, the separated claim bridge, threshold comparison and actual-cost true-up give each exhibit a stated decision purpose.

For the separate compliance appraisal, the ten-year annuity factor at 8% is 6.710081398941442. Discounted cost equals time-zero capital plus first-year outage loss divided by 1.08 plus annual operating cost multiplied by that factor. The equal-cost additional capital for Option B equals the discounted 12 outage saving plus the present value of its 2 annual operating saving. Payment-delay value uses 27 divided by 1.08 raised to month/12. The constant-balance finance diagnostic uses simple interest and its own distinct balance assumption.

Transaction use requires actual legal advice, technical confirmation, invoice/payment dates, committed liquidity, lender permissions, procurement approvals and tax treatment. A monthly nonnegative balance with hypothetical timely support cannot certify solvency or service continuity. Collection risk, technical acceptance, default consequences, reserve restrictions, compensation taxation and funding charges remain outside the quantified model. These limitations define the next evidence required; they do not supply missing approvals.

References

1. World Bank. Guidance on PPP Contractual Provisions,2019 edition. Chapter 3, printed pp 59-74. https://ppp.worldbank.org/sites/default/files/2021-03/Guidance%20on%20PPP%20Contractual%20Provisions_2019%20edition.pdf
2. World Bank PPP Resource Center. Change of Law, checklist and sample approaches, page undated. https://ppp.worldbank.org/change-law
3. HM Treasury. Standardisation of PF2 Contracts, December 2012, Draft. Chapter 16, printed pp 119-124. Historical contractual guidance. https://www.gov.uk/government/uploads/system/uploads/attachment_data/file/221556/infrastructure_standardisation_of_contracts_051212.pdf
4. European Union. Directive 2014/24/EU, Article 72; inspected consolidation dated 1 January 2026. Consolidation is a documentation aid; authentic acts are published in the Official Journal. https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:02014L0024-20260101
5. European Union. Directive 2014/25/EU, Article 89; inspected consolidation dated 1 January 2026, printed pp 88-90. Consolidation is a documentation aid. https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=CELEX:02014L0025-20260101
6. Cabinet Office. Guidance: Contract Modifications, updated 20 July 2026. Grounds 5-7. Current official guidance cited as guidance; direct current statutory text was not recovered. https://www.gov.uk/government/publications/procurement-act-2023-guidance-documents-manage-phase/guidance-contract-modifications-html
7. Cabinet Office. Guidance: transitional and saving arrangements, updated 15 April 2026. Paragraphs 4-6. https://www.gov.uk/government/publications/procurement-act-2023-guidance-documents-plan-phase/guidance-transitional-and-saving-arrangements-html
8. EPEC, European Investment Bank. EPEC Guide to Public-Private Partnerships, published 16 April 2026. Printed pp 44-46 and 196-198. https://www.eib.org/files/publications/20250124-160426-epec-guide-to-ppp-en.pdf
9. UAE Ministry of Finance. Federal PPP law announcement, Arabic page header 23 January 2024 and body dateline 18 January 2024. Scope announcement only; no statutory compensation provision asserted. https://mof.gov.ae/ar/news/ministry-of-finance-announces-new-federal-decree-law-no-12-of-2023-regarding-public-private-partnerships/
10. International Finance Corporation.2012 Performance Standards on Environmental and Social Sustainability; current page identifies a Sustainability Framework update. https://www.ifc.org/en/insights-reports/2012/ifc-performance-standards

All public sources accessed 9 October 2026. Numerical exhibits and recommended procedures are original author-created illustrations. No actual project claim, award, legal entitlement or financing commitment is asserted.

About the Author

Chennakeshav (CK) is a corporate finance and investment banking executive with 25+ years of global experience in deal origination, structuring and execution across M&A, growth capital and corporate strategy. He has led value-creation mandates for founders, corporates and funds — bridging the boardroom view to hands-on execution and close.

His career spans Morgan Stanley, HSBC, Lloyds Banking Group, EWEC, ADQ portfolio companies and Emirates Growth Fund, across TMT, real estate, fintech, deeptech, cleantech, infrastructure and energy. He has partnered with C-suite leaders, private equity and venture funds, sovereign wealth funds and family offices to finance complex fund raises and scale-up ventures, and has led M&A due diligence, post-merger integration and business-transformation initiatives to create value.

At Matchpoint Partners he is Managing Partner, leading the firm's corporate finance, M&A and capital-raising practice. He holds an MBA from London Business School, an engineering degree from VTU and a Master of Laws (LLM, in progress) from UCL London.

An active start-up mentor, CK mentors at Techstars, DIFC FinTech Hive, Startup Grind, Founder Institute and IN5, serves as Entrepreneur Mentor in Residence (EMiR) at London Business School, and judges the Entrepreneurship World Cup.

https://www.linkedin.com/in/ckadya/ https://www.matchpoint-partners.com/team/ck-adya.html