New nurse retention starts with a check-in calendar, not a single survey

A new nurse who struggled in week one but stays, and one who looked fine on paper and left at month eight anyway, show up identically on a single annual engagement survey. By the time that survey goes out, both stories are already finished.

A short check-in, timed to the moments new nurses actually hit friction, catches both stories while there is still time to act on them.

This guide covers one slice of the retention picture: the first year. It is a calendar of check-ins, what to ask at each one, how to compare across cohorts, and how to close the loop so new nurses see that answering was worth their time.

Set the check-in points before drafting anything: end of orientation, 30 days, 60 days, 90 days, six months, and one year. Put these dates on the calendar for every new hire on their start date, not whenever someone remembers to send a survey. A calendar that exists before the questions do is what keeps check-ins predictable instead of random.

Role clarity, preceptor support, workload, scheduling, and belonging should appear in some form at every checkpoint from the end of orientation through one year. Repeating this core set is what lets you read a trend line for one nurse and a pattern across a cohort, instead of six disconnected snapshots. Add checkpoint-specific questions around the repeated core, not instead of it.

Ask directly whether the nurse expects to be in this role a year from now, and keep it as one clearly labeled, standalone question rather than folding it into a general satisfaction score. The answer is self-reported intent, not a prediction, so treat a drop as a reason to ask more questions, not as a confirmed departure.

Line up this year's new hires against last year's cohort at the same checkpoint, not only against their own earlier answers. A cohort that scores lower on preceptor support at 60 days than the cohort before it is telling you something a single nurse's trend line cannot.

Tell new nurses, in some form, what changed because of the last check-in before asking them to fill out the next one. A checkpoint that never references the one before it teaches people that answering is optional.

Anonymous and confidential are not the same setting, and treating them as interchangeable is one of the fastest ways to lose trust before the first check-in even lands.

See anonymous employee surveys for the distinction and how to configure it correctly, and never promise anonymity from a setting alone without explaining what it actually covers.

These categories map to the non-negotiables above. Pull from each one at every checkpoint, and adjust the specific wording as a nurse moves from orientation toward the one-year mark.

Ask about role clarity to confirm new nurses know what is expected of them, not just whether they feel generally comfortable:

Preceptor questions should stay specific to the relationship, not the unit as a whole:

Workload and scheduling questions surface friction before it turns into a transfer request or a resignation:

Belonging questions ask whether a new nurse feels like part of the team, not just whether the team is friendly:

Keep this as a single, clearly labeled item, separate from satisfaction or belonging:

Use this list to confirm a check-in program covers the fundamentals before it goes live:

A check-in calendar only works once the questions are actually built, sent, and compared across checkpoints and cohorts. Build with AI can turn a plain-language description of a checkpoint into a ready-to-send survey, so a nurse educator or unit manager does not have to start from a blank page at every stage of the first year.

SurveyMonkey's employee survey guide covers distribution, timing, and anonymity setup in more depth if this is your first structured check-in program. Start with one checkpoint, run it for one cohort, and use that first round of answers as your baseline for every cohort that follows.