A booked interview can still hide stalled ownership. This control-board workflow helps U.S. and Canadian staffing agencies move candidates through scheduling, exceptions, and feedback.
A candidate can sit at "interview" in the ATS for days while nobody can answer a basic question: who must move this forward? For staffing and recruiting agency owners serving employers and candidates across the United States and Canada, that blind spot turns an interview scheduling workflow into calendar links, inbox threads, and quiet delays. Another reminder will not fix it. The agency needs a control system that defines when a candidate is ready to schedule, who owns each wait, and what happens when a booking breaks.
Here is a practical version that runs from client intake through post-interview feedback. It includes an interview-control board your team can test without replacing its ATS or calendar tools.
Interview coordination starts before anyone opens a calendar. The recruiter needs a qualified candidate. The client has to confirm the format and decision-makers. The candidate needs a clear next step. After the meeting, someone must collect feedback and decide whether to advance, hold, or close the process. A booked event proves only that one transition happened.
Scheduling products can remove real administrative work. Greenhouse, for example, documents self-scheduling for a candidate choosing from interviewer availability, while noting that multi-session interview stages still require the recruiter to use the regular scheduling flow. Its automated scheduling documentation shows that candidate preferences, interviewer availability, working hours, and invitation steps remain separate inputs and actions. Software can find a time. The agency still has to define what "ready," "confirmed," and "complete" mean.
PASMO's view is simple: "calendar link sent" is an open request, not progress by itself. Until the candidate books, the required interviewers accept, and the meeting details exist, the pipeline is waiting on a named person or decision.
A first version needs a short readiness rule. Before scheduling opens, the recruiter or coordinator should confirm the role, interview stage, required interviewers, meeting format, expected duration, candidate time zone, and the person authorized to resolve conflicts. Agencies working across the United States and Canada should store the time zone as data instead of burying it in an email sentence. "9:00" is not a complete appointment when the candidate, recruiter, and client may be in different zones.
The readiness rule should expose client-side gaps too. If a hiring manager has not named a backup interviewer, the agency does not have a scheduling problem yet. It has an ownership problem. If a panel needs three people but only one has shared usable availability, automation will reveal the constraint, not remove it.
Keep this rule small at first. Do not wait for a perfect interview-plan template across every client. Pick the fields that prevent the most common reversals, make them mandatory for one workflow, and record an explicit exception when someone proceeds without them.
The control board can live in the ATS, a connected operations table, or a shared view. Each row needs the candidate, client, role, interview stage, current state, next-action owner, due time, and latest meaningful event. Avoid a free-text status such as "scheduling." It hides several different waits.
| State | Required owner | Exit condition |
|---|---|---|
| Not ready | Recruiter | Role, stage, format, duration, interviewers, and candidate time zone are confirmed |
| Waiting on client | Client contact | Availability or a replacement interviewer is supplied |
| Waiting on candidate | Candidate coordinator | The candidate selects or proposes an acceptable time |
| Pending confirmation | Coordinator | Invites, meeting details, and required acceptances are present |
| At risk | Named exception owner | A conflict, decline, or missing detail is resolved or escalated |
| Feedback due | Recruiter or client lead | The decision and next candidate communication are recorded |
A row should change state because something happened, not because someone remembered to tidy the board. Submitted availability can move it to pending confirmation. A declined interviewer can move it to at risk. Once the interview ends, the row moves to feedback due instead of vanishing into a generic completed column.
The awkward work starts when the happy path breaks. A candidate requests an evening slot. The client changes the panel. An interviewer declines after the candidate accepts. A video link is missing shortly before the call. Each situation carries a different consequence, so one automated "please reschedule" message is a poor answer.
Give every exception a deadline and an owner. The coordinator can handle ordinary availability gaps. The recruiter should own candidate-sensitive changes and decide how to explain them. The client lead resolves repeated interviewer unavailability or missing feedback. The agency owner only needs escalation when a client repeatedly misses the operating agreement or the workflow exposes a capacity problem.
For cancellations, use a fixed recovery sequence: capture who cancelled and why, preserve the interview stage, assign the next action, send the appropriate message, and reopen scheduling with a deadline. Do not create a duplicate candidate stage merely to restart the calendar. That fragments the history and makes later bottleneck analysis unreliable.
Start with one client, one recurring role type, and one interview stage for two weeks. Choose a stage with enough volume to reveal delays but not so much complexity that the team cannot inspect every exception. Keep the existing calendars and ATS. The pilot is testing definitions, ownership, and transitions. It is not a technology-purchase exercise.
Review four transition measures: time from ready to first scheduling action, time from request to confirmed booking, number of rows that enter at risk, and time from interview completion to recorded feedback. Then sample a few candidate records manually. A faster average can still conceal a small group of people stranded without an owner.
At the end, remove fields nobody used and tighten any state that staff interpreted differently. Then decide which exceptions deserve automation. Stable reminders and state changes are sensible candidates. Decisions about candidate communication, client escalation, or swapping interviewers should stay with a person until the agency has clear rules and enough evidence to move that boundary.
If your recruiting team has plenty of calendar automation but still spends the day chasing confirmations and feedback, PASMO can help map the handoffs, design the control board, and connect a reliable first version to the tools you already use.