“It was loud” can mean a sharp crash that startled you, a low hum that lasted for hours, or music that made it hard to hear a phone call. The phrase is not wrong; it compresses several different experiences into one adjective. In a recurring noise complaint, that compression can create a familiar argument: one person says the sound is excessive, while another says it is ordinary. Recording more than an impression can make the disagreement more specific without pretending to end it.
Sound level is one dimension
A dB meter provides a reading about sound level at a particular moment. That is useful information, but it is not the whole experience. Duration, repetition, timing, the room where you hear the sound, and the kind of sound all matter to a person living with it. A brief impact and a steady mechanical hum may register differently in daily life even if a single reading cannot express that contrast.
Nor should a number be treated as a pass/fail answer. A measurement is shaped by where and how it was taken, and it does not identify the source. If conditions differ between readings, comparing them as if they were identical can mislead. The honest approach is to keep the context with the reading: time, place, and what was audible.
Describe the pattern as well
Suppose a neighbor's television is audible through a shared wall on several evenings. “Too loud” records your evaluation. A fuller entry might say that speech was intelligible in the bedroom, began around 10:40 p.m., and faded by 11:15 p.m. on the nights you noticed it. If you measured a level, record that separately. The description lets someone understand the quality and timing; the measurement supplies a different kind of detail.
This separation helps avoid a common trap: collecting numbers while leaving the actual experience vague. It also avoids the reverse trap of leaning only on emotional language. You do not have to choose between “I was disturbed” and “here is what I observed.” A useful record can state both, clearly marked.
Specificity is not certainty
There is a legitimate counterpoint: a log can look authoritative even when its entries are estimates. Exact-looking values may create more confidence than the method warrants. If you did not record the beginning immediately, say “about 10:40.” If the source is uncertain, say so. A careful range or qualified description is stronger than invented precision.
For repeated incidents, consistent notes can make comparison easier over time. The Noise Complaint app combines incident logging and timestamps with a dB meter; it also supports audio/video evidence, offline use, and PDF, Word, and Excel export. It is a documentation tool, not a judge of what a reading proves. The useful takeaway is to record enough context that numbers and lived experience illuminate one another. Do you find measurements clarify noise disputes, or do they sometimes distract from duration and impact?
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)