A person can remember the night a disturbance became unbearable and still struggle to explain how often it had happened before. This is one reason recurring noise can be hard to discuss: the event that triggers action is vivid, while the gradual pattern that led to it is scattered across evenings, half-remembered conversations, and interrupted sleep.

One bad evening can distort the whole timeline

After several quiet days, a single late-night episode may feel like proof that nothing has improved. After weeks of repeated interruptions, one quiet night may create the opposite impression: perhaps the problem has gone away. Neither reaction is irrational. People naturally give recent, intense experiences more weight than ordinary ones. But a timeline helps separate a memorable incident from the longer course of events.
There is a counterargument worth taking seriously. A detailed log can turn daily life into a monitoring project, and that may keep attention fixed on every sound. Some people are better served by a simple note only when an incident meaningfully interrupts their routine. Documentation should reduce confusion, not create a new source of vigilance or stress.

Build a timeline from small, sustainable notes

For a recurring disturbance, use the same few fields each time: date, when it was noticed, approximate end or last check, a neutral sound description, and any immediate effect that matters to you. A short entry such as “Tue, noticed repeated impacts around 11:20 p.m.; stopped hearing them before midnight; woke once” is more useful than a paragraph written weeks later from memory. If you do not know an exact end time, say that.
After several entries, review them as a sequence rather than treating each one as a separate verdict. Are incidents clustered on certain days? Do they tend to occur around a similar time? Are there long gaps? A timeline can reveal that the pattern is less frequent, more intermittent, or more concentrated than it seemed in the moment. That does not invalidate the disruption; it sharpens the description.

The record should keep uncertainty visible

Do not fill in missing nights as quiet nights unless you actually know that. “No entry” means no entry, not necessarily no noise. Likewise, a log of observed incidents is not a full account of every sound in a building. Keeping those distinctions explicit makes the record fairer to everyone and helps prevent an inference from hardening into a supposed fact.
The broader lesson is modest: the point of a timeline is not to make a complaint sound dramatic or conclusive. It is to give a person and a listener a shared sequence they can discuss. A practical record can make the difference between “this is always happening” and “these are the nights I noticed it.” How would you keep that process useful without letting it take over your attention?
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