Mind the Gap: Making Assessment Feedback Meaningful Through GROW Lessons

8 hours ago

8 min read

Moving beyond marks and grades to help students understand their mistakes, recognise their strengths and take ownership of improvement.

There is a familiar moment in teaching that I suspect most of us will recognise. You return a marked assessment, students immediately look for their mark or grade, compare it with the person sitting next to them, and then… move on.

All those hours spent marking, annotating and identifying misconceptions, and sometimes the most important part of the process is over in a matter of seconds.

It raises an important question: are we giving students feedback, or are we actually helping them use it?

This is something I've been reflecting on recently, particularly following a series of topic assessments with my GCSE Computer Science and A Level Business classes.

Rather than returning assessments and simply working through the answers together, I wanted to create a structured opportunity for students to interrogate their own performance, understand precisely where marks had been gained or lost, and identify meaningful next steps.

Enter GROW: Get Reflecting on Work.

Feedback is only useful if something happens next

We know that feedback has the potential to make a significant difference to learning. The Education Endowment Foundation's guidance on teacher feedback emphasises the importance of providing information that helps pupils move forward, alongside planning opportunities for them to receive and use that feedback.

That final part is particularly important.

A beautifully annotated assessment is not necessarily an effective assessment. Equally, a detailed mark scheme is of limited value if students never engage with it.

As teachers, we can spend considerable time identifying errors, writing comments and highlighting improvements. However, unless students are given the opportunity to process that information, the impact may be limited.

I wanted to shift some of that responsibility back towards the students.

Not by abandoning teacher feedback, but by making students more active participants in the process.

Introducing GROW: Get Reflecting on Work

The idea behind GROW is relatively straightforward.

Rather than treating assessment feedback as something that happens to students, I wanted it to become something students actively do.

For my recent lessons, I developed a structured activity called Mind the Gap, built around question-level analysis (QLA).

Students were given their marked assessments, the relevant mark schemes and a series of prompts designed to help them identify:

Where they had successfully demonstrated knowledge and understanding.
Where marks had been lost and, importantly, why.
Whether errors were caused by gaps in knowledge, misunderstood questions, imprecise terminology or weaknesses in exam technique.
What they needed to do differently next time.

The intention was not simply to produce a list of mistakes. It was to encourage students to think more carefully about the relationship between what they knew, what they wrote and what the examiner was actually rewarding.

I allocated approximately 20 minutes to the initial reflection, making it a manageable part of a normal lesson rather than an entirely separate assessment exercise.

Mind the Gap: Looking beyond the total mark

One of the limitations of focusing solely on an overall mark is that it tells us relatively little about the nature of a student's understanding.

Two students might achieve exactly the same score but have very different learning needs.

One may have secure subject knowledge but struggle to apply it to unfamiliar contexts. Another may understand the question structure but lack the technical vocabulary required for a fully developed answer.

A third might know the content but fail to provide sufficient detail.

If we respond to all three students in exactly the same way, we risk missing the opportunity for more targeted improvement.

This is where question-level analysis becomes particularly valuable.

During Mind the Gap, students work through their assessment question by question, comparing their responses with the mark scheme and identifying the specific reasons for any lost marks.

Crucially, I wanted students to move beyond writing things such as 'I need to revise more' or 'I need to write more detail'.

Those statements might be well intentioned, but they are rarely actionable.

Instead, students were encouraged to identify something precise:

'I need to explain how the cache improves CPU performance, rather than simply stating that it stores frequently used data.'

Or:

'My Business response included relevant knowledge, but I needed to develop the chain of analysis and link it more explicitly to the business context.'

Suddenly, the feedback becomes considerably more useful.

GROW in GCSE Computer Science

I first used the activity with my Year 10 GCSE Computer Science students following an assessment on systems architecture.

This topic provides an excellent opportunity for reflection because students are expected not only to remember technical information but also to explain processes and relationships accurately.

A student may be able to identify the purpose of a CPU component, for example, without fully explaining its role within the fetch–decode–execute cycle.

Similarly, students may recognise terms such as cache, registers or clock speed but struggle to explain their significance with sufficient precision.

During the GROW activity, students were asked to compare their answers directly with the OCR mark scheme.

They needed to consider whether they had:

Used appropriate technical terminology.
Explained concepts rather than simply naming them.
Included sufficient detail to access the available marks.
Answered the question that had actually been asked.

The distinction between knowing something and demonstrating that knowledge effectively in an examination was central to the task.

For students who had performed particularly well, I included an additional stretch and challenge activity. Rather than asking them to repeat work they had already mastered, they could deepen their understanding by exploring more demanding applications of systems architecture.

This mattered to me because feedback lessons should not become sessions in which the highest-achieving students simply wait for everyone else to catch up.

GROW in A Level Business

I also adapted Mind the Gap for my Year 13 A Level Business students.

Although the underlying principles remained the same, the focus naturally shifted.

At A Level, the challenge is often less about recalling an isolated fact and more about constructing a convincing, contextualised argument.

Students need to demonstrate accurate knowledge, apply that knowledge to the business in question, develop chains of analysis and, where appropriate, make supported judgements.

A student might produce a response that sounds confident and contains relevant terminology but still lose marks because the analysis is insufficiently developed or the evaluation lacks a clear justification.

The GROW task therefore encouraged students to examine the relationship between their written responses and the assessment objectives.

Were they demonstrating knowledge? Were they applying it effectively? Had they developed their analysis? Was their evaluation supported by a reasoned judgement?

This helped to make the sometimes rather abstract language of assessment objectives more tangible.

Rather than simply being told that their evaluation needed improvement, students could identify what was missing and how they might strengthen it.

Importantly, the activity also reinforced the value of reading mark schemes critically. They are not simply documents containing the correct answers; they provide insight into the qualities that distinguish different levels of performance.

Reflection needs to lead somewhere

There is, of course, a danger with any reflection activity.

Students can become very good at identifying what went wrong without necessarily doing anything differently as a result.

We have probably all encountered beautifully completed reflection sheets that have little discernible impact on subsequent work.

For that reason, I wanted the final stage of GROW to focus on action.

Students needed to identify a specific priority for improvement and consider how they would address it.

For some, this might mean revisiting a particular area of subject knowledge. For others, it could involve practising extended responses, developing more precise explanations or improving the way they interpret command words.

The important point was that the target needed to be specific enough to act upon.

Reflection should be the starting point for improvement, not the finished product.

As a teacher, the completed analysis can also provide useful information about patterns across a class. If several students identify the same misconception or weakness, that offers a valuable starting point for subsequent teaching.

Of course, identifying a gap does not automatically close it. Students still need opportunities to practise, receive further feedback and demonstrate improvement.

That is the next stage of the process.

Making feedback manageable

One of my ongoing interests is how we can make teaching and learning more effective without continually adding to teacher workload.

Feedback is an area where this tension can be particularly noticeable.

We want to provide students with meaningful guidance, but the solution cannot always be to write more comments, produce more documents or create increasingly elaborate marking systems.

What appealed to me about GROW was its relative simplicity.

The students already had their marked assessments. The mark schemes already existed. The additional resource was a structured set of questions to guide their thinking.

There was no need to produce an entirely new set of individualised feedback sheets.

Instead, the lesson created time and structure for students to engage with information that was already available.

It also gave me opportunities to circulate, question students and address misunderstandings as they emerged.

For me, that is an important distinction.

Effective feedback does not necessarily require more teacher input. Sometimes it requires better opportunities for students to make sense of the feedback they already have.

What about metacognition?

There is also an important metacognitive element to this approach.

Metacognition involves students developing awareness of their own thinking and learning processes, including the ability to monitor and evaluate their understanding.

When students examine why they lost marks, distinguish between knowledge gaps and examination technique, and plan a response, they are beginning to develop these skills.

However, we should not assume that students automatically know how to reflect effectively.

For some learners, being asked to 'identify your weaknesses' can be a surprisingly difficult task.

This is why scaffolding matters.

Providing prompts, modelling examples of useful reflection and explicitly discussing what makes an effective improvement target can help students engage more meaningfully with the process.

Over time, the aim would be to reduce that scaffolding as students become more confident in evaluating their own work.

What would I refine next time?

As with any classroom approach, I think it is important to distinguish between an activity that feels productive and one that demonstrably improves learning.

The GROW lessons provided a structured way for students to engage with their assessments, but the real test will be whether they can apply what they have identified to future work.

Next time, I would like to strengthen that connection even further.

One possibility is to begin a subsequent lesson with a short retrieval or application task linked directly to the gaps identified during GROW.

Another is to ask students to revisit their improvement targets after their next assessment and consider whether they have made progress.

I am also interested in how students might become increasingly independent in identifying the difference between missing subject knowledge and weaknesses in how they communicate that knowledge.

These are all opportunities to develop the approach further.

Final thoughts: Making feedback work harder

For me, the value of GROW lies in its simplicity and purpose.

It is not a revolutionary new marking system or an elaborate feedback framework.

It is a structured opportunity for students to stop, examine their work carefully and think about what needs to happen next.

In a profession where time is precious, I am increasingly drawn towards approaches that make better use of what we already do.

We assess students. We mark their work. We identify misconceptions. We provide feedback.

But perhaps the question we should be asking more frequently is:

What opportunities are we giving students to do something meaningful with that feedback?

Because ultimately, the mark is only a snapshot of where a student is at a particular moment.

The learning comes from understanding how to move forward.

And that is exactly what I hope GROW will help my students to do.

Have you tried structured question-level analysis or dedicated feedback lessons with your students? I'd be interested to hear how you help learners move beyond the mark and take ownership of their next steps.