Published November 8, 2026.
A new recruiting assistant meets the queue, the candidate, and the hiring manager all at once, and the first shift sets the pattern for every shift after it. A written script keeps the first day from depending on whoever happens to be free. It should name the work, the words, the limits, and the person to call when the answer is not on the page. The script is not a script for the candidate; it is a script for the assistant, so it should be short enough to use while the queue is moving.
Open the shift with a five-minute check
Start with the same five checks every morning: the shared inbox, the interview calendar, the candidate tracker, the urgent channel, and the handoff note from the previous shift. The assistant should mark each one as checked rather than assume it is fine. A missed calendar change can send a candidate to the wrong place, and a missed handoff note can repeat a question that was already answered. Write the check as a short list with a time beside each item. The first shift should finish the list before opening a new task. If a system is down, the assistant records the outage and moves to the next item instead of waiting. The end-of-shift note should say which checks were completed and which were blocked.
Use a candidate-first tone from the first message
The first message a candidate receives from a new assistant should sound like the business, not like a template that was copied from a vendor. Give the assistant three examples: a scheduling reply, a follow-up after an interview, and a message that says the team needs more time. Each example should name the next step and the expected response time. The assistant can adapt the wording but should keep the structure.
Forbid language that sounds like a status report to a manager. Candidates do not need to hear that the requisition is with the client or that the team is waiting on approval. They need to know what happens next and when they will hear. If the answer is not known, say when it will be known and who will provide it. Record the candidate's preferred channel and time zone in the tracker. A first shift that sends an SMS to someone who asked for email starts a trust problem that is hard to repair. The assistant should read the preference before sending, not after.
Keep the first-day queue small and owned
Give the new assistant one queue and one backup queue, not the whole recruiting operation. The primary queue should have a predictable volume and a clear definition of done. The backup queue should be opened only when the first is clear or when the supervisor asks. A first day that includes every channel produces shallow work and a tired new hire.
Name the person who answers questions about each queue and the hours they are available. If the supervisor is in a different time zone, give the assistant a written decision rule for the hours when nobody is online. The rule should cover rescheduling, urgent candidate issues, and anything involving a payment or a contract. The assistant should never have to guess about money. Set a target for the first day that is about quality, not volume. One clean scheduling round, one accurate tracker update, and one well-written candidate message are enough to prove the script works. Volume can grow after the assistant can explain why each step matters.
Write the escalation path on one page
The escalation page should list the situations that always go to a supervisor: a candidate who mentions a safety concern, a hiring manager who asks to change an offer, a request for a refund or a credit, and any message that threatens legal action. Put the channel and the response time beside each one. The assistant should be able to escalate without writing a long explanation. For everything else, give the assistant a decision rule and a way to record the choice. A scheduling conflict within the approved window can be resolved by the assistant, while a change to the interview panel goes to the supervisor. The line should be specific enough that two people reading the same case reach the same answer.
Review the escalation page at the end of the first week. Ask the assistant which case was hardest to classify and why. Add the case to the examples rather than writing a longer policy. A page that grows with real cases is more useful than a page written in advance.
Protect access and candidate data
Give the assistant a named account with the narrowest access that lets the first queue work. Do not share a supervisor's login, even for a day. The audit trail matters when a candidate asks who viewed a record or when a message is sent to the wrong person. A shared login makes both questions unanswerable.
Show the assistant where candidate data may be stored and where it may not. A personal note, a chat message, or a downloaded spreadsheet outside the approved system is not an acceptable place. If the assistant needs a temporary list, use the approved workspace and delete it at the end of the shift. Record the deletion.
Test the access before the first shift, not during it. A login that works but cannot open the calendar is a hidden stop. Record the systems tested and the person who confirmed each one. If a system is missing, the first-day plan should say what the assistant does instead.
Close the shift with a written handoff
The end-of-shift note should list what was completed, what is waiting, what was escalated, and what the next shift should check first. Keep it short enough to read in two minutes. Link the candidate records rather than repeating the details. The next shift should not have to reconstruct the day from a chat thread.
Ask the assistant to name one instruction that was unclear and one tool that slowed the work. The supervisor should fix one of those before the second shift. A first shift that produces no feedback is either perfect or unread. The goal is a script that improves with each new assistant, not a document that is defended unchanged.