Turn Scattered Noise Complaints Into a Dated Evidence Log
'It happens constantly' is not evidence, and everyone who deals with noise complaints knows it. This turns a running log into the two things a code-enforcement officer actually needs: how many incidents per week, and how many of them fall inside the local quiet hours. Local only; the log never leaves the tab.
- Log
- Dated entries counted per week and flagged for quiet hours
- local
- What it replaces
- A description nobody can act on
- $0.00
- Input
- Date, time, duration, and a note per incident
- no card
- Output
- Weekly counts and a pattern summary
- recomputed
What you pay otherwise
| Route | What you get | Cost |
|---|---|---|
| Lawyer's letter | Escalation before you have any evidence | $250+ |
| Moving out | Solving it by leaving | thousands |
| Complaining without a log | Your word against theirs, and nothing dated | nothing changes |
| This page | A dated log with counts and quiet-hours flags | $0 |
The workflow
Log every incident, including the minor ones
One line each: date, start time, how long it lasted, and a factual note. A log with 30 small entries is far more persuasive than five dramatic ones, because it shows a pattern rather than a grievance.
Write what you observed, not what you concluded
'Bass audible through the wall, 23:40–01:15' is evidence. 'They were deliberately targeting us' is an interpretation, and it weakens every factual line around it. Keep the notes boring.
Set your local quiet hours before you read the summary
The quiet-hours percentage is the figure that matters most, and it depends entirely on the window you enter. If your council's quiet hours are 22:00–07:00, say so — a 23:00 incident is then inside the window, not outside it.
Use the weekly count to decide when to escalate
Three incidents in a week is a conversation; fifteen across six weeks is a code-enforcement matter. The count tells you which one you have, so you escalate at the right moment rather than the angriest one.
Worked example
Sample: 9 entries over 6 weeks, quiet hours 22:00-07:00 Total incidents 9 Peak week 3 incidents (week of 2026-08-24) Inside quiet hours 9 of 9 (100%) Longest 120 min on 2026-08-24 Uploaded nothing — counted in the tab
Numbers above are sample data produced by the tool's own pre-loaded example, run in the browser — not averages or measured benchmarks.
What breaks this
Writing interpretations instead of observations undermines the factual lines around them — keep notes to what you heard and when. Logging only the worst incidents loses the pattern that makes the case. Guessing the quiet-hours window makes the most important percentage in the summary wrong.
Try it now
Nine entries across six weeks are loaded, all nine inside the 22:00–07:00 window. Move the quiet-hours start to 23:00 and the rate drops to 78% as two entries fall outside it.
Open the incident log →Go deeper: the printable log
The log is free forever. The $4 one-time tier adds:
- Printable log — the dated entries and the summary on one sheet for the officer — estimate: ~20 min saved reformatting before you file.
- Saved addresses shelf — keep up to 4 logs in this browser — estimate: ~15 min saved when a pattern resumes.
- Complaint letter export — the summary written into a complaint you can send — estimate: ~25 min saved drafting.