Interview Scheduling Form Template
Candidates state availability windows, time zone, format needs, and hard conflicts once — recruiting coordination without the seven-email thread.
Let’s find your interview time. Share your availability for the coming week and we’ll confirm one slot with a calendar-ready email — no back-and-forth.
We match it to your file — use the same address you applied with.
Interview scheduling is the highest-stakes calendar problem most companies run, because the person on the other side is deciding whether to work for you while you fumble it. The classic failure is the seven-email thread — "does Tuesday work?" "which Tuesday?" "what time zone?" — that reliably loses a day per hop and occasionally loses the candidate. This form collapses the thread to one structured exchange: the candidate states windows, zone, format needs, and hard conflicts once; the coordinator replies once with a confirmed slot.
Why these fields. The availability question asks for windows across five business days because that span is wide enough to guarantee overlap with a panel's calendars and short enough that nobody's answers go stale. The time zone field sits beside it as a required, explicit answer — zone confusion is the single most common scheduling failure in distributed hiring, and inferring it from an area code or an email signature is how 9am arrives at 6am. Hard conflicts get their own field because "generally free except Thursday" buried in prose gets missed; extracted, it never is. The stage dropdown tells the coordinator how long a slot to hunt for — a thirty-minute screen fits where a three-hour final loop cannot. And the format fork drives the form's logic with a purpose beyond logistics: choosing on-site reveals a travel-and-accessibility question, which arranges parking and step-free access before anyone has to ask — the kind of caring-by-default that candidates repeat to friends.
What we left out. Resume re-uploads and "tell us about yourself" fields — the candidate already applied; a scheduling form that re-interviews them signals disorganization. Also interviewer-picker menus: panel composition is the company's puzzle, and exposing it buys nothing.
Who uses this. Startup recruiters coordinating without a scheduling platform, agency recruiters juggling candidates across client time zones, university admissions running interview days, and internal mobility teams scheduling panels discreetly.
Make it yours. Send the link in your interview-invitation email with the role pre-agreed, and keep the five-day window honest — if your panel books out two weeks ahead, change the label to match. Filter the responses view by stage when coordinating multiple loops, and let a webhook push each response into your ATS so scheduling status lives where recruiters look. For senior or confidential searches, add a password in Settings so availability never circulates beyond the loop. Responses are visible only to your account, which is exactly where candidate availability belongs.
Candidate experience is scheduling. Before anyone evaluates skills, the candidate evaluates your emails. One clean ask, one fast confirmation in their own time zone — that is the first interview, and this form passes it for you.
Frequently asked questions
Why collect windows instead of offering bookable slots?
Panel calendars shift too fast for published slots to stay true. Windows from the candidate plus one coordinator pass produces a confirmed time with zero double-booking risk.
How does the accessibility question stay unobtrusive?
A logic rule shows it only when on-site is chosen — video candidates never see it, on-site candidates get accommodations arranged without having to raise the topic themselves.
Can responses land in our ATS automatically?
Yes — add a webhook and each submission POSTs to your endpoint in real time, signed, with retries. Map the stage and availability fields to your scheduling notes.
Who can see what candidates submit?
Only your account — responses live in your private responses view. Share specifics with the panel the way you already share candidate files.