The Interview Booking Run, From Open Invites to a Collision-Free Week

This is the procedure for turning a week of interview invites into confirmed slots on one calendar. A typical week mixes self-scheduling links, availability requests and assessment invites. The guide is for job seekers applying at volume with several employers moving at once. When you finish, you have a capped, buffered week with every time confirmed in writing in your own zone and no invite left unanswered for more than one business day.

What a finished interview booking run looks like

At the end of a run, every invite on your calendar is booked, answered with windows, or deliberately declined. No two calls collide, and no invite has gone unanswered for more than one business day. Getting there means understanding the three kinds of invite you will receive, because each fails in a different way.

These terms come up throughout this guide:

• Self-scheduling link: a link from the employer's scheduling tool that shows open slots, so you pick one yourself.
• Availability request: an email or form asking for your free windows. A coordinator then books the slot.
• Assessment invite: a test or exercise with a deadline and no live slot. It still takes time out of your week, so it goes in the inventory.
• Booking horizon: how far into the future a link will show slots.
• Minimum notice: the shortest lead time a tool allows between booking and the interview itself.
• Buffer: time blocked before and after a call for preparation and recovery.
• Availability grid: your single weekly map of the windows you are willing to offer, with buffers and work commitments already blocked.

The whole run uses short, fixed amounts of time. The inventory takes about 20 minutes, the grid about 20, and setting the order about 5. Each link takes a few minutes, each availability reply about 10, and each written confirmation about 5. The ongoing work is hold-and-release and a 2-minute reconfirmation close to each interview date.

How the scheduling tools behave by default

The employer's scheduling tool, and the way its admin configured it, decides most of what you can and cannot do with an invite. Know the defaults and you can tell a closed door from a setting.

The table hides a few mechanics that matter:

• Expiry is the sender's choice. On Greenhouse, whoever creates a scheduling link decides whether it can expire. No default window is published. Once a link expires, you can't use it to book or reschedule.
• Panels arrive as emails. Greenhouse self-scheduling only works for single-interview stages, so multi-session stages are scheduled by hand. That is why panel loops tend to arrive as availability requests.
• Dead links can look alive. If a coordinator cancels a pending Greenhouse request, the link stops working but the email stays in your inbox looking live.
• Your zone may be guessed. If your time zone hasn't been saved, Ashby infers it from your location.
• The fallback is optional. Ashby has a "suggested times" option for when no slot fits, but each employer decides whether to show it. Ashby can also send automatic reminders minutes, hours or days after a link or request goes out.
• Some tools are unknown here. I haven't established defaults for Workday or Lever. For those, rely on the link page itself and on the confirmation email.

The biggest one is the time zone anchor. Greenhouse and Ashby both default to 9-5 in the interviewer's time zone, so every hour of offset between you and the interviewer removes an hour of slots you can see. Calendly does the opposite and shows times in your zone. The same "Tuesday at 10" can mean different things depending on which tool sent the link.

Reschedule rights belong to the employer, not to you. Greenhouse needs an admin to turn on "Allow candidates to reschedule self-scheduled interviews". Ashby's limits are optional and default to unlimited. The same click can work at one company and fail at the next, so never assume.

Who sends your invites and how fast they expect a reply

Most invites come from coordinators. The best available data says that replying within one business day already puts you ahead of what most candidates expect. You don't need to reply instantly. You need to be consistent.

The percentages come from samples of 25, so treat them as directional. Two patterns are still useful in practice:

• Signature titles differ by market. In the samples, "Recruiting" is the US signature title and "Recruitment" is the UK one. A sender with either title owns the calendar, so send scheduling questions to them and not to the hiring manager.
• Who sends the invite differs too. In the UK sample of 25, coordinators cluster at large employers: NHS (4), with PwC, EY, Capgemini and Accenture at 2 each. Large employers tend to run structured, coordinator-led loops. Among the 49 US coordinators who list Greenhouse as a skill, OpenAI and Headway account for 2 each.

On speed, the evidence is thinner than vendor marketing suggests:

candidate.fyi is a scheduling vendor reporting its own platform data. No independent benchmark exists. Cronofy's survey covered 12,000 candidates in 7 countries. In it, the share who had left a process over slow scheduling fell to 42%, down from 49% the year before, and 31% said their first interview took 2 to 3 weeks to schedule. Candidates are waiting longer before giving up, so speed alone won't make you stand out. It still helps to be the candidate who never makes a coordinator chase.

The 2-day gap between 5.9 and 3.9 days comes from removing back-and-forth emails. A self-scheduling link only checks one interviewer's calendar against your click. An availability request is where you hand out windows you might also give someone else. That makes availability requests, not links, the main source of double-bookings.

How many interviews per week, and how much buffer between them

Cap live interviews at 3 to 5 per week, the range the Optimality practitioner newsletter recommends, and block a buffer before and after every call. Optimality's reasoning: more than five a week means interviewing twice in one day, with switching costs and split preparation.

How long a candidate's buffer should be is not established publicly. The only published buffer figures are on the interviewer side, such as 15 minutes between interviews to write feedback. Treat that as a floor, not a target. Your buffer has to cover re-reading the posting and the resume version you sent, getting settled, and recovering afterwards. Size it to how long you actually take to reset, then keep it fixed.

To build the grid:

1. Block your hard commitments first. That means work, existing appointments, and anything you can't move.
2. Mark interview windows in the gaps. Where the employer's tool anchors slots to the interviewer, check that some windows overlap the interviewer's 9-5 in their zone.
3. Attach a buffer to each window. Block it before and after, as part of the window and not as optional padding.
4. Write the weekly cap at the top. Once the week holds that many live interviews, close the remaining windows for that week.
5. Give assessments their own blocks. They have no live slot, but they still need protected time before their deadlines.

If you're scheduling interviews while employed, the grid shrinks to the time you can really protect. That makes the cap more important, not less. Each interview costs leave or rearranged work, so a week with fewer, well-protected calls beats a week of squeezed-in ones. Look for overlap at the edges of your workday, and remember that a tool anchored to the interviewer's 9-5 won't show evenings unless the employer has set it up to.

Which invite to book first

Book links that can expire or run out of horizon first, then employers that move fast, then later-stage invites. Anything with a hard deadline goes before anything that will wait.

How to read each axis:

• Deadline pressure. A link with a stated expiry, a booking horizon nearly used up, or a short minimum notice that lets slots fill quickly. Calendly's default minimum notice is 4 hours, so its near-term slots can fill fast.
• Employer pace. The invite came soon after you applied, or it came as a self-scheduling link rather than a request for availability. What it proves: this employer is likely to move to the next stage quickly. When it lies: a fast first invite from a large, coordinator-led process can be followed by slow later rounds.

Sources disagree on the default. One recruiting source (Leon Staff) says to book the earliest available slot. Optimality's weekly cap argues for protecting your performance over raw speed. My position: book the earliest slot that fits the grid. Never take an off-grid slot just because it is early.

When the cap forces you to choose between two invites with no deadline, use fit as the tiebreaker. Refolk scores how well you fit each posting you applied to, which gives you a defensible reason to give the scarce slot to the stronger match instead of whichever email arrived first.

The booking procedure, step by step

Run these nine steps in order on the day a batch of invites arrives. Steps 1 to 6 happen in one sitting, step 7 runs until every reply is settled, and steps 8 and 9 happen only when needed.

Step 1: the inventory fields

Log six fields per invite: type, stage, date received, booking horizon or deadline, sender, and status (open, booked, answered, declined). The date received is what holds you to the one-business-day rule. The horizon is what sets the order.

Steps 4 and 5: booking and replying

A self-scheduling link takes a few minutes. One scheduling vendor (VidCruiter) claims it takes under 2 minutes, but that is a vendor figure. After each booking, wait for the confirmation email and compare its time to the grid before you open the next link.

For availability requests, the traditional recruiter email asks for three to five windows. Some Ashby setups require a minimum number of days, but no default is published, so read the request carefully. This reply covers both cases:

Subject: Re: Interview availability for [Role]

Hi [Name],

Thank you for the invitation. I'm based in [city] and working in [your time zone]. These windows work for me:

- [Day, date]: [start] to [end] [your zone] / [start] to [end] [their zone]
- [Day, date]: [start] to [end] [your zone] / [start] to [end] [their zone]
- [Day, date]: [start] to [end] [your zone] / [start] to [end] [their zone]

Could you confirm the format (video link, phone or on-site) and who I'll be meeting? If none of these suit the panel, I'm happy to look at times you suggest.

Best regards,
[Your name]

Spread the windows across different days. Three windows on one afternoon can all be killed by a single meeting.

Step 6: written confirmation

The calendar invite is the record. Check the local time it shows, the format, and the link or address. If the invite and the email disagree, reply and ask which one is correct before the day comes. Once a slot is confirmed, prepare from the materials that employer actually received. Refolk keeps the tailored resume and cover letter for each posting, so your preparation for a booked call starts from the version on the interviewer's screen rather than your master copy.

Hold and release, and the one reschedule you get

Never leave one window promised to two companies. The moment one books it, withdraw it from the other in the same sitting. A reschedule is a one-time move with 24 hours or more of notice and 2 to 3 alternatives. How long employers hold the windows you offered is not established publicly, so assume any offered window can be booked at any moment.

The hold-and-release protocol

1. Mark shared windows. In the inventory, tag any window you have offered to more than one company.
2. Book, then release immediately. When company A confirms a shared window, email company B in the same sitting with a short note: that window has gone, and here are one or two replacements from the grid.
3. Never let a shared window ride overnight. The risk isn't a rude email. It's two coordinators each booking the same hour while you sleep.
4. Prefer unique windows. Where the grid has room, give each company its own windows and avoid the problem entirely.

The one reschedule

Sources agree on ideally 24 to 48 hours or more of notice, and on offering 2 or 3 alternatives. Cronofy advises employers to keep their reschedule rate under 10%, which tells you employers track reschedules as a metric. Nobody publishes how many candidates drop out at the reschedule step.

Before you write, look for a reschedule link in the confirmation or reminder email. Greenhouse only offers one if an admin has enabled it. On Ashby, once the reschedule cutoff has passed, you can no longer reschedule through the booking link and must contact the organiser.

Subject: Request to move my [Role] interview on [date]

Hi [Name],

I need to ask to move my interview on [date] at [time, zone] because [one-line reason]. I'm sorry for the change.

I can do any of these instead:
- [Day, date], [time] [your zone] / [their zone]
- [Day, date], [time] [your zone] / [their zone]
- [Day, date], [time] [your zone] / [their zone]

Whichever works best, I'll keep it fixed.

Best regards,
[Your name]

How the booking run goes wrong

Most booking failures are silent. A link looks live but is dead, a time looks right but is in the wrong zone, or a reschedule option you assumed existed was never turned on. Each failure below gives what it looks like, what is actually happening, and the check that catches it.

1. The expired link

• Looks like: an unopened invite in your inbox that you assume still works.
• Actually: on Greenhouse the sender may have set the link to expire, and an expired link can't be used to book or reschedule. A cancelled request also deactivates the link while the email stays put.
• Check: open every link in the booking session on the day it arrives.

2. "No available times"

• Looks like: the role has filled or the employer has lost interest.
• Actually: usually the 30-day horizon, the interviewer's 9-5 window in their zone, or, on a single-interviewer Greenhouse link, one person's full calendar.
• Check: email the sender, say the link shows nothing, and ask whether they can turn on suggested times or send their own windows.

No available times is a statement about one calendar in one time zone, not about the role.

3. Slots read in the wrong zone

• Looks like: you booked 10:00 and turned up at 10:00.
• Actually: Greenhouse and Ashby hours are anchored to the interviewer, and Ashby guesses your zone from your location if none is saved. Calendly, by contrast, shows your zone.
• Check: compare the time in the confirmation email with the time in your own calendar, and write both zones in every reply.

4. Daylight-saving drift

• Looks like: a cross-border slot that was right when you booked it.
• Actually: on Zoom, a meeting stays at the same time for the host across a daylight-saving change, so your local time can shift by exactly one hour. Users also report the dropdown offering only EST for a March date that falls in EDT.
• Check: reconfirm within 48 hours of the interview, every time a daylight-saving change sits between booking and interview day.

5. The silent reschedule block

• Looks like: you plan to use the link to move the slot if needed.
• Actually: self-rescheduling is off unless the employer enables it, and Ashby's cutoff sends you to the organiser.
• Check: look for a reschedule link in the reminder email before you rely on one.

6. The open-tracking signal

• Looks like: opening a link to look costs nothing.
• Actually: a secondary source claims recruiters can see a link opened three times without a booking. I could not verify this at the primary source.
• Check: open a link only when you're ready to book. Doing the inventory and booking in one session the day links arrive covers both this and failure 1.

7. The second reschedule

• Looks like: a reasonable request, given the first one went smoothly.
• Actually: every source treats it as disqualifying in practice.
• Check: never move a slot that has already moved.

There is also a quieter failure: a cap that looks right but has broken. Two interviews end up on one day because a coordinator booked a window you had already released, or because a panel was split into sessions. The weekly count can be fine while one day is overloaded. Count by day as well as by week.

Keeping the week current

The run isn't a one-off. Repeat the intake every day new invites arrive, and reconfirm every interview within 48 hours of its date. A booked week drifts as new invites, releases and daylight-saving changes arrive, so the grid has to be updated as often as the inbox.

Each day:

• New invites go straight into the inventory. They then get booked or answered within one business day.
• The grid is updated as soon as anything changes. Close each booked window, release each withdrawn one, and close the rest of the week once you reach the cap.
• Check the week ahead each evening. Run steps 6 and 9 for anything within 48 hours.

Where this guide relies on thin evidence, check locally. Buffer length, how long employers hold offered windows, and defaults for tools beyond Greenhouse, Ashby and Calendly are not publicly established. The source of truth is whatever each employer's link page and confirmation email actually say. If a tool behaves differently from the table above, trust the confirmation in front of you and write the difference into your inventory.