Every classroom has its loud hour. Mine is 1:30 to 2:30 — Year 2s, straight after lunch, doing continuous provision and table activities. For two years my role during that hour was, functionally, human volume knob: “voices down, please… gentle voices… that’s too loud now…” on a loop, maybe forty times an afternoon. It worked for roughly ninety seconds per repetition.
The thing that finally changed it wasn’t a new behaviour policy. It was projecting a live noise meter — a widget that listens through the classroom mic and shows the room’s volume as a moving level on the big screen — and then, crucially, handing the responsibility for it to the children.
Why seeing sound changes everything
Here’s the problem with “voices down”: six-year-olds genuinely don’t know how loud they are. Volume creeps. Each child adds a little to be heard over the child next to them, the room ratchets up, and nobody made a decision to be loud. When I said “too loud,” I was giving them feedback they had no way to calibrate against.
The meter fixes the calibration problem. The room’s loudness becomes a thing you can see — a level that climbs toward a line when the hum builds and settles when it fades. Suddenly “too loud” isn’t the teacher’s opinion; it’s a fact on the screen, visible to the exact same degree from every seat.
The first afternoon I turned it on, I didn’t even set a rule. The class just… watched it. A table would get giggly, the level would climb, and children would physically point at the screen and shush each other. I said “voices down” maybe twice that whole hour, and both times felt like I was interrupting a system that was already working.
The routine, as it actually runs
A term of tinkering later, here’s the shape of my noise meter afternoon:
1. We set the target together. At the start of the activity block I ask, “What kind of working is this?” Partner work gets a generous threshold; independent writing gets a strict one. Letting the class name it matters — they hold each other to a line they chose in a way they never held each other to mine. I keep a work symbols widget next to the meter showing the matching mode (partner talk, whisper, silent), so the expectation and the measurement sit side by side.
2. The meter is the referee, not the teacher. This is the whole trick. When the level crosses the line, I don’t scold — the class notices, and it self-corrects within seconds. My scripted response, if I say anything at all, is a mild “check the meter,” which is about as emotionally loaded as “check the weather.” The meter never gets frustrated, never has a tired day, and never singles anyone out. All the things that made my verbal reminders wear thin just don’t apply to it.
3. Quiet streaks earn something small. We play “beat the meter”: if the class keeps the level under the line for the full activity, it’s a tally toward Friday choosing time. Some afternoons I run a visible timer alongside — twenty minutes on the clock, level under the line, tally earned. The pairing of a countdown and a live meter is weirdly powerful; it turns self-control into a co-op game the whole room is playing together.
4. A noise monitor owns it. One of our rotating class jobs is Noise Monitor. That child gets to give the “check the meter” reminder before I do. Handing the reminder to a peer completed the handover — it is now genuinely not my job, and honestly the children are stricter about it than I ever was.
What I got wrong at first
I set the threshold too strict. Week one, I wanted library silence and set the line accordingly. The meter spent the whole afternoon in the red, the class learned the line was impossible, and they stopped looking at it. A threshold that’s always breached is the same as no threshold. Now I set lines the class can genuinely stay under with a bit of care — success has to be the normal state, with the line there to catch the drift.
I used it as evidence for telling-off. Early on I caught myself saying “look at that meter — I’ve had to remind you three times.” That converts the meter from a game into a surveillance device, and the goodwill drains fast. The meter works because it’s neutral. Keep it neutral.
I left it on during genuinely loud activities. Drama, celebrations, the last five minutes of a class game — some noise is the sound of the lesson working. I close the widget for those. A meter that’s ignored half the day teaches children to ignore it the rest of the day too.
I expected it to work without teaching. The meter is a tool, not a spell. We spent ten minutes on day one experimenting — whispering to watch the level sit low, all talking at once to spike it, one child clapping to see it jump. That ten minutes of “how does it hear us?” bought a term of buy-in.
The practical bits
The Boardee noise meter runs off whatever microphone the classroom computer has — my ancient laptop’s built-in mic is plenty, since the meter only needs relative loudness, not studio accuracy. Nothing is recorded; it’s a live level, like the bouncing bars on a stereo. It works with no login (my board saves on the classroom machine), so there was no IT request, no install, and it was on my projector about ninety seconds after I first found it.
One layout tip: I dock the meter next to my traffic light widget. The traffic light is my signal to the class (amber means finish your sentence, red means stop and look); the meter is the class’s signal to itself. Together they’ve replaced probably 90% of my whole-class verbal management during activity time.
The real result
The measurable win: my after-lunch hour now runs with two or three volume reminders instead of forty, and most days the children give them, not me.
The win I didn’t expect: the vocabulary. My Year 2s now say things like “we’re getting near the line” and “that was just a spike, we came back down” — they talk about their collective volume as a thing they steer. That’s self-regulation in the most literal sense I’ve ever managed to teach it, and it came from a microphone and a moving level on the screen.
