Pupils & progress
How to keep useful driving lesson progress records
A useful record helps you and the pupil pick up the thread next time. It explains the context of the Lesson, what was recorded and what you want to return to.
Keep the pupil record and Lesson context together
In the current pupil workspace, open Lessons for the appointment history and Progress for recorded learning. Details groups Learning and Records & admin; Notes can be expanded when needed. Available sections depend on your permissions.
The continuing pupil record answers “who are we teaching and what is their current context?” A Lesson record answers “what happened at this appointment?” Syllabus progress answers “what has been recorded against these topics?” Each is useful, but none replaces the others.
Before the Lesson, review the recent context: the last shared feedback, relevant progress, known meeting arrangements and any information the pupil has provided. After it, record the work against the correct appointment and topics. That makes it possible to return to a particular Lesson without guessing which general note referred to it.
A practical record can include the topic, the conditions or exercise discussed, the recorded level of support and the point you intend to revisit. Keep factual observations distinct from interpretations and plans. This is a writing framework for records, not an assessment method or instruction about how to teach a driving skill.
Write something the next reader can use
“Good Lesson” describes your impression but gives the next reader little to work with. Ask what a future version of you would need to remember before the next appointment. A short specific note can be more useful than a long account of every minute.
Vague: “Good Lesson. Junctions improving.”
More usable: “Today’s focus was junction approach. The recorded topic level is Prompted. We revisited the point discussed last Lesson; Amelia asked to return to it next time. Next-session plan: review that feedback together before agreeing the focus.”
The second note identifies the topic, its recorded state, the pupil’s contribution and a next action. It does not claim independent performance, a test outcome or an official assessment. Use the actual available topic and level labels rather than inventing a grade because it sounds more precise.
- Identify the correct Lesson and topic.
- Record the facts you can support.
- Separate the pupil’s comment from your observation.
- State a concrete point to revisit.
- Read the note once as someone who was not in the car.
If the note depends on private background information, consider whether that detail belongs in the published feedback. A useful learning summary should stand on its own without copying every staff note into the pupil’s view.
Decide what is ready to share
Recording and publishing are separate decisions. Staff may need working notes while the pupil needs a clear account of what has been shared. Check the intended audience before assuming that saving a note made it visible between Lessons.
In M&M, the pupil workspace shows permitted progress and published feedback. It does not expose the whole staff workspace. After publishing, check that the feedback conveys the intended meaning and points to the right Lesson. If a pupil cannot see it, first establish whether it was actually published and whether their access is enabled.
Use the feedback to support a conversation. A pupil can revisit the recorded topic and bring a question to the next Lesson; the record does not replace the Instructor’s judgement or the pupil’s own account of the experience.
Look for continuity over time
Before the next appointment, compare the latest progress with the context of recent Lessons. A topic label alone may not explain the conditions under which it was recorded. The dated Lesson feedback supplies context for that discussion.
Keep earlier Lesson summaries available when plans or topic levels change. At the same time, do not confuse earlier summaries with a complete archive of every feedback edit: M&M does not claim that broader revision capability here.
A syllabus coverage count describes recorded coverage. It is not a prediction that the pupil is ready for a test or likely to pass. Missing records may mean work has not been entered, rather than proving it has never been discussed.
Finish with a usable next step: what should be read, clarified or revisited before the next Lesson? The between-Lessons pupil guide explains how the shared view fits that routine.
How Miles & Minutes handles it
Miles & Minutes connects the continuing pupil record, Lesson context, syllabus topic assessments and published feedback. The pupil sees their permitted progress and feedback, not a copy of the staff workspace. Recorded coverage is not a test-readiness score, and earlier Lesson summaries do not imply a complete revision archive of every feedback edit.
Explore the product context: Pupils & progress, For pupils
These are current controlled-access workflows, subject to account permissions and school/provider settings. Your signed-in Help centre gives operational guidance for your available controls.
Read the feature information alongside these guides. The controls in your authorised account depend on your role and settings.
Explore instructor featuresRegister Early Access interest · an invitation is not guaranteed.