A Student Progress Report Another Instructor Can Use

Use a longitudinal driving-school student progress report to preserve conditions, assistance, comparable evidence and the next instructor’s decision.

A driving school student progress report should let the next instructor answer four questions before the car moves: What was tested? Under which conditions? What help was still required? What should happen next? A lesson number, a percentage, or “doing well” cannot answer those questions.

The useful record has two layers. Keep the evidence from each lesson, then maintain a short current handoff built from the latest comparable evidence. That stops the second instructor from either repeating everything or moving the student into a harder situation because one old score looked good.

Download the printable student progress and instructor handoff template, or copy the fields and worked example below into the system your school already uses.

A lesson record and a progress handoff do different jobs

The driving lesson plan template starts with one session: its objective, route, instruction, observed performance and next step. A longitudinal progress report asks a different question: what does the history of those sessions tell the next authorized instructor now?

Record What it preserves Decision it supports
Lesson record What happened in one completed session How to close that lesson and plan the next one
Skill history Comparable observations across several lessons Whether performance is becoming more independent or only changing with the setting
Current handoff The latest evidence, limits and next objective How another instructor should continue without guessing

The distinction is not only theoretical. The UK Driver and Vehicle Standards Agency publishes both a lesson-by-lesson record and a progress-summary record. Its guidance says a learner may move up or down its five levels and that one version records each lesson while the other shows progress across skills. That is British teaching guidance, not a U.S. recordkeeping rule, but it demonstrates why a single permanent grade loses important context.

Use this current handoff

Put this summary at the top of the student’s authorized instructional record. Refresh it after a meaningful new observation rather than adding another vague note.

STUDENT PROGRESS HANDOFF
Record reviewed on:
Current instructor:
Next instructor, if assigned:
Approved curriculum or course:

CURRENT OBJECTIVE
Skill and observable action:
Latest date assessed:
Conditions: road type, traffic, speed, weather, familiarity and vehicle:

LATEST COMPARABLE EVIDENCE
What the student completed independently:
Exact verbal prompts or questions still needed:
What was demonstrated or retaught:
Physical intervention, if any, and its trigger:
Student's useful self-assessment:

NEXT DECISION
Repeat / modify conditions / add one variable / reassess or refer:
Next objective and why:
Condition to preserve or avoid:
Unresolved safety or instructional question:

“Comparable” matters. If a student handled turns independently on an empty residential road but needed help at unfamiliar intersections with pedestrians, keep both observations. Do not replace them with an average. The difference in road complexity may explain the difference in performance.

Record assistance as something another instructor can recognize

A label such as “developing” is only useful when the next instructor knows what it meant. Pair any school-approved level with the assistance actually observed:

  • Independent: the student noticed and completed the action without a cue.
  • Prompted: the instructor supplied a reminder, question, timing cue or sequence cue.
  • Retaught: the attempt paused so the instructor could explain or demonstrate again.
  • Physically assisted: the instructor used an approved control or steering intervention and records what triggered it.
  • Not assessed: the lesson did not create a fair opportunity to observe the skill. A blank is not a failure.

The DVSA’s published levels move from introduced and helped through prompted, independent and reflection. Whatever scale your approved program uses, the transferable information is the observed behavior and help behind the label—not the label alone.

A two-lesson example shows the handoff

The student and figures below are fictional. They demonstrate the record, not a universal performance standard.

Observation Conditions and evidence What changes next
Lesson 1, right turns Familiar low-speed residential loop, dry daylight. Six opportunities. Four early reminders to scan for pedestrians before entering. No physical intervention. Repeat the same routine and setting. Ask the student to say where the scan begins before the first attempt.
Lesson 2, right turns Same road type with slightly more traffic. Six opportunities. The last four needed one early prompt in total. Speed and lane position were independent. Test transfer at unfamiliar low-speed intersections. Keep traffic complexity limited and return to the familiar loop if observation deteriorates.
Current handoff Right-turn control is stable in familiar low-speed settings. Pedestrian scanning improved from repeated reminders to one reminder, but unfamiliar intersections have not been assessed. Add one variable: route familiarity. Do not describe the skill as fully independent in all conditions yet.

The useful conclusion is not “83% complete.” The next instructor knows what is stable, what improved, what remains untested and which single change will reveal whether the skill transfers.

Update the report in three passes

  1. Close the lesson. Record the objective, conditions, independent actions, prompts, reteaching, interventions and student reflection while the details are fresh.
  2. Compare like with like. Add the observation to the relevant skill history. Check whether a change came from the student, the environment, the instructor’s assistance or several of those at once.
  3. Rewrite the handoff. State the latest defensible conclusion and one next decision. Preserve an earlier limit when the newer lesson did not test it.

Before another instructor accepts the lesson, ask them to name the last comparable evidence and the next variable. If they can only name the package lesson number, the handoff is not ready.

Keep the handoff narrow enough to share safely

Instructional continuity does not require every personal detail in the student’s account. Record the driving effect you observed, the assistance required and the next instructional decision. Keep unrelated family, health or personal conversation out of a general lesson note. The RouteOS guide to parent updates after a teen’s lesson explains why an internal lesson record and an authorized parent summary are related but not identical.

This template also does not replace any record, signature, retention period, curriculum or access rule that applies to your school. Those requirements vary by jurisdiction and program. Add required fields through the school’s approved process instead of treating a general progress template as a compliance form.

Where RouteOS fits

RouteOS sells driving-school software, so our interest is commercial. The current RouteOS Student Journeys and Student Information page shows completed appointments contributing to a shared journey, purchased lessons beside that journey and instructor access limited by assigned roles and student scope. The inspected September 2, 2026 code report likewise describes journey progress as a projection from orders, bookings, completions, student facts and outcomes rather than a staff-edited percentage.

The handoff template on this page is an operating resource. It is not a claim that every field shown here is enabled as a live RouteOS field for every school. Product setup, permissions, curriculum mapping and school policy still determine what staff can record and see.

Product evidence and the external progress-record source were checked September 13, 2026. Recheck this guide when RouteOS record fields, role behavior or the cited DVSA guidance changes.

Put the idea to work in your school.

See how RouteOS connects lesson scheduling with the rules, resources and routes behind your day.

See RouteOS in action