Key takeaways
- Horarium is a cloud K-12 timetabling tool with 40+ constraint types and localized help in 10 languages; Smootables starts from multi-year school planning before generation.
- Year planning, workload, workshops, and individual pathways stay inside Smootables instead of parallel spreadsheets.
- Pre-solve validation and typed infeasibility reports surface planning issues before a generation run.
- Pilot one term in parallel, then switch publication scope when results match.
Who should consider a Horarium alternative?
If your school uses Horarium (horarium.ai), or you are evaluating it from the best school timetable software 2026 roundup, this page is for you. Horarium is a cloud timetabling tool positioned for elementary, middle, and high schools, available on web, iOS, and Android. The vendor documents over 40 constraint types, Excel import, generation in roughly 1 to 10 minutes, a report of unsatisfied constraints, and PDF and Excel export. This is a fair comparison, not a takedown.
The short version: Horarium centers K-12 timetable generation with a broad constraint catalog and localized self-serve help. Smootables is school year planning-first. The two differ in institution fit, planning depth, and how much year, pathway, and vocational modeling sits in the product before generation.
Where does Horarium still fit, and where do vocational or planning-first schools look elsewhere?
Horarium is strong for K-12 schools that want fast cloud generation with constraint feedback and help in many languages. The columns below show where Horarium still fits and where vocational, technical, or planning-first schools may prefer the Smootables model.
Where Horarium still fits
Elementary, middle, and high schools that want a cloud tool on web, iOS, and Android with over 40 constraint types, adjustable importance weights, Excel import, and vendor-documented generation in minutes plus a report of unsatisfied constraints.
Horarium also ships roughly 90 help articles per locale across 10 languages, including pages mapped to specific constraint questions and solver error messages. Named customer testimonials cite schools in Romania, Colombia, Brazil, Mexico, Poland, and South Africa.
Where vocational and planning-first schools look elsewhere
Horarium's positioning and content target K-12 class-based schools: no vocational, workshop, work-based-learning, individual-pathway, or academic-year-planning content was observed anywhere on its site at capture. Its own help center is a tell for where the friction actually sits: roughly 90 articles per locale, several titled after the exact solver error a planner just hit, for example "for class 5A you configured more lessons (33) than the maximum possible (30)." That is genuinely useful self-serve support, and it also means the constraint conflict surfaces after generation, once a planner is already deep in a specific class's data.
For vocational college timetable software buyers and schools with mixed cohorts, that gap compounds: Horarium's workflow answers "does this constraint set produce a grid" before it answers "is the year plan feasible." Smootables checks the second question first. Pre-solve validation runs 13 checks before generation, and multi-year planning, teacher workload, pathways, and resources live in the same model the solver reads, not a spreadsheet plus a help-article search.
How is Smootables different from Horarium?
Horarium's product is a constraint configurator: enter or import your data, toggle and weight up to 40-plus constraint types, run generation (the vendor states roughly 1 to 10 minutes), and read the report of what did not fit. That loop rewards knowing which constraint to adjust next, which is presumably why roughly 90 of Horarium's help articles per locale exist to answer exactly that, several literally titled after the solver's own error text. Smootables starts a step earlier. The planning model holds academic years, terms, periods, courses, modules, pathways, workload, and individual student assignments, and generation (see automatic school timetabling) runs against that model, so validation can catch likely infeasibility before a solve starts rather than after it returns a report. For a step-by-step creation guide with Smootables workflow at each stage, see how to create a school timetable.
The practical difference is who has to understand the solver. Horarium's own documentation walks a planner through raising an importance weight and regenerating until the report clears. In Smootables, 13 checks run before the solve and name the blocking problem in the model itself, an over-allocated teacher, a specialist room short of capacity, availability windows that cannot overlap, and propose the correction. When no grid satisfies every hard constraint, the report is typed rather than a list of what did not fit, and unplaceable lessons wait in a holding area for a decision instead of forcing another full run. The AI planner assistant makes bulk model changes on request with a preview first, so the planner's time goes into the plan rather than into learning which weight to nudge next.
How does Smootables compare to Horarium in 2026?
The table contrasts Horarium and Smootables across institution fit, planning depth, validation, pathways, AI, localization, company location, and export. Horarium is strong for K-12 constraint workflows; Smootables is planning-first, so several rows reflect where the data lives rather than whether a solver runs.
| Dimension | Horarium | Smootables |
|---|---|---|
| Primary institution fit | Elementary, middle, and high schools (vendor positioning) | Vocational and technical colleges, multi-campus groups, and schools with individual pathways |
| Workflow | Excel or UI data entry, constraint configuration, generation, manual edit, export | Planning-first, then generate a timetable from the plan in one step |
| Year and period planning | Documented surface centers generation; no year-planning layer described at capture | First-class part of the model |
| Individual pathways and exemptions | K-12 class focus; no pathway or WBL model described at capture | Group, individual, and per-placement exemption support in the core model |
| Pre-solve validation | Unsatisfied-constraint report after generation | 13 validation checks before generation, with typed infeasibility reports |
| Constraints | 40+ constraint types with Active toggle and adjustable importance weight | Enforced hard constraints and 6 weighted soft constraints with school-configurable weights |
| Automation and AI | Constraint-based generation with manual edit and regeneration | CP-SAT solver plus a built-in AI planner assistant for in-app actions |
| Company location | Romania (Softix SRL) | Finland |
| Publication and export | PDF and Excel export after generation | PDF and Excel export plus read-only teacher views; SIS and calendar integrations are available |
What should schools validate when replacing Horarium in 2026?
When deciding whether Smootables is the right replacement, these are the scenarios where the planning-first model usually shows the biggest difference:
- Modeling workshops, work-based learning, and individual pathways, the layer Horarium's own K-12 positioning and help center do not describe
- Running pre-generation validation on a known-tight period, instead of adjusting a constraint's importance weight and regenerating until Horarium's unsatisfied-constraint report clears
- Comparing scenarios with timetable branches instead of overwriting a draft and starting a fresh 1-to-10-minute generation run
- Checking workload before any timetable is generated, not after reading Horarium's post-generation report
- Asking the planner AI to balance a constraint in plain language, instead of searching Horarium's help center for the article matching the exact error text
What is the migration path from Horarium?
Moving off Horarium is a parallel run, not a big-bang switch: keep Horarium generating live timetables while Smootables validates the same data underneath it. Compare TimetableMaster alternative if you are also evaluating other cloud generators. Horarium's own export path (PDF or Excel) is the starting point below; the steps run that export into Smootables, validate it, and hold one term in parallel before anything published changes.
- Export your data from Horarium to Excel or PDF.
- Import into Smootables with column mapping and a preview of exactly what will be created.
- Translate the constraints you had tuned in Horarium into the model: hard rules that must hold, and weighted objectives for the rest. Start with fewer than you had, and let the pre-generation checks tell you what the model is actually missing.
- Run the checks and read the typed report. This is the step that replaces the adjust-a-weight-and-regenerate loop.
- Generate one period alongside the Horarium timetable the school is running on and compare gaps, load and build time.
- Publish from Smootables one scope at a time once the parallel period holds up.
Questions schools ask when comparing Horarium and Smootables
Is Smootables a direct replacement for Horarium?
It can be for planning, generation, editing, and export. Horarium is optimized for K-12 class grids with a broad constraint catalog and localized help. Smootables focuses on year planning, vocational pathways, pre-solve validation, and AI-assisted editing. Many schools pilot Smootables when Horarium fits the grid but not the planning model behind it.
We are a standard secondary school, not a vocational college. Is Horarium the safer choice?
Horarium fits if you are mostly interested in timetable generation from teacher, group, and room lists. Smootables provides a more advanced multi-year school planning mode and focuses on a sophisticated tool for the planning step, in addition to timetable generation and editing.
Horarium cites large scale statistics. Should we trust them?
Treat vendor scale statistics as unverified unless they cite a review platform or independent source. Our competitor capture noted figures such as 42,000+ timetables and 3,500+ active users on Horarium pages without third-party sourcing. Evaluate both tools on your own pilot data instead.
What if Horarium generation is fast enough for us?
Horarium's stated 1-to-10-minute generation time is genuinely fast, and that was never really the question. The bigger cost sits on either side of it: configuring and weighting 40-plus constraints before the run, then reading the unsatisfied-constraint report and deciding what to adjust and regenerate after it. Smootables validates before the run, so the planner sees a conflict while the data is still cheap to change, not after committing to a generation pass.
Horarium's help center answers almost every constraint question already. Do we need anything more?
The help center is real and useful once you are past setup: roughly 90 articles per locale, several written to match the solver's own error text so a stuck planner can search for the exact wording on screen. What it does not do is stop the conflict from happening. Smootables runs the same category of check before generation, as part of the plan, so fewer schedules need that search in the first place.