How Can I Comment on My Bank's CRA Performance? The Print-and-Go Comment Desk Kit

Quick answer

Send a written comment to your bank — which must keep it in its CRA public file — and to the bank's federal regulator (the OCC, Federal Reserve, or FDIC), where examiners read it at the bank's next CRA examination. For proposed branch openings or closings, submit inside the comment window stated in the bank's public notice.

1. Gate 1: Confirm the regulator: Look up whether the bank answers to the OCC, the Federal Reserve, or the FDIC, because that agency scores the examination and reads your comment.
2. Gate 2a: Open the public file: Pull the bank's CRA public file online or at a branch and read the latest performance evaluation, the assessment areas, and the comments already on record.
3. Gate 2b: Watch the notice clock: If you are responding to a proposed branch opening or closing, submit inside the comment window stated in the bank's public notice instead of waiting for the exam.
4. Gate 3a: Map facts to the tests: Tie every observation to the CRA performance test an examiner will apply, with dates, locations, and community specifics.
5. Gate 3b: Write from the template: Fill in the matching comment letter template — general performance, branch notice, or merger window — and attach your evidence.
6. Gate 4a: Send it to both desks: Deliver one copy to the bank with a request that it enter the public file, and one to the regulator's current CRA submission contact.
7. Gate 4b: Log and follow up: Record the submission date, lane, and recipient in the tracker, then calendar the public-file check and the next public evaluation release.

Summary

A print-and-go comment desk: annotated public-file checklist, fill-in comment letter templates mapped to the CRA tests, branch comment windows, regulator routing, and a submission log.

This resource helps readers connect comment on bank CRA performance to classroom practice, standards-aware implementation, and responsible next steps for schools and sponsors.

Who This Kit Is For

Anyone can comment on a bank's Community Reinvestment Act performance, and the process runs on paper more than portals: you send a written comment to the bank, which must keep it in its CRA public file, and to the bank's federal regulator — the OCC, the Federal Reserve, or the FDIC — where examiners read it as part of the bank's next CRA examination. Proposed branch openings and closings carry their own publicized comment windows.

This kit is built for the two teams who have to run that process correctly. Bank CRA and compliance teams use it to publicize notices, log every comment that arrives, forward branch-window letters to the regulator, and keep the public file current. Administrators of community organizations, schools, and nonprofits use it to write comments with enough evidence that examiners can actually act on them.

It is deliberately procedural. If you need the background first — what the CRA is, how ratings are produced, or which activities qualify — the linked explainers and tools in the final section cover that. This kit assumes the bank exists, the community has a stake, and a letter needs to go out on time.

What Is Included

The Comment Desk includes five print-and-go pieces. Print the checklist for the file pull, keep the templates next to it, and run the tracker as your record of what left the desk and when. Each piece names its owner, its deadline source, and its follow-up step so nothing depends on memory.

• Annotated public-file lookup checklist — every file item, what to do when something is missing, and who to ask for it in writing.
• Fill-in comment letter templates — a general performance letter plus branch-notice and merger-window versions, each routing every claim to the performance test the examiner applies, from the legacy lending, investment, and service tests to the 2023-rule tests as compliance dates arrive.
• Branch comment window quick reference — how opening and closing notices work, where the deadline lives in each notice, and how to route letters to the OCC, the Federal Reserve, or the FDIC.
• Do's-and-don'ts sheet — the difference between an evidence comment an examiner can weigh and an opinion post nobody can use.
• Submission-log tracker — one row per letter: date, lane, recipient, channel, follow-up date, and the public-file check.

How To Use It: Pick Your Comment Lane First

Every comment travels one of three lanes, and the lane chooses your deadline, your recipient, and your template. Picking the lane first is the single habit that separates a letter an examiner can weigh from a letter that lands in the wrong window and quietly expires.

Start at the fork. If your concern is year-round performance, Lane 1 opens — no deadline exists, so the quality of your evidence becomes the clock. If a branch near you has posted a proposed opening or closing notice, Lane 2 opens — the deadline is printed in that notice, and missing it closes the window even if your evidence is strong. If a merger application is open for comment, Lane 3 opens — the application's comment period controls, and letters typically address both banks' CRA records. On the printed sheet the fork appears as three pick-one lane cards: circle your lane, and the card states that lane's deadline source, its recipients, and the matching template, so the lane decision is recorded at the desk before any drafting begins.

• Lane 1 — Routine performance comment: send anytime; recipients are the bank and its regulator; no deadline.
• Lane 2 — Branch opening or closing: respond inside the notice's comment window; the bank forwards the comment to the regulator.
• Lane 3 — Bank merger or acquisition: respond during the application's public comment period; the reviewing regulator's CRA staff read the record.

Checklist: The Annotated Public-File Lookup

The public file is the bank's on-the-record version of its CRA story, and banks must keep it available — online or at branches. Read it before you write: the file tells you the rating history, the assessment areas your letter should speak inside, and whether someone has already raised your issue on the record.

• Performance evaluations — note the current rating (Outstanding, Satisfactory, Needs to Improve, or Substantial Noncompliance) and the exam date, and reference both in your letter.
• Written public comments — under the legacy rule text, the file must include comments received for the current and the prior two calendar years; as the 2023 rule's provisions phase in, treat the current eCFR text as controlling and check what the file actually holds before relying on any window.
• Assessment-area maps — confirm your community sits inside the geography the bank is evaluated on; if it sits outside, say so explicitly.
• Branch information — as the 2023 rule's branch-notice provisions take effect, notices and related comments join the record; note what is present.
• Public notices — exam announcements show the evaluation rhythm; calendar a follow-up after your submission to look for the next public evaluation.
• Missing items — request anything absent in writing from the branch manager or CRA officer; the file is required to be maintained and made available on request.

Branch Windows and Where Each Letter Goes

Branch changes now carry their own public process. Under the agencies' 2023 final rule, banks publicize proposed branch openings and closings, accept public comments on them, and submit the comments they receive to their regulator; those provisions phase in with staggered compliance dates beginning in 2026, while the underlying duty to keep public comments in the CRA file applies now. Because day counts and guidance continue to evolve, treat the deadline printed in the bank's notice as the controlling date and verify the current rule text before relying on any rule of thumb.

Routing is by charter, and a misrouted letter costs weeks. The agency that examines the bank is the agency that should receive your comment, and each agency keeps current submission contacts on its CRA pages rather than in this kit — so confirm the address the week you send.

• National banks and federal savings associations answer to the Office of the Comptroller of the Currency; confirm the current CRA submission contact on the OCC's site before sending.
• State member banks answer to the Federal Reserve Bank of their district, and the same Reserve Bank receives comments on merger applications.
• State nonmember banks answer to the FDIC through its regional offices; the FDIC's CRA pages carry current contacts.
• Whatever the channel, send a copy to the bank itself and ask in the letter that it be placed in the CRA public file.

Do's, Don'ts, and the Submission Log

Examiners can use what they can verify. A comment that names dates, places, and community facts — and ties them to the performance test being applied — becomes part of the record a rating is built on; an opinion without anchors usually cannot be weighed.

The tracker closes the loop. One row per letter — date sent, lane, recipient, channel, and a follow-up date — turns a sent letter into a managed record: you can prove what was filed, check the public file for it, and show your board or the bank's examiner-facing team the full history at a glance.

• Do date and sign the letter with your organization's name, city, and a contact — verifiable authors carry weight with examiners.
• Do tie every claim to a fact: a date, an address, a branch, a product, or a service your community used or lost.
• Don't send a letter with no local evidence; generic praise or criticism gives the examiner nothing to weigh.
• Don't put a branch-notice objection in a routine letter — route it to the branch lane while the notice's comment window is open.
• Do log every submission the same day it leaves: date, lane, recipient, channel, and a follow-up date to check the public file.
• Don't expect one letter to move a rating; ratings come from the examination, and your comment becomes part of the record that examination reads.

Related Tool or Template

The Comment Desk works best alongside the rest of the CRA cluster. Run the rating logic before you write, confirm which compliance dates touch your bank, and read one real community activity dissected test by test so your letter speaks the examiner's language. If you are not certain the institution is CRA-covered at all, start with the coverage question instead. The Comment Desk is one piece of the Success CRA workflow suite: scope coverage, confirm your compliance dates, run the rating logic, then open the desk to write.

• Interactive CRA Rating Qualifier — see how the performance tests combine into a rating before you write.
• 2023 CRA Final Rule explainer — the tests, timelines, and data changes that shape what examiners can consider.
• CRA Compliance-Date Lookup — confirm which modernization dates apply to your bank.
• Qualified CRA activity anatomy — one partnership dissected test by test, a model for the evidence section of a letter.
• Coverage Gate Scoping Kit — settle whether an institution is CRA-covered before the desk opens.

Disclaimer

This kit is educational; it is not legal, compliance, financial, tax, or investment advice. How any comment, notice, or activity is treated depends on program facts, the bank's charter and regulator, and examiner review, and CRA consideration is never guaranteed by using a template. Verify current rule text, compliance dates, and agency submission contacts before relying on them, and consult qualified counsel for compliance decisions.

Next Steps

• Run the Interactive CRA Rating Qualifier
• Read the 2023 CRA Final Rule Explainer
• Check the CRA Compliance-Date Lookup
• See One CRA Activity Dissected Test by Test
• Open the CRA Coverage Gate Scoping Kit
• Open the CRA Goal-to-Action Planning Kit