Key takeaways
- Model academic years, terms, courses, and resources in one Smootables workspace before timetable generation.
- Planners collaborate on shared year plans; teachers and admins review and comment before publication.
- Completeness checks surface gaps before the constraint solver runs, not after a failed timetable solve.
- The year plan feeds automatic timetabling in Smootables; no parallel Microsoft Excel workbook to reconcile.
Why is school year planning a separate step from timetable generation?
Schools need terms, courses, groups, teachers, and rooms to be clear before any solver runs. Year planning is the structured phase where leadership and planners agree that structure; timetable generation is the constraint-based phase that places lessons into periods. Smootables treats both as one data model, not two exports linked by copy-paste.
Many schools still split that work across Microsoft Excel, Google Sheets, email, and a separate timetable tool. Smootables is school year planning software built so academic years, terms, periods, courses, and resources live in one workspace that feeds automatic school timetabling without re-keying. Before generation, see how to create a school timetable for the handoff-to-publication workflow.
How does school year planning software compare to spreadsheets and separate tools?
Buyers often compare Excel templates, standalone year planners, and timetable suites. The table below shows why a planning-first workspace that shares data with timetable generation reduces rework for vocational colleges, technical schools, and general secondary schools alike.
| Dimension | Spreadsheets / separate year file | Smootables |
|---|---|---|
| Year structure and terms | Tabs or files per term; manual sync when dates shift | Academic years, terms, school day profiles, and holidays in one model |
| Courses, groups, and pathways | Duplicate rows when groups or individual students change | Courses, groups, individual assignments, and exemptions as linked entities |
| Staffing and workload | Side calculations; contract errors found late | Workload panels and contract checks before timetable generation |
| Handoff to timetabling | Re-import or re-type into a timetable generator | Same model powers pre-generation validation and the constraint solver |
| Collaboration | Versioned filenames and one planner who knows the macros | Multi-planner access, presence, role permissions, and audit logs |
| Integration with SIS / MIS | Manual CSV exports each term | Structured import and integrations; Smootables stays planning source of truth |
What must schools decide before generating a timetable?
The same planning decisions must be explicit before the solver runs, no matter which tool a school uses. Smootables captures them as structured data so automatic school timetabling does not start on incomplete input.
- Academic calendar: terms, holidays, and school day profiles
- Course catalog and which modules run in which term or campus
- Student groups, mixed cohorts, and individual pathway assignments where applicable
- Teacher contracts, availability, skills, and target teaching loads across the year
- Rooms, workshops, labs, and equipment inventory with capacity rules
- Policy constraints you expect the solver to respect (lunch, gaps, pinned blocks)
Who is involved in the school year planning cycle?
Smootables gives each role visibility into the same year model. Leadership approves structure; planners maintain data; teachers and coordinators comment before publication, without emailing spreadsheet attachments.
School leadership
Track planning progress, staffing pressure, and feasibility in Smootables before the academic year locks. Approve terms, course offers, and resourcing once workload panels look sound.
Timetable planners
Model years and terms, distribute course hours, attach groups and resources, and run completeness checks. The same workspace later drives constraint-based generation, with no second database.
Teachers and coordinators
Review proposed plans via shared links, comment on assignments that affect them, and flag issues while they are still year-planning fixes, not post-publication timetable emergencies.
How do schools move from setup to timetable generation handoff?
School setup, year planning, and timetable generation share one live model in Smootables. The five steps below replace a spreadsheet planning season followed by re-importing the same data into a separate timetable generator.
- Configure the school in Smootables: campuses, academic years, terms, school day profiles, holidays, and the course catalog.
- Add resources: teachers with contracts and availability, rooms and equipment with capacity rules, and student groups.
- Plan teaching across the year: distribute hours by term, assign groups and individual students, set teacher and room preferences.
- Validate completeness: workload panels, staffing pressure, and pre-generation checks flag gaps before the solver runs.
- Hand off to automatic school timetabling with planning context intact; edit, pin, and publish from the same Smootables workspace.
Does the year plan feed automatic timetable generation in Smootables?
Yes. School year planning and timetable generation share one Smootables model. When a course moves term, a teacher's contract changes, or a workshop room goes offline, planners update the year plan once; the next constraint solver run and published views reflect that change.
Schools that outgrow Excel year planning gain the most: the year plan is no longer a workbook you reconcile against timetable exports. It is the source of truth for validation, generation, substitutions, and audit logs through the full academic cycle.
What completeness checks run before the constraint solver?
Smootables pre-generation validation surfaces year-planning gaps that legacy tools often reveal only after a failed solve. Fix these in the planning workspace before you run automatic timetabling.
- Courses missing groups, allocated hours, or assigned teachers
- Teacher contracts that do not match allocated teaching hours
- Rooms or equipment required but unavailable on the right campus or term
- Group conflicts and individual students with overlapping pathway choices
- Terms or periods with no teaching plan yet, or visible placement gaps
Questions schools ask about academic year planning software
Who in the school should own academic year planning?
Most schools assign year planning to a team led by the timetable planner, with leadership reviewing progress and approving structure. Smootables supports multiple planners, role-based access, presence indicators, and audit logs so the team collaborates without overwriting work.
How does Smootables import the school data we need for year plans?
Smootables supports structured import from spreadsheets, CSV, and timetable exports, plus AI-assisted extraction from messy files. You can also build a year from scratch and add resources as the plan matures.
Can we reuse last year's plan in Smootables?
Yes. Academic years can be archived, cloned, and compared. Many schools clone last year's structure, then adjust courses, hours, and groups instead of rebuilding the full model each summer.
Does Smootables replace our student information system (SIS)?
No. Smootables is the planning and timetable source of truth and integrates with your SIS, MIS, LMS, identity, and calendar systems. Student records stay in the SIS; scheduling decisions stay in Smootables.
How is Smootables different from an Excel year-planning template?
Excel templates capture a snapshot and break under multi-planner edits. Smootables keeps years, courses, resources, and constraints as a live validated model that feeds automatic timetabling and collaborative edits without fragile formulas.