Keep risk challenge visible when reporting lending-pilot exceptions
A credit committee can authorise a pilot exception while the risk function continues to record a concern. Later confirmation that documentary conditions were met does not, by itself, withdraw that concern. A governance narrative needs to preserve all three conclusions.
This guide helps financial-services reporting teams examine a commercial-lending climate-screening pilot. Its original fictional case separates exception authority, oversight acknowledgement and condition validation. It reviews institutional records only: no borrower assessment, credit recommendation, loan approval or disbursement decision is made or inferred.
Fix the decision and its authority before reading the status label
The Basel Committee’s June 2022 principles call for clear climate-related responsibilities in Principle 2. Paragraph 11 explains that the principles do not prescribe a particular board structure. That is limited governance context. The authority arrangements below are invented case facts, not a required structure for banks or a determination of domestic obligations. See the Basel principles, printed pages 2–3.
Fictional Bank B starts pilot P1 on 1 July 2025. Its approved internal scope covers new commercial applications in sectors S1, S2 and S3. The year-end register contains 60 new applications, of which 12 meet that scope. Eight have completed screening records and four remain incomplete. Two of the eight completed records have been referred for further review. Completion here means the pilot’s specified fields and screening record are present; it does not settle a referral.
Assume charter A1 is valid throughout the example and expressly assigns the following powers. These assignments are stipulated, not inferred from committee names. The exercise does not assess whether A1 is appropriate for a real institution.
Delegated Credit Committee: may authorise a documented exception to P1’s evidence requirement for a named pilot record, impose conditions and amend those terms through a new minuted decision. This pilot-only authority is separate from any actual credit approval. The committee cannot attribute an endorsement to Risk Control that Risk Control did not give.
Risk Control: records its challenge and validates the documentary conditions specified by the committee. It cannot waive or rewrite those conditions. A validation note answers whether the named evidence test passed; it changes Risk Control’s earlier assessment only if the note expressly revises that assessment.
Board Risk Committee: receives the pilot status paper and requests follow-up. Under A1, acknowledging that paper neither authorises an individual pilot exception nor amends the delegated committee’s conditions. Its oversight record must be read for what it actually considered and decided.
Business team: assembles pilot files and updates the tracking sheet. It has no condition-validation or exception-amendment power in A1. Its status label is therefore a statement to check against the authorised records, even when every file has been uploaded.
Read the challenge before the conditional exception
10 December 2025, RC10: Risk Control records a location-resolution concern in referral E01. The supplied climate-screening input describes a broad region rather than the operating-site detail sought by P1. RC10 says the proxy must not be represented as a site-specific assessment. The article supplies no hazard rating or judgment about the underlying business.
12 December, DC12: the Delegated Credit Committee authorises retaining the regional proxy as a documented exception for E01’s internal pilot record, subject to C1 and C2 below. DC12 expressly retains RC10’s limitation and requires both conditions to be validated before E01 is labelled “conditions met”. It does not approve a loan. The other referral, E02, has no committee decision by year-end.
C1 requires a corrected record cross-reference so E01 points to the exact regional input and version that the committee considered. Risk Control must compare the corrected reference with DC12’s cited input. This checks document identity, not whether the input measures site-specific risk.
C2 requires the pilot record to carry DC12’s limitation text: the regional proxy does not establish a site-specific assessment. Risk Control must check that the limitation is actually present in the final record. The condition preserves the unresolved distinction rather than requiring evidence that it has disappeared.
18 December, BR18: the Board Risk Committee receives a paper describing the pilot’s progress, E01’s conditional exception and E02’s pending referral. Its minutes record receipt and a request for an updated status. They contain no decision amending DC12. Neither the paper’s delivery nor the follow-up request establishes that C1 or C2 was fulfilled.
29 December, BT29: the business team uploads a revised E01 file and marks its tracker “closed”. The file contains the corrected cross-reference but omits the required limitation paragraph. An upload receipt establishes that a file arrived; it does not establish the contents required by C2 or the authority needed to validate them.
30 December, RC30: Risk Control checks the supplied file, validates C1 and records C2 as unmet because the paragraph is absent. It leaves RC10 unchanged. Assume this is the complete authorised condition evidence at 31 December. There is no waiver, amended committee decision or later December validation hidden elsewhere in the fictional records.
Write a year-end account that survives the authority check
The reporting snapshot is the end of 31 December 2025. A reviewer preparing the narrative on 7 January 2026 has the complete December pack and the later records described below. Preserve the snapshot separately from the date the reviewer assembled the evidence.
Supported sentence: “The pilot covered 12 of 60 new commercial applications; eight screening records were complete and four remained incomplete at year-end.” Its evidence is P1’s scope and the year-end application register. These are application counts, not lending value, distinct borrowers or a measure of risk reduced.
Supported sentence: “Of two referred records, one had a conditional pilot exception authorised on 12 December; the other awaited a decision. One of the authorised exception’s two documentary conditions remained unmet at year-end.” DC12, the referral register and RC30 support that statement. The business tracker’s closed label conflicts with the authorised condition result.
Supported sentence: “The Board Risk Committee received the pilot status paper on 18 December and requested an update.” BR18 supports that event. It cannot support “the board approved both referrals” or “the board waived the remaining condition”, because neither action appears in the minutes and A1 does not give this acknowledgement that effect.
Keep the next statement separate: “Risk Control’s location-resolution concern remained on record.” RC10 and RC30 support it. The existence of an authorised conditional exception does not establish that the risk function withdrew its concern. Nor does an unmet documentary condition establish a regulatory breach or a particular loan outcome.
Update the condition result without inventing an endorsement
5 January 2026, BT05: the business team supplies a corrected E01 record containing the required limitation paragraph. On 6 January, RC06 confirms that C1 remains satisfied and validates C2 against that version. RC06 expressly states that it does not change RC10’s location-resolution concern. These are later events, not evidence that the missing paragraph was present in December.
The later update can say: “Risk Control confirmed both documentary conditions on 6 January; its earlier location-resolution concern remains recorded.” E01 can now carry “conditions met” under the invented charter and DC12, while the December snapshot continues to show C2 unmet. The record has become complete for the specified condition test without becoming a site-specific assessment.
“Risk Control cleared all climate concerns” remains unsupported on 7 January. C2 was fulfilled by recording a limitation, not by removing the underlying uncertainty. This is the decisive review: read the operative words of the validation note before turning a condition result into concurrence with the exception or confidence in the underlying analysis.
Identify which new record could change each conclusion
If someone proposes dropping C2, ask for the delegated committee’s new minuted decision and its effective scope. A new file, an oversight acknowledgement or a Risk Control validation cannot amend DC12 under A1. If the committee did amend it, describe the change as an amendment or waiver, not as evidence that the original condition was fulfilled.
If someone says the location concern was resolved, ask for a Risk Control record that expressly revises RC10 and identifies its supporting assessment. Committee permission to retain a proxy cannot supply that separate conclusion. An amended exception and a revised risk assessment could occur on different dates; retain each record and the statement it supports.
Neither later event automatically resolves E02, completes the four unfinished screening records or extends P1 to the other 48 applications. Each statement stays attached to its own decision object. Do not convert the number of available minutes or validation notes into a percentage of effective climate-risk oversight.
Hand over the three decision trails together
The packet contains A1 and P1, the year-end population, RC10, DC12 with C1 and C2, BR18, BT29, RC30, BT05 and RC06. For each narrative sentence, point to the exact record, authorising role, date and remaining limitation. Keep the business tracker discrepancy visible alongside the authorised result so a later preparer cannot inherit its closed label uncritically.
Ask a second reviewer three questions: Which record authorised the exception? Which record established condition fulfilment, and when? Which record withdrew the original challenge? Here, the first two have different answers and the third has no supporting record. That pattern is a useful result, even though the latest condition status is complete.
Use aggregate schedules and controlled institutional references for the reporting pack. Borrower identities, loan files and restricted deliberations stay with authorised custodians. The fictional codes here illustrate decision relationships; they are not a proposal to publish identifiable application records.
Use the management sign-off guide for the separate approval of the final disclosure. For a different financial-services data task, the borrower and facility records guide addresses financed-emissions request relationships. Neither task is completed by this pilot-review exercise.
To discuss a scoped reporting-evidence review, contact Nitium Advisory with a non-confidential description of the decision trail and the question that remains open.
Source and limits
Basel Committee on Banking Supervision, Principles for the effective management and supervision of climate-related financial risks, June 2022. Paragraph 11 and Principle 2, printed pages 2–3; PDF pages 6–7.
Primary source checked 14 October 2026. All institutional records, roles, conditions, dates and counts are invented. This evidence exercise does not assess a real bank, determine regulatory applicability, establish effective oversight, offer legal or credit advice, or provide independent assurance.
Comments