FDIC FIL-76-2024 is a disaster-response guidance letter, not a new substantive rule. That distinction matters for banks, because the page should help a compliance, lending, and operations team understand how to respond to a real event without overstating what the FDIC has done. On October 18, 2024, the FDIC issued the guidance to help financial institutions respond to flooding in Alaska. The affected area identified by the FDIC is Juneau Borough, and the underlying flood event occurred from August 5, 2024 through August 6, 2024. FEMA later declared a federal disaster for selected areas on October 16, 2024.

This page is built for practical use by banks, not for a generic disaster overview and not for a borrower claims discussion. The useful question is: what should an institution actually do once the flood affects borrowers, branches, records, collateral, and deadlines? FIL-76-2024 answers that question with a familiar set of disaster-relief themes: work constructively with affected customers, preserve sound banking practices, document relief decisions, and keep the institution organized enough to explain its response later if an examiner or auditor asks.

What FIL-76-2024 Does in Practice

The FDIC states that it recognizes the serious impact of flooding on customers and operations in the affected area and will provide regulatory assistance to institutions subject to its supervision. For banks, that means the notice is a supervisory signal. It is permission to be practical, but it is not permission to be loose. Banks can extend repayment terms, restructure existing loans, or ease terms for new loans when those steps remain consistent with sound banking practices. The guidance also notes that the FDIC will consider relief from certain filing and publishing requirements and that disaster-related community development activity may receive favorable Community Reinvestment Act consideration.

That is the core operating model. Help the market recover, keep the file disciplined, and do not treat the event like an ordinary workout. A bank that uses the guidance well will be able to show why a modification was reasonable, why a filing was delayed, why a temporary branch arrangement was necessary, and how those decisions were tied to the actual flood conditions in Juneau Borough.

Start With Crisis Readiness, Even After the Event

Even when the disaster has already happened, the first useful step is to create a short crisis-readiness file for the event. That file should identify who owns the response, who is authorized to approve accommodations, how customers will be contacted, and where supporting documentation will live. If the bank still has impacted borrowers, this is the point at which operations, lending, compliance, facilities, and branch leadership should be looking at the same information instead of working from separate assumptions.

A simple response file can prevent avoidable drift. It should capture the date the flood began affecting operations, the FEMA declaration date, the date the FDIC guidance was issued, and the affected geography. It should also record the bank’s internal triggers for accommodations, such as payment deferrals, collateral inspections, temporary branch notices, and any expectation that a filing or publication may be delayed. This is not bureaucratic excess. It is what allows the bank to explain later why it acted when it did.

Make the First Triage Pass Operational

The bank should separate the response into a few practical buckets. One bucket is borrowers, another is collateral, another is facilities and customer access, and a fourth is records and reporting. Each bucket needs a person who can answer a basic question without escalating every decision: what is affected, what is the immediate risk, and what needs to happen next?

For borrowers, the key issue is whether the flood disrupted income, damaged property, or interrupted access to documents and contractors. For collateral, the issue is whether the bank still has a reliable view of condition, insurance, and repair timing. For facilities, the issue is whether a branch, kiosk, or temporary location needs updated notices or alternative operating procedures. For records and reporting, the issue is whether the institution can keep its regulatory file current while the recovery work is still underway.

This triage step is where many disaster files become messy. If the bank mixes borrower hardship, collateral repair, branch continuity, and reporting issues into one informal conversation, the result is a weak record. A cleaner approach is to create a separate log for each issue and then tie them together with dates and approvals.

Borrower Relief Should Stay Tied to the Flood Event

FIL-76-2024 encourages banks to work constructively with borrowers experiencing difficulties beyond their control because of flood damage. That means the accommodation should be linked to the event itself, not to a vague hardship label that could apply anywhere. The bank should be able to point to the flood damage, the impacted property or income stream, and the reason the relief was needed.

For a commercial borrower, that may mean a short-term extension while repair work is underway, a payment adjustment during tenant disruption, or a revised maturity schedule that matches contractor milestones. For a consumer borrower, it may mean temporary payment relief while a home is repaired, insurance proceeds are processed, or displacement is resolved. In both cases, the file should show the timing, the customer statement, the internal approval, and the expected review date.

The important compliance point is that the bank should not use the disaster as a reason to stop underwriting discipline. The FDIC’s guidance supports prudence, not shortcuts. If a loan is modified, the bank should still know whether the change is temporary, whether the borrower is likely to stabilize, and whether the accommodation remains consistent with sound banking practices.

Collateral, Insurance, and Documentation

Because this page is meant for bank operations, the documentation standard matters more than a generic disaster explainer. Banks should collect enough information to support the decision later, but not so much that the process becomes a bottleneck. A good file usually includes photos of the damage, repair estimates, insurance correspondence, borrower statements, contractor timelines, and any internal memo explaining the accommodation.

That does not mean the bank is adjudicating a consumer insurance claim. It means the bank is protecting its own credit file and making sure the accommodation decision has a factual basis. If collateral was damaged, if insurance proceeds are still pending, or if the repair timeline has shifted, those facts should be logged. The same is true if the bank needs to reassess its position after the immediate response period ends.

Where possible, the file should make clear who reviewed the information and when. A dated note from lending, a branch operations note, and a compliance review are often enough to show that the institution did not improvise its response without controls.

Branch Continuity and Customer Access

Branch continuity is one of the most visible parts of disaster response. If an office is inaccessible, if a temporary location is being used, or if a branch schedule changes because of the flood, customers need a simple answer quickly. The bank should confirm the hours, the location, the contact channels, and the timeline for any temporary arrangement. A good public notice is short, dated, and easy to update.

The same discipline should extend to the call center, website, and branch staff scripts. Customers should hear the same message no matter which channel they use. If the branch says one thing and the website says another, the bank has created confusion that will waste time and can undermine confidence in the response. In a disaster context, consistency matters as much as speed.

When temporary facilities are involved, the bank should also confirm whether notice or publication issues are implicated. The FDIC’s guidance recognizes that flooding can disrupt those requirements, but the bank still needs to track what changed, when it changed, and how long the exception is expected to last. That prevents a temporary accommodation from turning into a forgotten operational gap.

Compliance Interpretation: Relief With Guardrails

The cleanest way to think about FIL-76-2024 is as relief with guardrails. The FDIC is telling supervised institutions that it will take the disaster context into account, but the institution still has to act like a bank. That means the response should be reasonable, documented, and tied to the affected area. It also means the bank should not stretch the guidance into a broader policy statement that the FDIC never made.

In practical terms, the institution should avoid three mistakes. First, it should not assume the guidance eliminates all examiner scrutiny. Second, it should not apply flood relief outside the declared area. Third, it should not let temporary accommodations outlive their purpose without a second review. Disaster response is supposed to help the institution stabilize, not bury the file in a permanent exception bucket.

If the bank is unsure whether a proposed accommodation is still within the guidance, the safer approach is to document the factual basis and escalate internally before the decision is finalized. That is especially true if the change affects a larger commercial relationship, a significant exposure, or a branch operation that will last beyond the short recovery period.

Exam Readiness Means You Can Reconstruct the Response

Exam readiness in a disaster file is really reconstruction readiness. If someone asked six months later why the bank granted a deferral, relocated a customer notice, or delayed a filing, could the institution rebuild the story from the file? That is the standard to aim for. The answer should not depend on memory or a thread of emails that only one employee kept.

At minimum, the bank should be able to show the event date, the geographic scope, the type of relief offered, the dates of any internal approvals, and the expected re-evaluation date. If the bank received any board or committee briefing, that should be noted. If a filing or publication was delayed, the reason should be stated plainly. If the bank used temporary facilities, the timeline should be documented. That level of clarity is usually enough to keep a disaster file from becoming an exam problem.

It also helps to keep one person responsible for the master log. Disaster work often spans departments, and without a single coordinator the file tends to fragment. A master log does not have to be complicated. It just has to answer who did what, when, and why.

What Should Be in the Response Log

  • The flood timeline and the FDIC guidance date.
  • The affected geography and which customers or locations fall inside it.
  • The borrowers, facilities, and processes that were disrupted.
  • The accommodations that were granted and the approval dates.
  • The documents collected to support the decision.
  • The next review date for each active exception or modified loan.
  • Any reporting, publication, or branch-notice issue that needs follow-up.

How This Differs From Claims-Heavy Disaster Content

This page should not read like a consumer insurance article. The bank audience needs something different. A claims-focused page usually asks who is filing what and how the loss is being reimbursed. This page asks how the institution should manage credit, operations, notices, records, and examiner expectations while a disaster is still affecting the market. That difference is important because it keeps the article aligned with the actual FDIC letter and away from duplicate disaster-copy that can blur the page’s purpose.

Keeping the framing narrow also makes the page more useful. A bank team does not need a broad emotional summary of the flood. It needs a workable checklist, a way to support accommodations, and a record that can survive review. The more the page stays on that operational track, the better it serves the institution.

Practical Checklist for Bank Teams

If the institution is still working through the impact of FIL-76-2024, the next actions should be simple and concrete. Confirm the impacted population. Capture the dates. Decide which accommodations are temporary. Review any filing or publication issues. Check the branch continuity plan. Reconcile the response log against the actual customer activity. Then set the next review date so the file does not go stale.

That approach gives management a clean way to show that it took the FDIC guidance seriously without treating the letter like a blanket waiver. It also reduces the chance that a well-intended accommodation turns into a control weakness later. Disaster relief should be helpful, but it should still be controlled.

Handled that way, FIL-76-2024 is a useful playbook for the exact kind of institutional discipline banks need after a flood. It supports customer service, preserves the institution’s records, and keeps the response inside a sound banking framework.

My Law Tampa
Ready to speak with intake?

Share your details and we’ll follow up shortly.

Request Consultation

Frequently Asked Questions

What area does FIL-76-2024 cover?

The FDIC identified Juneau Borough in Alaska as the affected area for this flood guidance.

Does the guidance change the law?

No. It is supervisory relief and guidance context. Banks should treat it as an operational and compliance framework, not as a new statute or a blanket waiver.

Can a bank still use sound banking judgment?

Yes. That is the point of the letter. The FDIC expects institutions to work constructively with affected borrowers while staying within safe-and-sound practices.

Does the guidance help with filing and publishing issues?

It does. The FDIC says it will consider regulatory relief from certain filing and publishing requirements, but institutions should still document the issue and keep management informed.

Is this a claims or insurance page?

No. This page is designed for bank operations, documentation, branch continuity, and exam readiness.

Related Legal Resources

Leave a Reply