By February of a typical placement season, a placement officer is managing something like this: eight companies have confirmed dates, twelve are in negotiation, six have gone quiet, three have visited and their shortlists need follow-up, and two have given offers that students are still deciding on.
Every one of these tracks requires different action. Every week, something moves. And somewhere in a shared Google Sheet or a stack of email threads is the information you need to know what to do next.
This is the part of placement where organisations fail quietly. Not in a dramatic way, but in the way where a company that could have hired 15 students slips off the radar for two weeks and then tells you they have moved on.
The Minimum You Need to Track
For every company in your pipeline, you need to know five things at all times: where they are in the process, what the last action was and when, what the next action should be and when, how many students they are expected to hire, and who is the contact person.
If you cannot answer these five questions for every company in your pipeline within 30 seconds, you do not have a tracking system. You have a list.
The Stage Framework That Works for Indian Placement
Break your company pipeline into these stages:
Identified: you have the company name and some contact information. No outreach has happened yet.
Contacted: you have sent your initial invitation and batch information. Waiting for a response.
In discussion: the company has shown interest and you are negotiating dates, eligibility criteria, or other details.
Confirmed: a date is set, student eligibility is defined, and the company is committed.
Drive completed: the drive happened. You are now tracking shortlists, interview rounds, and offers.
Offer stage: students have received offers. You are tracking whether they have accepted, declined, or are waiting.
Placed: offers have been accepted and joining details are confirmed.
Closed: the company has completed their hiring for this season. Note the outcome for next year's outreach.
Moving a company through these stages requires a deliberate update whenever something changes. The moment a company confirms a date, someone has to move them from "in discussion" to "confirmed" and record the date. This sounds obvious but it is the discipline that breaks down under pressure.
Follow-Up Cadence That Does Not Annoy Companies
The companies that disappear from your pipeline are usually not gone. They are waiting to hear back from their internal team, or they had a budget review, or the relevant HR person was on leave. A follow-up at the right time brings them back.
For companies in the "contacted" stage with no response after ten days, one follow-up email. After another ten days, a phone call. If there is still no response, move them to a "low priority" sub-list and try again in three weeks.
For companies in "in discussion" with no update for seven days, a check-in call rather than an email. Negotiations stall for specific reasons and a call usually surfaces them faster than email.
For companies in "confirmed" status, a check-in one week before the scheduled drive to confirm logistics, student numbers, and any changes on their end. Companies sometimes change requirements or postpone without proactively telling you. This check-in catches those changes early.
Tracking Student Status Alongside Company Status
The company pipeline and the student status tracker need to be connected. When Company X shortlists 40 students, those 40 students need to know immediately. When 20 of them clear the interview and receive offers, their status changes so they are not included in shortlists for other companies unless they are eligible.
Managing this connection manually across a season with 30 companies and 400 students is where Excel starts to fail. The updates that need to happen quickly, like notifying shortlisted students the night before a drive, get delayed because someone has to manually cross-reference two spreadsheets.
The right system handles this automatically: when a company's shortlist is finalised in the system, eligible students are notified, their status is updated, and the TPO's view of the student pool reflects the change immediately.
What Slips Through Without Good Tracking
The placement losses that hurt most are the preventable ones. A company that was confirmed but rescheduled twice and then quietly dropped. A student who received an offer from two companies but no one followed up to confirm their decision, leaving both companies waiting. A company from last year that had a great experience but received no outreach this year because no one noted to contact them in September.
Good tracking prevents these. Not by being complicated, but by making sure the right information is in front of the right person at the right time.
If you want to see how Verfolia handles company pipeline management and student status tracking for a placement cell of your size, the best way is a 20-minute walkthrough. The link to get started is on our homepage.