“It annoyed me” and “the sound measured X” are not competing accounts. One describes a human response; the other describes a reading made under particular conditions. Noise disputes become harder when people expect one kind of statement to erase the other. A useful record lets both stand while being clear about what each can—and cannot—tell us.
Impact is real, but it is not a meter reading
Think of a person trying to work from home while a low hum travels through a wall. A short measurement may not look dramatic, yet the sound can remain noticeable through a long call. Another person may record a higher peak from a passing vehicle and barely notice it. Context, duration, timing, and the listener’s activity shape impact; a dB value alone does not summarize all of that.
At the same time, impact should not be turned into a measurement claim. “I could not concentrate” is a meaningful report of effect, but it does not establish a specific sound level. Keeping those statements separate makes it easier to discuss the event without dismissing either the person or the limits of the evidence. If a reading was taken, record where and when. If not, do not imply that one exists.
Build two clear columns in your thinking
It can help to imagine an incident note with two kinds of details. The first is observation: date, time, approximate duration, location, sound description, and any dB reading or audio/video evidence collected. The second is impact: woke me, interrupted a meeting, or was noticeable while reading. A separate line can identify uncertainty, such as an unknown source or an estimated duration. This is not bureaucracy for its own sake; it prevents observations and conclusions from becoming tangled.
The strongest counterargument is that this distinction may feel overly formal when someone is exhausted and wants a straightforward acknowledgment. That is understandable. A person should not need technical language to describe a difficult experience. The point is not to make complaints cold or disbelieved. It is to make their parts legible, so one person’s response is not mistaken for a universal measurement and a number is not used to invalidate an experience.
Specificity gives disagreement somewhere to go
If a neighbor, landlord, or property manager is asked to consider a recurring issue, precise notes can shift the conversation from “you are too sensitive” versus “you are inconsiderate” toward occasions, patterns, and possible explanations. They cannot guarantee agreement or determine an official outcome. They can make the concern easier to understand and questions easier to ask.
My view is that documentation should preserve both measurable information and lived impact without pretending they are the same thing. Record the sound as carefully as practical, then describe what it affected in plain language. That approach is more honest than either reducing an experience to a number or presenting personal impact as a measurement. A useful noise record is not a verdict; it is a clearer starting point for discussion.
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)