Investment & Execution
Before the next capital tranche: what delivery evidence matters?
A request for the next capital tranche brings a precise question: what must be established before this commitment is made? The answer depends on the agreed gate. Some gates require mobilisation; others require accepted delivery or an operating result. The evidence should establish the relevant condition and its remaining dependencies, rather than rely on an overall impression of progress.
In this perspective
Key takeaways
- Connect each evidence requirement to the particular funding gate, not to a general completion percentage.
- Distinguish expenditure, delivered outputs, acceptance and outcomes; each supports a different claim.
- Keep the decision authority, outstanding conditions and evidence limits visible together.
Begin with the commitment being requested
Identify the tranche, its purpose, the decision date and the conditions governing release. The reference point may be an approved programme mandate, a funding agreement or an authorised decision record. An early mobilisation gate need not establish benefits that can only arise later. Equally, evidence adequate for mobilisation may be insufficient for a gate requiring operational acceptance.
Follow the claim beyond the expenditure record
An invoice can support a claim that expenditure occurred. A delivery record may show that equipment arrived. Neither necessarily establishes installation, acceptance or the intended service outcome. Trace the precise claim to the record capable of supporting it, with the relevant period and boundary. Retain evidence of successful delivery, alongside exclusions, unresolved defects and obligations that continue after payment.
Hypothetical illustration: equipment delivered, acceptance unresolved
A programme requests its next tranche after receiving equipment for a new operating site. The progress pack reports the equipment as delivered. The agreed gate also calls for receiving-site acceptance, but that record is absent. Delivery is useful favourable evidence; it does not establish the separate acceptance condition.
Two explanations remain possible: acceptance has not occurred, or it occurred but the record was omitted. The receiving authority’s confirmation, relevant acceptance criteria and outstanding exceptions can distinguish them. Missing proof alone does not establish defective equipment or failed delivery. The release decision belongs to the authority designated for that commitment.
Make the remaining dependency actionable
For each unresolved condition, record the claim to verify, evidence owner, required proof and deadline before the affected commitment. If acceptance is conditional, identify what remains open and who can accept the residual obligation. A request to waive or change a gate is a separate decision for the competent authority; describing a condition as complete does not resolve it.
Preserve the basis for the next decision
The decision record should connect the evidence received to the applicable gate, including any revised scope, permitted exception and continuing obligation. A completed gate does not establish that all later phases are executable. The board, investor or other authorised decision-maker needs to distinguish what this tranche’s evidence supports from what subsequent commitments will require.
Bring this to the decision
Questions worth asking
- Which exact release condition does each document establish, and for which unit and period?
- Who can confirm acceptance, address an exception or authorise a changed gate?
- What remains unproven before this commitment, and who owns the required evidence?
Basis & limitations
This conceptual draft uses a hypothetical situation. It provides no security recommendation, funding instruction or client finding. Actual release requirements and decision rights follow the relevant mandate and governing arrangements. Missing records require clarification; they do not by themselves establish either fulfilment or failure.
Conceptual analysis · Editorial draft. No publication approval or completed independent review is represented. Framework links provide context for the reasoning; they are not external validation of the illustration.
Read about Execution Evidence