Advice & Resources
How to Use Learning Walk Data
Read activity, evidence quality and breadth separately, then act on the patterns you can genuinely trust.
Read activity, evidence quality and breadth separately, then act on the patterns you can genuinely trust.
Learning walk data is not simply a pile of visit notes to sort into themes. A strong process gives each response a clear place in a wider improvement enquiry: the work has a purpose, focus and scope; cycles organise the questions; classroom visits build the response picture; and evidence review helps leaders judge how much trust to place in it.
A learning walk enquiry is useful only when three separate things are understood: was the planned activity completed, is the evidence trustworthy, and where across the school did that evidence come from?
Keeping those questions separate prevents a high visit count from being mistaken for an accurate or representative picture. This guide sets out a recommended structure for holding the work together, from the initial plan to the decision that follows.
The levels are connected, but they do different jobs. Reading the data well begins by keeping each one clear.
Give the work a purpose, timeframe and optional scope so the whole improvement story stays connected.
A framework runs from focus to element to question. The focus is the main planning unit, and its questions inherit its priority.
Use a reusable combination of focuses and questions, with its own dates, visit length and classroom-visit target.
One or more staff use a selected cycle. A learning walk can contain several classroom visits.
Treat this as the calculation unit: record one response to every included question during each visit.
Notes and photographs do not sit in a separate generic record. They stay attached to the question and response they support, preserving the route from what happened in a classroom to the later insight.
A number in a tracker or report only makes sense in relation to the plan that produced it. Before interpreting a pattern, check:
Scope says where evidence may be gathered. It does not calculate how many visits are needed.
Scheduling says who will walk and when. It does not create or reduce the evidence target. Ad-hoc and scheduled walks can both contribute to the same cycle plan.
A useful planning method sets an intended evidence depth and gives each focus a priority. Translate those decisions into target responses for the questions, then calculate a sensible classroom-visit target for each cycle. These are transparent planning targets, not claims of statistical certainty.
Submitted classroom visits count as activity. Because every visit creates a response for each included question, visit progress and response progress are connected, but they are not interchangeable labels. Use your tracker, reporting view or dashboard to check:
The planned enquiry is not fully covered until every active cycle reaches its own classroom-visit target. Extra visits in one cycle do not compensate for an incomplete cycle containing different questions.
Reaching the activity target means the planned work happened. It does not yet mean the supporting evidence is strong, or that visits were spread widely enough to describe the whole intended scope.
Evidence assurance sits between completing walks and using their findings. Agree in advance whether evidence can be used as submitted, whether a sample will be moderated, or whether notes require review and approval before they contribute to reporting.
Evidence quality is not a score for the teacher or lesson. It is a judgement about how strongly the recorded evidence supports an answer to the enquiry question.
Evidence can be plentiful and well supported but still come from a narrow part of the school. Breadth asks what the enquiry has and has not represented. Look at rooms, year groups, classes or groups, subjects and observer spread where those details are available.
Breadth is not inferred from school size, pupil numbers or a high visit count. A breadth gap should stay visible and inform targeted follow-up; it should not silently recalculate the original evidence target.
Did we complete enough of the planned work?
How strongly does the evidence support the responses?
Where did visits happen, and what did we miss?
"Coverage" can describe whether the planned questions and cycles have received enough activity. Breadth describes where that evidence came from. Keep both visible: completing the first does not guarantee the second.
| What the review shows | What to do next |
|---|---|
| One cycle remains below target. | Complete targeted visits in that cycle; do not use surplus activity elsewhere as a substitute. |
| Activity is complete, but evidence quality is weak. | Improve evidence capture or review. More of the same weak evidence will not solve the problem. |
| Evidence is strong, but breadth is narrow. | Treat the finding as valid for the contexts seen and gather evidence from the missing parts of scope. |
| A pattern appears to change between cycles. | Check that the same questions and compatible contexts are being compared, then inspect the underlying evidence. |
| Activity, quality and breadth all support the pattern. | Celebrate the strength or choose a focused improvement action, then plan how the same question will be revisited. |
Compare change between cycles and between genuinely compatible enquiries. If the framework, question wording, scope or evidence conditions have changed substantially, describe the two pictures separately rather than presenting a false trend.
A school runs a half-term enquiry to understand how well new learning builds on prior knowledge. The relevant focus is high priority and its questions are placed across two cycles.
Staff complete scheduled and ad-hoc learning walks. Each walk includes several classroom visits, and each visit adds a response to every question in the selected cycle.
The cycle target is reached and reviewed evidence is strong, but a coverage check shows that Year 9 and one subject area are barely represented. Leaders do not call the result a whole-school finding; they arrange targeted visits to fill that gap.
With stronger breadth, a question-level review shows a repeated strength in making prior knowledge explicit, alongside one narrower development theme. Leaders share the effective practice, support the relevant team and revisit the same questions in a later compatible cycle.
A useful staff summary should preserve the enquiry story rather than present a detached percentage. Include:
Whole-school reporting should use patterns across the enquiry, not turn short visits into individual teacher judgements. Individual feedback should remain private and developmental. See our guidance on giving feedback after a learning walk and linking findings to professional development.
Volume shows activity. It does not prove evidence quality or representative breadth.
Each cycle carries its own questions and target. An overall total must not hide an incomplete cycle.
Assignments and dates organise delivery; they do not decide how much evidence a question needs.
Use the overview to find the pattern, then drill through the element and question to the evidence beneath it.
A strong learning walk process turns a school priority into a structured enquiry, the enquiry into manageable cycles, and classroom visits into question-linked responses and evidence. Reporting should preserve that structure, not compress it into a single score.
Check activity, quality and breadth as separate truths. When all three support the same pattern, return to the underlying evidence, choose a proportionate action and revisit the focus over time. That is how learning walk data becomes trustworthy improvement insight.
LearningWalks brings planning, evidence and insight together so every walk has a clear purpose.
Take our interactive 10-question quiz to see how your understanding stacks up. Get instant feedback — and a celebration if you ace it!
Bring planning, classroom evidence and insight together in one place — and turn what you see into meaningful improvement.
