DEV Community

Cover image for Record the Sound, Not the Assumption
Vincent Tran
Vincent Tran

Posted on

Record the Sound, Not the Assumption

A noise log can become less useful when every entry tries to prove too much. Someone hears a thud at 11:40 p.m. and writes “the upstairs neighbor is deliberately stomping again.” The time may be accurate, but the sentence blends an observation with a conclusion about its source and intent. If the source is uncertain, that leap can distract from the pattern the record is meant to show.

Separate what happened from what you infer

A more careful entry might say: “Several heavy impacts were audible from above at about 11:40 p.m.; they continued intermittently for roughly ten minutes.” If known, add where you were and what you could actually distinguish. Avoid filling gaps with certainty. This is not about minimizing an unpleasant experience; it is about making the account easier for another person to understand without first accepting your interpretation.

That distinction matters especially in shared buildings. A sound can travel through walls and floors, and a late-night impact does not by itself establish who caused it. Recording the audible event, its time, duration, and context preserves the useful information while leaving room for explanations you may not have considered.

Why precision beats accusation

There is a real counterpoint: people dealing with repeated disruption can feel that cautious wording softens a serious problem. But factual language is not the same as timid language. “Repeated impacts woke me on four nights this week” is direct. It describes a meaningful effect and a pattern without claiming knowledge you do not have.

A dB reading can add another kind of information, but it does not identify a source, explain intent, or capture the entire experience. Treat it as one observation alongside a timestamped incident note, not as a verdict. If the app allows you to log incidents, measure sound, and keep records offline, those are practical ways to preserve details while the memory is fresh. The judgment about what the record means remains yours.

A record should leave the right questions open

When you review entries later, separate direct observations, measurements, and interpretations. That makes it easier to spot what repeats and what remains uncertain. A strong record does not need to sound like an argument; it needs to show what you experienced clearly enough that someone else can follow the timeline.

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)