When writing down recurring noise, people sometimes wait until they have a complete explanation. They want to know whether the sound came from a particular unit, whether it was intentional, and whether it will happen again. That instinct is understandable, but it can make a record less useful: uncertainty about the cause does not erase what was heard. I would document the event first and reserve conclusions for later, if better information ever becomes available.
The source is often less certain than the sound
In an apartment, a thud can travel through a ceiling, a pipe can carry vibration, and a hallway can make a distant voice seem close. At midnight, it may be tempting to identify the neighbor above as the source simply because the sound seems overhead. But if you did not see what happened, that attribution is a guess. A factual note can still say where the sound seemed loudest and what it sounded like, while marking the source as unknown.
This distinction helps when events repeat. “Heavy impacts audible in the bedroom at about 00:20” can be compared with another entry from a different date. “The upstairs tenant was stomping again” adds an identity and intention that may not be established. A record that separates observation from inference is less likely to turn a solvable conversation into an argument over an unsupported accusation.
Detail does not mean certainty
There is a real counterpoint: overly cautious language can sound evasive, especially when someone has experienced the same disturbance many times. Repetition can make a source seem obvious, and people should not have to pretend they have no reasonable suspicions. But a suspicion is not the same thing as a timestamped observation. You can note that the sound appears to come from above while making clear that you did not confirm its origin.
It is also worth distinguishing what you heard from what you felt. “The bass was audible in the living room for about half an hour” records the event; “I could not concentrate on a call” describes its practical effect. Both can matter to a conversation, but combining them into one absolute claim obscures the difference. A measured dB reading, when taken, adds another observation. It does not identify a source or determine intent.
Make a record that leaves room to learn
A good log is not a courtroom script. It is a way to keep a series of observations available when memory becomes unreliable. Use dates, approximate times where necessary, plain descriptions, and explicit uncertainty. If you later learn more, add that context without rewriting what you originally observed. A careful account can still be direct: it need not minimize the disturbance to avoid overstating its cause.
Noise Complaint – dB Meter & Log supports timestamped incident logging, dB readings, and audio/video evidence, with offline use and PDF, Word, or Excel export. It helps keep observations organized; it cannot establish who caused a sound or guarantee how a dispute will be handled. Describing the unknown honestly is often what makes the known details easier to trust.
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)