Office hours are written once
A weekly window with lesson length, mode and room. A seasonal window has an end date, and a single day can be blocked without touching the rest.
One-to-one lessons are arranged over chat and cancellations get lost in the thread. Here a teacher writes their hours once and the student clicks a free slot: it becomes an ordinary lesson that the schedule, the register and the billing already know.
A weekly window with lesson length, mode and room. A seasonal window has an end date, and a single day can be blocked without touching the rest.
The window loses the teacher's own lessons, other bookings, blocked days and school days off. What is left is a list of slots to click.
The booked slot lands in the group schedule as an ordinary lesson, so the timetable, the register and the per-lesson payment plan all see it. There is no second calendar.
The school sets how many hours before a lesson cancelling is free. After that the lesson stays in the schedule and is charged, and the student reads this next to the button, not afterwards.
The teacher gets an in-app sign for a new slot and for a cancellation, the student gets a confirmation email. A parent books and cancels for their child from the same screen.
A module is a permission, and which records may be touched is settled on write, not in the menu.
| Role | Sees | Changes |
|---|---|---|
| Owner | Bookings across the school, every teacher's availability and the booking settings. | Every teacher's windows and blocks, bookings, cancellations and the three school numbers. |
| Teacher | Only bookings with themselves and their own hours. A colleague's schedule stays hidden. | Own windows and blocked days, booking a student from their groups and cancelling. |
| Student | One screen: the teachers from their groups, their free slots and their own bookings. | Books a free slot and cancels their own booking, with the consequence written by the button. |
| Guardian | The same screen as the student, separately for each linked child. | Books and cancels lessons for the child. Other people's children are out of reach. |
The things that only surface in the third week of working with the module.
The school sets how many hours before a lesson a cancellation is free: 24 by default, 336 at most. Before that line the lesson disappears from the schedule and the per-lesson plan does not count it. After it the booking becomes "Cancelled late", and the lesson STAYS in the schedule marked as cancelled late, so the instalment counts it. The consequence shows in the cancel dialog before anyone clicks. The owner changes the line in Settings, on the Bookings tab.
No. A booking first locks the teacher's schedule, then counts free slots again with the same function that draws them on screen, and only then creates the lesson. A second click on the same slot is told that it is already taken. Hours in which the teacher has other lessons in the Schedule are taken too, even in another group.
Only teachers assigned to their own groups. The lesson lands in the group through which the student knows that teacher, so a one-to-one group is an ordinary group with one student, created in Groups. A student with no group is told there is nobody to book with. A newcomer without an account cannot book: they come in through the CRM, and booking follows once they are a student.
200 open bookings on the Pro plan and 600 on the School plan. Open means booked and still ahead: a cancelled booking never counts, and a past one drops out on its own once its time passes. So the limit measures the current schedule, not history. It is hard: above it, booking is refused. Availability windows (40 per teacher) and blocked days (120 at once) have a fixed ceiling in code, not a plan limit.
Yes. A guardian has the My bookings screen with a separate section for each linked child: teachers, free slots and booked lessons. They book and cancel only for their own children, and an archived child leaves the screen. The confirmation email goes to the address on the student record, in the recipient's language. The school team sees on each booking who made it.
On the Availability tab. A window is a weekday, a from and to time, a lesson length from 30 to 180 minutes, a mode and a room, plus an optional "Valid from" and "Valid to" for a seasonal window. The window is cut into slots by lesson length. A day off for the teacher goes into the Blocked days section. A teacher edits only their own windows; management arranges anyone's.
The teacher gets an in-app notification about a new booking and about a cancellation, marked when it came late. The student gets a confirmation email with the time and the teacher's name. There is no reminder the day before yet. The lesson itself is an ordinary class, so it sits in the Schedule and the Journal like any other.
The module works and writes real lessons, but it is being tested: some things may still change. Every screen of it, including the student and guardian screen, carries a beta sign that cannot be dismissed, because it is the module's state, not a message. A school that does not want to rely on it switches it off in Settings: the data can then be read but not changed.
14 days on your groups and instalments. No card, no strings.