A structural guide for TPOs: accountabilities, staffing model, the four registers that hold everything together, employer demand generation, and the failure modes that quietly cost you offers.
A placement cell is judged on a single percentage published once a year, which hides how much of the work is unglamorous infrastructure. The cells that improve year on year are almost never the ones with the best-connected TPO — they are the ones whose records are clean, whose eligibility policy was published before the season, and who debrief recruiters after every drive. This guide covers the standing structure of the cell. The month-by-month calendar lives on the season page, and the runbook for a single company's visit lives on the drive checklist.
The cell is measured on offers, but offers are an output of five separate systems. When placement numbers disappoint, the useful diagnostic question is which of the five broke — because the remedies have nothing in common. A cell that is short of recruiters needs a very different intervention from one whose students are being shortlisted and then failing technical rounds.
The number and quality of organisations willing to give your campus a slot. This is a relationship pipeline with a lead time measured in months, not an email campaign.
Whether the batch can clear an aptitude paper, produce a parseable resume, and hold a technical conversation. Decided one to two years before the drive, not in the week before it.
Whether a confirmed visit runs cleanly: correct eligible list, working infrastructure, students who turn up, results collected the same day.
Whether you can answer a question about any student, any drive or any offer from the last three years without reconstructing it from memory and screenshots.
Whether students, faculty, parents and management all have the same information at the same time. Most placement-season conflict is an information asymmetry, not a disagreement.
Almost every affiliated institution runs some version of the same four-layer structure. What separates functioning cells from struggling ones is not the org chart but whether each row below has a named person — not a committee — and whether that person's other duties leave them the hours.
| Role | Owns | Typical failure when unowned |
|---|---|---|
| Training & Placement Officer | Employer relationships, offer policy, escalations, management reporting | Recruiter conversations restart from zero each cycle; no one can approve an exception on drive day |
| Department placement coordinators (one per branch) | Branch-level eligibility data, student communication, faculty mentoring for interviews | Eligible lists are wrong; branches with no advocate get fewer opportunities |
| Data / records officer | The four registers, drive files, report generation, submission data | Numbers differ between the report, the notice board and the accreditation file |
| Student placement coordinators (SPCs) | Drive-day logistics, registration chasing, peer communication, recruiter hosting | Staff absorb logistics and stop doing employer outreach |
| Training / readiness owner | Aptitude programme, resume and interview preparation, mock cycles | Readiness becomes a two-week panic before the first drive |
The student coordinator layer deserves more design than it usually gets. SPCs are the cheapest capacity you will ever have and the least stable: they graduate. Select them a full cycle early so the outgoing set trains the incoming one, cap the role at a defined number of hours, and write down two rules that prevent the predictable problems — an SPC may not coordinate a drive they are themselves sitting for, and no SPC ever communicates eligibility or results on their personal account. Publish the SPC list with photographs so recruiters and students know who is authorised to speak for the cell.
Everything the cell is ever asked for — the eligible list for a drive, the placement report, an accreditation submission, next year's pitch deck — is a query over four tables. Keep them in a spreadsheet if that is what you have, but keep them as four tables with stable identifiers, not as a folder of per-drive files. The single highest-leverage habit is that nothing is ever overwritten: a student's CGPA at the time of a drive is a different fact from their CGPA today, and you will one day need the first one.
One row per student, keyed on roll number: branch, admission year, expected graduation year, programme, current and per-semester CGPA, active and cleared backlogs, education gaps with reason, personal email and phone that survive graduation, resume version and date, consent status for sharing data with recruiters, and current placement status.
One row per organisation: legal name, sector, HR contact with designation, alumni link if any, every interaction with a date, JAFs received, drives conducted, offers made, offers converted to joining, and the current relationship state. This is the register that makes a TPO handover survivable.
One row per drive: drive ID, employer, date, mode, the JAF as an attachment, the exact eligibility criteria applied, and counts at every stage — eligible, registered, appeared, cleared each round, offered.
One row per offer, not per student: student, drive ID, role title, location, package components as stated in the letter, offer date, acceptance or decline, service agreement if any, and joining confirmation. Students with multiple offers are the reason this is separate from the student master.
The unit of employer engagement is the Job Announcement Form (also called a JNF or JAF depending on the institution) — the document in which a recruiter states role, eligibility, process, locations and compensation. Getting a completed JAF is the real conversion event in employer outreach, because it converts interest into something specific enough to act on. Structure outreach around producing JAFs, not around meetings.
Have a one-page campus profile ready and keep every claim on it verifiable: programmes and intake, branch-wise batch size for the graduating year, CGPA distribution, backlog policy, infrastructure available for tests and interviews, and past recruiters — only those you can evidence. Recruiters plan capacity, so the questions they ask before committing are almost always about volume and logistics rather than about excellence.
Readiness work fails when it is delivered as one-off sessions to whoever turns up. Run it as a measured pipeline instead: diagnose, tier, intervene by tier, re-measure. A baseline aptitude test and a resume audit — both at least a year before the season — give you the two numbers you need to decide where staff time goes. Publish individual results to individuals; publishing a rank list mostly demotivates the students who need the intervention most.
Two of these interventions have their own guides: the resume workshop kit covers turning a batch's documents around in a single supervised session with a scoring rubric you can hand to student coordinators, and the aptitude test preparation guide covers designing a semester-long programme with diagnostics, mock discipline and error logs.
Governance for a placement cell can be light, but it must be regular. A weekly meeting with a fixed agenda beats an occasional long one, because the cell's failure mode is drift rather than disagreement.
Report upward monthly, in a fixed format, whether or not there is good news: drives held, offers made, cumulative placed against the eligible cohort, pipeline for the next month, and the one thing you need from the institution. A cell that only reports at the end of the season has no standing to ask for resources during it. Publish the annual calendar at the start of the year so departments schedule examinations, project reviews and industrial visits around known drive windows rather than colliding with them.
Groups are fine for notification and terrible for record. If the only evidence of an eligibility decision is a message in a group of two hundred students, you cannot defend it later.
Backlog and gap rules invented drive by drive invite lobbying and produce inconsistency. Write the policy once, publish it before the season, and change it only between cycles.
Documents produced under deadline pressure are the ones that fail parsing. Collect a first version a year out and version it.
Counting verbal or provisional selections inflates the report and creates a reconciliation problem at submission time. Count what you hold a document for.
If employer contact history lives in a personal phone and inbox, a TPO transfer resets the cell. The employer master exists to prevent exactly this.
Attention concentrates on drives, which by definition serve students who are getting shortlisted. Track students with zero shortlists as a named cohort and intervene on them specifically.
Students disperse at graduation and become uncontactable within weeks. Capture higher-studies plans, competitive-exam intentions, self-employment and personal contact details before they leave, or you will be reconstructing outcomes from social media later.
Partner institutions get Resumere for their students at no platform cost — ATS-ready resumes, JD matching, and an HR partner network that sources from partner campuses.
The rest of the campus operations library.
Resumere is free for partner institutions. Your students build ATS-ready resumes; verified HR partners source from partner campuses.
These guides describe process and judgement, not recruiter-specific criteria. Eligibility rules, test patterns, compensation and hiring dates change every cycle and differ between campuses — always work from the Job Announcement Form and test invite you actually receive, and from the current official framework documents for any ranking or accreditation submission.