For the PBL team · Back of house

Behaviour data · 2026

Where, when and how our behaviour incidents are happening — mapped by term and fortnight so we can watch whether our PBL and wellbeing initiatives are shifting the picture.

School Bytes incidentsDistinct incidentsData to 16 June 2026

472

Incidents logged · Term 2

Average per week

52%

In the classroom

35%

In playground areas

Executive referrals

Across the year

Term by term

This export holds Term 2. As each term’s data comes across from School Bytes, it slots in here the same way.

Term 1No data yet

Term 2472 incidents

Term 3Awaiting data

Term 4Awaiting data

The trend

Incidents week by week

The clearest test of whether things are moving: the count of incidents logged each week across Term 2, grouped into fortnights.

Weekly incidents · Term 2

Each point is the number of distinct incidents that week. Week 9 (dashed) is still in progress.

Read it carefully. Incidents climbed steeply over the first month (Fortnight 1 to 2), then settled at roughly 125–135 a fortnight. A jump that size in a few weeks is more likely staff logging more consistently in School Bytes as the system embeds than behaviour itself tripling — worth confirming before drawing conclusions.

Under each term

Fortnight by fortnight

Our PBL focus runs in fortnights, so this is the unit that matters most for judging a focus area.

Incidents per fortnight

Fortnight 5 (*) is partial — only Week 9 so far.

What setting were they in?

The same fortnights, broken down by where incidents happened — so you can see if a focus area is shifting.

Classroom & learningSprite areaGAF areaTAC areaLines & transitionsToiletsOther / off-site

This is the chart to watch. If the school-expectations rollout is working, the playground slices (Sprite, GAF, TAC) should shrink as a share over time; if Ready to Learn and Berry Street are landing, the classroom slice should ease. Compare the shape of each fortnight, not just the totals.

Where

The settings, ranked

Where incidents are recorded points straight to which initiative has the most to do.

Incidents by setting · Term 2

Grouped into the areas we run expectations for.

Sprite expectations → GAF expectations → Ready to Learn →

What

The most common incidents

The primary type recorded for each incident — the top dozen.

Incident type · Term 2

One primary type per incident.

Who & what happened next

Stage and outcome

Which stages are most represented, and how incidents are being resolved.

By stage

Distinct incidents per stage.

By outcome

The primary outcome recorded.

Before you conclude

Reading this honestly

A few things to hold in mind so the numbers help rather than mislead.

Counts are distinct incidents. One incident involving several students is counted once, so these are events, not student tallies.
Logging is still embedding. The early-term climb most likely reflects staff using School Bytes more consistently. Rising recorded numbers can mean better recording, not worse behaviour — treat the trend as a baseline you’re building, not a verdict.
Term 2 only, to 16 June 2026. Week 9 and Fortnight 5 are partial. The fairest comparison will be the same fortnight across terms, once Term 3 lands.
Categories need tightening. “Other (in notes)” and blank outcomes are large. The more consistently staff pick a type and an outcome, the sharper every chart above gets.
To judge an initiative, pick its setting, follow that slice across fortnights, and ask whether its share is falling — the headline total is still moving with logging habits.

Keep it aggregate. This page only ever shows counts. Names, notes and individual records stay in School Bytes — never paste them here.