Use case
The daily fabric — without the spreadsheet mess.
Edullent handles the everyday operational layer most schools survive with three half-built tools and one heroic office manager.
Timetables, substitutions, fee status, alerts, settings, branch configuration — the routine work that has to happen every day for a school to function. Edullent ships this as a single coherent layer, not a bag of features.
The problem
What schools live with today
The timetable is in Excel. Substitutions are managed on WhatsApp. Fee status lives in a different software. Alerts go through the office. The result: every operational change requires four updates in four places, and one of them gets missed every week.
The flow
From signal to outcome.
Five steps. The same shape every Edullent use case follows.
School structure, classes, sections, teachers and timetables set once.
Daily operations — substitutions, alerts, fee actions — flow through one surface.
Stakeholders are auto-informed where it matters — parents on absence, owner on overdue fees.
Every operational change leaves a trail. Useful at inspection time.
Configuration evolves through the year — Edullent doesn't require a re-deploy.
What you get
Capabilities behind this use case.
Real product surfaces, shipping in the platform today.
Timetable
Class-wise, teacher-wise, with substitution baked in.
Fee status
Live, drillable, with parent reminders auto-shipped.
Alerts engine
School broadcasts, role-scoped alerts, holiday updates.
Settings
Per-school configuration without engineering involvement.
Branch fabric
Multi-branch groups: per-branch isolation with group-level aggregation.
Audit trail
Every operational change stamped — useful for inspections.
Who it changes
Role-by-role impact.
Group-wide operational health on one dashboard — fees, attendance, anomalies.
Substitutions, timetable changes, fee alerts — done from one place.
Today's schedule, today's substitutions, today's alerts — already in the app.
Fee status, holiday schedule, school broadcasts — no separate "office number".
Outcomes
What the pilots produced.
replaces timetable + WhatsApp + fee software + email circular
for a single-campus operational layer
multi-tenant fabric — no re-platforming to add a campus
Outcomes measured at Pilot Schools A, B and C in their first term. Anonymized by partner request. See customer stories.
FAQs
Questions schools ask about this use case.
When a teacher is marked absent, Edullent surfaces an eligible-substitute list for the principal — based on free periods, subject expertise and recent load. One tap notifies the chosen substitute and updates the affected class.
Yes — schools control the cadence, the wording template, the parent channel and the escalation list. Edullent's defaults are sensible; the toggles are real.
Edullent's spine is the intelligence + daily operational layer. Hostel and transport modules are on the roadmap and ship for institutions that need them; the core platform doesn't depend on them.
Each branch is isolated by default — its own timetable, its own fee structure, its own teacher roster. Group-level settings cascade down where the owner explicitly opts in. Nothing leaks across branches without a deliberate decision.
Continue exploring
See school operations on Edullent.
A 25-minute focused walkthrough on this one use case. Your school structure, your data shape, your real questions.