Interview schedule template for onsite and virtual loops
On this page
- What a schedule has to settle before it goes out
- The interview schedule template
- A filled example: a four-interviewer onsite loop
- Onsite versus virtual: what changes
- The interviewer-facing version
- Building the schedule without back-and-forth
- What goes wrong, and the fix
- Time zones and multi-region loops
- Confirming and handling last-minute changes
- Questions people ask
An interview schedule is the itinerary sent to a candidate and every interviewer once times are set: who the candidate meets, in what order, for how long, and where — a room, a video link, or a phone number. It is different from the invitation that proposes times and different from a panel plan that assigns competencies internally; the schedule is what everyone follows on the day itself.
Below is a template for both onsite and virtual loops, a filled example, and the details that cause the most confusion when they are missing. For the invitation that gets times agreed before this document exists, see interview invitation email templates; for what each interviewer should ask once the schedule is set, see panel interview plan template.
What a schedule has to settle before it goes out
- Order and duration of each session, with buffer between them.
- Who the candidate meets, by name and title, and their format — one-on-one, panel, or a working session.
- Where — the room and floor for onsite, or the specific video link and dial-in for virtual, not a generic "check your calendar."
- Who is the candidate's point of contact on the day, for a late start, a question, or a technical problem.
- What each session is about, in one line, so the candidate is not guessing what a "team session" versus a "hiring manager conversation" actually covers.
The interview schedule template
Copy this and fill in the brackets. The candidate-facing and interviewer-facing versions can be nearly identical; the difference is usually just an added internal note line for interviewers.
Subject: Your interview schedule — [Role] at [Company], [Date]
Hi [Candidate name],
Here's your schedule for [Date]. [Format: You'll be onsite at our office /
Each session is a separate video call, links below.]
[Time] – [Time] [Session name] with [Interviewer name, Title]
[One line: what this session covers]
[Room / video link / dial-in]
[Time] – [Time] [Session name] with [Interviewer name, Title]
[One line: what this session covers]
[Room / video link / dial-in]
[Time] – [Time] [Session name] with [Interviewer name, Title]
[One line: what this session covers]
[Room / video link / dial-in]
Point of contact for the day: [Name], [phone number]
[If onsite: Parking / building access / what to bring]
[If virtual: Please join 2–3 minutes early to test audio/video]
Looking forward to it.
[Your name]
A filled example: a four-interviewer onsite loop
An invented candidate and loop, written the way a usable schedule reads:
Subject: Your interview schedule — Product Manager at Fernwood Labs, Thursday Oct 1
Hi Alicia,
Here's your schedule for Thursday, October 1. You'll be onsite at our office — check in at the front desk and ask for Ravi.
9:00 – 9:45 AM — Product deep-dive with Ravi Sharma, Director of Product
Walk through a product you've shipped end to end.
Room 4B, 2nd floor
9:55 – 10:35 AM — Cross-functional working session with Maya Torres, Eng Lead
A 30-minute exercise scoping a feature together.
Room 4B, 2nd floor
10:45 – 11:15 AM — Stakeholder management with Devon Price, Marketing Lead
How you've handled disagreement with a partner team.
Room 2C, 2nd floor
11:25 – 12:00 PM — Hiring manager conversation with Priya Nair, VP Product
Your questions, and what the first 90 days would look like.
Priya's office, 3rd floor
Point of contact for the day: Sam Okoro, (555) 291-3340
Parking validation available at the front desk. Lunch after, no need to bring anything.
Looking forward to it.
Sam
Onsite versus virtual: what changes
| Element | Onsite | Virtual |
|---|---|---|
| Buffer between sessions | 10–15 minutes for walking and a short break | 5–10 minutes so a long session doesn't cascade |
| Location field | Room and floor, or "we'll walk you over" | A distinct link per session, not one recurring link for all |
| What to bring | Photo ID for building access, a printed resume if your office asks for one | Nothing extra; note the platform (Zoom, Teams, Meet) so the candidate has it installed ahead of time |
| Point of contact | A name and desk or phone number for arrival | A name and phone number for a dropped call or link that fails |
| Loop length | Half-day loops of 3–5 sessions are common | Split across two shorter days if the loop runs past 3 hours, fatigue changes how candidates answer late sessions |
The interviewer-facing version
Send interviewers the same schedule with one addition: which competency or area each of them owns, so nobody duplicates a question another interviewer already planned to ask. This can be as simple as a bracketed note next to their session name — "[covers: system design, ownership]" — or a link to the fuller panel interview plan if the loop has more than two or three interviewers. Interviewers should also get the candidate's resume and, where available, notes from earlier stages, so a hiring-manager session in slot four does not reopen ground the recruiter screen already covered in slot one.
Building the schedule without back-and-forth
Collect availability once, not per interviewer: a shared scheduling link or a single email asking each interviewer for two or three windows over the coming week beats five separate threads that each need a reply. Lock the candidate's time first, since they usually have the least flexibility (a single day off work, in many cases), then slot interviewers into it rather than the reverse. If an interviewer cannot make any of the candidate's available windows, swap them for someone who covers a similar competency rather than moving the whole loop, which is the change most likely to frustrate a candidate who already cleared their calendar once.
What goes wrong, and the fix
| Mistake | Fix |
|---|---|
| One generic video link reused for every session | A distinct link per session so a session that runs long doesn't lock the next interviewer out |
| No buffer between back-to-back sessions | Build in 5–15 minutes so a five-minute overrun does not cascade through the whole day |
| Session names with no description | One line per session on what it covers, so the candidate can actually prepare |
| No named point of contact | One person, with a phone number, for the day of |
| Schedule sent the morning of an onsite loop | Send at least two business days ahead so travel and childcare can be arranged |
Time zones and multi-region loops
Put the time zone next to every time on the schedule, spelled out rather than abbreviated ("2:00 PM Eastern," not just "2:00 PM"), and repeat it at the top of the email if the candidate and any interviewer are in different regions. A schedule with unlabeled times invites a candidate to assume their own local time zone, and a candidate who joins an hour early or an hour late because of a missing label reflects on the process, not on them. For loops with interviewers across more than two time zones, list each session's start time in the candidate's zone only — interviewers can check their own calendars — rather than showing three time zones per line, which is harder to scan under time pressure the morning of an interview.
What interviewers need before the loop starts
A schedule alone does not prepare an interviewer to run a good session. Send interviewers the schedule at least a day ahead, along with:
- The candidate's resume and the job description, so nobody is reading either for the first time in the room.
- What earlier sessions covered, if any, so the loop does not repeat the same two questions four times.
- The specific competency or area they own for their slot, and roughly how much time to leave for the candidate's own questions.
- Where to send feedback and by when — same day, while the session is fresh, rather than at the end of the week once every loop from the day has blurred together.
Interviewers who receive only a calendar invite with a candidate's name tend to run whatever interview they always run, regardless of what the loop actually needs from their slot. A short brief attached to the schedule is a small amount of extra writing that changes what happens in the room.
Confirming and handling last-minute changes
Ask the candidate to confirm receipt, the same way you would confirm any commitment that involves several other people's calendars. If an interviewer has to drop out on the day, do not simply delete their slot — either find a same-competency replacement or extend the neighboring session, and tell the candidate about the change before they walk into what looks like an empty room or an early finish. For a schedule that needs to move entirely rather than adjust in place, use the interview reschedule email template and resend a clean, updated schedule rather than a patch on top of the original.
If your team records interviews for scorecard evidence, note that in the schedule itself rather than surprising the candidate mid-session — a short line stating that notes are taken with a transcription tool, with a chance to ask questions about it, belongs on the invitation stage more than here, but a reminder line on the schedule does no harm.
Questions people ask
How is an interview schedule different from a panel interview plan?
A panel interview plan is an internal document that assigns which competency each interviewer owns and what they will ask. The interview schedule is the itinerary built from that plan — times, rooms or links, and who the candidate meets when — sent to the candidate and every interviewer so everyone has the same timeline.
Should the candidate see interviewer titles on the schedule?
Yes, first name and title is normal and helps the candidate prepare, for example knowing that the second session is with the hiring manager and the third is with a peer. Full LinkedIn-style bios are not necessary and can make the schedule harder to scan.
How much buffer should be built between interview sessions?
Five to ten minutes for a virtual loop, so one session running long does not cascade into the next. For an onsite loop, ten to fifteen minutes covers walking between rooms and a short break, which matters more the longer the loop runs.
Who owns sending the final schedule, recruiting or the hiring manager?
Recruiting, in most structured processes, because they are coordinating everyone's calendars and are the point of contact for changes. The hiring manager owns what happens inside each session, which is a different document — see the panel interview plan template.