AI for the Admin No One Sees: Referrals, Incident Notes, and Pastoral Paperwork
Teaching has obvious admin — reports, planning, marking. Pastoral roles have a second, quieter pile: referral write-ups, incident notes, meeting summaries, and the emails that follow them. It rarely gets talked about, but it's often the bigger time sink, because it has to happen immediately, between classes, with half the facts still settling in your head.
This is exactly the kind of writing AI is good at — turning messy notes into something clear, calm, and ready to send or file. Here's how to use it properly.
1. Turning rough notes into a formal incident record
After an incident, you usually have fragments: who, what, when, maybe a quote. Don't try to write the polished version yourself — dump the fragments into AI and let it structure them.
Prompt:
"Turn these rough notes into a formal incident record for our school's system. Keep it factual and neutral — no opinions, no assumptions about intent. Use this structure: Date/time, Students involved, What happened (chronological), Action taken, Follow-up required. Notes: [paste your raw notes]."
The "no assumptions about intent" instruction matters — it stops AI from writing things like "deliberately provoked," which you haven't established and shouldn't put in a record.
2. Drafting the follow-up email to a parent
Once the record exists, the parent email almost writes itself.
Prompt:
"Using this incident record, draft a calm, factual email to the parent. Open by stating the purpose, summarise what happened in 2-3 sentences, explain what action the school has taken, and end with an invitation to discuss further. Keep it under 150 words. Tone: respectful, non-defensive, assumes good faith from the parent."
Always read this one before sending — a parent email needs your judgement on tone for this family, not just AI's default.
3. Summarising a meeting in two minutes
Pastoral meetings — with parents, with senior leadership, with outside agencies — generate notes that need to go somewhere: a file, a colleague, a database. Don't write the summary from memory after the fact.
Prompt:
"Summarise these meeting notes into: Attendees, Key points raised, Decisions made, Actions (who/by when). Keep it factual, no interpretation. Notes: [paste]."
If you talk-to-text your notes during or right after the meeting, even messy, this prompt cleans them into something filed-ready in under a minute.
4. A weekly referral pattern check
This one is less about writing and more about noticing. Once a week (or fortnight), paste a list of referrals — student, reason, date, no identifying details beyond initials if you're cautious about privacy — and ask:
Prompt:
"Looking at this list of referrals, what patterns do you notice — by day, time, subject, or repeat names? What would you flag for follow-up?"
This is the kind of pattern-spotting that's easy to miss when you're handling referrals one at a time, reactively, between classes.
The privacy line
A genuine caveat, not a disclaimer for its own sake: be careful what you paste. Stick to first names or initials where you can, avoid pasting anything that would identify a student to someone outside the school if it leaked, and check your school's policy on using AI tools with student data before this becomes routine. The structure and drafting help is real — but it has to sit inside that boundary.
Why this is worth doing
None of this saves dramatic amounts of time on any single task. What it does is remove the friction of starting — the blank page, the "how do I phrase this neutrally" moment — on tasks you have to do constantly, under time pressure, often right after a stressful exchange. That friction, multiplied across a term, is where the hours actually go.
TeachSmarterAI helps New Zealand teachers use AI tools effectively. New posts every week.