LESSON 6 OF 6 · INTERMEDIATE
Close the loop after a no or yes
A no is information, not a challenge to overcome at all costs. Ask whether to close the conversation or reconnect later. A yes begins transition work: document conditions, owners, start requirements and support expectations. Review what was promised after onboarding. Retention depends partly on whether the real experience matches the conversation, and the recruiter should remain available to resolve gaps.
Write two follow-ups: a respectful pause and an acceptance handoff.
About 2 minutes reading + 12 minutes practice. Take longer when needed.
Apply the method
For a pause, confirm whether any future contact is welcome and record the person’s preference. For an acceptance, review the written terms, remaining conditions and transition responsibilities with the appropriate owners. Build a handoff that preserves the candidate’s priorities and specific promises. Schedule a review after the start to ask whether reality matches the conversation. Do not disappear when onboarding becomes another department’s task. At the same time, avoid taking over decisions belonging to HR, licensing or operations. Your role is to keep accountability visible and help resolve gaps, not to make promises beyond your authority.
A worked application
Fictional worked example: One LO declines because the timing would disrupt a trusted team. The recruiter offers a respectful close and follows the stated contact preference. Another accepts subject to a licensing clearance and defined support. The handoff identifies the licensing owner, the support contact and a first-week review. When a system-access issue appears, the recruiter connects the employee to the responsible owner and checks that the issue is actually resolved. The relationship remains useful after the yes without implying that recruiting alone guarantees retention.
Common mistake to avoid
A verbal yes is not the same as an unconditional start, and an accepted offer is not proof that every transition dependency is complete.
Work through the case
FICTIONAL SCENARIO
An LO declines because the move would disrupt a current team. A respectful pause protects trust. Another accepts but has unresolved technology access; the handoff must include an owner and deadline.
Make it practical
Write two follow-ups: a respectful pause and an acceptance handoff.
Compare your reasoning with a worked response
The pause respects communication preferences. The handoff lists conditions, tasks, owners and review dates without assuming licensing or access is already complete.
Takeaway
Use the method to explain your decision, identify what you still need to verify and choose an accountable next step.
Treat the response as a model for reasoning, not the only possible wording. Adapt it to the role, evidence and appropriate organizational guidance.
Connect this course to the complete process
Work through the connected case, practice the conversations and add this course’s work to your final project.