What Should a Small Bank Do First for the New CRA Reporting Timelines? The Four-Quarter Countdown, Tile by Tile
One model community bank's four-quarter countdown to its first post-2023 CRA reporting date — gap assessment, data mapping, dry run, and clean first submission.
banks
Quick answer
A small bank's first concrete move is a field-level gap assessment: an itemized comparison of its existing loan, investment, and grant records against the data fields the 2023 CRA final rule requires, run as soon as its reporting date is confirmed — because data mapping, the platform decision, and the dry-run filing all inherit their quality from that first inventory. The four-quarter replay below shows one model community bank running exactly that sequence to a clean first submission.
Confirm your date: Pull the reporting schedule that applies to your asset tier from your regulator's CRA pages and mark the first collection quarter and first submission deadline on a shared compliance calendar.
Run the gap assessment: Inventory every loan, investment, and grant record type against the required-field list in the final rule and sign off a one-page field inventory.
Map each field to a system: Trace every required field to its source system or flag it as manual, recording a coverage percentage your team can re-test each month.
Price build versus platform: Score both reporting routes on a weighted scorecard — field-map coverage, validation handling, format fit, audit trail, and total cost — before signing anything.
Remediate at the source: Add edit rules in the two or three upstream systems that produce most bad values, so errors stop re-entering the reporting extract.
Rehearse a full dry run: Produce a complete practice submission, let validation reject what it will, and reconcile accepted records back to core-system totals.
Lock the cadence: Convert the one-time project into a standing quarterly rhythm with a named owner per field and a calendar of collection, reconciliation, and submission dates.
Explore the eight-beat learning path lab and scenario practice prompts below.
Full written guide, sources, and FAQs
Summary
A small bank's first CRA reporting task is a field-level gap assessment. Replay the full four-quarter countdown — mapping, platform decision, dry run, submission — as one model community bank's tiles arm and clear, quarter by quarter.
This resource helps readers connect small bank CRA reporting timeline preparation to classroom practice, standards-aware implementation, and responsible next steps for schools and sponsors.
Quick Answer: Your First Move Is a Field-Level Gap Assessment
A small bank's first concrete move is a field-level gap assessment: an itemized comparison of the loan, investment, and grant records the bank holds today against the data fields the 2023 CRA final rule will require it to collect and report. Every later task inherits its quality from that inventory — you cannot map fields you have not listed, price a platform against unmapped data, or rehearse a filing that has no field map behind it.
Below, this replay follows Hartwell Community Bank, a model composite of a small charter crossing into CRA data reporting for the first time, through the four quarters before its first submission. Hartwell is not a real institution, and every figure in its countdown is illustrative; the companion replay on this site follows the same calendar from the missed-deadline side.
Public Context: What Changed for Small Banks Under the 2023 Rule
The 2023 CRA final rule, adopted jointly by the Federal Reserve, FDIC, and OCC and published in the Federal Register, rebuilt CRA data duties around record-level collection and reporting rather than the lighter paper files many smaller banks kept. Banks that qualify as small or intermediate small keep a lighter exam path than large institutions, but the modernized rule attaches new collection and reporting duties to some smaller charters, phasing in over several years; the rule as adopted set the earliest dates at January 1, 2026.
One caution belongs up front: parts of the rule have been challenged in litigation and the agencies have signaled reconsideration of certain provisions, so the schedule on this page is a planning frame, not a legal filing calendar. Confirm the dates that bind your charter on your regulator's CRA pages, then translate them into a working calendar with the interactive compliance-date lookup.
Record-level data: the rule shifts CRA data duties toward loan-level and activity-level records, replacing looser file-level habits many smaller charters kept.
Assessment areas: the modernized rule reworked how facility-based and digital-delivery banks define their areas; small, branch-based charters often see less change than large banks.
Phase-in schedule: collection and reporting dates step in over several years, which is why the countdown starts in the quarter the date is confirmed, not the quarter it arrives.
The Four-Quarter Countdown: Hartwell's Tiles, Quarter by Quarter
Set the countdown running — you control the pace. Advance quarter by quarter or scrub back to any tile, and watch the days-to-deadline counter fall as each tile arms at the start of its window and clears when Hartwell completes that quarter's deliverable. Four tiles, four artifacts: as each tile clears, its artifact card unlocks — the field inventory, the coverage map, the platform scorecard, the rejection log — and every tile carries a visible before-and-after state.
The sequence matters more than speed. A gap assessment produces the field list; mapping turns the list into system routes; the platform decision can only be priced against mapped data; the dry run tests the whole chain at once; and the final submission merely confirms what the rehearsal already proved. Skipping a step does not save time — it moves the cost into the rejection cycle later.
Step through the tiles below the way an examiner reads a file: each one names the artifact produced, the state before and after, and the number that proves the flip. All figures are the model composite's illustrative values — they describe Hartwell, not any real bank or industry average. And read this countdown alongside its published twin — the fallout ledger that replays the same calendar from the missed-deadline side — as two lenses on one compliance calendar.
Tile 1 — Gap assessment: the team inventories every loan, investment, and grant record type against the rule's required-field list. Tile flip: from unlisted to enumerated once the signed-off field inventory lands — the inventory opens as this tile's artifact card.
Tile 2 — Data mapping and remediation: every required field is traced to a source system or flagged as manual; Hartwell's first pass routes 41 of 48 fields into core systems and assigns the remaining 7 to manual handling. Tile flip: coverage moves from unmeasured to 85% system-mapped.
Tile 3 — Platform decision and first rehearsal: the bank prices build-versus-adopt against its own field map, chooses a reporting route, and loads a practice file; the dry run surfaces 9 rejection patterns, all traced back to two source systems. Tile flip: from undecided to rehearsed — the scorecard and rejection log open as artifact cards.
Tile 4 — Fix, rehearse, submit: remediation closes every rejection pattern, a second rehearsal clears with zero rejections, and the final submission reconciles to the core system's totals. Tile flip: from rehearsal to filed.
Standing tile — Cadence lock: the bank converts the one-time project into a quarterly collection rhythm with a named owner for every field. Tile flip: from project to routine, and the days-to-deadline counter resets toward the next collection quarter.
The Quarter 3 Decision Gate: Build the Reporting Stack or Adopt a Platform?
Quarter 3 is where most small banks feel the fork. One path extends the core system's existing report writer into a homegrown submission route; the other adopts a dedicated CRA reporting platform. Hartwell prices both options against the same five criteria and records the trade-offs on a weighted scorecard before any contract is signed.
The model bank chooses a platform, but the replay's lesson is that the scorecard — not the vendor demonstration — makes the decision defensible. Coverage is scored against Hartwell's own Quarter 2 field map, so a product cannot look ready on stage and fail in production when the real records arrive. The interactive platform-selection scorecard on this site extends these five criteria with an additional pillar, so use this scorecard as a preview of the full tool.
Field-map coverage: how many of the bank's mapped fields the route can source without manual entry.
Validation handling: how rejections surface, who clears them, and how each fix returns to the source system.
Format fit: whether outputs match the submission formats the agencies' collection systems accept.
Audit trail: who touched each record, when, and what changed.
Total cost: license or build spend plus the staff hours each quarterly close will actually consume.
The Dry Run: Where a Model Bank Finds Its Own Errors
A dry-run filing is a full rehearsal: produce a complete practice submission through the chosen route, let validation reject what it will, and reconcile every accepted record back to the core system's totals. Hartwell's first rehearsal surfaces errors that look trivial until they multiply — census tracts entered as street addresses, revenue typed as raw dollar figures instead of the required bands, and locations that do not line up with the assessment-area map.
The second pass clears because the bank fixed the source rather than the file: two upstream systems get edit rules, so bad values stop re-entering the reporting extract. That is the difference between cleaning one submission and building a reporting capability that survives the next quarter unchanged. The CRA data-error prevention kit on this site takes these same rejection families and turns them into a repeatable pre-filing checklist.
Tract coding: addresses without a verified census tract are the most common first-filing rejection in Hartwell's rehearsal.
Revenue bands: small-business and small-farm records need the rule's revenue categories, not free-form dollar amounts.
Geography: every record must land inside a defined assessment area, which turns the Quarter 1 map into a data problem, not just a planning one.
Count reconciliation: accepted record totals must tie to core-system reports before anyone signs the real filing.
Where Success Fits: Turning Reporting Readiness Into Community Impact
Reporting readiness and community impact run on the same calendar. As Hartwell locks its quarterly cadence, the same leadership table can plan the activities the data will describe — including sponsored financial education in local schools, which SuccessEdu delivers as structured, standards-aligned curriculum. Programs like these may qualify as community development services when they meet the criteria in regulators' guidance, and the sponsor materials on this site help bank teams organize the supporting documentation — without promising any exam outcome.
The rest of the CRA modernization cluster extends this countdown: the fallout replay covers the missed-date path, the ISB status kit settles eligibility questions, the large-bank data readiness kit shows what heavier reporting looks like, and the compliance-date lookup turns the schedule into dates on a wall.
Use the sponsorship calculator and planning kits to scope a school program while the data work is still in Quarter 2.
Pair every planned community activity with a documentation owner, so the activities file grows alongside the data file.
Bring teachers and district admins into the planning conversation early — school calendars move on their own cycle, not the bank's.
Limitations: What This Replay Can and Cannot Tell You
This page is a model replay, not a case history. Hartwell Community Bank is a composite assembled from public rule text and common reporting workflows; its countdown figures are illustrative and should never be read as completion rates, adoption data, or any real institution's timeline. No real deployment, exam, or regulator decision is implied.
The 2023 rule's provisions and dates have also been shaped by litigation and later agency actions, and asset-size thresholds adjust every year. Nothing here predicts how a regulator will apply the rule to a specific charter, and nothing in this report is legal or compliance advice — confirm current requirements with your primary regulator before committing a calendar.
The replay simplifies on purpose. A real bank may run these quarters in a different order, overlap platform selection with mapping, or inherit cleaner data from an existing mortgage-reporting process. Treat the four-quarter frame as a planning template to adapt, not a mandated sequence.
Sources
The public sources below anchor the factual spine of this replay — the final rule's text, the agencies' announcements, and the regulators' standing CRA pages. The composite bank, its countdown figures, and its decisions are illustrative constructions that trace to no listed source. Readers who need the governing language should start with the Federal Register document and their own regulator's CRA page.
Community Reinvestment Act Regulations — 2023 Final Rule (Federal Register)
Community Reinvestment Act — Federal Reserve Board Overview (Federal Reserve Board)
Federal Reserve Board Announces Approval of the Final CRA Rule (Federal Reserve Board)
FFIEC Community Reinvestment Act Resources (Federal Financial Institutions Examination Council)
Community Reinvestment Act — FDIC (Federal Deposit Insurance Corporation)
Common Questions
Which small banks actually need to prepare for CRA data reporting?
It depends on charter size and complexity. Banks that qualify as small keep a lighter exam path, while intermediate small banks and larger small institutions face new collection and reporting duties as the modernized rule phases in. Thresholds adjust annually, so the reliable first check is your regulator's current asset-size notice plus the ISB status and exam-path kit.
What does a CRA gap assessment actually produce?
A required-field inventory: one row for each data point the rule expects your bank to report, with a named source system, a responsible owner, and a pass-or-fail flag. It is the single artifact every later quarter in the countdown edits, extends, and re-tests.
How far ahead of the first reporting date should a small bank start?
The replay uses four quarters, which suits a bank starting from paper records or spreadsheets; teams that already produce structured loan reports may compress the plan to two. Whatever the starting point, the dry run should land at least one full quarter before the real date so there is room for rejection-and-repair cycles.
Is Hartwell Community Bank a real bank?
No. Hartwell is a model composite created for this replay so the sequence, the ledger, and the numbers could be shown concretely without implying any real institution's deployment, results, or examination outcome.
Will completing this preparation improve our CRA rating?
Clean, reconciled data removes a common source of exam friction, but no preparation sequence promises a rating outcome. Ratings depend on performance context, qualifying activities, and regulator judgment, and this report offers no regulatory, legal, or compliance advice.
Where should we confirm the dates that apply to our bank?
Start with your primary regulator's CRA pages and the final rule as published in the Federal Register, then use the interactive compliance-date lookup to turn the published schedule into a working calendar for your charter. Because the rule has been affected by litigation and later agency actions, treat regulator pages as the controlling source.
The 2023 CRA Final Rule replaced activity counts with outcome-based tests, added new data reporting duties, and set a phased compliance calendar. Here is what changes, track by track, and where financial literacy education fits.
CRA modernization deadlines depend on who regulates you, how big you are, and what kind of institution you are. Map the exact milestone calendar for your bank in under a minute.
Online-only banks draw CRA assessment areas from where they lend, not where they branch. This kit walks through the county-level trigger screen, whole-county area assembly, and the documentation file behind them.