Who this guide is for
Vocational and career colleges sit between standard secondary schools and higher education in scheduling complexity, and the market has not caught up. Most timetable software is either built for class-based secondary schools, or built for university course catalogs. Neither fits a college that runs workshops, mixed cohorts, individual pathways, and workplace learning alongside classroom periods.
This guide is for the planner, IT lead, or school leader who has to choose between those options. It is opinionated — Smootables is one of the categories below — but the dimensions and questions apply regardless of which product you choose.
Evaluation dimensions that usually matter
Vocational planners tend to weight these dimensions more heavily than a generic procurement checklist would suggest:
- Depth of the planning model — years, terms, courses, modules, and pathways, not just weekly grids
- Support for workshops, specialist rooms, and equipment as first-class resources
- Group, individual, and per-placement exemption handling
- Workload visibility before generation, not just after
- Pre-solve validation and infeasibility explanations
- Collaboration model — multiple planners, presence, audit logs, permissions
- Data migration from spreadsheets and legacy tools
- Daily change and substitution workflow
- Publishing, calendar export, and integration with SIS, MIS, LMS, and identity
- AI assistance that respects constraints and audit boundaries
Categories of products you will compare
Manual Excel or Sheets
Maximum flexibility, lowest tool cost. Becomes fragile beyond a small, stable schedule. Strong as an export format.
Legacy timetable suites
Mature generation, broad ecosystems (WebUntis-style publication and substitution). Settings-heavy, steep learning curve, optimization is often slower in practice than the 'automatic' label suggests.
Legacy automatic generators
Strong solvers, familiar to planners who already use them. Workflow patterns predate modern collaboration and AI.
AI-native planning platforms
Planning model and solver share the same data. AI assistance, structured imports, audit logs, and modern editing tools. Newer category — Smootables sits here.
How the categories usually compare on key dimensions
| Dimension | Excel | Untis | aSc | Smootables |
|---|---|---|---|---|
| Year and period planning depth | Manual | Strong with configuration | Limited | First-class |
| Solver-based generation | None | Strong | Strong | Strong |
| Individual pathways | Manual discipline | Class-first | Class-first | First-class |
| Pre-solve validation | None | Partial | Partial | Yes, with infeasibility reports |
| AI workflows | None | Not AI-native | Not AI-native | Built in with validated commands |
| Learning curve | Familiar | Steep | Moderate | Designed to be lower |
| Main tradeoff | Manual effort grows fast | Settings-heavy tuning cycles | Legacy workflow patterns | Newer product to validate |
Questions worth asking any vendor
These questions surface differences that a feature checklist will not:
- Show me how an individual student exemption is modeled and how it appears in the published timetable.
- Walk me through what happens when the solver cannot find a feasible solution.
- How do two planners working at the same time avoid overwriting each other?
- What does workload look like before any timetable is generated?
- How is AI scoped, audited, and prevented from bypassing hard constraints?
- What is the data migration path from our current setup?
- Which integrations are in place for SIS, MIS, LMS, identity, and calendar systems?
Where Smootables fits in the market
Smootables is positioned for vocational and career colleges that have outgrown spreadsheets but are not well served by legacy timetable suites. The planning model, solver, planner AI, and published views all share the same data, so individual pathways, workshops, and workplace learning are part of the core workflow rather than a configuration challenge.
It is the modern alternative to validate alongside legacy options, not a procurement-grade competitor on every feature row. For schools whose planning team spends weeks reconciling spreadsheets and tuning legacy settings, that tradeoff is usually worth a structured demo.
Questions vocational schools ask during evaluation
Is there an objectively 'best' product?
No. The right tool depends on scheduling complexity, planner team size, existing ecosystem, and how much spreadsheet legacy you carry. The dimensions and questions above are designed to make the choice transparent rather than tool-by-tool.
Should we keep our existing tool and add Smootables alongside it?
Many schools start that way: Smootables for year planning and workload, the existing tool for one more cycle of timetable generation. After one period, most schools move generation across as well, but it is not required.
What if our incumbent vendor matches the feature list?
Feature lists are noisy. Workflow fit is the real test. The vendor questions above are designed to expose how each product behaves under your scenarios — exemptions, infeasibility, validation, AI scope — rather than which checkboxes it can tick.
How long is a typical evaluation?
Two to six weeks for a structured demo and a parallel-run pilot. Larger multi-campus schools take longer. Smootables ships structured imports and AI-assisted extraction so the demo can use your real data.