Demo pack
For whoever is presenting. Test environment, made-up data: no real school, staff or pupils. Ballymore Primary School, week 11 of term 1.
The story in one paragraph
The school is now in week 11 of term 1 and is in good shape: about seven in eight planned lessons are recorded as taught. The planner shows a head teacher three things they would otherwise find out at the end of term. P2 has an ICT gap that needs teaching support. P5's teacher started recording late, so the class looks far behind although its assessment results show the teaching happened. And a closure day left the same lessons untaught in several classes. In five minutes the head teacher goes from "how are we doing?" to three specific actions, and watches the figures change as a teacher catches up.
The five findings to reveal
- Most classes are on track. Proves the tool does not cry wolf.
- P2 is behind in ICT only. A subject-level gap that needs support, not blame.
- P5 looks far behind, but its assessments are normal. Tells a recording gap from a teaching gap.
- The closure week's lessons were missed by several classes. Makes "most often missed" mean something.
- P3 dipped and has recovered. Shows change over time, not a snapshot.
The classes
| Class | Teacher | Profile | Outstanding |
|---|---|---|---|
| P1A | Mrs Aoife McCann | Steady, ticks as she goes; caught up after the closure | 88% |
| P2A | Mr Ciarán Doherty | Strong in Literacy and Numeracy, less confident with Scratch | 84% |
| P3A | Ms Rachel Kerr | Supply cover for a fortnight, has won half of it back | 80% |
| P4A | Mrs Siobhan Quinn | Everything taught, ticked and evaluated | 95% |
| P5A | Mr David Rafferty | New: taught it all, started recording in week 4 | 63%, 30 outstanding |
| P6A | Miss Niamh Gallagher | Probationary; ticks a week at a time on Fridays | 81% |
| P7A | Mr Mark Hutchinson | Transfer-test focus; ICT squeezed before the test | 87% |
| Each year's B class — Mr Peter Lenehan, Mrs Hazel Moore, Mr Owen Brady, Miss Laura Finn, Mrs Deirdre Walsh, Mr Shane Corrigan, Mrs Fiona Hughes — keeps up better, between 87% and 92%. P5B is the contrast that makes P5A's story: same year, same teaching, one teacher recording it. | |||
Every year has two classes, A and B: a lesson belongs to a year group, so only classes in the same year are ever due it. With one class a year nothing could be "missed by more than one class" and the whole closure story had nowhere to live. Each B class has its own teacher and its own habits. A week is nine lessons here: 4 Literacy, 4 Numeracy and 1 ICT. The PE lessons are Healthy Kids' material and belong to Tannaghmore alone (DEC-008), so no other school sees them — which is why this school's week counts nine and not ten. Pupils appear as initials or a school ID. The planner has no pupil name column anywhere, by design (DAT-007) — say so if data protection comes up: it is a strength, not a gap.
The script, about five minutes
-
The headline 30s · Overview, as the head teacher
Show: the headline card, left to right — 86% on plan; the week-by-week line against the 90% target, with its low in week 3; and the 117 lessons behind, with P5A (30, nothing ticked weeks 1–3), P3A (14, mostly weeks 3–4) and P2A (11, mostly ICT) named.
"The school is in good shape: 86% of this term’s lessons are recorded as taught. The line shows how each week went — the early weeks dipped and it has run near the target since. And the planner has already worked out where the gap is: nearly half of it is three classes, each for a different reason, so you don't have to go hunting."
-
The subject picture 30s · Overview, by subject
Show: ICT at about 75%, with Literacy at 89% and Numeracy at 86% — ten points and more between them.
"ICT is the subject slipping across the school. That's common in primary, where confidence with ICT varies between teachers. Let's see where it comes from."
-
The ICT gap in P2 45s · By year group
Show: P2 strong in Literacy and Numeracy, ICT far behind; open a lesson to read the teacher's own note — "I need more confidence with Scratch myself".
"This isn't a class that's behind; it's one subject. That's a support conversation — pairing the teacher with a colleague — not a performance one."
-
P5: recording, not teaching 60s · Today, as the Co-ordinator
Show: P5's row flagged with 30 outstanding and "No ticks all term"; then its week 6 assessment results, in line with the other classes.
"On paper P5 looks far behind. But nothing at all in the early weeks, then normal from week 4, and the assessment results are as good as anyone's. The teaching happened; the record didn't. A five-minute catch-up fixes it."
There is no "Remind teacher" button in this build. Don't reach for one: the catching-up in step 6 is where the action happens.
-
The closure week 45s · Overview, lessons most often missed
Show: the week-7 lessons at the top, missed by both classes in the years that never caught up — P5, P6 and P7.
"This is what a single closure day does. Some classes caught up, others didn't, so those lessons are now a whole-school gap you can decide to slot back in before Christmas."
-
The live moment 60s · two windows
Do: in a second window, pick P5's teacher and tick a week's lessons on Today. Switch back to the head teacher's Overview and reload.
"That's the teacher catching up, and the head teacher sees it straight away. No spreadsheets, no chasing emails."
This is the most persuasive minute of the demo. Leave P5's early weeks unticked beforehand so there is something to do.
If there is more time
- This week. The Co-ordinator's grid: squares per lesson, one class not started. Explain that a teacher who ticks on Fridays is a normal pattern, not an alarm.
- Looking ahead. Planning settings in the administration app: term 2 has more weeks of lessons than teaching weeks, and the school chooses which to drop.
- Roles. The same school seen as a teacher, a Principal and an administrator, including what each cannot do.
Likely questions
- Is this real school data?
- No. Invented school, staff and pupils throughout.
- Won't teachers feel monitored?
- The planner tells a recording gap from a teaching gap (P5), and a support need from a performance problem (P2). It leads to conversations, not judgements.
- How long does ticking take?
- Seconds a lesson, and a week's worth can be done in one go.
- What about closures and disruption?
- The closure week shows the effect across the school and which lessons to reschedule.
- Can it handle composite classes, like P3/4?
- Not yet. A class has exactly one year group; composite classes are an open decision (DEC-007). Say so plainly — they are common in smaller schools here.
- Why are pupils shown as initials?
- By design: initials or the school's own ID, never names (DAT-007), which keeps the planner low-risk under data protection rules.
Before you present
- The seed has been run, so the school is back to its known state.
- The planner opens at the Overview and the figures look like the table above.
- ICT is clearly the lowest subject.
- "Lessons most often missed" has the closure week's lessons at the top, missed by more than one class.
- P5's row on the Co-ordinator's Today is flagged, with its backlog and the "no ticks all term" line.
- P5's early weeks are still unticked, ready for the live moment.
- Two windows open: head teacher in one, P5's teacher in the other.
- No screen shows 0% beside "on track", and no class label is printed twice.
- You know step 4 has nothing to click.
Known limits of this build
| Item | Status | What to do in the demo |
|---|---|---|
| Pupil names | Not stored, by design (DAT-007) | Say so: it is a strength if data protection comes up |
| Composite classes | Not supported; decision open (DEC-007) | Answer honestly if asked |
| "Remind teacher" | Not built | Step 4 has no click; the live catch-up carries the action |
| Lessons by day of the week | The planner holds a week, never a day | Don't promise "4 of 9 expected by Wednesday" — the figures are per week |
Reset: running the seed job puts the school back exactly as it was — it clears every tick and result for these classes first, including anything ticked during the demo, then writes the known state again. Run it after a demo so the next one starts from the same place, and write down any question you could not answer.