1–3 weeks in spreadsheets
Excel, aSc, NIKA or FET. Any change in teaching load means half a day of rework.
Built in minutes, never breaks the norms, tells you what’s in the way — and after a substitution changes only what it must.
For private schools, lyceums and school networks. In the browser and on your phone.
Press the button to see the recalculation after a substitution.
Excel, aSc, NIKA or FET. Any change in teaching load means half a day of rework.
A teacher falls ill, a part-timer swaps a day — and the timetable turns into patches full of gaps.
SanPiN compliance is checked by hand, or not at all. Violations surface when it’s too late.
The software says “impossible” and doesn’t tell you which rule is in the way.
Teaching load, classes, rooms and teacher preferences. Your Excel file or an export from aSc or FET will do.
In minutes. Gaps, load balance and norms are visible at once. If something can’t be built, it tells you why.
Move lessons by hand or enter substitutions. Recalculation changes as little as possible.
Subgroups and streams, double lessons, alternating weeks, terms, part-time teachers.
Shows whether it’s proven that nothing better exists — or how far the best still is.
Illness, leave, a moved lesson — the rest of the timetable stays in place.
SanPiN and UzSanPiN health norms — at build time, not at inspection.
The engine only sees codes like T-07 and 7B. Names stay with the school.
Excel, PDF, iCal, aSc and FET. You can leave at any time.
We test on the XHSTT archive the same way the official evaluator does.
No need to bend to the software. Choose how your school moves between rooms.
We’ll move your data over from your current software — no starting from scratch.
A timetable in minutes instead of weeks, and a clear score of how good it is.
The cloud instead of a single computer, access from your phone, automatic norm checks.
Optimization with a quality score, works in the browser, recalculates substitutions, support in Russian and Uzbek.
An API for embedding, health norms out of the box, explanations of why it won’t build.
Building your own generator takes months. Plug in the API for generation, validation and substitutions, and embed the widgets under your own brand.
POST/v1/schedulesBuild a timetable and get its scorePOST/v1/validateCheck a ready one against norms and preferencesPOST/v1/substitutionsFind a substitute with minimal changesGET/v1/exportExcel, PDF, iCal, aSc or FET// POST /v1/substitutions — T-07 is absent on Wednesday { "schedule_id": "sch_2026_autumn", "absence": { "teacher": "T-07", "date": "2026-10-07" }, "policy": { "minimize_changes": true, "keep_norms": "uz_sanpin" } }
{
"status": "optimal", // best option proven
"changed_lessons": 3,
"total_lessons": 900,
"metrics": { "teacher_gaps": 4, "norm_violations": 0 },
"changes": [
{ "class": "7B", "slot": "wed-2", "from": "T-07", "to": "T-11" }
]
} Send us your timetable and teaching load as they are. We’ll run them through A Generator and show you:
The engine works only with codes: T-07, 7B, Rm 214. Teacher and student names stay with you. Everything you upload can be exported back in open formats.
The audit is free. The subscription depends on the number of classes and features — we’ll quote it after the audit. Platforms using the API get separate terms.
The timetable itself is built in minutes. Most of the time goes into collecting teaching load, rooms and preferences. If they’re already in Excel, aSc or FET, it goes faster.
A Generator shows exactly what’s missing and which rules contradict each other, for example “a teacher has more lessons than free slots”.
Yes. The timetable and the source data export to Excel, PDF, calendar and the aSc and FET formats.
Yes, the workspace runs in the browser on a computer, tablet and phone. Nothing to install.