DEV Community

Cover image for Describe the Noise Before Guessing Its Source
Ba Phuc Tran
Ba Phuc Tran

Posted on

Describe the Noise Before Guessing Its Source

When an upstairs chair scrapes across the floor at midnight, it is tempting to write down “the neighbors were making unreasonable noise.” That sentence combines a sound, a guess about its source, and a judgment about the people responsible. It may reflect how the moment felt, but it gives a later reader little to work with. Clear documentation is not about denying annoyance; it is about separating what you heard from what you concluded.

Describe the sound before naming a cause

“Three short scraping sounds, followed by a heavier thump, audible in the bedroom around 12:05 a.m.” is more useful than a confident source attribution when you did not see what happened. Note the location where you heard it, its character, and its approximate duration. If you are not sure whether it came from above, next door, or a shared space, say so. Precision includes knowing where your knowledge ends.
This distinction matters because ordinary apartment sounds travel unpredictably. A vibration can move through a wall or floor, and a sound that seems close may have another origin. A dB meter cannot identify a neighbor either. It records a level, not an address or intention. Using a reading to claim more than it can establish weakens rather than strengthens the account.

Separate impact from inference

It is still important to capture the effect. You can write that the sound interrupted sleep, woke a child, or made a conversation difficult, if that is what happened. Put that beside the description rather than replacing it. “The impacts woke me twice” reports an experience; “they are doing it to keep me awake” assigns motive. Those are very different claims.
Consider a recurring evening noise that varies from night to night. A log with times, duration, room, and a short description can help reveal whether the events cluster at a certain hour. A few readings taken under similar conditions may add another detail, but they do not establish a universal threshold or prove a rule was breached. Consistency is more valuable than dramatic language.

Make a record a reader can follow

In a tense dispute, each side may remember the same event differently. A contemporaneous note gives you something more stable than recollection alone. Be specific without pretending to certainty: “between about 12:05 and 12:20,” “intermittent low thumps,” or “source unclear” are careful formulations. If you have audio or video, note what it captures and what it does not. Evidence has limits, and acknowledging them is part of being fair.
The Noise Complaint app offers incident logging with timestamps and a dB meter, plus audio/video evidence capture, offline operation, and PDF, Word, and Excel export. Those tools can help organize observations, not determine who caused a sound or what a complaint should conclude. The practical principle is simple: record the event, record its impact, and label your interpretation as interpretation. When you document a noise, where do you draw the line between a useful inference and an unsupported assumption?
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)