The committee should receive a decision package

A committee package should let an authorised decision-maker choose a bounded exposure. The central question is what can be committed now, under which conditions, with what consequence if the underlying proposition changes. A large model, document list and presentation can supply useful material without answering that question. The recommendation should state the choice, the evidence supporting it and the unresolved dependencies that retain a decision consequence. An analytical team has not finished its work merely because every discipline has submitted a report. It must connect those reports to the authority being requested.

This chapter follows the completed fictional case CR-DELAYED. Its Model Committee Chair authorises a maximum USD1.00m diligence exposure during the initial pre-service gate, for source verification, dated-cash reconciliation and recipient-term review. Implementation expenditure and financing commitment remain HOLD. This limited information-purchase mandate is separate from the project fixture's initial investment and from the conditional opening protection amount. No unprovided diligence expenditure is inserted into the project appraisal. The record states that omission instead of pretending that the fixture prices every decision cost. The named roles and deadlines below are authored conventions, not a real institution or agreement.

The investment thesis should be expressed as a causal chain. A service need supports a defined operating proposition; that proposition requires a delivery system; the system produces cash under specified rights and conditions; that cash supports obligations and the capital objective. Each link has different evidence. The committee should be able to see where a technical conclusion ends and a commercial assumption begins. A list of positive attributes conceals weak connections. A causal thesis makes the dependencies available for challenge and allows later monitoring to ask whether the original basis still holds.

The recommended structure should follow from the identified problem. If construction uncertainty governs the exposure, completion funding and conditions deserve prominence. If collection timing governs service reliability, the liquidity bridge deserves prominence. If operating rights constrain the horizon, maturity and end-state assumptions deserve prominence. A structure should not be defended simply because it resembles a familiar transaction. The package should explain the mechanism by which each material term responds to a particular risk, while showing residual exposure. That explanation prevents a long list of protections from substituting for a coherent financing judgment.

Interpret the base case through the evidence supporting its inputs. For demand, cost, contracts and debt capacity, the committee package should identify accepted facts, selected assumptions and conditional propositions, then explain the cash perimeter that connects them to present value and coverage. The calculation supplies the result of those specified inputs; the underlying evidence determines how much reliance the committee can place on it. A favourable result therefore belongs at a defined link in the decision chain. The recommendation should show which unverified input could change that result and which condition protects the institution while the input is tested.

The downside section should use mechanisms that can change the decision. Repeating a base case with arbitrary reductions can demonstrate mathematical sensitivity, but it may miss the relevant failure path. A delayed receipt, unfinished interface, unrenewed right or change in operating burden can require a different response. The package should identify what changes, what is held constant and which obligation becomes difficult. It should then connect the analytical result to an action that is operationally and institutionally available. A downside without an action owner is a description of exposure, not a control over it.

The recommendation should distinguish conditions precedent from ongoing obligations. A condition precedent prevents a commitment or use until a specified matter is accepted. An ongoing obligation governs conduct after the exposure exists. They offer different protection. A promised future study cannot resolve a fact on which the institution is relying at the moment of commitment unless the remaining exposure is intentionally bounded. The package should identify the event that closes each condition, who can accept it and whether acceptance requires fresh committee authority. Vague conditions can create an appearance of caution while leaving the original gap unresolved.

Evidence gaps should retain their importance after being assigned. A register with an owner and due date can organise work, but the committee still needs to understand the consequence if the answer is adverse or late. Some gaps affect confidence around an otherwise robust choice; others determine whether the project can operate or pay. The record should separate those cases. An unresolved matter should not become immaterial merely because it appears in a long appendix. The package can prioritise it by showing the proposition affected and the point at which exposure would become difficult to reverse.

Risk allocation should be represented as a relationship between obligations and capabilities. Naming a party in a contract or register does not establish that the party can control the cause, meet the cost or provide cash at the relevant date. The package should connect the assumed allocation to authority, resources and response options. It should also identify interfaces where several parties depend on one another. A committee can then judge whether the structure concentrates risk with a capable party, divides it sensibly or leaves an important residual with the project. Counting allocated risks alone provides little basis for that judgment.

The funding recommendation should contain a sources-to-uses reconciliation appropriate to the decision stage. A preliminary package may show a range and the work needed to refine it. A binding commitment should implement accepted scope, timing and terms in a transaction model. The committee should see the difference between committed resources, conditional resources and assumed future receipts. A total that balances through an unidentified plug does not explain who will fund the project when the plug is needed. The recommendation should make the residual requirement visible and state whether the institution is being asked to bear it.

The committee should receive the strongest competing explanation. A positive project thesis can survive a serious counterargument, but only if the analysis addresses the mechanism rather than the tone of the criticism. A competing delivery option, smaller initial scope, shorter financing horizon or balance-sheet approach may offer greater flexibility. The package should identify the circumstances in which that alternative would dominate. If the recommendation still stands, the reason should be explicit. This is especially useful when the proposal depends on a forecast far beyond the reliable evidence horizon. A committee can accept uncertainty while preserving the ability to learn and change direction.

The record should distinguish analytical confidence from the institution's willingness to bear exposure. A team can conclude that a proposition is poorly evidenced while the committee deliberately accepts a bounded speculative commitment. Conversely, a well-evidenced proposition can fall outside the institution's mandate or risk capacity. Those are different judgments and should not be merged into a single score. The package should show the state of evidence and the rationale for the chosen exposure separately. Doing so keeps later performance from rewriting what was actually known or intentionally accepted at approval.

The authority map should route each material variance to monitoring, correction, a waiver, suspension of further use or a return to committee. Set that route before the variance occurs. The accepted transaction model and documents should connect materiality to the affected mechanism and obligation, then name who can act, what evidence is needed and the response deadline. The route is useful only if it can deliver a decision while the corrective option remains available. Where the normal committee cycle is too slow, the package should identify an authorised interim response or hold exposure pending the required decision.

The package should leave an audit trail of accepted editions. Technical reports, commercial assumptions, terms and calculations can change during negotiations. A model hash alone is insufficient if the referenced scope or agreement belongs to a different version. The approval record should identify the coherent set of documents and assumptions that informed the decision. Later amendments should show which proposition changed and whether the change requires renewed authority. The purpose is not administrative perfection. It is preserving the meaning of the commitment when several teams continue developing the project after the committee has acted.

The closing recommendation should remain short enough to use. It can state the proposed exposure, accepted basis, material conditions, residual risks, competing option and return-to-committee triggers. Supporting chapters and annexes can carry the evidence. The decision-maker should not have to reconstruct the recommendation from dispersed qualifications. A package is effective when a reader can trace a material condition to the proposition it protects, and trace an adverse change to the authority that will respond. That clarity converts analytical effort into a decision system while preserving the limitations of the underlying work.

At the start of the fictional diligence interval, the Model Assurance Analyst verifies the unchanged delayed project file and the appended bridge lineage. The base and stressed requirements are not competing estimates from different assumptions left unspecified: the latter changes CFADS by the declared fixed factor while preserving service. The analyst records both and recommends the stressed amount for the Chair's selected exposure policy. This is a completed arithmetic finding. It is not a completed source-capacity finding, because the case deliberately supplies no funding offer, bank access record or account-use agreement.

At the evidence gate D minus 10 assumed business days, the Protection Review Lead has no accepted source and access evidence, and the Payment Verification Officer has no dated collection/payment reconciliation. The Finance Appraisal Lead also has no agreed carrying cost or loss-bearer record. The Chair therefore retains HOLD and terminates the limited mandate at its cap or gate, whichever arrives first. The verified annual balance is retained for future comparison, but it supplies no authority to commit implementation capital. The record is completed because it identifies the unresolved objects, owners and resulting action, rather than claiming that an unanswered worksheet has satisfied diligence.

The reprofile branch does not automatically replace failed protection. The Model Assurance Analyst has reproduced its improved coverage and unchanged positive stressed project value. The Payment Verification Officer still lacks recipient acceptance and a complete financing-price comparison. The Chair records TERMS HELD for that branch as well. If a recipient refuses the proposed later payments, the branch stops. If terms are later accepted, it returns for a new bounded decision with an updated date and exposure perimeter; it does not inherit approval from the exhausted diligence mandate. This explicit hand-off prevents an attractive computed ratio from authorising a materially different obligation calendar.

The adverse walk-through is intentionally unambiguous. Suppose the source has only the original base opening amount available under the fixed stress. The auxiliary calculation records unpaid early service. Suppose instead the larger conditional amount is nominally offered but usable cash arrives after the obligation. The annual model cannot resolve that date failure. In both cases implementation remains held, for different reasons. The first has a quantified annual insufficiency; the second has unresolved temporal availability. The record preserves that distinction because their cures and evidence owners differ. Neither later replenishment nor a positive project NPV pays an earlier unfulfilled obligation.