Why Your Savings Rate Lags a Rate Hike by Months, Not Days
A policy-rate hike is wholesale news. Your savings APY is a retail decision, made on the bank's own schedule and self-interest — which is why the two rarely move together.
Every rate hike produces the same two-part reaction from savers: relief that yields might finally rise, and confusion about why a personal account barely budged. The confusion is reasonable. A policy rate is a wholesale price — roughly, what banks charge each other for short-term funding — and the trip from that number to the APY posted on a retail savings account is neither immediate nor proportional. Understanding the plumbing between the two explains most of what feels arbitrary about a bank's rate behavior.
The rate you see is a decision, not a reflex
A policy-rate change does not flow automatically into deposit pricing the way a wholesale commodity price flows into a retail shelf tag. Every institution chooses, deliberately and on its own calendar, how much of that move to pass through to depositors. The decision weighs how badly the bank currently needs deposit funding against how much depositor inertia it can safely lean on. A bank sitting on ample deposits and modest loan demand has little incentive to move quickly — every basis point it doesn't pay is margin it keeps. A bank actively growing its loan book, by contrast, needs the funding and will move faster to attract it. The identical policy announcement produces different retail outcomes depending on which side of that equation an institution sits.
Why the lag runs one direction
The asymmetry is the part savers notice most: rates that were slow to rise seem to fall fast. This is not a coincidence or a conspiracy — it is the predictable result of who benefits from delay. On the way up, delay preserves margin for the bank, so the incentive is to wait, watch competitors, and move only enough to avoid losing deposits outright. On the way down, delay costs the bank margin, so the incentive flips toward moving quickly. Neither behavior is unique to any one institution; it is closer to a universal feature of how deposit pricing works, which is exactly why it is worth planning around rather than being surprised by.
Consider two hypothetical banks reacting to the identical policy move. Bank A is sitting on more deposits than it currently needs to fund its lending, so it raises its savings rate by a token amount and calls it a day — the move costs it very little in retained margin, and depositor inertia means it loses almost no balances by under-reacting. Bank B is actively growing its loan book and needs fresh deposit funding now, so it raises its rate closer to the full move, accepting a thinner spread in exchange for the funding it needs. Both banks received the same policy signal. Their responses diverge entirely based on their own funding position, not on how "fair" either response is. This is why comparing your own account's reaction to a hike against a friend's account at a different institution is often comparing apples to oranges — the policy move was identical, but the two banks it landed on were not.
Deposit beta, in practical terms
The industry shorthand for this pass-through is deposit beta — the share of a policy move that eventually reaches savers, and how quickly. A beta near one means a rate tracks policy moves closely and promptly; a beta near zero means the account barely reacts regardless of what happens upstream. Beta is not a fixed property of an account type so much as a property of the institution and its current funding posture, which is why two savings accounts with identical marketing copy can carry very different betas. It is also why a rate that looked competitive eighteen months ago can quietly become mediocre without ever being cut — the market moved and the account simply didn't follow at the same pace.
Reading the lag as a signal, not a grievance
Once you see the lag as a business decision rather than an oversight, the practical response becomes clearer. A slow-moving account after a hike is not a bug to complain about — it is information about how much competitive pressure that institution feels it's under. Comparing your own account's yield against publicly available high-yield options every few months turns an abstract complaint into a concrete data point: either your institution is keeping pace, in which case staying put is reasonable, or it isn't, in which case the lag has become a quiet tax on your balance. The check costs a few minutes and requires no login beyond your own statement and a general sense of where competitive yields tend to sit.
What actually moves the needle for you
None of this means chasing every headline rate the moment a policy meeting concludes — that kind of reflexive movement has its own costs, discussed at length elsewhere on this site. It means calibrating expectations correctly: a policy-rate hike is the beginning of a process, not an instant update, and the process runs on the bank's timetable, not the calendar's. The savers who do best are not the ones glued to policy announcements but the ones who periodically check whether their own account's beta still looks reasonable relative to the market — and who understand that the same lag working against them on the way up is, perversely, working in their favor if they've locked something in before rates started falling. Reading the lag correctly turns a source of frustration into one more data point in an otherwise unemotional decision.
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.