Move a completed client interview to a usable evaluation, an authorized next step and a recorded candidate update. Keep those three handoffs separate so a returned form does not hide an unfinished decision.
A client manager sends the agency a short message: “Good interview; waiting for the team.” The recruiter marks feedback received. The candidate still has no next step, the account manager cannot promise another interview, and nobody owns the remaining decision.
A staffing interview feedback workflow should close that gap. It turns a completed interview into an accountable sequence: collect job-related evidence, obtain the client’s authorized disposition, then communicate the approved outcome or an honest interim update. It belongs in the Review → Engage part of the external-worker lifecycle, before assignment acceptance and onboarding.
This is a recommended operating method for staffing agency account managers, recruiters and client program owners. It does not set a legal response deadline or replace your client’s hiring policy. Set timing, information access and approval authority for the actual engagement.
Agree the handoff before the interview finishes
The agency account manager owns the cross-company case. The client names the person who can approve the next step and a backup for absences. Interviewers provide evidence; the candidate-facing recruiter communicates only what has been authorized. One person may hold several roles, but the responsibilities should remain explicit.
Use the approved job order to establish the role, interview stage, criteria, reviewer and expected response window. The staffing job order intake checklist covers those upstream agreements. This workflow starts once a specific interview has actually happened; a cancelled appointment should return to scheduling, not start a feedback clock.
Confirm completion and its timestamp with the responsible participant. Attach the candidate and requisition references, interview stage, client decision owner, agency case owner, response due date and candidate’s promised update date. Record the timezone and business-hours convention rather than writing “tomorrow” into a shared case.
Robert Half’s interview protocol recommends making notes promptly, gathering other interviewers’ feedback while the discussion is fresh, and telling candidates when to expect contact. Translate that guidance into named actions rather than another reminder with no owner.
Keep three clocks, not one feedback checkbox
The distinction is operational: information arriving, authority being exercised and the candidate being told are different events. Maintain a compact case register with the following fields. A shared record can implement it; you do not need a new application to test the process.
| Clock | Start and completion evidence | Owner and open-work test |
|---|---|---|
| Evaluation | Starts at confirmed interview completion; ends when the required job-related notes and recommendation are accepted as usable. | Client interviewer supplies evidence; agency case owner checks completeness. A blank form or unexplained rating does not close it. |
| Decision | Starts at interview completion; ends when the named client authority approves advance, decline, a defined hold, or a specific further assessment. | Client decision owner. An interviewer’s positive reaction is not necessarily approval to make an offer. |
| Candidate update | Starts at interview completion; records the first substantive update, each promised follow-up and final outcome communication separately. | Candidate-facing recruiter. Sending an interim update does not close an unresolved decision. |
Also retain the current blocker, next action, action owner, due time, original evaluation reference and communication record. Keep the first agreed deadline when a revised one is approved; otherwise repeated extensions make a late case appear on time.
For comparison, PersiaHR’s feedback response-time documentation describes measuring how long candidates wait for a response or decision after a hiring stage. The three-clock register here is a proposed operating design, not a claim about that product or a universal industry standard.
Route each response to an executable next state
At the agreed deadline, ask what is missing—not simply whether the client replied. A useful evaluation addresses the agreed role criteria, gives supporting observations and distinguishes a recommendation from a decision. Use the existing interview scorecard template if the evaluation itself needs structure; do not invent a second scoring method inside this handoff.
| Case state | Responsible action | Evidence needed to leave the state |
|---|---|---|
| Awaiting evaluation | Case owner requests the missing interview record from the named reviewer; account manager contacts the backup if the agreed window is missed. | Usable evaluation or a documented blocker with a new owner and review time. |
| Evaluation incomplete | Return the specific missing criterion or unexplained recommendation to its author. Do not rewrite an interviewer’s judgment on their behalf. | Clarification linked to the original record; preserve the earlier version. |
| Panel disagreement | Client decision owner arranges a criterion-based review. Identify whether more evidence is genuinely needed. | Authorized disposition and rationale, or a defined assessment with owner and due date. |
| Decision awaiting authority | Route the recommendation to the delegated approver. Recruiter sends an accurate interim update by the promised contact time. | Approval reference, permitted next action and any conditions. |
| Role or terms changed | Account manager returns the change to the job-order owner. Confirm whether the candidate still wants the revised opportunity. | Approved revised brief and candidate response before treating earlier interest as current acceptance. |
| Disposition authorized | Recruiter communicates advance, decline or the defined hold; coordinator creates the approved next task. | Message or conversation record, next owner and outstanding acknowledgment where needed. |
Silence is not a rejection, and praise is not an offer. If the client cannot decide, ask the authorized owner to specify what remains open, who will resolve it and the next review point. An indefinite hold should remain visible as unresolved work, not disappear into “feedback complete.”
Update the candidate without inventing a decision
Agree one candidate-facing contact so the client, recruiter and account manager do not issue conflicting messages. An interim update should say what is known, what remains undecided and when the recruiter will next make contact. Do not imply that a delay means success, rejection or a guaranteed start date.
Separate internal evaluation notes from the explanation approved for sharing. Confirm the recipient and role before sending, share only relevant information through your approved channel, and route sensitive or inappropriate comments to the client’s HR or policy owner rather than forwarding them verbatim. Do not circulate another applicant’s evaluation to explain a comparison.
Once a rejection is authorized, the candidate rejection email templates cover the downstream message. For an advance, confirm the next interview or assignment step and any outstanding conditions. Sending an invitation is not proof that the candidate accepted it; retain the acknowledgment or leave the scheduling task open.
Worked example: returned notes, unfinished placement
Illustrative case: an agency places contract analysts with a client. A Tuesday interview ends at 11:00 CT. The parties have chosen a Wednesday noon evaluation deadline and promised the candidate a Wednesday 15:00 update. These are sample operating choices, not required or recommended universal turnaround times.
The interviewer returns notes Tuesday afternoon and recommends advancing. A second panel member has not supplied evidence for an agreed requirement, and the client sponsor must authorize the next stage. The case owner records “evaluation incomplete,” names the missing input and leaves both the decision and final communication open.
At Wednesday noon the missing note arrives. The evaluation clock can close, but the sponsor is unavailable. The account manager activates the agreed backup approval route. Before 15:00 the recruiter tells the candidate the review is still awaiting an authorized next step and gives a specific follow-up time, without promising an offer.
On Thursday the delegated client approver authorizes a final interview. The recruiter communicates that decision and the coordinator requests availability. The feedback case can record its outcome communication, while a linked scheduling task remains open until the time is agreed. The timeline exposes the approval delay rather than blaming a completed evaluation or claiming an unconfirmed booking.
Where Workhint fits
The Workhint Workflow Engine describes configurable request, approval and assignment steps, routing to defined roles, and required details, files or notes before work progresses. Those building blocks are relevant to separating an evaluation submission from a client-authorized next step.
The Workhint solution for staffing managers describes reviewing worker profiles, skills, documents and availability before approval into a staffing network. That is the relevant staffing context; it does not establish a prebuilt interview-feedback module or automatic synchronization with a client’s applicant tracking system.
A practical configuration brief is to capture candidate, job order, interview completion, evaluation reference, decision authority and update commitments; assign missing-input and approval reviews to named roles; and require disposition evidence before release to the next task. Treat that as proposed workflow requirements. Test an incomplete form, absent approver and changed role with sample cases before relying on the configured system. Keep any unverified external-system transfer manual and accountable.
Review open cases as well as completed response times
At the team’s chosen review cadence, list overdue evaluations, decisions awaiting authority and missed candidate-update commitments separately. Include unresolved cases and their age; an average calculated only from completed responses can hide the longest waits. Distinguish elapsed time from business-hours time and use one documented convention.
Review recurring causes with the client: unclear criteria, missing panel evidence, unavailable approvers or changed requirements. Change the handoff responsible for the delay instead of sending more generic reminders. Close a case only when its approved disposition, communication evidence and next owner are recorded.
FAQ
How quickly should a staffing client return interview feedback?
Agree a response window for the role, urgency, panel and approval process before interviewing. Record separate expectations for usable evaluation and authorized next steps. This guide does not prescribe a legal deadline or universal benchmark.
Does a completed scorecard mean the candidate can advance?
Not necessarily. A scorecard records evaluation; the delegated client authority must still approve the next action if that is the agreed process. Keep those events separate.
What should the recruiter do if the client is late?
Escalate through the named account and client owners, identify the actual blocker and keep the candidate’s promised update. Share an accurate interim status rather than infer a hiring outcome from silence.
Can one case cover several candidates?
A job order can provide shared rules, but keep candidate-specific evidence, decisions and messages distinct. A panel debrief does not prove that each person received the appropriate update.
Leave a Reply