Easy & Efficient
Design conflict‑free timetables and exam schedules in minutes. AutoTimetable understands teachers, rooms, subjects and constraints, then generates an optimized plan for your entire school.
What’s different: a directory‑native data model, a long‑running web worker you can pause or resume, hybrid solvers (heuristics + CP‑SAT repair), and a single JSON pipeline from admin → teacher portal → optional cloud—plus manual grid editing after generation, teacher‑wise workload statistics, inbuilt substitution, and exams in the same stack.
| Class | Mon | Tue | Wed | Thu | Fri |
|---|---|---|---|---|---|
| X‑A | Maths T001 |
Science T014 |
English T009 |
Hindi T021 |
Games T040 |
| XI‑Sci | Physics (Lab) Lab‑1 |
Chemistry Lab‑2 |
Maths T031 |
CS Lab‑3 |
PE Ground |
Trust cannot be scheduled, but schedules created by AutoTimetable can be Trusted & Used in Real Schools.
- by A2Z‑MySchoolApp Team
A schedule defends from chaos and whim. It is a net for catching days.
— Annie Dillard, The Writing Life
Most schools juggle a desktop timetabler, a separate cover system, and ad‑hoc files. AutoTimetable is built as one web application where LDAP, optimization, substitution, exams, backups, and optional cloud sync share the same architecture—here’s what that unlocks.
Rare in K‑12 timetabling
Timetable input, constraints, and published timetableGenerated JSON live in your directory, not a hidden local file.
That means SSO‑aligned access, IT‑auditable attributes, and backups that fit your existing identity governance—unusual for timetable products, which are usually siloed.
Operator-grade web UX
Long optimizations run in a PHP background worker with checkpoints—not a single blocking desktop session. Admins can pause, resume, or stop safely, then continue from saved state: a novel control model for school timetabling in the browser.
Hybrid, not one-trick
Switch engines (SA, GA, Tabu, CSP, LAHC, GDA, phased strategies, and more) in one UI, with a default SA + CP‑SAT pipeline that tightens feasibility. Combining memetic / annealing search with OR‑Tools style resolution in one school product is a standout differentiator.
Single source of truth
Substitutions merge into the same timetableGenerated document with structured metadata (e.g. portal overlays by day).
Optional Firebase push reuses that JSON—no parallel spreadsheet truth for “what teachers see today.”
First-class structures
Combined periods across sections and synchronized optional / skill bands (e.g. skill streams) are modeled as scheduling primitives—not afterthoughts—so real Indian board layouts map cleanly to the engine.
Full lifecycle in one app
Inbuilt substitution, exam clash scheduling, multiple backup & restore slots, exports, and AI template shortcuts sit in the same webapp—reducing vendor sprawl and integration risk.
Wording reflects product architecture as documented in the user manual; enabled modules and solver lists may vary by deployment.
AutoTimetable sits directly on top of your LDAP directory and understands the way your school actually runs: classes, sections, staff, rooms and constraints.
Why this stack is novel — directory-native data, hybrid solvers, and one JSON for admin, portal & cloud.
Start from curated templates (CBSE, MP Board, custom boards) and map them to your real subjects using shortcuts. The system finds the closest matching subject name automatically when you apply a template.
Honour teacher expertise, preferred loads and free periods. Automatic substitution suggestions ensure classes keep running even when staff are absent.
Define which rooms are best suited for which subjects and let the engine propose allocations that respect lab capacities, special rooms and constraints.
No separate spreadsheet workflow: mark absences by day and period, run smart substitution with priorities (free periods, load, class category, games teachers, CT lunch rules), and see successful vs failed placements with reasons.
timetableGenerated for the portalEach teacher sees their weekly timetable from LDAP. When admins save substitutions, overlay metadata highlights who is covering, uncovered absences, and class‑teacher duty notes—so staff always see today’s truth.
timetableGenerated JSON
Connect Firebase Realtime Database via LDAP‑stored app credentials. Each time the master
timetable (with substitution overlays) is saved, the latest timetableGenerated document can be written to
/timetables for mobile apps, dashboards, or parent portals.
Create several independent restore points before major edits, term rollovers, or experiments.
Roll back timetableGenerated, constraints, input grids, or GA session snapshots without losing other work.
Schedule the same subject across multiple sections of one grade in a shared slot: one teacher, one room pattern, aligned periods—exactly how assembly halls, shared academics, and combined batches run in real schools.
Model optional streams and skill bands (e.g. skill1–skill19) so every participating section gets the same period index for that stream—labs, vocational blocks, and split groups stay in lockstep.
Rules aren’t “all or nothing”: tune which constraints apply, how strongly they bite (hard vs soft / weights), and review a summary before each GA run so you know what the optimiser will enforce.
The optimiser doesn’t have the last word: edit the live grid in the browser—swap teachers, rooms, or subjects cell‑by‑cell (or via your deployment’s manual mode tools), then validate clashes before you save to LDAP.
See fairness and load at a glance: per‑teacher period counts, free periods, consecutive teaching stretches, and subject mix—ideal for HOD review before you publish or when you negotiate last‑minute tweaks.
From the admin substitution screen to every teacher’s phone: one pipeline. LDAP remains the system of record; the teacher portal and optional Firebase mirror keep daily operations visible without exporting CSVs.
Built into the product—no bolt‑on. Configure periods, lunch, games staff, and “never substitute” lists in LDAP.
Generate substitutions for a chosen weekday; review period‑wise, teacher‑wise, and room‑wise updated grids.
Results merge into timetableGenerated under structured metadata for downstream consumers.
Teachers open the portal to see their standard weekly pattern plus substitution overlays: which periods are covered by a colleague, which remain absent, and notes for class‑teacher duties. Updates appear after admins save from the substitution workflow—no duplicate data entry.
When enabled, the same JSON published for the portal can be PUT to Firebase Realtime Database at
/timetables on every save—ideal for App Check–aware clients or a companion app that listens for live updates.
Credentials are read from your LDAP app‑details entry; your IT team controls keys and rules.
Cloud sync is optional. Treat Firebase secrets and service accounts like any other production credential.
Admins can maintain parallel backup slots (LDAP snapshots, server-side files, or exports) and restore selectively—ideal before bulk substitution days, exam week freeze, or trying an alternate solver path. Pair with pause / resume so you always have a known-good baseline to return to.
Model combined periods across sections, synchronized optional streams, long-running optimization with full operator control, and choose from many algorithms—from CP‑SAT hybrid defaults to Tabu, GA, CSP, and more. Use multiple backup & restore points whenever you change constraints mid-run or compare solver outcomes.
Same subject, type, teacher & room across multiple sections of one grade are locked into the same period—ideal for shared lectures, labs, or assembly-style blocks. The engine groups rows automatically from your timetable input.
skill1–skill19 bands keep all sections of a grade aligned in time for that stream,
while each section can run different subjects, teachers, and rooms in the same slot—perfect for optional / split groups.
Long optimizations run in the background. Pause at safe checkpoints, resume without losing progress, or stop cleanly before changing parameters or LDAP data—so admins stay in control during peak season.
Pick the algorithm that fits your problem: default SA + CP‑SAT, GA + SA, Tabu, CSP, LAHC, GDA, hybrid / mixed / tight, quantum-inspired, optional FET CLI, and phased strategies.
The live app’s solver dropdown may hide or disable individual options per deployment; the manual lists each engine and typical use.
Step-by-step: input rules, constraints, optimization, substitution, exams, and troubleshooting.
Read the full user manualProject‑based: we generate and hand over one academic year—ideal if you only need a fresh master timetable.
₹34,999 + GST · per engagement
Typical campus: up to ~1,200 students · 1 campus
Always‑on web access, teacher portal, and optional realtime sync—best for daily operations.
₹89,999 + GST · per year
Subscription · renews annually
Software and data stay on your servers—maximum control for IT policies and compliance.
₹3,49,999 + GST · one‑time licence
Includes 1 year premium support · AMC from ₹44,999/yr
Prices are illustrative for planning; campus size, LDAP complexity, training days, and statutory taxes may change the final proposal. For quotes and intro offers, contact sales@idas.co.in or +91 8319635193 (Sales/Info/Support Team). Third‑party trademarks and competitor pricing mentioned in the survey are for context only and may change without notice.
Extend the same data‑driven engine to exams. Plan exam slots per subject, per class, with automatic checks for clashes across rooms and invigilators.
| Date | Class | Subject | Room | Invigilator |
|---|---|---|---|---|
| 10 Mar | X‑A | Mathematics | Room 12 | T021 |
| 12 Mar | X‑A | Science | Lab‑2 | T017 |
The exam scheduler understands the live timetable and prevents double booking of rooms or invigilators across overlapping slots.
AutoTimetable is designed to be operated by school admins and senior staff. No scripting, no spreadsheets—just structured data, intelligent defaults and clear dashboards. See what makes the architecture novel before you dive into the steps below.
Fresh notes on common pain points in older school timetabling software and practical ways to avoid them.
Older timetable tools often lock classes to static slot templates. One transfer, one maternity leave, or one room change can force a full rebuild because dependencies are hidden. Modern rule-based timetabling should re-balance only affected clusters and preserve stable parts of the week.
Many older systems show clashes only after final generation, so admins spend hours trial-and-error editing. Better systems surface violations while entering constraints: teacher overloads, room collisions, and subject sequencing issues should appear before long solver runs start.
Legacy portals usually treat substitutions as separate paperwork, disconnected from the timetable grid. This creates uncovered periods and stale teacher views. A modern substitution layer should patch the active timetable directly and keep teacher-facing schedules synchronized in real time.
In older products, exam scheduling is often a disconnected module requiring re-entry of rooms, invigilators, and sessions. That duplication introduces inconsistency and missed clashes. Unified scheduling should reuse the same core data model across regular timetable and exam operations.
Older software frequently supports only one “latest” save, so one wrong bulk update can erase validated work. Reliable operations require multiple named snapshots, quick restore points, and exportable archives that let schools test changes without fear of irreversible loss.
A recurring issue in legacy scheduling tools is weak load-balancing logic: some teachers get back-to-back heavy days while others get fragmented split days with idle gaps. Fair scheduling must optimize weekly totals and daily spread together, especially for part-time and specialist teachers with narrow availability windows.