Seasonal Vacancy Patterns: Planning for Predictable Nurse Turnover Cycles

The January Spike Nobody Budgeted For

The schedule looks fine in December. Then January arrives, and within three weeks four resignation letters land on the same desk — two from nurses who just cleared their retention bonus, one headed back to school, one relocating after a spouse's job change. None of it is a surprise to anyone who has run a unit for more than a year. It happens every January. It happened last January too. The problem isn't that turnover spiked — it's that nobody put it on the calendar until it was already a staffing crisis.

Seasonal nurse turnover patterns are one of the most predictable things in workforce planning, and one of the least planned for. Resignations don't distribute evenly across twelve months. They cluster around bonus payout dates, school calendars, fiscal year transitions, and a handful of other recurring triggers that repeat year after year at most facilities. This piece walks through why those cycles exist, how to find your own facility's version of them, and how to turn a known pattern into a recruiting and budget plan instead of a recurring fire drill.

Why Seasonal Nurse Turnover Patterns Exist

Three forces drive most of the clustering, and all three are structural rather than random.

The first is compensation timing. Facilities that pay retention or sign-on bonuses on an annual schedule — often at the one-year mark or at calendar year-end — effectively hand a subset of staff a natural exit window the moment the payout clears. A nurse who was going to leave anyway has little financial reason to leave before collecting the bonus, and every reason to leave shortly after.

The second is the academic calendar. A meaningful share of bedside nurses are pursuing further credentials, supporting a spouse's graduate program, or timing a household move around a child's school enrollment. Those decisions compress around semester boundaries — spring and fall starts in particular — producing resignation bumps that have nothing to do with unit conditions and everything to do with the school year.

The third is the budget and fiscal cycle. Facilities that finalize annual budgets, close out performance reviews, or set new pay bands at a specific point in the year tend to see resignations rise right after that point, especially if the new numbers disappoint. A nurse who was on the fence often waits to see the raise before deciding whether to stay.

None of this requires a published national statistic to be true — it's visible in almost any facility's own exit-date history once someone actually plots it by month instead of by quarter or by year. Industry-wide, turnover itself is already elevated enough to make timing matter: the 2026 NSI National Health Care Retention & RN Staffing Report put RN turnover at 17.6% for 2025, up from 16.4% the year before. A workforce already losing that share of its RNs annually can't afford to be caught flat-footed by the predictable third of that turnover that clusters in a few weeks each year.

Mapping Your Own Facility's Resignation Calendar

The exercise itself is simple, and it doesn't require new software to start. Pull two to three years of resignation dates — not just counts, actual dates — and plot them by month. Most nurse leaders who do this for the first time are surprised at how clean the pattern is. A unit that feels like it loses people "constantly" often turns out to lose almost nobody in June and October, and nearly everyone in January and August.

Once the monthly shape is visible, overlay it with the known triggers:

• Retention or sign-on bonus payout dates, and the one-year anniversary of major hiring waves
• Spring and fall academic semester start dates
• The facility's budget finalization and merit-increase announcement dates
• Open enrollment and benefits renewal periods, which sometimes trigger exits timed to preserve continuous coverage
• Local seasonal employers (school nursing, summer camp medicine, snowbird-market facilities) that compete for the same licensure pool at predictable times of year

A facility doesn't need every one of these triggers to matter — usually two or three explain most of the clustering. But until the dates are actually overlaid on the resignation calendar, it's easy to misattribute a January spike to "morale" when it's really a bonus-timing artifact, or to blame a unit's leadership for an August dip that's really a school-calendar effect repeating across the whole system.

A pattern you can't see on a calendar can't be planned for — it can only be reacted to.

Budgeting and Recruiting Around Predictable Cycles

Once the seasonal shape is mapped, the planning question changes from "how do we stop turnover" to "how do we make sure the predictable part of it doesn't become a crisis." That's a different and more tractable problem.

Recruiting pipeline timing. If exits reliably cluster in January and August, the recruiting pipeline needs to be building in November and June — postings live, interviews scheduled, offers extended — so replacement hires are closer to starting when the vacancies actually open, rather than beginning the search the week a resignation letter arrives. Days-open tracking makes this concrete: if a role historically takes 78 days to fill (the national RN Recruitment Difficulty Index reported in the 2026 NSI report, ranging 56–102 days by specialty), a January vacancy that isn't posted until February is already most of a quarter behind.

Budget staging. If a fiscal year-end merit cycle reliably triggers a resignation bump in the weeks after announcements, that's a known cost that belongs in the staffing budget rather than a surprise line item discovered in Q2. Facilities that build a seasonal vacancy allowance into the budget — rather than treating every post-cycle resignation as an exception — tend to handle the gap with planned overtime or a pre-arranged per diem pool instead of an expensive last-minute travel-nurse contract.

Float pool and cross-training staging. Units with well-documented seasonal exposure can pre-position float staff or cross-trained coverage in the weeks leading into a known spike, rather than scrambling to redeploy staff from elsewhere in the system after the fact.

None of this requires predicting the future with precision. It requires acknowledging that the future already has a shape, visible in the facility's own history, and building the recruiting and budget calendar around that shape instead of around the fiscal year's arbitrary boundaries.

Turning a Pattern Into a Forecast

Mapping last year's resignation dates is a good start, but it's a backward-looking exercise. The more useful version projects forward: given this unit's historical seasonal shape, current headcount, and known upcoming triggers (a bonus anniversary cohort, a semester start, a budget announcement date), how many vacancies should be expected over the next two quarters, and when?

That's the logic behind a rolling six-month vacancy forecast — weighting projected openings not just by headcount but by how each role is actually staffed (a 0.5 FTE per diem slot doesn't carry the same forecasting weight as a 1.0 FTE core position). Readers building this out for the first time may find it useful to walk through the mechanics in a companion piece on six-month vacancy forecasting and the related explanation of FTE-weighted headcount, both of which cover the arithmetic in more depth than fits here.

Days-open tracking plays a supporting role too: a facility that already knows its average time-to-fill by role and specialty can convert a seasonal vacancy forecast into a staffing-gap forecast, rather than just a resignation forecast — which is the number that actually determines whether a unit will be short-staffed on a given week.

Worth noting separately: seasonal clustering and the longer-horizon retirement wave some facilities face are different problems with different timelines, even though both show up on the same vacancy report. A unit anticipating a concentrated wave of retirement-eligible staff over the next several years should treat that as its own planning exercise — covered in more detail in our piece on the retirement cliff in nursing — rather than folding it into a month-to-month seasonal calendar.

What a Dashboard Adds — and What It Doesn't Replace

A spreadsheet plotting resignation dates by month is a legitimate and sufficient tool for a single unit or a small facility, and nothing above requires anything more sophisticated. Where a dashboard adds value is in doing that plotting automatically across every unit at once, flagging which units' seasonal patterns diverge from the facility norm, and rolling days-open and FTE-weighted vacancy data into the same forecast without manual re-entry each month.

To be direct about what that dashboard is and isn't: it tracks turnover dates, vacancy counts, and pay-band benchmarks against public BLS wage data. It holds no patient information, does not connect to an EHR, and does not touch the scheduling system. It's a workforce-analytics layer sitting next to those systems, not inside them. For facilities that want to start with the spreadsheet version of this exercise before considering anything more automated, the Nursing Vacancy & FTE Forecasting Workbook in the store walks through the same monthly-pattern and forecast logic described above in a ready-to-use format. A broader walkthrough of how the pieces — turnover tracking, wage benchmarking, retention risk scoring, vacancy forecasting — fit together is also available in the nursing workforce analytics guide.

Building the Seasonal-Planning Habit

The point of mapping seasonal nurse turnover patterns isn't to eliminate the January spike or the post-semester bump — most of those exits are personal decisions a facility has limited power to prevent. The point is to stop being surprised by something that happens every year. A recruiting pipeline that's already moving in November, a budget that already has a line item for the February gap, and a float pool that's already cross-trained before August — none of that requires predicting anything. It requires looking at a calendar that already exists.

Start with one unit's resignation dates over the last two years. Plot them by month. The pattern is probably already there, waiting to be planned around instead of reacted to.

Want the monthly breakdowns and planning triggers delivered as they're published? Join the newsletter and get workforce-planning notes like this one in your inbox.