What to Send the Placement Cell After a Drive Closes

A placement officer’s actual question after a drive, almost every time, is some version of “who cleared, who did not, and can you tell me why.” Not a dashboard link. Not a promise to follow up. A list, with a reason column that isn’t blank, sent back inside a day or two while the drive is still fresh enough for the college to explain results to the students who ask.

Most employers are bad at this, not out of indifference but because the reason column is genuinely hard to fill in by hand. A recruiter who ran forty phone screens personally can recall roughly why each one went the way it did. A recruiter reviewing the output of an AI-screened drive across three hundred candidates has no equivalent memory to draw on, and if the screening tool doesn’t hand over a specific reason per candidate, “we did not select them at this time” becomes the only honest thing left to write, which is also the least useful thing a placement cell can pass along to a rejected student.

Why the reason column is the actual deliverable

A placement cell isn’t asking who got the job for its own sake, colleges already know their offer count from the joining letters. What they’re asking for is something they can say to the sixty students who didn’t get an offer, because those students go back to the same TPO’s office asking what they should work on next season. Training and placement cells are explicitly measured on this kind of student-facing follow-through as part of the role, not just on placement rates, which is exactly why “no reason given” reads as a broken relationship rather than a minor omission.

Where the reason actually lives in HireQwik

Every candidate who reaches a verdict in a HireQwik drive lands in one of four bands: Strong Go, Go, On Hold, or No Go, visible per candidate in HR’s dashboard. For candidates who didn’t reach a full interview at all, a more specific tag exists: a failed phase-0 knockout question ends the call inside the first one to two minutes and gets logged as a Reject verdict tagged “knockout,” which is a materially different and more useful thing to tell a placement cell than a generic no. “Did not meet the JD’s minimum notice-period requirement” is something a TPO can relay to a student and have them understand immediately. “Did not proceed” is not.

Combined with the resume-match score that ran before the interview stage, HR has two layers of reason available for any candidate: a pre-call relevance score if they never got invited, and a knockout tag or interview verdict if they did. Building the results report is largely a matter of exporting those two columns per candidate, not writing new explanations from scratch.

What actually goes in the report

A results report a placement cell can use has, at minimum, four columns per candidate: name or roll number, the stage they reached, the verdict or reason, and whether they received an offer. What separates a useful version from a frustrating one is that middle column being specific rather than generic. “Rejected at resume stage, below JD match threshold” and “rejected at interview, knockout: notice period exceeds 60 days” are both things a TPO can explain in thirty seconds. “Not selected” forces the TPO to either guess or tell the student to ask the recruiter directly, which usually goes nowhere because that recruiter is already three drives further into the season.

For the On Hold band specifically, resist the urge to report those candidates as either a yes or a no before HR has actually made a final call. Placement cells generally accept “still under review, decision expected by [date]” as an honest status, more so than a report that quietly recodes every On Hold as a rejection just to close out the spreadsheet on time.

What the report actually looks like, row by row

Here is roughly what a workable export looks like for four candidates out of a larger batch:

Four rows, four different outcomes, and every non-offer row still tells the student something specific enough to act on. The 21CS077 row in particular is the one most reports get wrong: a generic export would show “rejected” with nothing else, when the actual, dashboard-visible reason is a single disqualifying answer about availability, not a broader judgment on the candidate’s ability.

When a placement cell pushes back on a result

Occasionally a TPO will write back disputing a specific rejection, usually for a student they know well and expected to do better. The knockout tag and resume-match score make this conversation short instead of defensive: pull up that one candidate’s record, read back the exact question that triggered the knockout or the specific relevance gap in the resume score, and either confirm the result stands or flag it for a manual second look if something looks genuinely off, like a resume-parsing error on an unusual formatting choice. What you want to avoid is a placement cell developing the sense that “not selected” is a black box no one can explain even when directly asked, because that’s what erodes a college relationship faster than any individual rejection does.

The timing question, and why async screening changes it

A placement cell asking for results the same evening a drive closes isn’t being impatient, it’s normal for a well-run campus to expect same-day or next-day results as the standard, not the exception. That timeline is realistic for HireQwik specifically because the interview itself doesn’t require a recruiter to sit through each call: candidates self-schedule and complete a structured voice screen on their own time within the drive window, and the verdict is generated as soon as the call ends, not batched for a recruiter to review one by one afterward. A drive that closes its interview window at 9 PM can have every verdict populated well before HR’s team is back at their desks the next morning, because the screening itself ran overnight without a human bottleneck in the loop.

That said, do not report results the moment every candidate has a verdict if any candidates are still sitting in the Needs Review band waiting on a human decision. The honest promise to a placement cell is “results by tomorrow morning for everyone who has a final verdict, with the handful still under review flagged separately,” not a report that looks complete but silently omits the cases HR hasn’t actually decided on yet.

What we deliberately don’t claim here

There’s no published industry standard for how fast an employer owes a placement cell a results report, and this isn’t proposing one. What’s above is what our own drives have supported operationally, given how the verdict pipeline works, not a service-level commitment every vendor or every employer can match. A drive running a smaller candidate pool through manual phone screens will structurally take longer to produce reasons for every rejection, because there’s no equivalent of a knockout tag being generated automatically as each call happens. That’s a genuine tradeoff of screening at scale by hand, not a criticism of teams doing it that way.

The summary number a placement cell also wants

Alongside the per-candidate rows, most TPOs also ask for a short summary at the top: how many applied, how many reached interview, how many received offers, and where in the pipeline the biggest drop happened. This is a byproduct of the same data, not a separate report to build. If seventy resumes came in and only twelve reached an interview, the summary line “58 did not clear the JD’s minimum relevance threshold at the resume stage” tells a TPO where to focus student preparation for the next drive, which is a more useful thing to receive than a raw twelve-out-of-seventy ratio with no explanation of where the funnel narrowed. A placement cell that understands its students are consistently getting filtered at the resume stage, not the interview stage, can act on that by working with faculty on resume quality before the next company visits, instead of guessing that interview performance is the problem when it isn’t.

What about candidates who never joined the call

Not every non-offer outcome comes from a knockout or a low score. Some candidates clear the resume stage, get a self-schedule link with a calendar invite attached, and then never actually book a slot, or book one and reschedule until they hit HireQwik’s limit of three reschedule attempts within 72 hours of the first booking, at which point the slot picker locks and the candidate needs HR to manually reset it before trying again. If nobody does, that candidate sits in an unresolved state that a simple pass or fail export tends to flatten into “did not proceed,” the same unhelpful phrase this whole report is trying to avoid.

The more honest row for this case is “did not complete scheduling” or “reschedule limit reached, no follow-up requested,” distinct from both a knockout Reject and a below-threshold resume score. It tells a placement cell something genuinely different: this student was invited and qualified enough to reach the interview stage, but something on the logistics side, not the screening itself, is why they don’t show up in the interview-complete rows. That distinction matters for a TPO working with a specific student afterward, because the advice is completely different. A knockout Reject means work on a specific gap. A stalled booking means check in with the student about whether they actually saw the invite, since colleges commonly report students missing self-schedule emails that land in a promotions tab or get buried under other placement-season mail.

It’s worth resisting the temptation to lump this category in with genuine No Go verdicts just to keep the report to three clean columns. A student who never received a usable invite and a student who was interviewed and scored poorly are not the same outcome, and a placement cell that later discovers the first group was miscounted as the second loses trust in every other row of the report along with it, not just that one line.

Building this row is the same export habit as the rest of the report: pull whoever cleared the resume stage but has no interview-complete verdict once the drive’s booking window closes, and split them by whether they never opened a slot at all versus hit the reschedule ceiling without resolving it. That split alone answers most of the “wait, what happened to this student” follow-ups before they’re even asked.

The take

The gap most employers have with placement cells isn’t speed, it’s specificity. A same-day list with a blank reason column earns the same frustrated follow-up email as a report sent a week late. The knockout tag and the resume-match score already sitting in HireQwik’s dashboard are what turn “not selected” into something a TPO can actually explain to a student, and building that habit into how a drive closes costs a recruiter one export, not a new process.

If you’re running a drive across more than one campus, pair this with keeping one college’s cohort from crowding out the others on the combined shortlist, since a placement cell asking why its students look thin on the results report is often the same underlying visibility problem showing up on the other side of the drive. And for the candidate-facing side of a knockout rejection specifically, silence is usually the worse failure mode, not the reason itself, as covered in the case against silent rejection.