ai-screeningrecruitingcampus-hiring

How to Hand Over a Recruiter's Roles Mid-Drive When They Go on Leave

HireQwik September 18, 2026 10 min read

Every campus season, somebody on the team goes on leave at the worst possible moment. A wedding in the family, a medical week, a resignation that takes effect faster than anyone planned. The recruiter is gone on Thursday, their four roles are mid-drive, and around 600 candidates are somewhere between “applied” and “shortlisted.” The question on Friday morning is not whether to hand over, but how to do it without anyone falling through the gap.

Handover is one of the reasons we built a single screen that lists every job description against its owner. Before that, an admin moving four roles had to open each role, find its owner dropdown and change it one by one, which is fine for one role and error-prone for ten. This post walks through the order we recommend, what moves when you change an owner, and the one mistake that makes roles disappear from a recruiter’s view.

What actually moves when a role changes owner

It helps to be precise about this, because people tend to expect either too much or too little.

In HireQwik, ownership is attached to the job description. When an admin changes the owner, everything tied to that role shows up for the new owner, straight away:

  • Inbox. New and pending applicants for that role.
  • Interviews. Scheduled, completed and cancelled AI interviews for the role.
  • Shortlist. Resume screening runs against that job description.
  • Exports. The new owner’s Excel export now includes the role’s candidates.

What does not change is just as important. Candidates are not re-screened. Interviews already booked still happen at the booked time. Recordings, transcripts, resume evidence and tier decisions all stay exactly where they were. The candidate never knows anything changed, which is the point.

The order that avoids stranded candidates

Step 1: Find everything the recruiter owns

Open Team Management and go to the Role assignments card. It lists every job description in the workspace with its current owner. Note every role owned by the person going on leave. If two roles share a similar name, the card labels them so you can tell them apart; mixing up two near-identical roles is one of the easier ways to hand over the wrong candidates, and we have written about duplicate job description names separately.

Step 2: Decide who takes each role

Not every role has to go to the same person. A common split is to give volume roles to whoever is already running a similar drive, and give senior or sensitive roles to the TA lead. Resist the temptation to leave a role unassigned “for now.” An unassigned role is visible to every member, which in practice means nobody feels responsible for it.

Step 3: Change the owner on each role

Use the owner dropdown on the Role assignments card for each role. The change applies immediately. There is no batch job and no waiting period.

Step 4: Have the new owner check their views

Ask the new owner to open their inbox, interview list and shortlist and confirm the handed-over roles are there. This takes two minutes and catches the only real failure mode, which is assigning a role to the wrong person.

Step 5: Only then remove the old account, if they are leaving

This is the step people get backwards. If the recruiter is leaving the company, removing their account is the right thing to do, but do it last. A role still owned by a removed person is not counted as unassigned, so it drops out of every member’s view and only admins can see it. Nothing is lost, but a role that nobody’s screen shows is a role nobody works. Reassign, verify, then remove.

If the recruiter is only on leave and coming back, there is nothing to remove. Hand the roles back when they return using the same card.

A worked example: four roles, three people, one Friday

Here is how the Friday-morning handover might look for a team in the middle of May. The numbers are illustrative, but the shape is common.

The recruiter going on leave owns four roles:

RoleStage of the driveCandidates in flight
Graduate trainee, Pune campusInterviews running dailyAbout 320
Graduate trainee, Hyderabad campusApplicants still arrivingAbout 180
Customer support associateShortlist being reviewedAbout 70
Senior data analystTwo finalists with hiring managerAbout 30

The TA lead does not hand all four to one person. The Pune and Hyderabad campus roles go to the recruiter already running the Chennai campus drive, because the rubric, the knockout questions and the rhythm of a campus week are the same. The support role goes to the recruiter who hired for support last quarter and already knows the hiring manager. The senior analyst role, which is about relationships more than volume, goes to the TA lead.

That is three changes on the Role assignments card and one short message to each person. By 10 a.m. the Chennai recruiter’s interview list shows three campuses instead of one, the support recruiter has a shortlist to review, and the TA lead has two finalists to chase. The roughly 600 candidates involved see nothing different. The Pune interviews booked for that afternoon run on schedule, and applicants still arriving for Hyderabad land in the new owner’s inbox automatically.

Notice what the example avoids. Nobody was promoted to admin to “see everything for a while,” no role was left unassigned so that “whoever is free can pick it up,” and nothing was re-screened.

Read the role’s settings before the next batch

Because knockouts, the scoring rubric and any auto-reject or auto-advance settings belong to the role rather than the person, the new owner inherits all of them. This is usually what you want: the drive keeps running on the same rules, and candidates are treated consistently before and after the handover.

It also means the new owner is now responsible for decisions they did not make. Before the next batch of applicants lands, they should spend ten minutes on three things:

  1. Knockout questions. What ends a call early, and would they agree with it? A knockout that made sense to the previous owner can be wrong for a new location or shift. Our post on knockout rejections covers what to look for.
  2. The scoring rubric. Especially for freshers, where calibration drifts. See calibrating a rubric for freshers.
  3. Automation. If auto-reject or auto-advance is switched on, the new owner should decide consciously to keep it, not discover it later.

What the new owner should do in the first hour

Beyond the settings, a short first-hour routine keeps the handover invisible to candidates:

  • Sort the interview list by tier and review any Strong Go or Go candidates waiting for a decision. These are the people most likely to accept another offer while nobody is looking.
  • Look at upcoming bookings for the next two days so there are no surprises about volume.
  • Check the inbox for approvals. Applicants waiting for approval before they get a booking link cannot move forward until someone acts.
  • Send hiring managers a one-line note that you now own the role. They will otherwise keep emailing the person on leave.
  • Skim the last few completed interviews before making any new decisions. Reading two or three transcripts and scores is the fastest way to calibrate against how the previous owner was judging candidates.

What stays exactly as it was

A few things are workspace-wide and are not affected by who owns a role, which removes some common worries:

  • Slack and Microsoft Teams alerts go to the channels an admin configured for the whole workspace, so candidate alerts keep arriving in the same place during and after the handover.
  • Candidate booking links keep working. Candidates pick slots and join interviews the same way regardless of which recruiter owns the role.
  • Stop controls stay on the role’s campaign. If the new owner spots a problem, they can stop the screening campaign for that role without affecting anyone else’s.

Temporary cover versus a permanent handover

The mechanics are identical, but the intent changes what the new owner should do.

Temporary cover is about keeping the drive moving. The covering recruiter should avoid changing the role’s rubric, knockouts or automation unless something is clearly wrong, because the original owner will return to a role they no longer recognise. A useful habit is to keep a short running note of decisions taken during the cover: candidates moved to On Hold and why, anyone overridden, any hiring manager conversations. When the recruiter returns, an admin moves the roles back on the same card and the note becomes the handback briefing.

A permanent handover is the opposite. The new owner should treat the role as theirs and review everything properly, including whether the job description still reflects what the hiring manager wants. It is also the moment to remove the old account, in the order described above.

A handover that starts as temporary and quietly becomes permanent is where things drift. If cover is running past two or three weeks, decide explicitly which one it is.

If the person leaving is an admin

Handing over a recruiter’s roles is straightforward. Handing over an admin’s responsibilities has two extra steps, because only admins can manage the workspace.

  1. Check how many admins remain. If the departing person is one of two, promote someone before they go. Otherwise the team is one sick day away from nobody being able to reassign anything.
  2. Hand over the workspace settings as well as the roles. Admins control where Slack or Microsoft Teams alerts go and any ATS connection. Make sure the remaining admin knows where those are set, especially if the departing admin set them up.

The account owner is a special case. The owner cannot be removed from the workspace at all, which protects the team from losing its account holder. If the person who created the workspace is leaving the company, talk to us about the account before they go rather than trying to work around the rule.

Common handover mistakes

  • Removing the account first. The most frequent one. Their roles drop out of every member’s view until an admin reassigns them.
  • Promoting the cover recruiter to admin. It gives them every role in the company when they needed four.
  • Splitting a role’s candidates by hand. Ownership moves whole roles. If two people genuinely need to share one, split it into two job descriptions instead.
  • Forgetting the hiring manager. The workspace moves instantly; people’s email habits do not.

Plan for the handover before anyone leaves

The smoothest handovers we have seen were decided before anyone was actually on leave. Two habits make that possible:

  • Keep a named backup for every role. It does not need to live in the tool. A short line in the team’s drive plan, “backend roles: Asha, backup Ravi,” means the Friday-morning decision is already made.
  • Keep at least two admins. Only admins can change ownership. If your only admin is the person on leave, nobody can hand anything over. We explain the reasoning in choosing access levels.

A hiring drive does not pause for a leave application. The goal of a handover is that candidates never notice it happened, and with ownership attached to the role rather than the person, that mostly comes down to doing five small steps in the right order. For the broader picture of running one drive across several recruiters, see splitting AI screening by role. If you want to try a handover on a real workspace, book a demo.

Frequently asked questions

Do scheduled AI interviews stop when I reassign a role to another recruiter?

No. Changing who owns a role only changes whose screens it appears on. Candidates who already booked a slot still get their interview at the same time, and completed interviews keep their recording, transcript and scores.

Should I reassign a recruiter's roles before or after removing them from the workspace?

Before. In HireQwik, a role still owned by someone who has been removed is no longer unassigned, so only admins can see it. Reassign first, check the new owner can see everything, and remove the account last.

Does the new owner inherit the previous recruiter's automation settings?

Yes, because settings such as knockouts, the scoring rubric and any auto-reject or auto-advance bands belong to the role, not the person. That is convenient, but the new owner should read them before the next batch of applicants arrives.

See your own candidates screened

Book a 30-minute demo. Bring a live JD and we'll screen against it, then start with a pilot on your own candidates before committing to anything.