The Six-Week Lag: Why Deposit Rates Trail Fed Announcements
There's a real, structural reason deposit rates take weeks to catch up to a rate decision — and knowing the shape of that lag is more useful than watching the calendar for a specific number of days.
Savers who track rate decisions closely often notice the same pattern repeatedly: a policy announcement lands, financial media covers it extensively, and then... nothing changes on their savings statement for what feels like a surprisingly long stretch. Eventually something does shift, but rarely on a predictable timeline that lines up neatly with the announcement date. The lag is real, it has structural causes, and understanding its shape is more useful than trying to pin down an exact number of days it should take.
Why there is no single, fixed lag
The honest starting point is that there is no universal, fixed number of weeks between a policy decision and a deposit rate response — the framing of a single consistent lag is a simplification. What is real is that the response is never instantaneous and is driven by each institution's own internal process for reviewing and updating its rate sheet, a process that takes real time regardless of how quickly the underlying policy signal itself became public.
The internal process behind a rate sheet update
A bank or credit union's savings and CD rates are not adjusted automatically the moment a policy decision is announced — they go through an internal review, typically involving a treasury or asset-liability management function that assesses the institution's current funding needs, its competitive position against other institutions it tracks, and its own read on where the broader rate environment is likely headed before finalizing a new rate sheet. That process, even when it moves efficiently, takes real calendar time — days at the fastest, often weeks — before a decision reaches the public-facing rate a saver actually sees.
Competitive pressure is a bigger driver than the calendar
A meaningful accelerant on this process is not the announcement itself but what competing institutions do in response to it. An online, deposit-hungry institution moving quickly to capture rate-sensitive savers creates competitive pressure on other institutions to respond in kind, sometimes faster than they otherwise would have. This means the actual pace of rate movement across the industry is partly a function of how aggressively the most competitive players choose to move, not simply a function of how much time has passed since the policy decision.
Why some institutions barely move at all
On the other end of the spectrum, institutions with less need to attract new deposits — because they already have ample funding from other sources, or because their customer base is less rate-sensitive and unlikely to leave over a modest rate gap — have limited incentive to move quickly, or sometimes to move at all on smaller decisions. This is not a flaw in the system; it is each institution rationally responding to its own funding situation, which has little to do with the policy announcement's headline size.
What this means for a saver trying to time a move
Given that the lag is real but not fixed, trying to time an account switch around a specific expected number of weeks after an announcement is a weak strategy — the better approach is checking current rates directly, periodically, rather than trying to predict when a change will land. A standing quarterly habit of comparing your account's actual current yield against a few competitive alternatives captures whatever lag has already played out, without requiring any prediction about how long the lag will run in any specific cycle.
The asymmetry that compounds the lag question
It is worth layering in the previously discussed asymmetry: institutions tend to move faster when a change favors them and slower when it does not. This means the lag itself is not symmetric — a saver watching for a rate improvement after a favorable policy shift should expect a longer, less certain wait than a borrower watching for a rate increase on a variable product after an unfavorable one. Building that asymmetry into expectations prevents the recurring frustration of watching a savings rate lag for what feels like an unreasonably long stretch while other rates in the same news cycle moved quickly.
The lag between a policy decision and a deposit rate response is real, structurally caused by each institution's internal review process and competitive positioning, and not reducible to a single predictable number of weeks. The productive response is not trying to time the lag precisely, but building a periodic, direct-comparison habit that catches the change whenever it actually lands — treating your own account's current yield, checked regularly, as the only reliable evidence of where things actually stand.
Rather than trying to predict a specific lag length, it is more useful to place your own institution somewhere on a spectrum: aggressive online institutions competing hard for deposits tend to sit at the fast end, large deposit-flush institutions with extensive branch networks tend to sit at the slow end, and most regional banks and credit unions fall somewhere in between depending on their specific funding situation at any given moment. Knowing roughly where your institution tends to sit sets more realistic expectations than assuming every bank moves on the same clock.
None of this is an argument for simply waiting patiently and trusting that your rate will eventually catch up on its own — some institutions lag not because of a temporary internal review process but because they have made a durable choice to compete less aggressively on deposit rates, in which case waiting produces nothing. The periodic direct-comparison habit is what distinguishes a temporary, process-driven lag from a permanent, strategic one — and only the comparison itself reveals which situation you are actually in.
Liked this read?
Subscribe to The Weekly Rate Floor — every Monday, the top three rates worth your time, the one to skip, and the loan window we think is closing.