Bookedly Blog
Guides on booking requests, lesson packages, student records, reschedules, group classes, and the small admin loops that can crowd out teaching.
Start here
Chasing a late payment is the most awkward admin task a solo tutor does — and the most avoidable. A clear records habit, a policy stated up front, and one calm script handle almost every case.
Read articleBrowse topics
A practical starting point for separating requested times from confirmed lessons before the message thread gets noisy.
Keep package price, amount paid, lesson credits, and balance changes close to the student record.
Check open time, class history, and balance state before moving a lesson to a new day.
Latest
Tutors lose real income to no-shows, but chasing after the fact fails. A prevention-first message system: expectations at booking, confirmations that stick, and a humane late policy.
Timing and wording rules for lesson reminder messages, with ready-to-send day-before and day-of templates that cut no-shows without nagging students.
A practical, not anti-spreadsheet comparison: the five failure patterns that appear when tutor admin outgrows a sheet, and what actually changes when lesson context moves into a workspace.
A realistic Friday or Sunday reset for solo tutors: clear requests, confirm the week, review package balances and payment statuses, handle reschedules, and pick one improvement — in under sixty minutes.
The operational handoff from first inquiry to confirmed first lesson: what to capture at intake, how the fit check works, and where tutors quietly lose students between the yes and the first slot.
A fair comparison: where booking links genuinely help solo tutors, where they lose lesson-package context and student history, and the specific signs that it is time for a tutor workspace.
Bookedly for solo tutors