Recruiting operations

Close a candidate relocation request with a dated approval

A remote recruiting operations guide for recruiting leaders and hiring teams, focused on relocation requests with explicit evidence, review rights, and a dated close.

Remote Talent Acquisition Editorial Team8 min read
Editorial recruiting workflow illustration for Close a candidate relocation request with a dated approval

Book a free recruiting call

Discuss a defined recruiting workflow, its owners, and its operating boundaries.

Plan a free call

# Close a candidate relocation request with a dated approval

Published November 5, 2026

The control this relocation requests needs

A relocation requests control begins with the requisition or candidate event that opened the case. The coordinator may assemble the source record, check the agreed evidence, and write the open question. The recruiting owner keeps every decision that changes a candidate, an offer, an interview commitment, or a hiring outcome. Remote Talent Acquisition places that boundary beside the relocation requests queue so a new coordinator does not borrow authority from an earlier search. The evidence standard separates an observed gap from a hiring judgment.

The common gap in relocation requests is a record that looks current while the source evidence is absent. A pipeline can show movement even when the scorecard, the consent note, or the approval is missing. Record the source, the date observed, the candidate reference, and the next action before the case advances. That habit lets a reviewer rebuild the file without a private conversation. A rejection note cites the specific evidence gap and the reviewer who closed it.

What the relocation requests record must show

Every relocation requests file should say who opened it, which source was checked, what changed, and who approved the close. Include the candidate reference, the role, the reviewer, the recruiting owner, and the destination. Keep the observed fact separate from the hiring interpretation. A reviewer should be able to follow that path in under a minute. The panel owner checks the calendar and the interview date before confirming the slot.

The evidence standard for relocation requests is intentionally modest. Write the source date and mark a missing value as missing instead of filling it from memory. When two records disagree, preserve both and route the narrow question to the recruiting owner. Remote Talent Acquisition keeps the original source beside the correction note. A second reviewer can rebuild the screening decision from the scorecard without a private conversation.

Where authority stops

The coordinator may prepare, check, record, and route. The recruiting owner keeps any decision that changes an offer, a candidate commitment, access, or a hiring outcome. When a relocation requests case raises a privacy question, a bias concern, a dispute, or a request outside scope, preserve the facts and route it. A deliberate stop protects the candidate experience when the exception is real. The panel owner checks the calendar and the interview date before confirming the slot.

Access to the relocation requests file follows a least-privilege rule. Each coordinator gets an individual account, and the permission set is limited to the written scope. The recruiting owner reviews that access when the assignment changes or the search ends. Remote Talent Acquisition records the review date with the relocation requests file. Any missing candidate evidence is marked missing until the source arrives.

Exceptions that stop the case

Predictable relocation requests exceptions include a missing source, two records that disagree, an expired consent, an unavailable owner, an unsigned approval, or a request outside the agreed scope. Record the exception and the exact missing field so the next reviewer does not repeat the search. Use a short approved reason list so counts stay comparable. Keep the source, the date observed, the named owner, and the next check with the record. Any missing candidate evidence is marked missing until the source arrives.

If a relocation requests exception touches an offer, a candidate commitment, a privacy question, a bias concern, or a public hiring statement, the dependent action waits for the recruiting owner. Do not infer approval from silence or from a prior similar search. The resolution should say what was decided and where the evidence lives. Keep the source, the date observed, the named owner, and the next check with the record. A rejection note cites the specific evidence gap and the reviewer who closed it.

How to verify and close

To verify relocation requests, inspect the candidate record, the scorecard, the offer approval, the consent state, or the candidate-visible message. A sent email or a moved card proves activity, not that the record changed. Confirm the field or outcome the work was supposed to affect. If the destination cannot be checked, the case is not complete. A rejection note cites the specific evidence gap and the reviewer who closed it.

The close note records what was checked, who approved it, what changed, and what would reopen the case. The recruiting owner should be able to read one record later and explain the close without contacting the original coordinator. Remote Talent Acquisition keeps the relocation requests close note with the source evidence. Keep the source, the date observed, the named owner, and the next check with the record. A second reviewer can rebuild the screening decision from the scorecard without a private conversation.

Review a bounded support plan

Discuss a defined recruiting workflow, its owners, and its operating boundaries.

Plan a free call

Continue reading

Three related guides

Plan the next recruiting workflow

Discuss a defined recruiting workflow, its owners, and its operating boundaries.

Plan a free call