AI Screening Setup: Campus Drive vs. Lateral Hire

One Tuesday afternoon, a TA lead at a mid-size IT services firm set up two HireQwik campaigns back to back: a 2,800-candidate campus drive for a support-engineer role, and a 4-candidate lateral search for a senior architect opening. Same setup screen, same four steps, same “paste the JD, connect the sheet” flow. What she configured inside those screens looked almost nothing alike. That gap — same tool, different setup choices — is what this post walks through, for anyone about to run AI screening setup for campus vs lateral hiring at the same company.

If you haven’t set up a campaign before, start with our step-by-step setup guide — this post assumes you know the four steps and focuses specifically on what changes between a high-volume campus drive and a small, senior lateral search.

The five setup choices that diverge

Before the details, here’s the shape of the difference at a glance:

The rest of this post walks through why each of these five diverges, not just that it does.

The rubric review takes longer for lateral, not shorter

For both campaign types, HireQwik drafts a scoring rubric automatically from the JD. The mistake teams make is assuming a small candidate pool means a quick rubric review. It’s the opposite. A campus JD for a support-engineer role is usually written tightly — clear degree requirement, clear technical baseline, clear communication expectation — because the hiring manager has written dozens of versions of it before. A senior architect JD is often looser: “10+ years, strong system design background, leadership experience” reads reasonable to a human and produces a rubric with more room for the auto-generated version to miss nuance the hiring manager actually cares about. For a campus drive, a five-minute rubric skim is usually enough. For a lateral senior search, budget real time to sit with the drafted rubric and correct anything that reads generic — a bad rubric on 4 candidates costs you a meaningfully higher share of your total pool than a bad rubric on 2,800 does.

Knockout questions serve opposite purposes

On a campus drive, knockout questions exist to protect recruiter time at scale — a hard disqualifier (a specific certification, a location requirement, a minimum CGPA) ends the call in the first two minutes so nobody spends 15 minutes interviewing someone who was never eligible. With 2,800 applicants, even a small percentage failing an obvious knockout adds up to hours of screening time saved.

On a lateral search, the volume math doesn’t justify the same aggressiveness — you have 4 candidates, not 2,800, so ending a call early doesn’t save meaningful recruiter time. But knockouts still matter for a different reason: they enforce a hard requirement consistently across a tiny pool where a human interviewer might unconsciously bend the rule for a candidate they like on paper. If “must have led a team of 5+” is a genuine requirement, a knockout question makes sure it gets checked the same way for candidate 1 and candidate 4, instead of being asked more or less rigorously depending on how the conversation is going.

Auto-decide bands: turn on for volume, leave off for judgment calls

This is the setup choice with the clearest campus-vs-lateral split. Auto-decide lets you set thresholds so candidates scoring below a reject cutoff or above a fast-track cutoff get sorted automatically, leaving only the middle band in HR’s manual review queue. On a 2,800-candidate drive, that’s close to essential — without it, HR is manually reviewing a Strong Go candidate who scored 96% just as carefully as a borderline one who scored 61%, which is not a good use of anyone’s time.

On a 4-candidate lateral search, we’d generally advise leaving auto-decide off, or setting thresholds far more conservative than you would for campus. With so few candidates, the cost of a human spending 10 extra minutes reviewing every single one is trivial, and the cost of an automated system making a wrong call on 25% of your total pool is not. Auto-decide is a volume tool, and recruiting-coordination research bears that out: the time savings from automation compound with volume, which is exactly why a tool built for 2,800 candidates doesn’t automatically make sense for 4. At lateral-hire volumes, the volume problem it solves mostly doesn’t exist yet.

Scheduling windows and reschedule pressure run in opposite directions

Campus drives run on a compressed clock — you’re often trying to close a screening phase within days, so a tight self-schedule window (interviews available for the next 48-72 hours) keeps the whole drive moving. Lateral candidates are almost always currently employed, which means they’re screening around a live job, and a 48-hour window is often unrealistic. One recruiting-ops breakdown of passive-candidate hiring makes the same point from the other direction: candidates who aren’t actively job-hunting weigh scheduling flexibility as heavily as the role itself, since they’re fitting your process around a job they’re not leaving yet. Give lateral searches more scheduling runway.

That difference matters for HireQwik’s reschedule limit too, which caps every candidate at 3 reschedule attempts within 72 hours of their first booking regardless of campaign type. On a campus drive, a candidate who burns through 3 reschedules inside 72 hours is usually a low-intent applicant and the lock is a reasonable filter. On a lateral search, a currently-employed senior candidate juggling a live job and two other interview processes can hit that same limit for entirely legitimate reasons — a client emergency, a manager pulling them into back-to-back meetings. It’s worth telling your recruiters up front that a locked slot picker on a lateral candidate isn’t automatically a red flag the way it more often is on a campus applicant, so nobody drops a strong senior candidate over a scheduling technicality.

Sheet structure: one big sheet vs. several small ones

Campus drives typically funnel from a single source — a careers-page form, one ATS export, one placement-cell spreadsheet — so one connected sheet per JD, growing continuously, is the natural structure behind HireQwik’s trigger-based screening. Lateral searches more often pull from several sources at once: a recruiter’s manual sourcing list, a referral tracker, an agency submission sheet. Rather than merging those into one sheet (which usually means someone manually copy-pasting rows and occasionally duplicating a candidate), it’s cleaner to connect whichever single sheet is the recruiter’s actual working list and treat the others as feeders that get copied in — small enough volume that manual consolidation before the sheet connects is faster than building an automated merge.

How long to leave a campaign open

Campus drives are built around a fixed window by design — the sheet fills quickly, the drive screens through a defined batch, and the campaign effectively closes once that batch is processed, even if the trigger config technically stays live. A campus JD trigger left open indefinitely just keeps accepting stragglers from a placement cell weeks after the real drive ended, at which point candidates are getting invited into a process the hiring manager has mentally already closed.

A lateral search behaves the opposite way. There’s rarely a single batch — candidates arrive one or two at a time over weeks, from sourcing, referrals, and inbound applications, and the JD trigger genuinely should stay open until the role is filled. The practical implication for setup: build a habit of checking in on campus campaigns to close them out once the batch is screened, while lateral campaigns need essentially the opposite discipline — remembering to actually close them once an offer goes out, since nothing else naturally signals that the campaign is done.

What doesn’t change between the two

It’s worth naming what stays identical, because it’s easy to assume everything is different: the self-schedule flow with its calendar .ics invite works the same way for both. The HR dashboard sorts both into the same Strong Go / Go / On Hold / No Go verdict structure. And the underlying screening conversation format — a structured voice interview rather than a resume keyword match — doesn’t change based on seniority. What changes is entirely in the setup choices: how tightly you review the rubric, how aggressively you use knockouts and auto-decide, and how much scheduling slack you build in.

If a campaign of either type looks configured correctly but candidates aren’t flowing through, the cause is rarely the campus-vs-lateral distinction itself — it’s usually one of the six causes we cover in why a Google Sheet stops triggering interviews, which apply the same way regardless of which setup choices you made above.

Setting up two campaigns from the same JD-upload screen doesn’t mean configuring them the same way. Treat the rubric review, the knockout list, auto-decide, and scheduling windows as four separate decisions each time, and the setup screen does the rest. If you’re planning a mixed batch of campus and lateral requisitions and want a second opinion on where to set the thresholds, talk to us before you go live rather than guessing on the first one.