Examiner-Ready Documentation

Examiner-ready documentation is a loan file complete enough that a regulator can reconstruct the credit decision without asking anyone a question. It shows what was known at approval, what policy required, and why the loan was approved anyway where it was.

Formula

What the standard means

A loan file is examiner-ready when someone who was not in the room can open it years later and follow the decision end to end: what the borrower asked for, what the analysis showed, what the institution's credit policy required, where the deal fell short, who approved the shortfall, and on what basis.

The test is reconstruction without narration. If answering an examiner's question requires a phone call to the lender who booked the loan, the file has failed the standard, and that is true even when the underlying credit decision was sound.

What an examiner is actually testing

Examinations are not re-underwriting exercises. Regulators are testing whether the institution does what it says it does. That breaks into a few specific questions.

Was the credit analysis performed and documented at the time of approval rather than reconstructed afterward. Were the institution's own policy limits applied, and where a deal exceeded them, was the exception identified, approved at the right authority level, and tracked. Is the risk rating supported by the analysis in the file. Are the assumptions behind the cash flow traceable to source documents rather than asserted. And is the pattern across the portfolio consistent, or does the file quality drop as the deals get harder.

What a complete file contains

  • The credit memo as presented, not a later summary, with the analysis and recommendation intact.
  • Source documents behind every figure: rent roll, operating statements, borrower and guarantor financials, tax returns, appraisal, environmental report, title.
  • Policy citations connecting each tested metric to the section of the credit policy that sets the limit.
  • Exception documentation for every deviation, naming the exception, the mitigant, the approver, and the date.
  • Approval record showing the authority level used and, where applicable, the loan committee minutes.
  • Risk rating rationale tied to the institution's rating definitions.
  • Ongoing monitoring: covenant testing, annual reviews, and updated financials collected on the schedule policy requires.

Why files fail

The most common failure is not a missing document but a missing connection. The DSCR appears in the memo, and the policy minimum appears in the manual, and nothing in the file states which policy section the number was tested against. An examiner reading the file cannot tell whether the test was performed or the number was simply reported.

The second failure is the undocumented exception. A deal closes slightly outside a concentration limit, everyone in the room understood why, and nothing records it. Years later the deal looks like a policy breach that nobody caught rather than a decision the institution made deliberately.

The third is drift between the memo and the source. A rent roll is updated during diligence, the spread is corrected, and the memo still carries the earlier figure. The file now contradicts itself, and reconciling it becomes the examiner's finding rather than a rounding difference.

Why it compounds

Documentation quality is judged across the portfolio, not deal by deal. A pattern of incomplete files invites a broader review, which costs management time, can affect examination ratings, and in a stressed credit environment shapes how much benefit of the doubt an institution receives on classification. The work of building a defensible file is front-loaded; the cost of not building one arrives at the worst possible moment.

Related terms

Credit memo, policy exception, loan committee, stress testing.