When noise keeps returning, “it lasted a long time” is often the detail people remember—and the detail they can least support later. Duration sounds simple, but repeated start-stop events make it surprisingly hard to estimate. I think a useful incident history should record pauses as well as the overall span. That takes a little more care than writing down a single end time, but it avoids turning a scattered evening into one uninterrupted block that never happened.
One event can contain several episodes
Picture a late evening when a drill or heavy banging comes from somewhere in a shared building. It begins at 19:10, stops at 19:18, returns around 20:00 for ten minutes, then there is another burst after 21:00. If someone later writes “construction noise from 19:10 to 21:15,” the note implies more than two hours of continuous sound. If they instead record each interval, the history preserves both the full window and the gaps.
This distinction is not pedantry. A neighbor who heard only one burst may reasonably remember the evening differently from someone who experienced all three. A clear record can accommodate both observations instead of insisting that one person’s impression must erase the other’s. Describing a pause is useful information, not evidence that the disturbance was insignificant.
Precision without false exactness
There is a trade-off between detail and effort. Looking at the clock every minute can interrupt whatever you are doing, and a timestamp remembered later is never as precise as one made at the time. But an incident log need not claim laboratory precision. “About 20:00” is more honest than a made-up exact minute; “two short returns before 21:15” is better than silently filling in what you did not observe.
For each episode, note what you could actually tell: approximate start, end or pause, and a plain description of the sound. If you measured sound levels, keep the measurement associated with the time it was taken rather than treating it as a summary of the whole evening. A dB reading and a duration answer different questions. Neither tells you by itself what caused the noise, whether it was unreasonable, or what outcome another person should reach.
A timeline should make uncertainty visible
The strongest objection is that careful logging can feel like work imposed on someone already dealing with an unwelcome disturbance. That is fair. Keep the method simple enough to sustain: record a new interval when the sound returns, and mark estimates as estimates. Skipping an entry is better than inventing one. Over time, separate intervals can show whether the pattern is brief, intermittent, or more continuous than memory first suggested.
Noise Complaint – dB Meter & Log can keep timestamped incident notes and dB readings together, with optional audio/video evidence and PDF, Word, and Excel export; it also works offline. It is a practical way to organize what you observed, not a promise of a particular complaint outcome. The central habit is simply to distinguish the span of an evening from the actual periods when noise was heard.
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)