This guide is a Results Day Readiness Pack for Heads of Year and Sixth Form teams who want structure without losing humanity. It is designed for the moments that matter most: a student holding back tears, a parent demanding an instant appeal, a safeguarding concern that cannot wait, and a queue that grows faster than your capacity. The aim is to reduce panic by giving staff a shared triage language, a simple rota, and ready-to-use scripts and messages.
It is not a decision engine. It does not replace professional judgement, exam board guidance, or your school’s safeguarding policy. It is also not an “AI-run” approach. Where AI is mentioned, it is only for rehearsal and drafting, with human sign-off and minimal data. If you want a deeper look at rehearsing scenarios with care, see results day war-room scenario planning.
In the first 90 minutes, clarity beats heroics. Aim for a small set of named roles, each with a single priority, and a visible rota board (paper is fine). The key is to prevent your most experienced staff from being pulled into every conversation.
You typically need a greeter and queue manager at the entrance to your support space, a triage lead who makes quick routing decisions, and two or more conversation leads who can hold supportive, time-bound meetings. Add a data runner (someone who can check timetables, course requirements, or internal notes without dragging a conversation lead away) and a documentation lead to log outcomes and handovers. If you have a sixth form or careers specialist, ring-fence them for “next steps” conversations rather than general reassurance. Build in micro-breaks; five minutes off rota every half hour can prevent a well-meaning adult from snapping at the wrong moment.
If you are building repeatable routines for busy school days, the workflow thinking in building AI workflows that stick translates well, even when you are not using AI at all.
The simplest triage is four queues. You are not labelling students; you are choosing the right kind of help, fast. Post the four queues on a wall and train staff to route within 60 seconds.
This queue is for high emotion, low information need. The priority is containment and co-regulation: a quiet seat, water, a calm adult, and a short plan for the next 20 minutes. Avoid deep problem-solving while distress is high. A student who has done “worse than expected” may still be able to take constructive steps, but not until they can breathe and think.
This queue is for students who are ready to act: course changes, resits, alternative routes, entry requirements, and timelines. Keep it concrete. A simple “options grid” helps: what you can do today, this week, and after term starts. Where relevant, signpost to your existing careers and progression processes.
This queue is for dissatisfaction that may become formal. Your goal is to listen, de-escalate, and move from accusation to process. Avoid debating grades in the corridor. Offer a structured route: what can be reviewed, what evidence is needed, and when you will respond. Keep language neutral and avoid implying outcomes.
If you want boundary-setting language that protects staff and students during high-stakes conversations, exam season AI traffic-light boundaries includes useful phrasing patterns you can adapt.
This queue jumps the line. It includes disclosures, threats of self-harm, missing student concerns, and any situation where you cannot confidently keep a student safe in the next hour. Your triage lead should have a direct line to the safeguarding lead and a clear location for private conversations. Staff should never feel they must “handle it themselves” because the room is busy.
For conversation approaches that prioritise wellbeing, see AI for student wellbeing conversations (particularly the sections on tone, pacing, and non-leading questions).
Scripts are not about sounding robotic. They reduce cognitive load when emotions run high. Keep them short, kind, and consistent.
Try: “I can see this is a lot to take in. You’re not in trouble, and you’re not on your own. Let’s take two minutes to breathe, then we’ll decide the next best step together.”
For mixed results: “These grades are information, not a judgement on you. Let’s circle what went well, then look at the subjects that need a plan.”
For missed grades: “It makes sense to feel disappointed. There are still options today. I’m going to ask a few quick questions so we can choose the right route.”
For clearing or alternative routes: “We’ll focus on what you can control in the next hour: who to contact, what to say, and what you need to have ready.”
For appeals: “I hear that you feel this doesn’t reflect your work. I can’t promise an outcome, but I can promise a clear process. Let’s go through the steps and what evidence we need.”
Try: “Thank you for getting in touch. Today can be emotional. Our priority is your child’s wellbeing and next steps. We’ll be clear about the process and timelines.”
If a parent is angry: “I understand you’re upset. I want to help, and I can do that best if we take this step by step. I’m going to note what you’re concerned about, then explain what we can do today.”
If they demand an instant decision: “I can’t make that decision in this moment. What I can do is book a call today, outline the process, and confirm what we need from you.”
For safeguarding concerns: “Thank you for telling us. We’re taking this seriously. I’m going to connect you with our safeguarding lead now, and we’ll agree the next actions.”
Escalation works when thresholds are explicit. Agree them in advance and share them in the staff briefing. A practical approach is to define three levels: handle in-room, escalate to specialist, escalate to safeguarding/leadership.
For example, “handle in-room” might include routine reassurance, basic next steps, and straightforward timetable queries. “Escalate to specialist” could include complex progression routes, disputes requiring formal documentation, or multiple subjects affected. “Escalate immediately” includes any safeguarding disclosure, inability to contact a parent/carer when needed, or a student who cannot be safely left alone.
Handovers should be written, brief, and factual. Use a standard note format: time, staff initials, student identifier (use your internal ID rather than a full name where possible), what was said (verbatim for key phrases), actions agreed, and who owns the next step. This is also where event-operations discipline helps; AI event ops workflows has a useful mindset for logging, handovers, and human sign-off.
Ready to Revolutionise Your Teaching Experience?
Discover the power of Automated Education by joining out community of educators who are reclaiming their time whilst enriching their classrooms. With our intuitive platform, you can automate administrative tasks, personalise student learning, and engage with your class like never before.
Don’t let administrative tasks overshadow your passion for teaching. Sign up today and transform your educational environment with Automated Education.
Keep templates ready in your preferred channels, but always review the tone before sending. Results Day messages should be calm, specific, and non-technical.
For good news (SMS/email): “Congratulations on your results. We’re proud of your hard work. If you’d like to discuss next steps or course choices, support is available today between [times].”
For mixed results: “Results can bring mixed feelings. If you’d like to talk through options, our team is available today. Please come to [location] or call [number]. We’ll help you plan your next steps.”
For missed grades: “If your results weren’t what you hoped, please don’t panic. There are still routes forward, including course changes, resits, and alternative pathways. Come to [location] or contact [number] today.”
For clearing or urgent progression routes: “If you’re considering alternative courses or placements today, have your results to hand and be ready to note reference numbers. We can support you with what to say and who to contact.”
For appeals: “We can explain the review and appeals process and the timelines involved. Please contact [email/number]. We will log your request and confirm the next steps in writing.”
For social posts, keep it general and privacy-safe: “Results Day support is available on site and by phone today. Please be kind to yourself and to others. If you need help with next steps, we’re here.”
AI can help you practise, not decide. The safest use on Results Day is scenario rehearsal and message drafting that never includes pupils’ personal data, never automates outcomes, and always has human sign-off.
Scenario rehearsal means prompting an AI tool with a fictional situation to practise your responses. For example: “Role-play a conversation with a student who missed entry requirements by one grade and feels ashamed. Help me respond with empathy and clear next steps.” You can then refine the language into your own voice and align it to policy. Keep these prompts generic: no names, no unique circumstances, and no identifiable combinations of subjects and grades.
For drafting messages, treat AI like a first-draft assistant. Ask for three tone options (warm, neutral, firm), then choose and edit. Do not paste in screenshots of results, student emails, or complaint threads. If you need a structured way to evaluate tools and risks quickly, GPT-5 rapid evaluation protocol offers a practical checklist mindset you can adapt to any model.
Before you print scripts or schedule messages, run four quick checks: tone, accuracy, inclusion, and accessibility. Tone should be calm and non-judgemental, avoiding euphemisms that can sound dismissive (“it’s not that bad”). Accuracy means aligning to your actual processes and timelines; a perfect template that promises the wrong thing will create complaints.
Inclusion matters because Results Day language can unintentionally exclude. For SEND, keep instructions concrete and chunked, and offer a quieter space without making it feel like a punishment. For EAL families, avoid idioms and consider a short translated “support available” message where you can do so responsibly. Accessibility also includes format: larger font, clear headings, and phone numbers written with spacing for readability.
The day after Results Day, capture learning while it is fresh. Log volumes for each queue, peak times, staffing pinch points, and the top five questions asked by students and parents/carers. Note which scripts worked, which escalations were unclear, and where documentation slowed you down. If you used AI for rehearsal or drafting, record what helped and what felt risky, so you can tighten boundaries next year.
This is also your evidence base for improvement: what to keep, stop, and scale. You may find it useful to structure that reflection using an audit approach like end-of-year AI audit evidence pack, even if your changes are mostly human and procedural.
May your Results Day feel calmer, kinder, and more under control.
The Automated Education Team
Black Friday can feel like a rare chance to “save” on AI subscriptions, but …
Three years after ChatGPT’s release, schools have enough experience to …
December in schools brings a familiar spike: cover changes, heightened …
Microsoft Ignite can feel like a firehose of AI updates, but schools need a …
Report writing in 2025 is less about “which chatbot is best” and more about …
Three years into LGR22, many schools report real gains in clarity and …
Anti-Bullying Week works best when it moves beyond awareness and into …
Remembrance teaching asks for careful language, accurate sources, and …
Mock season often fails for predictable reasons: revision plans are …
Tulemuste päev võib tunduda emotsioonide, küsimuste ja kiireloomuliste otsuste tulvana. See …
Resultatdagen kan kännas som en flod av känslor, frågor och brådskande beslut. Det här …
Results Day voi tuntua tunteiden, kysymysten ja kiireellisten päätösten tulvalta. Tämä ihmiset …