Published October 27, 2026.
Why the first 90 days need fixed dates
Early attrition is rarely a single dramatic event. It accumulates from a missing login, a schedule that never matched the interview, and a manager who kept postponing the first real conversation. Fixed check-in dates force those small failures into view while they are still cheap to correct.
Put the dates on the offer-to-start checklist rather than in a manager's memory: day 7, day 30, day 60, and day 90. Each date gets a named owner, a 15 to 20 minute slot, and a record in the onboarding system. If the date slips, the system shows the slip instead of silently dropping the conversation.
Assign one owner and one backup
The hiring manager owns the day 30, 60, and 90 conversations. The onboarding coordinator or a peer buddy can own day 7, because the first week is mostly logistics. Name a backup for each date so vacation and shift coverage do not erase the cadence.
Write the ownership on the new hire's first-week schedule. Employees should know who is meeting them, what the meeting is for, and that the meeting is not a performance rating. A short calendar invitation with the purpose in the title prevents the check-in from being mistaken for a disciplinary step.
Day 7: confirm the basics worked
The day 7 call covers six practical items: system access, equipment, assigned buddy, schedule accuracy, first real task, and pay and benefits enrollment. Ask open questions such as what took longer than expected and what is still missing. Record each answer as resolved, open, or not applicable.
Most first-week exits trace back to one of those items remaining broken while the employee was told to be patient. Escalate an unresolved access or pay issue the same day. An open equipment ticket that has no owner and no date is a retention risk, not an administrative detail.
Day 30: test role fit against real tasks
By day 30 the employee has done enough work to compare the job with the posting. Ask which tasks matched expectations, which did not, and which parts of the role are still unclear. Bring the actual job description and the first-month task list so the conversation references specific work.
The manager records one adjustment that can be made in the next 30 days and one question that needs a decision from someone else. Send the employee a two-line summary after the meeting. That summary is evidence that the conversation produced something other than goodwill.
Day 60: find the friction that predicts exit
At day 60, shift from orientation to friction. Ask about schedule stability, workload spikes, unresolved questions from day 30, and whether the employee knows how their work is judged. These are the conditions that show up in exit interviews months later.
Use a simple red, amber, green mark for each condition and a reason code for amber and red. Red means the employee described a problem that already affects attendance or engagement; amber means a known problem without a current effect. The manager owns the next action and the date.
Day 90: decide, document, and hand off
The day 90 meeting closes the structured onboarding period. Confirm that the employee has the tools, the role clarity, and the relationships needed to work independently. Ask what the organization should keep doing and what it should stop doing for the next new hire.
Record a decision: continue with the standard manager cadence, extend structured support for 30 days, or escalate a specific fit concern. Extending support is not a failure label. What matters is that the decision is written, dated, and visible to the next reviewer.
Keep the cadence during peak season
Peak season is when check-ins disappear first. Protect the cadence by shortening the meeting rather than canceling it, and by moving ownership to the named backup for the week. A ten-minute call with three questions is better than a skipped month.
Review completion weekly with two numbers: check-ins completed on time and open actions past their date. Post the counts by team without ranking individuals. When a team misses two weeks in a row, the operations lead should examine the schedule rather than send a reminder email.