The Problem
Education businesses that promise placements live and die by their placement cell — and most placement cells run on spreadsheets. Staff chase students one by one for resumes, collect documents over email and WhatsApp, and track who reached which interview in a sheet nobody fully trusts. Recruiter contacts sit in someone's phone. There is no single answer to simple questions: how many students are placement-ready? How many resumes are still pending? Where does each candidate stand right now?
For Parmanand Group, admissions already ran on Pinelogix CRM. So rather than bolt on a separate placement tool — and re-enter every student — we built the placement cell as a native module of the CRM. A student now flows from enquiry, to admission, to placed, inside one system.
Automatic Hand-off from Admissions
The trigger is the CRM lifecycle itself. When a lead reaches the "admission done" stage, the system automatically creates a placement student record, carrying over name, course, batch year, and contact details. There is no duplicate data entry and no student who slips through the gap between "admitted" and "placement-ready." The placement cell's pipeline begins populating itself the moment admissions close.
Secure, Self-Service Resume Collection
Instead of staff chasing students, each student receives a private link to a structured resume form — no account, no password. The link is backed by a one-time token that expires after 12 hours, so data collection is both frictionless for the student and secure for the institution. If a link lapses, staff regenerate a fresh one in a click.
The form is comprehensive by design. It captures personal and location details, a repeatable education history, work experience for lateral candidates, skills and certifications, job preferences and expected salary, document uploads (photo, ID proof, education certificates, experience letters), and a final declaration with a digital signature. Flexible sections — education and experience entries — are stored as JSONB, so the schema bends to each student without a migration.
Standardised Resume Generation
Once a student submits, the platform generates a clean, standardised resume PDF from the structured data. Every candidate is presented in the same professional format, which means recruiters compare like with like and the institution's brand stays consistent across every profile it sends out.
Custom Pipelines and a Recruiter Database
Placement teams work differently, so pipelines are dynamic. Admins define their own stages — "Form Sent", "Resume Received", "Shared with Recruiter", "Interview Scheduled", "Placed", "Not Interested" — each with a colour and, where relevant, a terminal state (placed or dropped). Students move through stages with full visibility for the whole cell, and every transition is written to an activity log against the student.
Alongside candidates, the module keeps a central recruiter and organisation database — companies, HR contacts, industries, and locations — so relationships are built and reused season after season rather than rebuilt from scratch.
Engineering Decisions
Token-based public forms. The resume form is the only part of the system a non-user touches, so it is deliberately isolated: a single-use, time-limited token grants access to exactly one student's form and nothing else. No authentication surface is exposed to the public.
JSONB for the flexible parts. Education entries, experience entries, and certifications vary wildly between a fresher and a lateral hire. Storing them as JSONB arrays keeps the relational core clean while letting the resume capture whatever a candidate actually has.
Centralised, with origin tracking. The placement cell spans the whole institution rather than a single CRM workspace, but each student record remembers the workspace and CRM agent it originated from — so the placement team sees everyone in one place without losing the link back to admissions.
The Outcome
The placement office stops living in spreadsheets. Students self-serve their own data, every resume looks the same, every candidate carries a clear status, and a dashboard reports total candidates, resumes submitted versus pending, and pipeline distribution at a glance. Because it is part of Pinelogix CRM, the same platform now carries a student from first enquiry all the way to a signed offer — one system, one record, no hand-offs lost in between.