Documentation
Use this documentation hub to move from first setup to a reviewable timetable: start a project from scratch or from existing information, define the school week, add classes, teachers, subjects, rooms, and rules, then generate, review, edit, publish, or export.
Use these focused docs when you need step-by-step help for one part of the Schedull workflow.
A good timetable starts before generation. Gather the school data that actually limits lesson placement, then enter it in the same order your school reasons about scheduling.
Schedull separates timetable planning into a few core objects and workflow surfaces. Understanding these terms makes setup and troubleshooting much easier later.
| Concept | Meaning |
|---|---|
| Project | The workspace for one school, year, campus, or planning cycle. It stores schedules, classes, subjects, teachers, rooms, rules, and generated results. |
| Timetable structure | The teaching days and time slots available for lessons. A project can use one shared structure or class-specific structures. |
| Class | A student group that receives lessons during the week, such as a year group, course, section, or classroom group. |
| Subject | A lesson type assigned to a class, with a weekly session count and optional teacher or room requirements. |
| Teacher | A staff member who can teach one or more subjects and can have availability, workload, and timing rules. |
| Classroom | A physical or specialist space that can be reserved for lessons when room planning is part of the timetable. |
| Rule | A requirement or preference that guides placement, such as unavailable slots, spacing between sessions, or preferred teaching times. |
| Project Hub | The readiness view that summarizes setup progress, health checks, and next steps before generation, review, or fixes. |
Start from scratch when you want a clean setup, or start with information from a file or a blueprint when the school already has reusable data. Name the project clearly so the planning cycle is easy to recognize later.
Define teaching days, breaks, and time slots before adding detailed data. Use one shared structure unless some classes genuinely need different days or period counts.
Complete the core teaching data before generation. Weekly subject loads, teacher assignments, and class lists are the foundation of every valid timetable run.
Enter teacher availability, part-time limits, specialist rooms, and classroom or building requirements where they matter. Use mandatory rules for real blockers and preferences for better patterns.
Check the Project Hub before generating. Use it to spot missing setup pieces, review health signals, and confirm that the project data, teacher availability, room requirements, and rules are ready for a generation run.
Generate a draft timetable, review it from class, teacher, and room views, use manual editing for final school judgement, then publish or export the version the school will actually use.
When you start generation, Schedull uses the timetable structure, classes, teachers, subjects, rooms, and rules in the project to place sessions into the week. Progress appears in the browser while the app searches for a valid result, and the project health and generation reports help explain what to review next.
After a result is ready, review it from class, teacher, and room views. Look for uneven days, late lessons, room pressure, and teachers with tight availability, then use manual editing for final corrections before publishing a shared calendar or exporting the timetable.
If generation cannot find a timetable, the cause is usually overloaded weekly requirements, limited teacher availability, specialist room pressure, or too many mandatory rules competing for the same slots.
| Problem | What to check |
|---|---|
| No timetable found | Compare each class's weekly subject total with its available periods and remove any rule that is only a preference. |
| Teacher has too few available slots | Check part-time blocks, fixed meetings, and subjects assigned to the same teacher across multiple classes. |
| Imported or reused setup needs cleanup | Review imported classes, subjects, teacher assignments, and timetable drafts before regenerating. Fix duplicates and confirm that the school week matches the real timetable structure. |
| Special rooms or buildings are creating conflicts | Review lab, gym, workshop, classroom, and building requirements. Only require a specialist space when the lesson truly needs it. |
| Some sessions must stay fixed | Represent the real difference in the timetable structure or the underlying rules before the next generation run, then use manual editing afterward for small final changes that do not need to become permanent constraints. |
Use these pages when you need a focused workflow guide, rule guidance, support answers, or plan information.