Onboarding after the hire: the clean handoff from recruiting to day one

Many teams treat 'contract signed' as the finish line. That's an expensive mistake. Weeks often lie between the signature and day one - a silent phase where the new person hears nothing from you, while possibly receiving a counter-offer from their old employer. This is exactly where hires drop out after you invested months in the search.

Onboarding starts on the day of the offer, not on day one. The phase before is called pre-boarding and is the cheapest lever against early attrition there is: a few targeted messages and preparations keep the bond warm and make day one productive rather than chaotic.

On hire, a legally important split occurs. The application - CV, cover letter, ratings, interview notes - belongs in the recruiting system and is subject to a retention window there. The hired person's personnel file is something new: it's created in the HR system, kept for a different purpose under a different legal basis, and from then on collects contract, payroll and performance data.

The mistake to avoid: copying the entire application file unchanged into the personnel file. Interview ratings and rejected-candidate comparisons have no place in the personnel file. The clean practice is to hand over only the master data relevant to the employment from the ATS and leave the application documents in the ATS archive with their own retention window.

Pre-boarding isn't a big programme but a few deliberate touchpoints. A warm welcome message right after the offer. A short note on what happens on day one - when, where, who's the contact. Ordering hardware and access early enough so the laptop is there and the account exists on day one. And ideally a personal message from the direct team, so the new person has a face before they arrive.

A good first day has a clear plan, no idle hours, and a person explicitly responsible for guiding the new hire through the day. What matters here isn't perfection but predictability: the new person should feel they were expected.

The first 90 days decide retention. Set clear expectations early, schedule a first feedback conversation after about two weeks and a second after six to eight weeks. Asking regularly in this phase 'is it going well, are you missing anything' catches problems before they become a resignation.

The hired person's application data stays in the ATS archive under a retention logic. Equally important: the applications of the rejected competitors. They too must not sit indefinitely. A clean window - often anchored to the period for possible discrimination claims - followed by anonymisation is mandatory, not optional.

In KI BMS this retention runs per candidate as a default: you set a window, anonymisation happens automatically afterwards, and every step is in the audit log. That way the hire creates no special task - the split between application archive and new personnel file is the natural consequence of the process, not extra homework.