Skip to content
Edustians
School pupils in uniform

The week

One timetable, and everybody is looking at the same one.

Periods, subjects, teachers and rooms, with substitutions handled the morning they are needed — and the current version in the hand of every teacher, parent and student, not on a noticeboard.

A timetable printed in April is wrong by June.

Somebody leaves, a section is split, a teacher is on leave for a fortnight. The master copy is updated; the photocopies on eleven staffroom walls are not. Every conversation about the timetable begins with working out which version the other person is holding.

What Edustians does about it

Each of these is built and working today. Where something is not, the questions below say so plainly.

  • One version, everywhere

    Change it once and every teacher's phone, every parent's app and every student's screen shows the change. There is no second copy to fall behind.

  • Clashes caught while you are making them

    A teacher in two rooms in the same period is refused at the moment you try it, not discovered on a Monday morning.

  • Substitutions before the first bell

    A teacher marked absent frees their periods; the office assigns cover and the substitute is told on their own phone, with the class and room.

  • Each teacher sees only their own week

    Not a grid of eleven hundred cells. Their periods, their sections, their rooms, today first.

The questions worth asking a vendor

Including the ones where our answer is no. A school that buys on a promise and finds a gap does not renew.

Will it build the timetable for us automatically?
No. Automatic timetable generation is not built, and we would rather say so than have you find out in August. You build the timetable; the system holds it, checks it and distributes it.
Can we run different timetables for different terms?
Yes, and the previous one stays readable so you can see what a week looked like in September.

Instead of a wall of logos

What you can check for yourself.

  • Your data never leaves India

    Hosted in Mumbai. Every institution's records are separated inside the database itself — not by a line of application code somebody could forget to write.

  • Built for the DPDP Act 2023

    Parental consent, withdrawal and erasure are working features, including the stricter rules that apply to a child's data.

  • UDISE+ without the fortnight

    Your return is generated from the records you already keep, and every figure can be opened up to show the rows it came from.

  • Readable by everyone

    Measured against WCAG 2.2 AA across every screen on every release — because a grandparent at the school gate uses this too.

See it with your own school's data.

A working demonstration on your own classes, your own fee structure and your own report card format — not a slide deck.