The first week of a private lesson decides whether the next three months run smoothly. Students who leave that week with clear goals, a settled schedule, known materials, and one agreed communication channel show up prepared; students who leave with a vague “we will figure it out as we go” drift into reschedules, mismatched expectations, and the slow fade of a course that never quite started. Onboarding is not bureaucracy — it is the small amount of structure that lets the actual teaching begin without friction, and it takes about one organized week to do well.
This checklist covers the first-week routine for a new student, adult or child. It pairs with the trial lesson structure for private tutors — the trial is where fit is tested, and onboarding is where the working relationship is built — and it leans on the printable student goal sheet for the first private lesson as the artifact that captures the goal-setting step. Communication patterns build on the parent update message template, and the materials step connects to the course materials maintenance checklist. One boundary matters throughout: collect what the teaching requires and nothing more, because a tutor who hoards personal data creates a privacy obligation they do not need; the general principles in the GDPR overview are a reasonable reference for data-minimization thinking, without this article becoming legal advice.
Start With Fit Questions
Before goals or logistics, confirm the fit the trial suggested. Ask what the student wants to be different after three months, in their own words — the answer often surprises both sides, and it quietly exposes mismatches before money and time are committed. Ask what has not worked before: the previous course, the self-study attempt, the tutor who moved too fast. Ask about constraints honestly — time available, energy patterns, deadlines that matter — because a plan that ignores constraints is a plan that fails politely. With children, ask the parent what they observe and then ask the child separately; the two answers differ, and the difference is diagnostic. This conversation takes twenty minutes and does more for retention than any teaching technique, because students stay with tutors who heard them in week one. Write the answers down — not verbatim biography, but the two or three facts that will shape the plan.
Set Goals And Write Them Down
Turn the fit conversation into two or three concrete goals with the student, not for them. “Get better at French” is a wish; “hold a ten-minute conversation about daily life without switching to English” is a goal, and the difference matters because only the second can be measured in week six. Use the printable student goal sheet for the first private lesson to capture the agreed version in the student’s own phrasing where possible — ownership of wording becomes ownership of the goal. Set a checkpoint date at the same moment, roughly six weeks out, when the goals get revisited openly. The checkpoint does two jobs: it measures progress, and it signals that progress is expected, which is itself motivating. A goal written down with a date next to it transforms the vague hope of improvement into a shared project with a schedule, and shared projects survive the rough weeks that kill vague hopes.
Lock The Schedule And The Materials
Two logistics failures end more private courses than pedagogy ever does: an unstable schedule and missing materials. Fix the schedule first — same day, same time, treated as fixed unless genuinely impossible — because lessons that float around the week get squeezed out of it, one exception at a time. State the cancellation norm at the same moment; a sentence about notice periods agreed in week one prevents the resentment of month three. Then materials: decide what the student needs before each lesson, who provides it, and where it lives. Run the list through the course materials maintenance checklist so nothing depends on memory. For online lessons, this includes the technical baseline — platform, backup connection plan, and a quick equipment check in week one rather than a frozen screen in week four. Ten minutes of logistical clarity here buys back an hour of friction across the course.
Agree The Communication Channel
Decide now where lesson-related communication lives — one channel, agreed by both sides — so that homework, schedule changes, and quick questions do not scatter across three apps and two inboxes. State response-time expectations in both directions: when the student can expect an answer, and when you expect homework questions before rather than after the deadline. For younger students, set the channel and expectations with the parent explicitly, and use the parent update message template pattern for the recurring update rhythm. The channel decision sounds trivial and is not: scattered communication is where assignments get lost, reschedules get argued, and small frictions accumulate into the feeling that the course is disorganized. One channel, one rhythm, one set of expectations — the whole system fits in a two-minute conversation, and it protects every later week.
Set Practice Expectations And A Privacy Boundary
Close the week by making practice concrete. Agree how much, how often, and what “done” looks like — and connect it to the goals from earlier in the week, so practice reads as the path to the student’s own target rather than assigned labor. Be honest about minimums: twenty minutes five times beats two hours once, and students who know the real minimum stop treating anything less than perfection as failure. Then the boundary: onboard with data-minimization in mind. You need contact details, the goals, and any learning-relevant context the student or parent volunteers — you do not need identity documents, medical details, or family circumstances beyond what affects the lessons. Store what you collect somewhere with basic protection, share it with nobody, and delete it when the course ends. This is not legal advice, just good practice: the less unnecessary data you hold, the less there is to lose, and students trust tutors who are visibly careful with their information.
The First Week At A Glance
| Step | What goes in it | When |
|---|---|---|
| Fit questions | Goals in the student’s words, what failed before, constraints | Day one conversation |
| Goals written down | Two or three measurable goals plus a six-week checkpoint | End of day one |
| Schedule and materials | Fixed slot, cancellation norm, materials list and owner | Days two to three |
| Communication channel | One channel, response expectations, parent loop if relevant | Days three to four |
| Practice and privacy | Practice minimums and a data-minimization boundary | End of week one |
Five steps, one week, every item a conversation rather than a form — the checklist is short on purpose, because onboarding works when it feels like care rather than administration.
What Onboarding Is Not
Two clarifications keep the checklist healthy. Onboarding is not an interrogation: every question exists to shape the teaching, and questions that do not shape the teaching should not be asked — this is where the privacy discipline and the pedagogy meet. And onboarding is not a one-time form: the goals get revisited at the checkpoint, the schedule gets renegotiated when life changes, and the channel expectations get adjusted as the relationship matures. The first week establishes the system; the months that follow maintain it. Tutors who treat onboarding as an ongoing posture — clarify goals when they drift, restate norms when they slip — find that the “slow fade” students rarely fade at all, because the structure that would have caught them was never only in week one. That is the real return on one organized first week: not a completed form, but a course that stays intentional long after the checklist is done.