Duplicate student rosters
Which candidate list is current?
Every drive creates a new copy of eligible students. When academic records or backlogs update, drive spreadsheets stay behind.
One workspace for theentire placement season.
Bring student records, opportunities, eligibility, drives, offers and reporting into one institution-owned operating system.
Built for the full placement lifecycle
Most placement operations run on systems that disagree.
Resumes in inboxes, eligibility criteria in spreadsheets, shortlists in messaging groups, and offers in unverified emails. Every coordinator, department and student keeps their own copy, and none of them agree.
Untraceable eligibility
Can this decision be audited?
Criteria, rules and policies are calculated by hand under time pressure, leading to disputes and unexplainable rejections.
Unverified outcomes
Did the office verify these terms?
WhatsApp claims and unverified off-campus offers skew institutional reporting without a verifiable audit trail.
Everything a placement team runs, finally in one place.
From the first student import to the last joining update, each workflow builds on the same scoped, auditable record.
Student foundation
A verified record, ready for every next step.
- Mapped CSV/XLSX imports
- Student 360 and Official Profile PDF
Opportunity engine
Eligibility that can explain its answer.
- Explainable pass and fail reasons
- Immutable application snapshots
Drive operations
From the first shortlist to D-Day.
- Conflict-aware scheduling
- Live round progression
Offers and outcomes
Every offer has a traceable path.
- Office offer verification
- Internships, PPO and joining
Student communication
Fewer queues outside the placement office.
- In-app and email notifications
- Scheduled announcements
Reporting and control
Numbers that return to the same record.
- 13 canonical reports
- CSV/XLSX background exports
The season moves forward.
The record stays together.
- 01
Prepare
Import students, verify records and publish the placement policy.
- 02
Open
Approve recruiter access, publish JAFs and explain eligibility.
- 03
Operate
Run applications, rounds, scorecards, schedules and D-Day.
- 04
Settle
Verify offers, capture responses, PPOs, joining and outcomes.
- 05
Reconcile
Use one metric library across dashboards, reports and exports.
Not another collection of isolated tools.
The platform follows the operating model of a placement cell, so handoffs do not become new spreadsheets.
Build the season
- Institutions, campuses and programmes
- Placement and internship cycles
- Versioned policies and registration
- Companies, contacts and recruiter access
Run the process
- JAF approval and applications
- Shortlists, rounds and attendance
- Panels, rooms, slots and conflicts
- D-Day board and scorecards
Close the loop
- Verified campus and off-campus offers
- Responses, restrictions and joining
- Internship outcomes and PPO conversion
- Reports and operational exports
Keep people aligned
- Student and recruiter portals
- Placement Help and forum
- Announcements and notifications
- Calendar, search and saved views
One system. It looks different to everyone who uses it.
The placement office coordinates the season while students and recruiters get focused, responsive workspaces of their own.
Placement office
One operating picture for the placement cell.
See the season pulse, act on attention queues and open the source record behind every number.
- Dashboard metrics with denominators
- Student 360 and scoped action history
- Reports, saved views and exports
Your portal stays recognisably yours.
Each tenant keeps its own domain, identity and accent while the product structure remains consistent for every role.
- Domain
- Per tenant
- Identity
- Logo + favicon
- Accent
- Primary actions
Alpha University Institution settings
01Your domain02Your identity03Your accent
Built for groups of institutions. Isolated by design.
Security is product behaviour: what a person can do, which institution they can do it in, and what remains on record.
01
Tenant isolation
PostgreSQL row-level security is forced for tenant data.
02
Permission + scope
Permissions and institution scope decide which records are reachable.
03
Privileged MFA
MFA protects privileged actions and sensitive recovery paths.
04
Audit trail
Business actions and authentication events are recorded separately.
Time-limited vendor session
Read-onlyScope locked
05
Visible support
Support access is read-only, time-limited, visible and audited.
Straight answers. Before you commit.
Clear product boundaries make a better pilot and a more reliable placement season.
Does Modus TNP need another Modus product?
No. TNP is designed to operate as a standalone product. The current UMS adapter is a development adapter, not a live integration.
How is student eligibility decided?
Published, versioned rules are evaluated deterministically. Missing required data fails closed with an explanation, and submission re-runs eligibility before saving a snapshot.
Can recruiters publish jobs and offers directly?
No. Recruiters can request access and submit opportunities, but the placement office retains approval. Recruiter-issued offers remain hidden from students until the office verifies them.
Does the platform support internships and PPOs?
Yes. Internship cycles, internship offers and official outcomes are kept distinct from final placement. An accepted internship can be linked to a PPO in a placement cycle without auto-accepting it.
Which communication channels are included?
Event notifications use in-app and email. Announcements can also use consent-based WhatsApp templates where configured. SMS and calendar sync are out of scope.
Is this production-ready?
Not yet. The current product is code-verified for staging. We are inviting institutions to book a demo and discuss pilot readiness.
See your placement operations on one record.
Bring the spreadsheet. We’ll map the season.