Numbers can make a noise account sound objective, which is why they are tempting in a tense conversation. Yet a dB reading and a clear complaint are not the same thing. A measurement may contribute useful context; it cannot, by itself, describe the full experience or explain what caused the sound.
Keep the measurement in context
Suppose a resident hears intermittent low thumps late in the evening and takes a reading during one burst. That value belongs to a moment, at a particular place and under particular conditions. It does not automatically characterize the whole evening, identify which room or person produced the noise, or establish how often it happens. If the log presents the number without those limits, readers may infer more than the measurement supports.
A more careful entry pairs a reading, when available, with the time, duration, location of the observer, and a plain-language description. “Meter reading at the living-room doorway during a short burst” is more transparent than a number presented as though it were a universal summary. The written account does not need to make technical claims; it needs to say what was actually observed and when.
Clarity is not the same as force
Some people argue that complaints should lead with the strongest number because it is concrete. Others prefer a narrative description because it reflects how the disturbance affected ordinary activity. Both instincts have merit: a number can sharpen an account, while a description can explain why the event mattered. The mistake is expecting either one to do both jobs.
Consistency helps here. Using a similar method from one incident to the next can make entries easier to compare. But consistency does not remove uncertainty about measurement conditions, and it does not make a reading scientifically validated. An honest record can acknowledge that one event was measured and another was not, rather than smoothing the difference away.
Describe the sequence, not a verdict
For a recurring issue, the sequence across days may be more informative than one striking reading. Did short events happen at a similar hour? Did they last longer on one night? Were there nights without a disturbance? These are practical questions a timeline can help answer without speculating about motive or assigning blame. A record can support a clearer discussion precisely because it does not announce a verdict.
I would use measurements as one ingredient, not the headline that stands in for everything else. Pair them with timestamps and a factual description, and make the limits visible. That approach may feel less forceful than a single dramatic number, but it is easier to explain and harder to misread. When you see a sound-level reading in a complaint, what context makes it useful to you?
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)