Learning objectives
- Build a digital incident log that holds up to scrutiny.
- Apply a fair three-strike escalation ladder.
- Use restorative scripts that end conflict, not extend it.
- Know when (and how) to escalate beyond your classroom.
Why you document everything
Most discipline problems escalate not because the pupil is uncontrollable, but because the teacher has no record. When a parent challenges you ("My child says you punished him for nothing"), an incident log with dates, times, what was said, and what was done resolves the conversation in 90 seconds.
Documentation isn't bureaucracy — it's protection. For you and for the pupil.
The incident log — Google Form template
Create one Google Form titled "Incident Log — JSS1A". Fields:
- Date & time (auto-fill)
- Pupil name (dropdown from class list)
- Where it happened (Classroom / Corridor / Field / Other)
- What happened (paragraph — describe in factual, neutral language)
- Who else was involved (paragraph — names of witnesses)
- Action taken (Warning / Move seat / Detention / Parent called / Escalated to Head)
- Strike number (1 / 2 / 3)
- Follow-up needed (checkbox — call parent, restorative chat, etc.)
💡 Writing rule
Describe behaviour, not character. Wrong: "Tunde was rude." Right: "Tunde said 'shut up' to Ada when I asked him to begin the task."
The three-strike ladder
| Strike | Your action | Communication |
|---|---|---|
| Strike 1 | Private verbal warning. State the rule broken and the expected behaviour. 30 seconds. Move on. | None to parents. |
| Strike 2 | 5-minute private "restorative chat" after the lesson. Pupil signs the incident log. Lose 1 ClassDojo point. | WhatsApp the parent that day: factual, brief. |
| Strike 3 | Escalate to Form Master / Head of Year. Pupil meets with both. Detention or community task assigned. | Formal phone call to parent. Invite to school if needed. |
Strikes within a week. Reset every Monday morning — same logic as points.
Restorative scripts (use word-for-word)
The goal of restorative discipline is repair, not retribution. Three scripts that work:
Script 1 — When a pupil is disruptive
"Tunde, I want you to learn well today. Right now what you're doing is making that harder for you and for Ada. We had an agreement when we wrote the charter. Are you able to keep it now?"
Script 2 — After Strike 2 (private chat)
"Three things. First, what happened today? Second, who was affected? Third, what will you do differently tomorrow? I'll write down what we agree."
Script 3 — Calling the parent
"Good afternoon Mr Musa, this is Mrs Adeyemi from JSS1A. I'm calling because of an incident today involving Bashir. I want to share what happened and agree how we'll handle it together. Is now a good time, or shall I call back this evening?"
When to escalate beyond your classroom
Always escalate same-day if any of the following is true:
- Physical fight or threat of violence
- Bullying with a clear pattern
- Anything involving a safeguarding concern (Unit 7 covers this in detail)
- Any incident involving school property damage
- Third strike in the same week
- Any pupil with a wellbeing or family-context concern you can't address alone
Never carry a serious incident home. Tell your Head of Year before you leave the building.
🎬 Demo — A textbook Strike 2
1:50pm. Tunde shouts across the class for the second time. You walk over quietly. "Tunde, stay back two minutes after the bell, please."
2:35pm bell. Class leaves. Tunde stays. You sit beside him.
You: "What happened?" He explains.
You: "Who was affected?" He thinks.
You: "What will be different tomorrow?" He commits.
2:38pm. You log the incident on the form. He signs (initial). You send a one-line WhatsApp to his mother: "Mrs Bello, just a heads-up — Tunde and I had a short chat after class today about call-outs. Nothing serious, but I wanted you to know. He's agreed to a fix."
Total time: 4 minutes. Documented. Repaired. No drama.
✍ Exercise 4.1 — Build your incident system
Before the next school day:
- Build the incident log Google Form with all 8 fields.
- Print one Strike 2 restorative chat script to keep on your desk.
- Decide who you escalate to at Strike 3 — Form Master? Head of Year? Note their phone number.
Deliverable: Form link and printed script saved to your culture pack folder.
Knowledge check
Unit 4 — Discipline & Escalation
4 questions. Choose the best answer for each.
Question 1 of 4
Why is the incident log important?
Question 2 of 4
Which entry is correctly written?
Question 3 of 4
A Strike 1 in this system is best handled by:
Question 4 of 4
Which of these is a MUST-escalate-same-day situation?
Unit summary
- Document every incident — factually, briefly, on the same day.
- Three strikes, reset weekly, escalation rules clear in advance.
- Restorative scripts repair relationships; punishments alone don't.
- Some incidents always escalate same-day. Know the list.