The Autumn Evidence Already on File: A Department Meeting for Examiner Feedback

The evidence already on file

When the examining boards publish their annual reports, many departments receive a document of considerable precision and then place it in a shared folder for later. Later rarely arrives. The report is read by the subject leader, perhaps summarised in a briefing, and then overtaken by the immediate demands of the term. Yet it remains one of the few pieces of external evidence that speaks directly to the discipline: what candidates wrote, where they misread the question, which concepts they conflated, and which skills they failed to deploy under examination conditions.

The argument here is not that examiner reports should become another compliance task. It is that they deserve a protected slot in the department calendar because they contain evidence that can improve curriculum thinking. The meeting proposed below takes thirty minutes, requires no additional data collection, and produces no more than three changes. Its purpose is to move a department from reading feedback to acting on it without turning the exercise into a review of individual teachers.

Before the meeting: a one-page reading protocol

The subject leader should prepare a single page, printed or displayed, with the following instructions. The protocol is deliberately narrow so that the meeting does not become a general discussion of examination performance.

• Read only the sections of the report that relate to the specifications taught in this department. Ignore generic commentary unless it bears directly on those courses.
• Highlight verbs that describe candidate behaviour: omitted, misread, conflated, described, applied, evaluated, failed to structure. These are the observable actions that will anchor the discussion.
• Note one strength and one lost opportunity for each question or strand under consideration. The strength matters because it identifies what should be protected in the scheme of work.
• Mark any pattern that appears in more than one question. A single comment may be incidental; a repeated pattern is curriculum evidence.
• Bring one question to the meeting: “What did students need to know or be able to do that the evidence suggests was not secure?”
• Leave judgements about individual colleagues outside the room. The report describes candidates, not teachers.

This protocol is not a reading comprehension exercise. It is a way of ensuring that colleagues arrive at the discussion with the same evidence and a shared vocabulary. It also prevents the meeting from drifting into anecdote, which is the usual fate of examiner feedback sessions.

The thirty-minute structure

Minutes 0–5: purpose and boundaries

The chair opens by stating the intended output: two or three concrete changes to curriculum sequencing, modelling or assessment, each with an owner and a review date. The chair also states what the meeting is not: it is not a performance review, not a discussion of individual classes, and not a route to additional marking. A visible timer helps. The meeting should end on time, even if the discussion is unfinished, because an overlong meeting signals that the task is larger than it is.

Minutes 5–15: silent reading with the protocol

Colleagues read the same pages and annotate them using the protocol. Silence is not an awkward absence of collaboration; it is the condition for a focused discussion. The subject leader collects the annotations on a flipchart or a shared document, grouping comments under three headings: what candidates did well, where marks were repeatedly lost, and what appeared to be misunderstood. This is the only note-taking required.

Minutes 15–25: three questions

The chair leads a discussion structured around three questions. The wording matters because it directs attention to student performance rather than teacher deficiency.

1. What did candidates do well that we should deliberately protect in our teaching?
2. Where did candidates lose marks repeatedly, and what did they appear to misunderstand or fail to do?
3. Which of those patterns is within our control through sequencing, modelling or assessment?

The third question is the bridge to action. It prevents the department from listing every weakness in the report and instead forces a judgement about what can reasonably be changed. A pattern that reflects a whole-school issue, such as examination access arrangements, may need to be escalated. A pattern that reflects the order in which a concept is taught belongs in the department’s own planning.

Minutes 25–30: decide two or three changes

Each change should be recorded in a simple format: what will change, which year group or course it affects, who owns it, and when the department will review it. The owner is not necessarily the subject leader; it should be the person best placed to make the change. The review date should be soon enough to matter, perhaps six weeks, and should rely on existing student work rather than a new data collection.

Examples of proportionate changes include adding a short retrieval cycle on command words before the next assessment, modelling a full answer with annotated examiner commentary, or moving a threshold concept earlier in the scheme of work so that it is revisited rather than encountered once. Vague commitments such as “improve exam technique” should be rejected because they cannot be reviewed.

Three levers: sequencing, modelling and assessment

Sequencing

Examiner reports often reveal that candidates could perform a skill in isolation but not in the order required by the examination. A department might decide to interleave a previously secure topic with a newer one, or to teach a foundational concept before a related application rather than after it. The change should be visible in the scheme of work, not merely agreed in conversation.

Modelling

Where candidates lost marks for structure or explanation, the report may point to a gap between what teachers modelled and what students were asked to produce. A useful change is to model a response using the examiner’s language, showing students where marks are awarded and why. This is not the same as providing a template; it is making the discipline’s conventions explicit.

Assessment

Assessment changes should be modest. A department might adjust the balance of a end-of-unit assessment so that it mirrors the demand of the examination, or add a short question that requires students to apply a concept in an unfamiliar context. The purpose is to generate evidence for the next review, not to increase the assessment burden.

Keeping the meeting honest

The final safeguard is the review date. At the next department meeting, the owner of each change reports briefly on what has been tried and what student work shows. If a change has not happened, the department should decide whether to abandon it or revise it. This is not a failure; it is evidence that the original action was too ambitious or poorly specified. The discipline lies in choosing few changes and reviewing them properly.

Examiner reports are not a verdict on a department. They are a record of what candidates did under particular conditions, and they are most useful when read alongside the curriculum that produced those candidates. A thirty-minute meeting will not solve every issue raised in the report, but it can convert a neglected document into two or three deliberate improvements. That is a reasonable return on half an hour.