Chapter 12. Preboarding and Closing the Loop

How to use this chapter

Working scenario. The candidate has accepted the offer, the team has congratulated each other, and the vacancy is nearly closed. One week before

their start date, the candidate writes to say their current employer has offered them a promotion. IT has not yet ordered access, the manageer has not prepared the first week, finalists have not been sent a status update, and rejection reasons remain blank.

Formally the offer is accepted. Systematically, hiring is not yet complete.

What actually went wrong here: the team marked the finish where the final control loop was needed.

A role is only closed when the person has started, the team is ready for launch, the remaining candidates have received a correct status, finalists have not been lost, and lessons from the vacancy have been captured.

Preboarding is the period between an accepted offer and the first working day. Closing the loop is broader: hand over

context to HR, the manager, and IT; prepare for launch; maintain contact with the candidate; close statuses in ATS;

reject the remaining candidates properly; retain strong finalists; run a retrospective; and update the rules.

If this loop is not closed, the company loses the value of the work already done.

Read this chapter as an operational checklist for the last 10–30 days of hiring. If candidates accept the offer

but do not start, begin with risks and the communication cadence. If the new hire walks into chaos, look at

context handover and launch readiness. If recruitment does not learn from closed roles, use the retrospective and data sections. If an agency closes a placement but does not manage warranty-period risk,

see the agency sections.

Remember in one phrase: hiring does not end with an accepted offer but with a reliable start and closed

commitments.

If you have this task Go to section What you will get

Understand preboarding boundaries 1 Process from accepted offer to start

Reduce post-offer non-start risk 2 Risk map and communication cadence

Divide agency / internal recruitment 3 Who is responsible for what after the offer is accepted

Set up context handover 4 Handover to manager, HR, IT, and buddy

Minimum starting point

An accepted offer is not yet a completed hire. At a minimum, the following is needed before day one.

Step What to do Deliverable

1 Appoint an owner of the pre-start period and set the day-one date Preboarding owner

1. Why an accepted offer is not the end of hiring

An accepted offer shows the candidate's intention to join. But before the first working day there is a risk period: the candidate is finishing their current role, receiving a counter-offer, discussing the move with their family, comparing alternatives, waiting for documents, and observing the speed and quality of the new company's communication. If silence follows the accepted offer, trust falls. For the company this period is also risky. The manager may think recruitment has finished, HR may expect the manager to prepare the start themselves, IT may assume the request will arrive later, and the recruiter may believe everything is now with the onboarding team. As a result, the first day becomes an improvisation and the new hire receives a signal: the process inside is worse than it appeared at interview. What counts as closing a role

2. Preboarding: process, risks, and cadence

Preboarding is the managed preparation of a new hire's start before the first day. It should not replace

onboarding. Its purpose is to maintain trust after the offer, prepare documents and infrastructure, remove uncertainty, confirm the start date, and give the person their first orientations.

Preboarding risk map

Risk How it manifests What to check Action

Counter-offer Current employer offers Counter-offer or new offer, reasons to Calm check-in, do

a promotion or new offer, new decision to leave, updated not pressure

scope confidence

3. Agency and internal recruitment: versions

of closing the loop

After the offer is accepted, the agency and the internal recruitment team face different tasks. Internal recruitment owns the start, documents, access, onboarding, and internal communication. The agency

typically does not manage the client's internal systems but can reduce post-offer non-start risk, support the candidate until the start date, help the client notice delays, and maintain the relationship after the placement

is closed.

Area Agency Internal recruitment

Candidate check-in Maintains contact until the start date, HR / recruiter runs the preboarding cadence

monitors counter-offers and

doubts

Client / manager readiness Reminds the client of launch readiness and Hiring manager responsible for the first-week plan

communication

4. Context handover without overload or breaches

Context handover is the transfer of responsibility and necessary context from the recruitment process to the manager, HR, IT, buddy, and onboarding owners. Good context handover does not forward all notes at

random. It transfers only what is needed for the start and is lawful / ethical to use: role, start date, agreed

terms, motivational drivers, expectations, support needs, risks for productivity ramp-up, and the first-week plan. Context handover pack

5. Launch readiness: first-day preparedness

Launch readiness is the verification that day one will not fall apart due to minor operational failures. For the candidate, day one confirms or destroys what the company promised during the offer process. If the role was sold as

organised and professional, yet the person arrives without access, the manager is unavailable, the laptop is not ready, and nobody knows the plan, trust collapses immediately. Launch readiness checklist

6. Post-offer non-start prevention and maintaining trust until start date

Post-offer non-start is a situation where the candidate has accepted the offer but does not start. Reasons vary: counter-offer, another offer, fear of the move, document problems, personal circumstances, poor communication, company unreadiness, and changed conditions. Some reasons cannot be controlled, but the likelihood can be reduced through honest preboarding.

7. Strong finalists and respectful closure of relationships

Closing a role does not mean that all unsuccessful finalists should disappear from view. Strong finalists

are strong candidates who were not hired for a non-critical reason. Working with them links Chapter 12 to the talent pipeline: a respectful rejection, preserving context, consent / permission for future contact, and fit-for-future-

roles tags turn a completed process into a future opportunity.

Closing process for a strong finalist

Thank you for the strong process and the time spent on final meetings. This time we selected a candidate whose experience more closely matched the current priority of the role: [brief reason]. At the same time, we valued your experience in [area], and we see potential alignment with [direction / type of role]. If you are comfortable, we will keep in touch and return only when a relevant opportunity arises; before any new conversation we will update your expectations and the relevance of your interest.

8. Role retrospective: what the closed vacancy taught us

A role retrospective is a short review of a closed vacancy after an accepted offer or a start. The aim is not to find blame but to update the system: criteria, sourcing assumptions, interview cycle, salary band, SLA, offer process, preboarding, and candidate experience. Retrospective agenda

9. Closing statuses, data, and communications

Closing the loop goes beyond the new hire. All participants in the process must receive proper closure: candidate statuses updated, rejection reasons selected, notes cleaned, privacy / consent rules checked, open tasks closed, reports made usable. Otherwise ATS becomes an archive of hanging promises. ATS clean-up checklist

10. How to measure preboarding and closing the loop

The metrics in Chapter 12 must answer the question: does the accepted offer turn into a successful start, and does the

hiring system learn after the role is closed? Counting hires is not enough. You need to look at

conversion from accepted offer to start, launch readiness, post-offer non-start rate, time to start, candidate

communication, and retrospective completion.

Metrics and formulas

Metric Formula What it shows How to use it

Start rate Started hires / accepted What proportion of accepted Check preboarding and non-

offers offers turned into starts start risks

Post-offer non-start rate Non-starts after offer / Analyse counter-offers, silence,

accepted offers Losses between acceptance and start documents

Time-to-start Start date minus accepted- Length of the preboarding period Plan the risk-management

offer date cadence

Launch readiness Completed readiness First-day readiness Manage HR / IT / manager

completion items / mandatory items tasks

First-week blocker rate Hires with critical blockers / Quality of preparation Fix access, equipment,

started hires manager plan

Strong finalist retention rate Future-fit finalists Future-fit finalists Is the warm pipeline being Improve the talent pipeline

documented / eligible finalists retained?

Loop-closing rate Closed tasks / mandatory Process completion cleanliness Monitor ATS and

closing tasks communications

Retrospective completion rate Completed retrospectives Is the system learning? Embed continuous

/ closed priority roles improvement

Misinterpretations

Poor interpretation Better interpretation

"Post-offer non-start means the candidate is unreliable" Check preliminary terms check, counter-offers, silence,

documents, and changed conditions

"Day one is HR's problem; recruitment is already done" The recruiter is responsible for context-handover quality until

responsibility is explicitly transferred

"No need for a retro; the role is closed" A closed role provides data for the next role

"Strong finalists are a nice-to-have" Finalists can reduce the cost of unfilled vacancies for

future roles

11. Using HarmonyATS as an example

Using HarmonyATS as an example, Chapter 12 treats the ATS as a facts layer: stage, candidate status, notes, source,

rejection reason, time-to-hire, candidate movement, and vacancy state. It is important not to turn the system into bureaucracy. Only fields that help retain the person, avoid corrupting analytics, and preserve

lessons are needed.

HarmonyATS element How to use it Caution

Candidate status Accepted, hired, declined, post-offer Status must reflect reality

non-start, rejected, future-fit