Key takeaways
- aSc Timetables is strong as an automatic timetable generator; Smootables starts from the planning model before generation.
- Year planning, workload, and individual pathways stay inside Smootables instead of parallel spreadsheets.
- Pre-solve validation and infeasibility reports show planning issues before a generation run.
- Pilot one period in parallel, then switch publication scope when results match.
Who should consider an aSc Timetables alternative?
If you currently use aSc Timetables, or have used it on a previous evaluation (see also best timetable software for vocational schools), and you are looking at modern alternatives, this page is for you. It is a fair comparison, not a takedown. aSc is a long-established automatic generator: its official site reports roughly 30 years on the market, use in 173 countries, and 150,000 schools (verify this independently before relying on vendor marketing claims; the school count is large enough that it is worth checking).
The short version: aSc starts from timetable data input and generation. Smootables is school year planning-first. The two product visions differ in where the data lives, when validation happens, and how planners stay in control.
Where does aSc still fit, and where does it limit planning-first schools?
aSc Timetables remains a capable generator with a broad constraint catalog, a setup wizard, a lesson grid, and testing tools before generation. The columns below show where aSc still fits and where planning-first schools may prefer the Smootables model.
Where aSc still fits
Schools with a stable timetable model, a planner comfortable with detailed setup and constraint dialogs, and a working flow around aSc Timetables Online, aSc Substitutions, mobile access, class register, calendar, or room booking.
aSc's automatic generator is long-established, the input model is familiar to planners with timetabling backgrounds, and official reseller pricing is a one-time licence per edition with later maintenance.
Where it limits planning-first schools
aSc supports seminars, courses, groups, joins, and individual student timetables, but those features are configured as timetable inputs. Smootables puts period planning, workload, pathways, resources, validation, and editing into the same planning model before generation.
For vocational college timetable software buyers, the gap between 'the generator works' and 'the plan is feasible' is where much of the planner time goes.
How is Smootables different from aSc Timetables?
Smootables shares the same broad category as aSc Timetables: automatic generation with hard and soft constraints. It starts earlier in the lifecycle. The planning model holds academic years, terms, periods, courses, modules, pathways, workload, and individual student assignments. Generation runs against that model (see automatic school timetabling), so validation can catch likely infeasibility before the solve. For a step-by-step creation guide with Smootables workflow at each stage, see how to create a school timetable.
Editing is modern: drag-and-drop, swap, split, pin and regenerate, slot insight before a drop, branches, undo, and audit logs. A built-in AI planning agent lets planners make large changes fast: describe what you need in natural language and review bulk updates on the same planning model.
How does Smootables compare to aSc Timetables in 2026?
The table contrasts aSc Timetables and Smootables across workflow, year planning, individual pathways, validation, workload visibility, AI, editing, company location, and publication. aSc is strong as a generator; Smootables is planning-first, so several rows reflect where the data lives rather than whether a solver runs.
| Dimension | aSc Timetables | Smootables |
|---|---|---|
| Workflow | Setup wizard, lesson grid, and automatic generation | Planning-first, then generate a timetable directly from the plan in one click |
| Year and period planning | School year, days, periods, and cycles in setup; broader period planning usually separate | First-class part of the model |
| Individual pathways and exemptions | Seminars/courses, groups and joins, and individual student timetables | Group, individual, and per-placement exemption support in the core model |
| Pre-solve validation | Testing, advisor checks, statistics, and draft timetable before generation | Validation before generation, with infeasibility reports |
| Workload visibility | Statistics and checks around generation | Available throughout planning |
| Automation and AI | Automatic generation with configurable complexity and constraint relaxation | Automatic solver plus a built-in AI planner assistant for in-app actions |
| Editing | Manual card moves, locks, undo/redo, custom views, filters, and swaps | Drag/drop, pin/regenerate, slot insight, branches, undo |
| Company location | Slovakia (asc Applied Software Consultants, s.r.o.) | Finland |
| Publication and substitutions | aSc Substitutions, mobile app, class register, calendar, and room/event booking | Built into the same workspace; integrations available |
What should schools validate when replacing aSc 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 individual pathways and exemptions without a parallel spreadsheet
- Running pre-generation validation on a known-tight period
- Comparing scenarios with timetable branches instead of overwriting drafts
- Asking the planner AI to balance a constraint and reviewing the proposed change before applying
- Checking whether planners prefer a modern, clean interface after aSc's settings-rich workflow
What is the migration path from aSc Timetables?
Moving off aSc Timetables is a parallel run, not a big-bang switch. Compare Untis Timetables alternative if you are also evaluating enterprise suites. The steps below export your aSc model, import it into Smootables, validate before scheduling, and run one period in parallel before you change the published source of truth.
- Export your current model from aSc (courses, teachers, rooms, groups, constraints).
- Import the model into Smootables using structured import with column mapping, or AI-assisted extraction for older exports.
- Validate the model in Smootables. Pre-solve validation will surface mismatches that are easier to resolve before scheduling.
- Run one period in parallel. Keep aSc as the published source of truth while you verify the Smootables result.
- Switch publication for one scope (campus, program, or period) once the parallel run looks correct.
- Roll out to the rest of the school in subsequent cycles. We support piloting and data migration so testing Smootables is fast and practical.
Questions schools ask when comparing aSc and Smootables
Is Smootables a direct replacement?
It can be. It replaces the planning, generation, editing, and publication steps. Schools using EduPage features alongside aSc can run both in parallel during transition.
What about migration of historic timetables?
Smootables supports structured import and AI-assisted extraction from spreadsheets and legacy exports. Historic timetables can be imported as reference; planning typically restarts from the next academic period.
Will planners need to relearn everything?
The core concepts are familiar: courses, groups, teachers, rooms, constraints, generation. The workflow is more planning-led and editing is more modern, but the conceptual model is recognizable to any aSc planner.
Does Smootables support the same level of constraint configuration?
Yes for the constraints that matter most: hard constraints on conflicts, capacity, availability, and dependencies; soft constraints for balance, gaps, preferences, and priorities. Some specialised switches are handled through the planning model or AI workflows rather than copied one-for-one.
What if our current generation step is fast enough?
Generation speed is rarely the deciding factor. The bigger gain is the time before and after generation: validation that catches problems earlier, and editing that keeps the planner in control afterwards.