An interview schedule template that survives a real drive
On 23 October 2026, a hiring team we work with told us on a feedback call that not all of their profiles had come through from their sheet. They were right. The rows that never got an interview invitation had no email address, and many of them had been sourced from LinkedIn, where an export often carries no email at all. No email meant nothing to send a booking link to, and those rows were being skipped without any sign on screen.
We fixed the silent part the next day. The lesson for anyone running an interview schedule template was bigger than the bug: a schedule sheet fails at its columns long before it fails at its size. This post gives you a template that holds up in volume hiring, the rules that stop the common failures, and the honest signs that your spreadsheet has stopped being the right tool. If you’ve already outgrown it, the guide to interview scheduling software covers what to look for next.
What is an interview schedule template?
An interview schedule template is a spreadsheet that tracks who is being interviewed, for which role, when, by whom and with what result. A good one has two views: an internal schedule the hiring team works from, and a short itinerary sent to each candidate, so the team’s notes never reach the person being interviewed.
Google’s AI Overview for this search made the same two-view point on 11 November 2026, and it’s the right starting place. Most templates online are one tab that tries to be both, which is how interviewer comments end up pasted into a candidate email.
The columns that matter, and why each one is there
Here is the column set I’d start from. Every column earns its place by preventing a specific failure.
| Column | Example | What it prevents |
|---|---|---|
| Candidate ID | C-0141 | Duplicates when the same person applies twice |
| Name | (as on the résumé) | Mismatched rows when two people share a first name |
| (required) | Rows that can never receive an invitation | |
| Phone | +91 98xxx xxxxx | No way to reach a candidate whose email bounces |
| Source | Job portal / referral / campus / LinkedIn | Not knowing which channel produced your hires |
| Role | Customer Support Executive | Interviewing someone for the wrong job |
| Applied date | 2026-11-04 | Slow responses to the earliest applicants |
| Stage | Screen / Round 2 / Final | Losing track of who is where |
| Slot date and time | 2026-11-12 18:30 | Arguments about what was agreed |
| Time zone | IST | Candidates in another city or country joining an hour off |
| Interviewer | (name) | Two rounds booked with the same person at once |
| Format and link | Video, [joining link] / In person, [venue] | Candidates turning up to the wrong place |
| Status | Invited / Booked / Done / No-show / Withdrawn | A sheet nobody trusts |
| Reschedule count | 1 | One candidate moving six times |
| Outcome | Advance / Hold / Reject | Decisions living only in someone’s head |
| Notes | (internal only) | Context lost between shifts |
Two of those columns deserve a rule of their own. Email is required, and the sheet should flag any row without one the moment it lands, not when the invitations go out. And the candidate ID is not the row number. Row numbers change the moment someone sorts the sheet, and then every reference to “row 212” in your emails points at a different person.
Two tabs: the internal schedule and the candidate itinerary
Keep the team’s working view and the candidate’s view physically separate.
The internal schedule is the full table above, one row per candidate per round. It has the notes, the outcomes and the interviewer names. It’s shared only with the hiring team.
The candidate itinerary is what each candidate receives: role, date, time with the time zone, format, link or address, length, what to bring and one contact. It’s generated from the internal tab (with a simple lookup on the candidate ID) or written into the confirmation email. It never includes the notes or the outcome columns.
If your round has several steps on one day, such as a test followed by two interviews, the itinerary lists them in order with times. That is where panel and in-person days most often go wrong: the team knows the sequence and the candidate doesn’t.
Status values that keep the sheet honest
Free-text status columns are where spreadsheets go to die. One person writes “done”, another “completed”, a third “interviewed - good”, and no filter or count works any more. Use a drop-down list and nothing else:
- Invited: the invitation has gone out.
- Booked: the candidate has a slot.
- Rescheduled: they moved; the new slot is in the slot column.
- Done: the interview happened.
- No-show: they booked and didn’t join.
- Withdrawn: they told you they’re out.
- Expired: the booking deadline passed without a booking.
Seven values are enough to answer the questions you’ll actually be asked: how many did we invite, how many booked, how many showed up, how many are still waiting. Outcome is a separate column on purpose. A candidate can be “Done” and still “Hold”, and mixing the two is how strong candidates get lost in a “done” filter.
Rules that stop the common sheet failures
These are small, and each one closes a failure I’ve seen in real hiring sheets.
- Freeze the header row and never merge cells. Merged cells break sorting, filtering and every lookup.
- One date format, written out. Use YYYY-MM-DD in the sheet. A form timestamp in D/M/Y read as M/D/Y turns 4 November into 11 April, and nobody notices until a candidate is chased for an interview that’s months away.
- Time zone in its own column. “6:30” means nothing to a candidate in Dubai applying for a Pune role.
- Phone numbers as text with the country code. Otherwise the sheet strips the leading plus sign or turns the number into scientific notation.
- Edit history on, and one owner. Google Sheets keeps version history; use it. Name one person who owns the structure, even if ten people edit rows.
- Never delete a row. Mark it Withdrawn or Expired. Deleted rows are how you end up re-inviting someone who said no.
- Validate the email column. A simple rule that the cell contains “@” and a dot catches most typos before they cost a lost candidate.
When the spreadsheet breaks: four signs
A spreadsheet is a fine scheduling tool for a few dozen candidates. It doesn’t fail all at once; it fails at the edges. These are the four signs I’d watch for.
1. Rescheduling never reaches the sheet. The candidate emails the interviewer, the interviewer agrees, and the sheet still shows the old slot. Yello’s 2019 poll of 200 recruiting, talent and staffing people found that more than 74 percent call last-minute changes and rescheduling a challenge, and in a sheet every change depends on someone remembering to type it.
2. Two people book the same slot. The sheet doesn’t stop it. It only shows it afterwards, if someone looks.
3. Candidates wait days for a reply. When scheduling is “email me your availability and I’ll update the sheet”, the sheet is only as fast as the busiest person in the chain.
4. There’s more than one copy. “Interview schedule FINAL v3 (Priya’s edits).xlsx” is the end of a single source of truth.
If two of those are true for you this month, the sheet has become a job, and that job is mostly copying information from one place to another.
From spreadsheet to scheduled: keep the sheet, drop the typing
Here’s the thing most “move off spreadsheets” advice gets wrong: the sheet isn’t the problem. For most Indian hiring teams, the Google Sheet is where candidates arrive: a form response, a job portal export, a campus list from a placement cell. Throwing it away means re-training everyone who feeds it.
The part worth automating is everything after the row lands. In HireQwik, candidates come in from a connected Google Sheet or a bulk upload of PDF or Word résumés, every résumé is scored against the job’s own requirements, and the shortlisted candidates get an email link to book their own interview slot, with reminders before the deadline. Nobody types a slot into a cell, and nobody chases a reply to “what time works?”. The sheet stays the list of candidates; the booking, the reminders and the status come back from the system. When you need the result in a spreadsheet again, the recruiter inbox exports to Excel or CSV.
That October call is also a reminder of what automation doesn’t fix: a booking link still needs an email address in the row. Clean intake columns matter more once a system is reading them, not less.
A worked example: 300 rows on a Monday
To make the difference concrete, picture this, as a hypothetical: a customer support role opens on Monday and 300 applications land in the sheet by Wednesday.
With the sheet alone, a coordinator filters the rows, decides who to call, and emails maybe 120 people asking for their availability. Replies trickle in over three days. Each one has to be matched against two interviewers’ calendars and typed into the sheet, then confirmed with a second email. Twenty people ask to move. Thirty never reply and need chasing. By the following Wednesday, perhaps 70 interviews are booked, and the sheet is a day behind reality.
With the sheet as intake and a booking link for times, the same 300 rows are scored as they arrive, the shortlist gets an invitation with a link and a Friday deadline, and the coordinator’s job becomes watching three numbers: invited, booked, not yet booked. The second email goes only to the not-yet-booked group, once, halfway to the deadline. The candidates who need an evening slot take one without asking.
The hours saved aren’t the main win. The main win is that the candidates who were going to drift away in a three-day reply chain book on the day they’re invited.
A template you can copy
Paste this header row into a new sheet, add drop-down validation on the Status, Stage and Outcome columns, and freeze row one.
Candidate ID | Name | Email | Phone | Source | Role | Applied date |
Stage | Slot date | Slot time | Time zone | Interviewer | Format |
Link or venue | Status | Reschedule count | Outcome | Notes
Then add a second tab called “Itinerary” with only: Candidate ID, Role, Slot date, Slot time, Time zone, Format, Link or venue, Length, Bring, Contact. Fill it with a lookup on Candidate ID from the first tab so it can’t drift.
Two small additions help once the sheet is shared. A filter view per interviewer lets each person see only their own rows without changing what everyone else sees. And a small summary block at the top (invited, booked, done, no-show, counted with COUNTIF on the Status column) gives the hiring manager the only numbers they’ll ask about.
What to keep in the sheet even after you automate
Some things should stay in a spreadsheet you control, whatever tool books the slots:
- The intake list, in the same columns, so sources and placement cells keep sending data the way they’re used to.
- The source column, because it’s how you’ll learn which channel produced the people you hired.
- The decision log for later rounds, if your next rounds are still booked by hand. Once a candidate passes the screen, HireQwik’s next-round booking puts the candidate into a colleague’s open time and sends each of them a calendar invite, but plenty of teams still track final rounds in their own sheet, and that’s fine.
- A weekly export, so the hiring history doesn’t live in only one system.
What shouldn’t stay there is the back-and-forth about times. If you want to compare how much of that you can retire, the post on how to reduce interview no-shows and our India data on when candidates choose to book are the next two reads.
Start with the columns, not the tool
If your schedule sheet works today, keep it, and fix three things this week: make email mandatory, give every candidate an ID that isn’t the row number, and replace free-text status with a drop-down. Those three alone will tell you how many candidates are actually waiting on you.
When you’re ready to see what the booking side looks like from the candidate’s chair, take a short live AI interview on our site, or book a walkthrough with your own job and we’ll run it on your sheet’s columns.
Frequently asked questions
What columns should an interview schedule template have?
At minimum: a unique candidate ID, name, email, phone, source, role, applied date, current stage, slot date and time with a time zone, interviewer, format or joining link, status, reschedule count and outcome. The email and the candidate ID matter most: without an email there is nothing to send an invitation to, and without a unique ID duplicates creep in.
Should I use Excel or Google Sheets for an interview schedule?
Google Sheets if more than one person edits it, because everyone sees the same version and you get edit history. Excel is fine for one coordinator working alone. Either way, lock the header row, use drop-down lists for status values and keep one row per candidate per round.
When should we move interview scheduling out of a spreadsheet?
When the sheet starts needing a person whose main job is updating it. Typical signs are double bookings, candidates waiting days for a reply, reschedules that never reach the sheet, and more than one version of the file in circulation. At that point keep the sheet as the list of candidates and let a booking link handle the times.
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.
Existing customer? Sign in