No owner
Everyone thought someone else called the parent.
Task Manager turns admissions callbacks, fee escalations, and ops chores into owned tasks with due dates, reminders, and completion proof.
“Please follow up” on WhatsApp has no owner, no due date, and no proof it happened.
Everyone thought someone else called the parent.
Tasks float until complaints arrive.
Staff reopen five screens to understand the issue.
Leaders cannot see open vs overdue work.
Operational depth your team will use every cycle — not a shallow feature list.
Personal and team queues.
Attach admissions leads, fee accounts, or tickets.
Urgent / normal with SLA hints.
WhatsApp/email/push via Alerts.
Sub-steps for complex jobs.
Reassign with history.
Open, overdue, and completed KPIs.
Admission callback, fee chase, document pending.
A clear path your staff and parents can follow without training manuals.
From a module action or manually.
Pick owner and due date.
Complete checklist and notes.
Mark done with timestamp proof.
The right people see the right slice of the pipeline.
Works admission follow-ups.
Owns defaulter calls.
Tracks facilities/ops jobs.
Watches overdue KPIs.
Each module is an edge in the campus operating graph — not a silo.
Measurable ops wins institutions report once this module runs inside ScholarERP.
“Our admissions overdue list went from “unknown” to a ranked queue counselors clear each morning.”
Straight answers for setup, integrations, and day-two operations.
Yes — stage changes and cold-lead rules can spawn follow-up tasks.
No. Tasks are internal; parents see outcomes via portals/alerts.
Due dates and priority conventions support operational SLAs; escalate with reminders.
It is campus operations tasking — not a generic enterprise IT ticketing suite.
Link leads, assign owners, and fire a reminder.