Lessons are the individual teaching sessions in Bobbin - a scheduled session between a Tutor and one or more Students. In an organization that runs Bobbin on its own, an Administrator creates and schedules Lessons directly in Bobbin. Every Lesson belongs to a Course.
Creating a lesson
Because every Lesson belongs to a Course, make sure the Course exists first, with the right Students and Tutors on it (see Courses (for non TC users)). You then create the Lesson against that Course, choosing:
the Course the Lesson belongs to;
the Tutor delivering it;
the Student or Students attending;
the date, time and duration.
Once created, the Lesson appears in the Planned stage, ready for a Lesson plan.
Creating a lesson from a Course
When you create a Lesson from a Course, you can pre-select the objectives you want to cover in that session. Bobbin uses those objectives to auto-draft the Lesson Plan for you, which you can then refine or edit.
Where the Student's last Progress Report included Next steps, those are fed into the plan too, so it picks up from what was agreed last time.
After the Lesson, its insights can show which of the Course objectives were actually covered, grouped by module. That's a cross-check rather than an automatic update — Course Coverage on the outline still moves when someone ticks a topic by hand.
Join links
Each Student on a Lesson gets their own join link. A link belongs to one Student — anyone who opens it joins the Lesson as that Student — so links shouldn't be passed around, and each Student should get their own. It's what keeps attendance and the Lesson insights accurate.
Tutors can see the join links for their own Students on the Lesson page, so they can resend one to a family who can't find it.
Emails about a lesson
Because you manage everyone in Bobbin, Bobbin does the emailing. Administrators control which of these go out under Workspace > Settings > Emails:
Send lesson-scheduled emails when lessons are created — Students, Tutors and Clients get the Lesson details when it's booked.
Send reminder emails before lessons start — a reminder shortly beforehand, in each person's own timezone.
Send emails when lessons are rescheduled or canceled — participants are told what changed.
Send attendance emails after lessons start — Administrators and Clients get an email ten minutes in showing who is present and absent.
A Student added without an email address won't receive any of these, though their Client still will.
After you create a lesson
From here, a Lesson follows the same path for every Bobbin organization: it moves through Planned, Awaiting Report and Complete, with a Lesson plan beforehand and AI insights, a transcript and a report afterwards. Rather than repeat it here, see:
Lessons — the full Lesson lifecycle, Lesson plans, AI insights, transcript and recording.
Creating a Lesson Report and Completing a Lesson Report — finishing a Lesson and sending the report.
Two things worth knowing up front: a Lesson doesn't need a usable recording to be completed and billed — the Tutor just writes the report themselves — and each Lesson has a Notes tab where Administrators can record Internal notes that nobody else can see.
Editing or canceling a lesson
A Tutor's permission level on the Course controls whether they can add, edit, complete or delete its Lessons; Administrators can always manage them. You can edit a Lesson's details or remove it while it's still in the Planned stage.
If reschedule emails are switched on, moving or canceling a Lesson tells its participants what changed.