How to Run a Pupil Progress Meeting Efficiently

Pupil progress meetings can be some of the most useful conversations in a school. They can help staff spot pupils who are stuck, understand what is getting in the way, agree practical support and check whether previous actions have worked.

They can also become one of the least useful parts of the school calendar: too much data, too many spreadsheets, too many pupils discussed at surface level, too little time spent on teaching, learning, attendance, behaviour, SEND, confidence or what will actually happen next.

The difference is usually not the meeting title. It is the design. A good pupil progress meeting is focused, prepared, honest and action-led. A poor one becomes a data-reading exercise where teachers explain numbers everyone could have read before they walked into the room.

This guide explains how to run pupil progress meetings efficiently, whether you are a headteacher, senior leader, phase leader, head of department, SENCO, pastoral lead or teacher preparing for one. It covers what to discuss, what to avoid, how to use data without drowning in it, how to keep workload sensible and how to make sure the meeting leads to better support for pupils.

What is a pupil progress meeting actually for?

A pupil progress meeting should answer one central question: what do pupils need next?

It is not simply a meeting to look at assessment scores. It is not a meeting to blame teachers for gaps. It is not a meeting to produce a long list of interventions that nobody has time to run. It is not a meeting where every child is briefly named and nothing changes.

At its best, a pupil progress meeting brings together assessment evidence, teacher knowledge and wider pupil context so staff can make better decisions. Those decisions might be about classroom teaching, intervention, attendance, SEND support, pastoral care, behaviour, parental contact, curriculum gaps, homework routines or exam preparation.

The meeting should leave staff clearer than when they arrived. If everyone leaves with more confusion, more paperwork and no agreed action, the meeting has not worked.

Start with a purpose, not a spreadsheet

The quickest way to ruin a pupil progress meeting is to begin with too much data and no clear purpose.

Before the meeting is scheduled, leaders should decide what the meeting is trying to achieve. For example:

• identify pupils at risk of falling behind in reading, writing or maths;
• review the impact of recent interventions;
• look at progress for disadvantaged pupils;
• check whether pupils with SEND are accessing the curriculum;
• plan support for pupils below expected standard;
• review Year 11 or Year 13 exam readiness;
• understand why a year group’s attendance is affecting progress;
• spot pupils who are coasting despite meeting expected standards;
• agree next steps for pupils whose behaviour is blocking learning.

A meeting about all of these at once will usually be too broad. Choose the focus. The sharper the purpose, the more useful the discussion.

If the meeting is about pupils falling behind, this related parent-facing guide may be useful for understanding the kinds of concerns families may raise: How to Know If Your Child Is Falling Behind at School.

Keep the meeting small enough to work

Large meetings can be useful for sharing messages, but they are often poor for detailed pupil discussion. If too many people are in the room, the conversation becomes either performative or too general.

Think carefully about who needs to attend. Depending on the focus, that may include:

• class teacher or subject teacher;
• phase leader or head of department;
• senior leader responsible for progress;
• SENCO;
• pastoral or behaviour lead;
• attendance lead;
• pupil premium lead;
• teaching assistant or intervention lead, where relevant.

Not everyone needs to attend every meeting. A Year 6 writing progress meeting may need different people from a Year 9 attendance and behaviour meeting. A small, well-prepared group will usually achieve more than a large room full of people half-listening.

Decide which pupils will be discussed before the meeting

One of the biggest inefficiencies is trying to discuss too many pupils. If a meeting is 45 minutes long and 40 pupils are on the agenda, the conversation will become shallow. Staff may name concerns, but there will be no time to understand them.

It is usually better to focus on a smaller number of pupils in more depth. Choose pupils based on the meeting purpose. For example:

• pupils below expected standard but close to securing it;
• pupils whose progress has slowed unexpectedly;
• pupils with high prior attainment who are coasting;
• pupils whose attendance has dropped;
• pupils whose behaviour incidents are increasing;
• pupils receiving intervention whose progress needs review;
• pupils with SEND whose support plan may need adjusting;
• pupils who are doing well and whose success needs understanding.

Do not only discuss pupils who are underperforming. Sometimes the most useful question is: “Why is this working well for these pupils, and what can we learn from it?”

Use data as a starting point, not the whole conversation

Assessment data is useful, but it is not the pupil. A score may tell you that a child is below expected standard, but it will not tell you why. It may show that a group’s progress has slowed, but it will not reveal whether the cause is attendance, weak prior knowledge, poor reading fluency, curriculum sequencing, assessment design, lack of confidence, behaviour, working memory, language, SEND, mobility or home circumstances.

The meeting should move quickly from “what does the data say?” to “what does this pupil need?”

Useful data might include:

• recent assessment results;
• teacher assessment judgements;
• reading ages or fluency checks;
• attendance and punctuality;
• behaviour incidents;
• homework completion;
• SEND information;
• intervention records;
• pupil premium status;
• previous attainment;
• book or work scrutiny evidence;
• teacher observation.

But avoid collecting data just because it can be collected. Every piece of data brought to the meeting should have a clear purpose. If nobody uses it to make a decision, it probably should not be there.

Prepare a one-page summary, not a data dump

For most pupil progress meetings, a one-page summary is more useful than multiple spreadsheets. The summary should show enough information to support decisions without overwhelming the discussion.

A simple summary might include:

• meeting focus;
• pupils to discuss;
• current attainment or assessment point;
• previous attainment or baseline;
• attendance percentage;
• key SEND or pastoral notes where relevant;
• current intervention or support;
• teacher’s main concern;
• proposed next step;
• review date.

The aim is not to remove professional judgement. It is to stop the meeting being spent finding basic information that should already be visible.

Ask better questions

The quality of a pupil progress meeting depends heavily on the questions asked. Weak questions produce weak action.

Instead of asking, “Why is this pupil not making progress?”, try more precise questions:

• What exactly can the pupil not do yet?
• Is the gap knowledge, skill, fluency, confidence or independence?
• Can they do it with support but not alone?
• Is the issue subject-specific or visible across the curriculum?
• Has attendance affected learning time?
• Is behaviour causing missed instruction or practice?
• Is reading or vocabulary limiting access?
• Could working memory, processing, attention or language be a barrier?
• Has the pupil had enough guided practice?
• What has already been tried, and did it work?
• What is the smallest useful next step?

Good questions turn a general concern into an actionable plan.

Separate attainment, progress and effort

Pupil progress meetings often become confused because staff talk about attainment, progress and effort as if they are the same thing.

They are different.

Attainment is where the pupil is now against a standard or curriculum expectation.

Progress is how far the pupil has moved from their starting point.

Effort is how the pupil is engaging, trying, practising or responding.

A pupil may be below expected standard but making strong progress. Another may be working at expected standard but coasting. A third may be trying hard but making little progress because the support does not match the barrier.

This distinction matters because the action will be different. A pupil with low attainment and strong progress may need continued support and confidence. A pupil with high attainment and weak progress may need challenge. A pupil with good effort but limited progress may need better diagnosis. A pupil with weak effort may need motivation, routine, pastoral support or behaviour intervention.

For a parent-facing explanation of expected standard language, see What “Working at Expected Standard” Actually Means.

Do not let the meeting become a blame exercise

Pupil progress meetings can create anxiety for staff if they feel like a public accountability test. When that happens, teachers may arrive defensive, over-explain data, or feel pressured to promise interventions they cannot realistically deliver.

Accountability matters, but the most effective meetings are problem-solving conversations. The tone should be professional, honest and focused on action.

Instead of:

Why are these pupils underperforming in your class?

Try:

What are you noticing with these pupils, and what support would help us move them forward?

Instead of:

Why has this intervention not worked?

Try:

What did the intervention improve, what did it not address, and what should we change next?

This does not lower expectations. It makes the conversation more likely to produce useful change.

Look for patterns before individual fixes

Individual pupil discussion is important, but meetings become inefficient if every pupil is treated as a completely separate problem. Sometimes several pupils are struggling for the same reason.

Look for patterns:

• Are many pupils weak on the same topic?
• Is vocabulary affecting access across a group?
• Are pupils struggling with multi-step instructions?
• Is a class weak on extended writing?
• Are attendance issues concentrated on certain days?
• Are behaviour incidents happening during transitions?
• Are disadvantaged pupils missing homework more often?
• Are pupils with SEND struggling with the same task format?

If ten pupils have the same gap, the answer may not be ten separate interventions. It may be reteaching, better modelling, curriculum adjustment, guided practice, vocabulary support or a change to classroom routines.

Use the “barrier, action, owner, review” model

An efficient pupil progress meeting should reduce each significant concern to four things:

• Barrier: what is stopping progress?
• Action: what will be done next?
• Owner: who is responsible?
• Review: when will we check impact?

For example:

• Barrier: A pupil cannot answer inference questions because vocabulary is limiting understanding.
• Action: Add pre-teaching of key vocabulary before guided reading sessions for three weeks.
• Owner: Class teacher, with support from reading lead.
• Review: Recheck responses in three weeks using a short inference task.

This is far better than writing “monitor reading” or “needs support”. Those phrases sound like action, but they rarely change practice.

Keep actions realistic

One of the most common problems in pupil progress meetings is overpromising. Staff leave with long action lists that cannot possibly be delivered. By the next meeting, actions have not happened, and everyone feels frustrated.

Efficient meetings protect staff workload by choosing fewer, better actions.

Ask:

• Can this action actually happen within the school week?
• Who has the time and skill to do it?
• Does it require training, resources or timetable changes?
• Will it replace something else, or simply add more work?
• How will we know whether it worked?
• Is this the most likely action to make a difference?

If an action sounds impressive but cannot be delivered, it is not a good action.

Review previous actions first

Before discussing new concerns, review what was agreed last time. This is essential. Otherwise, meetings become repetitive: the same pupils, the same concerns, the same vague actions, with no honest review of impact.

Start with:

• What was agreed?
• Did it happen?
• If not, why not?
• If it happened, what changed?
• What evidence do we have?
• Should we continue, adjust or stop?

This prevents intervention drift. Some support should continue. Some should change. Some should stop because it is not working or because the pupil no longer needs it.

Do not confuse intervention with impact

Schools can become very good at listing interventions. But the existence of an intervention is not the same as progress.

“She is in a reading group” does not answer whether her reading is improving. “He receives maths intervention” does not explain whether the intervention is targeting the right gap. “They have a mentor” does not prove attendance, behaviour or confidence has changed.

Every intervention should have a purpose and review point. Ask:

• Why is this pupil receiving this intervention?
• What specific barrier is it addressing?
• What should improve by the review date?
• How often is the intervention happening?
• Is attendance at the intervention good?
• Is it transferring back into classroom learning?
• What will we do if there is no impact?

If nobody can answer these questions, the intervention may need redesigning.

Bring attendance into the conversation early

Progress meetings often focus on assessment scores while attendance sits in a separate system. That is a mistake. If a pupil has missed significant learning time, progress discussion needs to include attendance.

A pupil may not be failing to learn because the teaching or intervention is wrong. They may simply not be present often enough to benefit from it. Another pupil may attend school but miss key lessons because of lateness, appointments, internal truancy, behaviour removals or anxiety-related absence.

Ask:

• Is attendance affecting this pupil’s access to teaching?
• Are absences linked to particular days or subjects?
• Is punctuality causing missed starts to lessons?
• Has the family been contacted?
• Is there anxiety, illness, transport, bullying, SEND or home context behind the absence?
• What is the attendance plan, and who owns it?

For more on this, see Attendance Strategies That Actually Improve Persistent Absence and Attendance Push Before Summer.

Include behaviour, but make it precise

Behaviour can block progress, but vague behaviour labels do not help. Saying “behaviour is poor” is not enough. The meeting needs to identify what behaviour is affecting learning and when.

For example:

• Does the pupil struggle to start work?
• Do they disrupt during teacher explanation?
• Do they avoid writing tasks?
• Do they become dysregulated after break?
• Are incidents linked to a particular peer group?
• Are they removed from lessons and missing teaching?
• Is behaviour worse when work is too hard or too open-ended?

The action depends on the pattern. It might be a seating plan, entry routine, check-in, scaffolded work, restorative conversation, mentor support, SENCO involvement, behaviour plan or parental meeting.

Related guides include How to Reduce Behaviour Incidents in the Summer Term and Managing Behaviour During Low-Motivation Months.

Do not leave SEND as an afterthought

If a pupil has SEND, or if staff suspect an underlying need, the meeting should consider whether classroom teaching and support are properly matched to the pupil’s barriers.

Ask:

• What is the pupil’s identified need?
• Do staff know the key strategies?
• Are reasonable adjustments in place?
• Is the pupil accessing the same curriculum, and where are the barriers?
• Is support promoting independence or creating dependence?
• Does the pupil need SENCO review?
• Is the support plan current?
• Is there evidence that the support is working?

For pupils with working memory, attention, communication, literacy or sensory needs, the barrier may not be lack of effort. It may be that the task design, classroom routine or assessment format is making it harder for them to show what they know.

Useful related resources include Neurodiversity in the Classroom, How to Create a Sensory-Friendly Classroom on a Budget and SEN Support vs EHCP: What Is the Difference?.

Discuss classroom teaching before adding intervention

Intervention is sometimes necessary, but it should not be the first answer to every progress concern. Most pupils spend far more time in ordinary lessons than in intervention. If the classroom barrier remains, a short intervention may not be enough.

Before adding a new intervention, ask:

• Can this be addressed through reteaching in class?
• Does the pupil need clearer modelling?
• Is there enough guided practice?
• Are instructions too complex?
• Is vocabulary being explicitly taught?
• Are checks for understanding frequent enough?
• Is feedback leading to improvement?
• Do pupils know what success looks like?

Sometimes the most efficient action is not “send the pupil somewhere else”. It is “adjust tomorrow’s lesson”.

Use a strict meeting structure

Efficient meetings need structure. Without it, the discussion expands to fill the time and often drifts into anecdotes.

A simple 45-minute structure might look like this:

• 5 minutes: clarify purpose and review previous actions.
• 10 minutes: identify key patterns in the data and teacher evidence.
• 20 minutes: discuss priority pupils or groups.
• 5 minutes: agree actions, owners and review dates.
• 5 minutes: confirm what will be recorded and shared.

For a 30-minute meeting, reduce the number of pupils. Do not try to force a 60-minute agenda into 30 minutes.

Appoint a chair and a recorder

Every pupil progress meeting needs someone to chair it and someone to record actions. These may be the same person in a small meeting, but the roles must be clear.

The chair keeps the meeting focused by:

• sticking to the purpose;
• stopping unnecessary data reading;
• asking for evidence where claims are vague;
• moving discussion towards action;
• protecting time;
• ensuring workload is considered;
• checking that actions have owners.

The recorder captures:

• pupil or group discussed;
• barrier identified;
• agreed action;
• person responsible;
• review date;
• communication needed with parents or staff;
• any safeguarding, SEND or attendance follow-up.

Do not record long narrative minutes unless there is a specific reason. A clear action log is usually more useful.

Use a simple action log

A pupil progress action log does not need to be complicated. In fact, the simpler it is, the more likely it is to be used.

A practical format is:

The action log should be reviewed at the next meeting. If it is created and forgotten, it is only paperwork.

Avoid “monitor” as an action

“Monitor” is one of the most common but least useful meeting actions. It often means nobody is doing anything different.

If monitoring is genuinely needed, define it:

• Who is monitoring?
• What exactly are they checking?
• How often?
• Where will it be recorded?
• What will trigger further action?

For example, “monitor homework” is weak. “Form tutor checks homework platform with pupil every Monday and Thursday for three weeks, then reviews missed deadlines with head of year” is much stronger.

Bring pupil voice where appropriate

Sometimes adults discuss a pupil for 15 minutes without anyone knowing what the pupil thinks. That can lead to the wrong action.

Pupil voice does not need to be complicated. Before the meeting, a teacher, tutor or pastoral lead might ask:

• Which part of the subject feels hardest?
• When do you feel most confident?
• What helps you get started?
• What makes it harder to concentrate?
• Do you know what to do when you are stuck?
• Is anything outside the lesson affecting your learning?

Pupil voice should not override professional judgement, but it can reveal barriers adults have missed. A pupil may say they do not understand the homework platform, cannot read the board, feel embarrassed asking for help, are avoiding a peer, or do not know how to revise.

Decide when to contact parents

Parent communication should not be an automatic afterthought. Sometimes parents need to know early. Sometimes school needs to gather more information first. Sometimes the action will only work if home and school are aligned.

Contact parents when:

• attendance is affecting progress;
• homework patterns are persistent;
• behaviour is affecting learning;
• the pupil is distressed or losing confidence;
• SEND support may need review;
• intervention requires consent or home support;
• there has been a sudden change in progress;
• school needs more context.

The message should be specific and constructive. Parents should not only hear from school when things have already gone wrong. For a parent-facing guide that may help staff think about communication tone, see How to Talk to Your Child’s Teacher When You’re Worried.

Protect teacher workload

Pupil progress meetings should not create unnecessary workload. If staff need to spend hours preparing data that will be mentioned for 30 seconds, the process is wrong.

To protect workload:

• use data already collected where possible;
• avoid asking teachers to duplicate information in multiple formats;
• limit preparation to the pupils being discussed;
• send the agenda in advance;
• keep action logs simple;
• avoid unrealistic intervention promises;
• review whether meeting actions actually improve outcomes;
• stop collecting information that nobody uses.

The best pupil progress systems are lean. They produce better decisions, not bigger folders.

If workload is a wider concern, see 10 Time-Saving Hacks for Teachers: Planning, Marking and Admin.

For primary schools: keep the focus close to the classroom

In primary schools, pupil progress meetings often involve class teachers, phase leaders, senior leaders and sometimes the SENCO or intervention staff. Because one teacher usually knows the child across several subjects, the conversation can be rich — but it can also become too broad.

Primary meetings work best when they focus on:

• reading fluency and comprehension;
• writing stamina, transcription and composition;
• maths fluency and reasoning;
• attendance and punctuality;
• language development;
• SEND barriers;
• emotional readiness to learn;
• transition points between year groups.

For younger pupils, small changes can matter: seating, adult check-ins, phonics grouping, vocabulary pre-teaching, manipulatives, handwriting support, reading practice, attendance routines or parent communication.

For secondary schools: avoid subject silos

In secondary schools, pupil progress meetings can become fragmented because each subject has its own data, assessments and concerns. A pupil may appear to be struggling in English, but the same issue may show in history, geography and science because the real barrier is reading, vocabulary or extended writing.

Secondary meetings should look for cross-subject patterns:

• Is the pupil struggling in all written subjects?
• Are maths difficulties affecting science or technology?
• Is homework missing across several subjects?
• Are behaviour incidents concentrated in practical lessons?
• Is attendance affecting particular subjects more than others?
• Does the pupil have a trusted adult in school?
• Are subject teachers using consistent strategies?

Heads of year, SENCOs and pastoral teams can be especially important in secondary progress meetings because they see patterns that individual subject teachers may not.

For exam year groups: focus on the highest-impact actions

In Year 11 and Year 13, pupil progress meetings can easily become stressful. There is less time, higher pressure and often a long list of pupils who could benefit from support.

Efficiency matters. Focus on actions most likely to improve outcomes:

• attendance at key lessons and intervention sessions;
• specific topic gaps;
• exam technique;
• revision habits;
• coursework or NEA deadlines where relevant;
• confidence and exam anxiety;
• access arrangements;
• parent communication;
• pupils at key grade boundaries;
• pupils at risk of disengagement.

Do not create a plan so complex that pupils and staff cannot follow it. Exam-year support should be sharp, targeted and reviewed frequently.

For disadvantaged pupils: avoid assumptions

Pupil premium and disadvantage discussions need care. The meeting should not assume that all disadvantaged pupils need the same thing, or that every gap is caused by the same barrier.

Ask:

• Which disadvantaged pupils are doing well, and why?
• Which pupils are not making progress, and what is the specific barrier?
• Is attendance a factor?
• Is homework access or study space an issue?
• Is reading, vocabulary or background knowledge limiting access?
• Are pupils accessing wider opportunities?
• Is support discreet and respectful?
• How will impact be measured?

Disadvantage is a category for funding and monitoring. It is not a diagnosis. The action still needs to match the pupil.

For pupils already meeting expectations: ask whether they are moving forward

Pupil progress meetings often focus on those below expectations, but pupils who are “fine” can still need attention. Some may be coasting. Some may be quietly losing motivation. Some may have high prior attainment but weak current progress. Some may be meeting expectations while capable of more depth, fluency or independence.

Ask:

• Are they making progress from their starting point?
• Are they being challenged?
• Are they developing independence?
• Do they avoid difficult tasks?
• Are they producing work at the depth expected?
• Could they explain their thinking more clearly?
• Do they need enrichment, extension or more precise feedback?

A progress meeting should not only be about catching pupils up. It should also be about helping pupils move on.

Use meetings to improve teaching, not just allocate support

If progress meetings only produce pupil-by-pupil actions, they miss a bigger opportunity. They can also help leaders understand where teaching, curriculum or assessment may need adjustment.

For example, a meeting may reveal:

• a topic was not secure before moving on;
• pupils need more explicit vocabulary teaching;
• assessment questions did not match taught content;
• pupils need more modelling before independent work;
• a scheme of work needs resequencing;
• homework is not reinforcing the right knowledge;
• feedback is not leading to improvement;
• teachers need CPD on adaptive teaching or questioning.

These findings are valuable. They move the meeting from pupil management to school improvement.

Make the review cycle clear

A pupil progress meeting is only useful if there is a review cycle. Staff should know when actions will be checked and what evidence will be used.

Review cycles might be:

• two weeks for attendance or behaviour actions;
• three to four weeks for short intervention impact;
• half-termly for assessment and curriculum gaps;
• termly for wider progress reviews;
• more frequently for exam-year pupils at risk.

The review date should match the action. Do not wait a term to check whether a pupil has attended a weekly intervention. Do not review a major curriculum change after three days.

Avoid common pupil progress meeting mistakes

Common mistakes include:

• discussing too many pupils;
• reading data aloud instead of analysing it;
• focusing only on attainment, not progress;
• ignoring attendance and behaviour;
• treating SEND as separate from progress;
• agreeing vague actions such as “monitor” or “support”;
• creating too many interventions;
• not reviewing previous actions;
• failing to assign owners;
• collecting data that does not inform decisions;
• turning the meeting into teacher blame;
• leaving without a review date.

Most of these problems can be fixed through better meeting design.

A practical pupil progress meeting template

Schools can adapt the following template.

Before the meeting

• Confirm the focus of the meeting.
• Select priority pupils or groups.
• Send a short agenda.
• Prepare one-page data and context summary.
• Ask staff to bring specific evidence, not general impressions.
• Review previous action log.

During the meeting

• Start with the purpose.
• Review previous actions and impact.
• Identify key patterns.
• Discuss priority pupils or groups.
• Identify barriers.
• Agree realistic actions.
• Assign owners.
• Set review dates.

After the meeting

• Share the action log with relevant staff.
• Communicate with parents where needed.
• Make sure support actually begins.
• Check actions before the next meeting.
• Review impact, not just completion.

Example: turning a weak discussion into a useful one

Weak discussion:

Amelia is below expected standard in writing. She needs intervention. We’ll monitor her.

Better discussion:

Amelia’s ideas are strong when discussed orally, but her written work is short and poorly structured. The barrier appears to be planning and sentence construction, not understanding. For the next three weeks, the class teacher will provide a paragraph scaffold during independent writing and the teaching assistant will rehearse the sentence orally before she writes. We will review two independent writing samples at the end of the month.

The second version identifies the barrier, avoids a vague intervention label, assigns action and sets a review point.

Example: when attendance is the real barrier

Weak discussion:

Jayden is not making progress in maths. He needs extra support.

Better discussion:

Jayden’s maths gaps match lessons missed on Mondays and Fridays. Attendance is 86%, and he has missed the start of the fractions unit. Before adding intervention, the attendance lead will contact home, the class teacher will provide a short catch-up task for the missed prerequisite knowledge, and the form tutor will check attendance patterns over the next two weeks.

This avoids treating the symptom as the cause.

Example: when a group issue needs teaching adjustment

Weak discussion:

Eight pupils did badly on the science assessment. Put them into intervention.

Better discussion:

Eight pupils missed the same questions on variables and fair testing. This suggests a class-level misconception rather than eight separate intervention needs. The teacher will reteach this concept using a worked example and practical scenario next lesson, then use a five-question check two days later.

Sometimes the efficient action is reteaching, not withdrawal.

How senior leaders can make meetings more useful

Senior leaders set the tone. If leaders use progress meetings to catch teachers out, staff will prepare defensively. If leaders use them to solve problems, staff are more likely to be honest.

Senior leaders should:

• define the purpose clearly;
• limit unnecessary data preparation;
• focus on barriers and action;
• ask what support staff need;
• look for curriculum and teaching patterns;
• protect workload;
• ensure agreed actions are followed up;
• evaluate whether meetings improve outcomes.

A good question for leaders after each meeting is: “What will be different for pupils because this meeting happened?”

How teachers can prepare well

Teachers do not need to arrive with pages of notes. But they should be ready to discuss pupils accurately.

Before the meeting, teachers can prepare by asking:

• Which pupils am I most concerned about, and why?
• What evidence supports that concern?
• What have I already tried?
• What helped, even a little?
• What do I think the barrier is?
• What support would help me help the pupil?
• Is this an individual issue or a wider class pattern?

This kind of preparation is efficient because it focuses on professional judgement, not paperwork.

How to know whether your pupil progress meetings are working

A school should periodically review whether its pupil progress meetings are worth the time. This does not need to be complicated.

Ask:

• Are meetings leading to clear actions?
• Are actions actually happening?
• Are actions reviewed?
• Are staff clearer after the meeting?
• Is data preparation proportionate?
• Are the right people in the room?
• Are pupils receiving better support?
• Are repeated concerns reducing?
• Are meetings improving teaching or only adding intervention?
• Does the process protect workload?

If the answer to most of these is no, the meeting format needs redesigning.

Final thoughts

An efficient pupil progress meeting is not a faster version of a bad meeting. It is a better-designed conversation.

It starts with a clear purpose. It uses data carefully. It focuses on a manageable number of pupils or patterns. It asks what is getting in the way. It agrees realistic actions. It assigns owners. It reviews impact. It protects staff workload. Most importantly, it changes something for pupils.

The best pupil progress meetings do not simply describe who is behind. They help schools understand why, decide what to do next and check whether that action made a difference.

If a meeting does that, it is worth the time. If it does not, it is just another spreadsheet with chairs around it.

Frequently Asked Questions

What is a pupil progress meeting?

A pupil progress meeting is a structured discussion about pupils’ learning, attainment, progress and barriers. It usually uses assessment evidence, teacher knowledge and wider context to agree next steps for pupils or groups.

How often should schools hold pupil progress meetings?

It depends on the school, phase and purpose. Some meetings are termly, while others are half-termly or more frequent for exam groups, attendance concerns or targeted interventions. The frequency should match the action being reviewed.

Who should attend a pupil progress meeting?

The right people depend on the focus. This may include class teachers, subject teachers, heads of department, phase leaders, senior leaders, the SENCO, attendance lead, pastoral lead or intervention staff. Keep the group small enough to make decisions.

What data should be used in a pupil progress meeting?

Use data that helps decision-making: assessment results, teacher judgements, attendance, behaviour, SEND information, intervention records, reading data and work evidence. Avoid collecting data that does not lead to action.

How many pupils should be discussed?

Fewer pupils discussed well is usually better than many pupils discussed superficially. Select pupils based on the meeting purpose, such as those below expected standard, those whose progress has slowed, or those needing review after intervention.

What is the biggest mistake in pupil progress meetings?

The biggest mistake is spending too much time describing data and too little time identifying barriers and agreeing actions. A meeting should answer what pupils need next, not simply repeat what the spreadsheet says.

How can schools reduce workload around progress meetings?

Use existing data, avoid duplicate forms, send a focused agenda, limit the number of pupils discussed, keep action logs simple and stop collecting information that nobody uses.

What should an action from a pupil progress meeting include?

A good action should identify the barrier, specify what will happen, name the person responsible and include a review date. Vague actions such as “monitor” or “support” should be avoided unless clearly defined.

Should parents be contacted after a pupil progress meeting?

Sometimes. Parents should be contacted when home-school communication is needed, such as attendance concerns, homework patterns, SEND support, behaviour issues, intervention planning or significant changes in progress.

How do you review whether an intervention is working?

Check whether the intervention is happening as planned, whether the pupil is attending, whether the targeted skill or barrier is improving, and whether progress is transferring back into normal classroom work.

Should pupil progress meetings focus only on pupils below expected standard?

No. They should also consider pupils making slow progress, pupils who are coasting, disadvantaged pupils, pupils with SEND, pupils with attendance issues and pupils who may need more challenge.

How can leaders make pupil progress meetings more useful?

Leaders can make them useful by setting a clear purpose, keeping data proportionate, asking precise questions, focusing on barriers, agreeing realistic actions, reviewing previous actions and protecting staff workload.