One common mistake in noise documentation is treating a decibel reading as if it explains the whole incident. It does not. A number can describe a measured sound level under particular conditions, but it cannot, by itself, tell you what made the sound, whether it came from a neighbouring unit, or how disruptive it felt to the person hearing it.
Measurement answers a narrower question
Suppose a resident hears a steady hum through a shared wall and opens a meter app. The reading changes when they move toward the wall, when traffic passes outside, and when a refrigerator cycles on. None of those changes necessarily identifies the source. The measurement is an observation of sound at the microphone in that moment, influenced by the room and surroundings. Treating it as a source detector overstates what it can do.
That limitation does not make measurement useless. It can add a comparable detail to a log when a person uses it consistently and records the context. A timestamp, approximate duration, location, and short description help the reading sit inside an incident rather than float alone. If the device or measurement method is informal, that should remain understood; careful notes do not turn a consumer reading into laboratory-grade evidence.
Keep experience in the record too
There is a competing concern: focusing on numbers can appear objective, while words such as “intrusive” or “distressing” can sound subjective. But dropping lived impact would also leave out something important. A short burst that wakes someone can matter more to them than a longer, quieter sound. Duration, timing, repetition, and personal effect are different dimensions, not rivals where only one is legitimate.
A clear entry might therefore distinguish the layers: “At 22:15, a pulsing low sound was audible in the bedroom for about 18 minutes; meter reading varied while traffic passed; it interrupted reading.” That wording does not claim a cause, a legal standard, or universal harm. It tells a reader what was noticed and where uncertainty remains.
Use precision where it helps
The useful disagreement is not “numbers or descriptions.” It is whether a particular measurement adds context without being asked to prove more than it can. For a changing, intermittent sound, a careful written account may be more informative than a single peak value. For comparing similar moments, a reading may help. Choose the tool for the question, record its limits, and let the combined account stay modest.
iOS: https://apps.apple.com/se/app/noise-complaint-db-meter-log/id6779021010?l=en-GB Android: https://play.google.com/store/apps/details?id=com.quiet.log.noise.tracker
Top comments (0)