Most tutors don't have a timetable. They have a pile of WhatsApp messages, a Google Calendar with half the lessons missing, and a memory that works until it doesn't. Every Sunday night becomes a reconstruction project: who's coming this week, at what time, and did Sara's mum ever confirm the reschedule?
A real tutoring timetable fixes this, and building one takes about an hour. Here's how to do it properly, whether you're a solo tutor with five students or a centre coordinating ten groups across three tutors.
Step 1: Lock in your recurring sessions first
Recurring lessons are the skeleton of every tutoring timetable. Most of your students come at the same time every week, so stop recreating those sessions manually.
List every student or group with a fixed weekly slot and place them on the timetable first. These blocks shouldn't move, and you shouldn't have to think about them again. If you're using software, set them up as recurring sessions once; if you're on a spreadsheet, mark them as fixed and shade them differently from one-off bookings.
A common mistake is treating every week as a blank page. Tutors who rebuild their schedule weekly spend 2-3 hours on coordination that a recurring setup does in zero.
Step 2: Define your bookable hours and protect everything else
Decide when you're available for new lessons, and make that window explicit. Maybe it's Tuesday and Thursday 16:00 to 20:00 and Saturday mornings. Everything outside that window is closed: that's your time for lesson prep, admin, and your actual life.
This single decision eliminates most scheduling chaos, because chaos comes from being theoretically available all the time. When a parent asks "can you do Sunday at 21:30?", the answer stops being a negotiation and becomes a policy.
If your platform supports student self-booking, this is where it pays off: publish your bookable hours, and students fill them without a single back-and-forth message. The timetable fills itself, but only inside the boundaries you set.
Step 3: Add buffer time between sessions
Back-to-back lessons look efficient on paper and fail in practice. A lesson runs five minutes over, a student joins late, you need two minutes to pull up the next group's materials, and suddenly you're 15 minutes behind for the rest of the evening.
Build 10-15 minute buffers between sessions. For online tutoring, buffers also absorb the small technical frictions: checking the classroom is ready, reviewing your notes from the student's last session, loading the worksheet.
Step 4: Put group sessions at anchor times
Group classes are the hardest blocks to move; five families have organised around that slot. Treat them as anchors: fixed, prominent, and scheduled at the times that work for the majority (typically right after school or early evening).
Then arrange your flexible 1:1 sessions around them. Never do it the other way around; rescheduling a group is ten conversations, rescheduling a 1:1 is one.
Step 5: Decide your reschedule policy before you need it
Reschedules are where timetables die. Without a policy, every cancellation turns into a negotiation, and your week dissolves into exceptions.
Decide now:
- How much notice does a student need to give? (24 hours is standard)
- Do late cancellations get a make-up lesson, or is the session counted?
- Where do make-up lessons go: a dedicated weekly slot, or your bookable hours?
Write it down, tell every student once, and apply it the same way every time. A reschedule policy isn't strictness; it's what makes the rest of the timetable trustworthy.
Step 6: Track what actually happened, not just what was planned
A timetable tells you what should happen. Attendance and time tracking tell you what did. Per student, you want to know: how many sessions they've attended, how many they've missed, and how much lesson time they've received.
This matters for three reasons: parents ask ("how many lessons has he actually had this month?"), billing depends on it if you sell hour packages, and patterns of absence are the earliest signal that a student is about to drop out.
If you're tracking this in a notebook, it works until you have more than a handful of students. Past that point, you want attendance recorded automatically when sessions happen.
Step 7: Review the timetable monthly, not weekly
Weekly tinkering is how timetables stay fragile. Instead, do a monthly review: which slots consistently no-show? Which evenings are overloaded? Is a group outgrowing its time? Adjust once a month, communicate the changes once, and let the timetable run.
Spreadsheet vs. dedicated tutoring software
A spreadsheet or Google Calendar can hold steps 1-4. Where they break is everything after: they can't enforce your bookable hours, students can't book themselves in, reschedules are manual edits, and attendance lives in a separate file that drifts out of date.
Dedicated tutoring scheduling software handles the full loop: recurring sessions you set once, self-booking inside your published availability, automatic attendance and time tracking per student, and, in TeamLilit's case, the live classroom attached to every session. The timetable isn't just a plan, it's where the teaching actually happens.
For a solo tutor, the switch saves a couple of hours a week. For a tutoring centre running multiple tutors' timetables, it's the difference between a coordinator role and a setting.
The one-hour timetable setup, summarised
- Place all recurring sessions, the fixed skeleton
- Publish your bookable hours, close everything else
- Add 10-15 minute buffers
- Anchor group sessions, flex 1:1s around them
- Write a reschedule policy and apply it uniformly
- Track attendance and hours per student automatically
- Review monthly, not weekly
Set it up once, and Sunday nights go back to being Sunday nights.
Ready to move your timetable off the spreadsheet? Start a free 14-day trial. No credit card required.
