Reporting mechanisms: the map, and why children don't use it

Every safety lesson in every curriculum ends the same way — report it, tell someone — which makes it strange how rarely anyone teaches what reporting actually does, where the buttons lead, and why a child would believe the process worth using. The gap matters because the evidence says children mostly don't report: cyberbullying surveys consistently find large fractions of victimized children telling no adult, and children's own stated reasons form a teachable list — nothing will change, it will make things worse, I'll be blamed, my device will be confiscated. Reporting is a system children must trust before they'll use it, and trust is built by understanding plus experience — both teachable.

The map (Australia-first)

Layer 1 — in-platform tools: block and report, on every mainstream service. Blocking is instant self-protection; reporting feeds moderation. Both are anonymous to the reported account on major platforms — a fact children widely don't know and consistently overestimate the visibility of ("they'll know it was me"), which alone suppresses use. Teach it as fact: the person is not told who reported them.

Layer 2 — the statutory layer. Australia's eSafety Commissioner operates what most countries lack: complaint schemes with legal teeth, including the cyberbullying scheme for children — if a platform fails to remove serious cyberbullying material targeting an Australian child, eSafety can compel removal — plus the image-based abuse scheme (for shared or threatened intimate images) and illegal-content reporting, all at esafety.gov.au. The existence of an appeal beyond the platform changes the "nothing will change" arithmetic, and Australian children and schools should simply know it exists.

Layer 3 — crime: the ACCCE (accce.gov.au) for online child sexual exploitation (the grooming page's pathways), police for immediate danger.

Layer 4 — the adult next to the child: for a primary-age child every path above properly runs through a trusted adult — the child's job is telling; the adult's job is routing (and reacting well). Schools formalize this: online incidents belong in the same child-protection and anti-bullying processes as everything else, with the same documentation — and a school that tells students what happened next (within privacy limits) is building the "reporting works" evidence base in its own hallways.

Teaching reporting as competence

The framing battle decides usage. "Snitching" kills reporting among exactly the bystanders who could use it most safely; the counter-framing that works is infrastructure: the report button is the fire alarm — using it is what a competent person does, it protects the next kid too, and nobody calls the fire alarm a dobber. Three facts to install alongside: reports are private (see above), blocking is always allowed (no one is owed access to you), and reporting plus telling an adult is the standard play for anything that felt serious — the button handles the content; the adult handles the child.

What the evidence doesn't say

• It doesn't show platform reporting works reliably — moderation outcomes are opaque and uneven, and children's skepticism is partly earned; the honest teaching is "report anyway, and tell an adult — the second one always works."
• It doesn't quantify eSafety-scheme deterrence — the scheme's value to teach is the existence of an appeal, not a statistical promise.
• It doesn't make reporting the child's burden — the adult response determines whether a first report is followed by a second; underreporting is substantially an adult-behavior problem wearing a child-behavior label.

In the classroom

1. Tour the actual buttons — where report and block live on the platforms your students use; abstractions don't survive the moment of need.
2. Teach the privacy fact — "the person is not told who reported" removes the single biggest stated barrier.
3. Run the fire-alarm framing explicitly against the snitching frame — name both, let the class argue it once, settle it.
4. Tell reporters what happened — every well-handled small report a school processes visibly is a deposit in the credibility account the serious cases will need to draw on.

How Wiz Kids applies this

The simulated apps all carry working report and block controls, and safety scenarios require using them — children practice the mechanical act (find the button, choose the reason, block the sender) in Owl Post and the chat scenarios, with the privacy fact and the fire-alarm framing delivered in-fiction at first use. Australian pathway awareness (eSafety exists; it can make platforms act) sits in the teacher-facing material, where routing decisions actually live.

References

• eSafety Commissioner — the cyberbullying (children), image-based abuse, and illegal content schemes: esafety.gov.au.
• Online Safety Act 2021 (Cth) — the statutory basis for the schemes.
• Hinduja, S., & Patchin, J. W. — Cyberbullying Research Center survey series: victimization and (under)reporting rates, and children's stated reasons.
• Livingstone, S., et al. (EU Kids Online) — the tell-nobody findings and barrier evidence across countries.

© Glu IO Pty. Ltd. — Wiz Kids (wiz.kids). Link freely; republication requires permission — see terms. Found an error in our reading of the research? We correct fast: tell any teacher piloting Wiz Kids.