Most banks experience an FDIC examination in two phases: the scramble before it, and the exam itself. The scramble — weeks spent reconstructing evidence from shared drives, email threads, and spreadsheets — is so routine that many compliance teams assume it is simply what preparation is. This is an anonymized account of a community bank that skipped that phase, because the records examiners asked about already existed in a live system of record.
Key Takeaways:
- The pre-exam scramble exists because most banks store compliance evidence in places built for storage, not retrieval: shared drives, inboxes, and spreadsheets
- A community bank ran a recent FDIC examination from a live system of record where obligations, controls, recurring work, and evidence were already connected
- Requests that historically took days of reconstruction were answered in minutes, with the source requirement, control, owner, history, and evidence attached
- Exam readiness built this way is a byproduct of daily execution, not a project that begins when the first-day letter arrives
What FDIC Exam Preparation Usually Looks Like
An FDIC consumer compliance examination does not begin when examiners start their review. It begins with pre-examination planning: the examiner-in-charge reviews the bank's history and risk profile, scopes the examination, and sends the bank an information request well before the review work starts. The FDIC Consumer Compliance Examination Manual describes this process, and the document request list that accompanies it is long: policies and procedures, monitoring and audit results, complaint records, training documentation, board and committee minutes, product disclosures, and more.
For most banks, receiving that list starts a reconstruction project. The current policy version is on a shared drive, probably. The complaint log is a spreadsheet last maintained by someone who left in March. The approval that closed last year's audit finding lives in an email thread, and the board reporting that proves compliance had directors' attention is scattered across meeting packets in three different folders.
The frustrating part is that the underlying work usually happened. Holds were placed, complaints were resolved, reports were delivered. What the scramble reconstructs is not the work — it is the proof, which was never captured in a way that could be retrieved on demand.
What This Community Bank Did Differently
Before its most recent examination cycle, the bank had moved compliance operations onto a single system organized around a chain: source → obligation → control → work → evidence. Each regulatory source was mapped to the specific obligations it imposes. Each obligation was tied to one or more controls. Each control generated recurring work with a named owner and a due date, and completing that work captured evidence at the moment of completion — the notice sample, the reviewer sign-off, the report that went to the committee.
Nothing in the system was assembled for the exam. The records existed because that is how the bank ran its compliance work every week. Attestations and management sign-offs lived in the same place, attached to the work they certified.
So when the examination information request arrived, preparation did not mean reconstruction. It meant deciding what to export and how examiners would receive it — records that already existed, in context, with history intact.
How Examiner Requests Were Answered From the Live System
Three request types appear in nearly every consumer compliance examination. Here is how each was answered from the live system.
"Show us your Reg CC hold notice process and support"
Funds availability requirements live in Regulation CC, 12 CFR part 229, including the disclosure requirements of § 229.16 and the exception holds of § 229.13. The traditional response to this request is a policy PDF plus a hurried sample of hold notices pulled from the core system.
The live-system response started from the obligation itself: the Reg CC entry, citing the underlying sections, linked to the bank's controls — including a recurring review of exception hold notices. From there, the response carried the control's named owner, its completion history for the review period, and the evidence attached to each completion: notice samples and reviewer sign-offs. One request, one connected thread, minutes to produce.
"Show us complaint handling for the last review period"
Complaint management draws attention in every consumer compliance exam because complaints are a leading indicator of everything else. The traditional response is a spreadsheet with gaps that get explained verbally.
In the live system, each complaint was a work item with an intake date, category, owner, resolution, and closure evidence — and the periodic complaint-trend report to the compliance committee was itself a recurring control with each cycle's report attached. Answering the request meant filtering the period and exporting the record set, resolution times and trend reporting included.
"Show us board reporting on compliance"
Examiners want to confirm the board received substantive compliance reporting on a regular cadence, not that a deck exists somewhere. Traditionally that means hunting through minutes and meeting packets.
Here, board and committee reporting was a recurring control. Each cycle carried the report delivered, the meeting date, and the acknowledgment. The history view showed the cadence had operated all year — which is the actual question behind the request.
Exam Readiness as a Byproduct of Execution
The lesson is not that this bank found a faster way to prepare. It is that preparation as a distinct activity mostly disappeared. When evidence is captured at the moment work completes, the binder assembles itself continuously: every completed task adds a page, and nothing is retroactive.
That is the difference between exam readiness as a project and exam readiness as a property of how work happens. Projects decay — a binder assembled for this exam is stale within a quarter. A live system of record does not decay, because it is the same system the team uses on Tuesday morning to route work. Our guide to compliance exam preparation for banks covers the project version; this model replaces it.
None of this changes what examiners evaluate. It changes the distance between doing the work and proving the work — and that distance, measured in days of reconstruction, is what makes examinations painful. For the standards evidence must meet, see what makes evidence examiner-ready.
How to Move Toward a Live System of Record
Getting here does not require a transformation program. It requires connecting things the bank already has: an inventory of obligations mapped to their sources, controls tied to each obligation, work made recurring with named owners, and evidence captured at completion instead of reconstructed later. This is exactly what a compliance execution platform does.
Canarie is built around that chain — source, obligation, control, work, evidence, attestation, examination request — so the records examiners ask about are the same records the team works from daily. When a request arrives, the answer is a query, not a project.
See what your next exam looks like when the evidence already exists →
Frequently Asked Questions
What does the FDIC request before a consumer compliance examination?
Before the review begins, the bank receives an information request developed during pre-examination planning, a process described in the FDIC Consumer Compliance Examination Manual. Typical items include compliance policies and procedures, monitoring and audit results, complaint records, training documentation, board and committee minutes, and product disclosures. The list is scoped to the bank's risk profile, so higher-risk areas draw deeper requests.
What is a live system of record for compliance?
A live system of record stores regulatory obligations, the controls that address them, the recurring work that operates those controls, and the evidence that the work happened as connected records, updated as part of daily operations. The defining test is simple: when an examiner asks a question, the answer is retrieved rather than reconstructed. If proving something requires assembling documents from multiple locations, the system of record is not live.
Does a live system of record improve exam outcomes?
It changes the speed, completeness, and confidence of responses — examiners receive answers with the source requirement, owner, and history attached instead of assembled artifacts. It does not manufacture compliance that never happened; a system of record proves work that was done, so its value depends on the work actually being performed. What it eliminates is the worst scenario: work that was done but cannot be demonstrated.
How long does FDIC exam preparation take without one?
Banks routinely spend weeks between the information request and the start of the examination reconstructing evidence, and the effort repeats every cycle because nothing about the scramble is durable. For teams pulling from shared drives, email, and spreadsheets, the request list is effectively a research assignment. When records are already connected, preparation shrinks to scoping decisions and exports.