Campus Recruiting Coordination: Running a Season, Not a Req

The fall calendar looks manageable in July. Four schools, two career fairs, a bootcamp partner cohort, a couple of virtual sessions. Someone builds a spreadsheet with dates in it and everyone agrees it is handled.

Then a single afternoon in late September puts your recruiters in front of a few thousand candidates, and the interview requests arrive the next morning. Not spread over six weeks like a normal req. All at once, for the same three interviewers, against the same four rooms, with feedback expected before those candidates finish talking to everyone else.

Nothing about that is a sourcing failure. It is what happens when a process designed to handle hard things one at a time gets handed all of them in the same week.

This Is a Cohort Problem, Not a School Problem

Campus is where this shows up most sharply, which is why it gets the name. But nothing about the problem requires a school.

* Bootcamp and training partnerships that graduate thirty or forty people in the same week.

* Apprenticeship and returnship cohorts with one intake date a year.

* Rotational and graduate programs where every hire has to start together.

* Seasonal ramps before a retail, warehouse or support peak, which are batched without being early-career in any sense.

* Military transition programs where candidates become available on a fixed separation timeline.

All of them deliver hiring as a batch instead of a queue, and all of them break in the same place. If your team runs any intake with a fixed start date and a fixed group, the rest of this applies whether or not anyone visits a campus. The external benchmarks below are drawn from college recruiting, because that is where the research is, but the structure they describe is not school-specific.

Campus Recruiting Is a Batch, Not a Queue

In req-based hiring, difficulty is sequential. A hard panel this week is followed by a straightforward screen next week, and the gaps between hard things are where a team recovers. Nobody plans those gaps. They just exist, and they quietly do most of the work of keeping a coordination process viable.

A batched season removes them. One university career fair can put 400 employers and more than 4,000 students in the same building across a five-hour afternoon, with on-campus interviews scheduled for the following day. Handshake's platform data puts September and January as the two peak months for internship recruiting, which means the concentration is not one bad week you got unlucky with. It is the structure of the season.

NACE's benchmarking finds roughly 70% of employers now recruit in both fall and spring for full-time and internship roles, and the timing of offers has shifted with it: fall and winter offers fell from 81% in 2023 to just under 64%, while spring and summer rose from 19% to over a third. The batch has not flattened out. It has split into two, which means most teams now run their heaviest coordination weeks twice a year instead of once.

Swap the career fair for a bootcamp demo day, an apprenticeship intake or a pre-peak seasonal ramp and the shape is identical. Only the owner of the calendar changes.

The Clock Is Closing From Both Ends

This is the number that should decide how you staff the season. Two figures from the same NACE benchmark series, moving in opposite directions: the employer clock lengthened from just under 25 days in 2021 to 27.3 days, and the student response window contracted from around 14 days to 9.

A four-week decision cycle against a nine-day answer window is not a candidate experience problem. It is an arithmetic problem. And the market is tight enough that it bites: NACE's 2026 student survey puts the average graduating senior at 0.79 job offers, with 43% holding an offer before graduation day. When a candidate does have two offers, the one that arrived first is not competing on merit anymore.

Renege rates track this directly. NACE puts them at roughly 7% for full-time offers and 10% for internships, and the full-time figure rose again in the 2025 benchmark cycle. A renege in a batch is worse than a renege in a queue, because the backup candidates were interviewed in the same two weeks and have already made their decisions by the time you get back to them.

Those specific figures are college data. The structure behind them is not. Any cohort interviewing in parallel produces the same race between your decision cycle and their answer window, and a bootcamp cohort fielding offers in the same fortnight behaves exactly like a graduating class.

Panels Are the Format These Seasons Run On, and the Hardest to Schedule

Multi-interviewer formats do not scale the way single interviews do. Every additional interviewer is another calendar that has to stay clean, and the coordination cost tracks the number of connections between sessions rather than the number of sessions. Ashby's data across 5.1 million interview events puts the practical effect plainly: 34% of panels get scheduled within a day, against 54% of single-event interviews. That is all-hiring platform data, not campus data, which is the point. The penalty is in the format, not the source.

Cohort hiring runs on panels almost exclusively, and it runs them in blocks: assessment centers, on-campus interview days, bootcamp partner days, rotational program loops. Our own platform data says what that costs when it is worked by hand. Availability-based coordination averages 243 minutes of back-and-forth per interview, against 27 minutes when a candidate self-schedules. A single 40-interview day is therefore about 162 hours of coordination behind it, or roughly four weeks for one person. We broke that arithmetic down in detail in our piece on what it takes to run 40 interviews in one day.

Then add churn. The structural reschedule rate across recruiting organizations runs at 14%, and manual decline handling in our data sits unresolved for about 68 hours. In req-based hiring, a 68-hour rebuild cycle is invisible. In a batched season, it is longer than the notice you get.

Staff for the Peak Day, Not the Average

Most cohort plans are built on annual volume divided by weeks, which produces a number that is true and useless. The season does not arrive at the average. It arrives at the peak, and the peak is what your staffing has to survive.

The capacity side has been moving the wrong way. Ashby's benchmarks show coordinator headcount per organization falling from roughly four in early 2022 to about two by the end of 2023, while the coordinators who remain schedule anywhere from 14 to 47 interviews a week depending on the team. SHRM's 2026 benchmarking puts the median recruiter at 25 requisitions, rising to 100 at the largest organizations. A cohort intake lands on top of that, not instead of it.

Volume is not shrinking to meet the smaller team. NACE's spring 2026 update has employers planning 5.6% more new graduate hires, and 8.7% more at organizations with over 5,000 employees. Internship hiring is up 3.9%, with intern conversion at 63.1%, its highest in five years. Against a median annual college recruiting budget of $114,000, almost none of which is coordination capacity, the peak is where the program is actually decided.

Four Things to Change Before the Season Starts

* Commit interviewers for the season, not per interview. Per-interview asks work in a queue because each one is small and separable. In a batch, the same interviewer gets asked eleven times in two weeks and starts declining around the sixth. Get a season-level commitment in writing, with named alternates per interview type, before the first event.

* Set the feedback deadline before day one. Same-day feedback is what batched hiring needs and what nobody agrees to under pressure. Pick the turnaround while the calendar is still theoretical, put it in the interviewer commitment, and make the scorecard the thing that closes the loop rather than a debrief you have to schedule.

* Stop collecting availability by email. This is where the 243-minute figure earns its keep. Every hour spent reconciling calendars by hand is an hour the finished schedule has to survive unchanged, and at a 14% reschedule rate it will not. Our guides to interview scheduling best practices and automated interview scheduling cover the mechanics.

* Instrument two numbers now. Your reschedule rate and your decline turnaround are the only two figures that predict whether a batched season holds. Measure them in August on ordinary reqs, while there is still time to fix what they tell you. Our list of interview coordination metrics covers what to instrument first, and reducing coordinator workload covers what to do about it.

One honest caveat on the internal figures here. This is one platform's data, weighted toward enterprise teams running complex panel loops, and cohort programs vary enormously by industry and source. The method transfers even where the numbers do not. Measure your own peak week rather than inheriting ours.

Where candidate.fyi Fits

Everything above comes back to one constraint: how fast the schedule can be rebuilt when it moves. In a queue, a slow rebuild is absorbed by the gap before the next hard thing. In a batch, there is no gap, so rebuild speed becomes the ceiling on the whole season.

That rebuild is the work an AI coordination layer absorbs. fyi handles 46% of scheduling tasks autonomously while candidates self-serve another 26%, leaving the 28% that genuinely needs judgment. The throughput difference is what makes a peak week ordinary: an AI-enabled coordinator handles about 158 interviews per week against roughly 30 manually.

Two customer numbers make the same point, and neither is a campus program. Zendesk went from 225 to 445 interviews scheduled per week in a month. Relativity Space cut scheduling turnaround from 2.8 days to 16.2 hours in six weeks. On a nine-day answer window, that is the difference between an offer that lands first and one that lands second.

Frequently Asked Questions

What is campus recruiting coordination?

Campus recruiting coordination is the operational work of running early-career hiring as a batch: booking panel interviews around school calendars and career fair dates, holding interviewer commitments across a season, managing rooms and virtual links at volume, and closing feedback fast enough to make offers before candidates accept elsewhere.

Is campus recruiting only for universities?

Campus recruiting specifically means sourcing from colleges and universities. The wider umbrella is early careers, which also covers bootcamp partnerships, apprenticeships, returnships and military transition programs. The coordination problem is wider than both: any intake with a fixed start date and a fixed group behaves as a batch, including seasonal ramps that are not early-career at all.

When does campus recruiting season start?

It depends heavily on industry, but Handshake's platform data identifies September and January as the two peak months for internship recruiting. Consulting and finance timelines run earlier, often more than a year ahead of a program start. NACE finds roughly 70% of employers now recruit in both fall and spring, so most teams plan two peaks rather than one.

How is cohort hiring different from req-based hiring?

Req-based hiring is sequential, so hard coordination arrives one piece at a time with recovery gaps in between. Cohort hiring is batched, so panel availability, room capacity, interviewer fatigue and same-day feedback all land in the same weeks. The annual volume can be identical while the peak load is several times higher.

How long should a campus offer deadline be?

NACE's advisory guidance describes a one to two week window as the common norm for offer deadlines, with intern-to-full-time conversions often given two weeks and sometimes up to two months. NACE does not mandate a window. The practical constraint is that average student response time is now about 9 days.

How many recruiting coordinators do you need for a peak season?

Size to the peak week, not the annual average. A manually coordinating coordinator handles roughly 30 interviews per week, so a 120-interview peak week needs four coordinators working on nothing else. Automation changes the answer more than headcount does: an AI-enabled coordinator handles about 158 interviews per week.

What is the biggest coordination risk in batched hiring?

A late interviewer decline inside a batched block. Manual decline handling in candidate.fyi's data sits unresolved for about 68 hours, against 21 hours resolved autonomously, and a 14% structural reschedule rate means a 40-interview day carries roughly six rebuilds. In a season with no gaps, those rebuilds have nowhere to go.

The Bottom Line

Campus recruiting is not req-based hiring with more candidates in it, and it is not really about campuses either. It is the same work delivered as a batch, and a batch punishes exactly the things a queue forgives: per-interview interviewer asks, email availability collection, a rebuild cycle measured in days, and staffing sized to an average. That is as true of a bootcamp cohort or a seasonal ramp as it is of a graduating class. The numbers that matter are the ones closing from both ends, 27.3 days from interview to offer against a 9-day answer window, and the ones you have not measured yet, your reschedule rate and your decline turnaround. August is when fixing those is cheap. If your peak week is the thing you are worried about, book a demo and we will map it against your live pipeline.