Campus Placement Drive Management Portal

Placement season runs on notice-board PDFs, Google Forms and a flood of WhatsApp forwards: students miss deadlines, apply to drives they are not eligible for, and nobody knows which round they are stuck in. The TPO, meanwhile, cannot see at a glance how many eligible students each drive has. This project replaces that chaos with a single portal. Drives carry structured data — role, CTC breakup, eligibility rules, rounds, deadline — instead of a PDF. Applying is one tap, but the tap is gated: the portal checks the student's verified profile (CGPA, branch, backlogs, batch) against the drive's criteria before accepting. Each application then travels a round pipeline — aptitude, coding, technical, HR — with the student's position visible throughout. A dashboard surfaces deadlines this week and offer decisions pending. The eligibility engine and the round state machine are the project's technical core.

1. The TPO publishes a drive: company, role, CTC breakup, eligibility rules (CGPA, branches, backlogs), rounds and deadline.
2. Students browse drives; each card shows eligibility status computed live from their verified profile.
3. An eligible student applies with one tap; resume and marksheets attach automatically and the application enters round 1.
4. Round results are recorded per application; clearing a round advances it, with the student's pipeline position always visible.
5. Offers appear on the dashboard with CTC and an acceptance deadline; accepting or declining is recorded.
6. Deadline badges escalate as closing nears, and closed drives stop accepting applications automatically.

Tech stack:

• HTML5, CSS3, JavaScript (frontend)
• PHP 8 / Laravel (backend)
• MySQL (drives, students, applications, rounds)
• Role-based access (student, TPO admin)
• REST endpoints for drives and applications

• [Drive publishing] TPO creates drives with role, CTC breakup, eligibility criteria, selection rounds and application deadline.
• [Auto eligibility check] Applications are validated against CGPA, branch, backlog and batch rules from the student's verified profile before acceptance.
• [One-tap apply] Eligible students apply with verified resume and marksheets attached automatically from their profile.
• [Round pipeline tracking] Applications move through aptitude, coding, technical and HR rounds with per-round status visible to the student.
• [Student dashboard] Applications, shortlists, offers and this week's deadlines in one view, with an offer-acceptance countdown.
• [CTC breakup display] Fixed pay, joining bonus and variable components shown transparently per drive.
• [Deadline management] Closing-soon badges and deadline sorting so no student misses a drive.

• Complete portal source code (frontend + backend)
• MySQL schema with migrations (drives, students, applications, rounds, offers)
• Eligibility rule engine and round-pipeline state machine
• Student dashboard and TPO drive-management views
• Seeded demo data: drives, companies, applications, offers
• Project report PDF (eligibility design, state machine, ER diagram, test cases)
• PPT presentation for final review
• Viva Q&A preparation document (eligibility rules, round transitions, role-based access)

• Student profiles are marked verified by the TPO in the demo; real document verification workflow is future scope.
• Communication (emails, SMS about shortlists) is shown as in-portal notifications; real delivery needs provider accounts.
• The demo covers one college; multi-college or pool-campus drives are future scope.
• Offer analytics for the TPO (branch-wise placement stats) are a reporting extension, not in the demo.
• Resume parsing is out of scope — resumes attach as uploaded files.