Neighbor Noise Complaint, Response

Purpose

This procedure guarantees that a noise complaint against an already-installed generator ends with a measured answer, compliant or not, and why, rather than a guess pulled from the original commissioning file or a promise the shop cannot keep. A shop that waves off a complaint because the site passed once at install risks an ordinance citation landing on the customer while a five-minute panel check would have caught a degraded seal or a schedule that drifted into quiet hours. A shop that instead caves to an angry call and proposes a bigger enclosure without measuring first spends effort solving a problem that was never confirmed to exist. Either failure costs the same thing: the customer's confidence that the shop actually knows what the unit is doing.

Scope

Covers the response once a noise complaint reaches the shop, from the customer, a neighbor directly, or a code-enforcement or HOA notice, for an already-installed residential or light commercial standby unit. Does not cover the pre-install siting calculation, ordinance comparison, and mitigation sizing method, owned in full by the sound attenuation and setback standard; this procedure reuses that standard's distance-doubling and measurement method for re-verification rather than re-deriving it. Does not cover a hum or whine the owner reports at close range from their own unit, a mechanical bearing, winding, or belt diagnosis owned by that sibling troubleshooting file, though this procedure's inspection step may route there.

Roles and responsibilities

The procedure

1. Log the complaint precisely: date, time, duration, what was heard, weather or wind, and who reported it. Acceptance: a written record with every field filled, not a one-line voicemail summary. Wrong looks like scheduling a visit off "someone's complaining about the generator" with no time or date attached. Stop rule: if the complaint arrived with a citation, a deadline, or a hearing date, that window governs scheduling ahead of the normal queue, it does not sit in the standard callback rotation. Hazard: none; a records step. If the person delivering the complaint is heated on the call, acknowledge it and commit to a scheduled visit; do not argue the point or promise an outcome before anything has been measured.
2. On site, before touching the unit, confirm the currently adopted ordinance or HOA limit fresh, not the figure sitting in the install file. Ordinances and covenants get updated after a unit is commissioned, so a site that passed once can now fail against an unchanged unit. Acceptance: a written limit sourced from the current ordinance section or HOA document, not carried over from the commissioning record. Wrong looks like citing the old install-file figure without checking whether it changed. Stop rule: no diagnosis proceeds until the current limit is confirmed in writing. Hazard: none; a records check.
3. Take an actual sound-level meter reading at the property line and the specific location named in the complaint, under the same load and time condition that triggered it wherever practical. An exercise-cycle complaint gets measured during an exercise cycle, not an unrelated midday idle reading. Acceptance: a measured dBA figure at each point, with load state, time of day, and wind noted. Wrong looks like measuring at a convenient visit under a condition that does not match what was reported. Stop rule: if the complaint concerns the auto-exercise schedule specifically and the tech cannot be on site during the actual run, the visit is rescheduled to coincide with it rather than measured off-condition and called representative. Hazard: standing near a running, loaded unit puts the tech close to a moving fan, belt, and hot exhaust discharge; stay clear of moving components and the discharge path while reading the meter.
4. Where the reading exceeds the current limit, physically inspect the unit and its mitigation for degradation before assuming the original siting calculation was simply wrong. Check enclosure panels for a gap or a perished seal, mounting isolators for wear that lets vibration couple to the pad, and the muffler or silencer for a failure. Acceptance: a specific mechanical finding documented, panel gap, degraded isolator, failed muffler, or a clean inspection with nothing degraded. Wrong looks like proposing a bigger enclosure before confirming the current one is even intact. Stop rule: any degraded component found gets repaired first; a missing panel seal does not justify a full enclosure upgrade before the cheap fix is tried and re-measured. Hazard: reaching around a running enclosure to check panel fasteners and isolators risks contact with the moving fan or belt; shut the unit down for any close panel inspection rather than checking it live.
5. Where inspection finds nothing degraded and the reading still exceeds the limit, re-run the mitigation selection from the sound standard, repositioning, an enclosure, or a barrier, recomputing against the current limit exactly as that standard specifies. Acceptance: a revised computed figure that, once installed, is confirmed by a re-measured reading, not the manufacturer's rated reduction alone. Wrong looks like adding a generic accessory without recomputing whether it actually closes the specific gap measured. Stop rule: no mitigation is accepted as sufficient without a re-measured figure that passes. Hazard: installing an enclosure panel or barrier near the control compartment on an energized unit risks contact with live control wiring; de-energize control power per the manufacturer's procedure before working inside the compartment.
6. Check the auto-exercise schedule against the ordinance's posted quiet hours independent of the sound-level finding. A compliant dBA reading at the wrong hour is still a violation in most ordinances. Acceptance: the exercise schedule's start time confirmed outside posted quiet hours. Wrong looks like confirming the dB level and never checking whether the run time itself is the actual problem. Stop rule: any exercise scheduled inside posted quiet hours gets moved regardless of whether the dB level passes; a compliant unit run at the wrong hour is still the wrong hour. Hazard: none; a controller settings check.
7. Re-measure after any repair, mitigation, or schedule change, at the same points and under the same condition as step 3, before considering the complaint resolved. Acceptance: a post-fix reading at or under the current limit at every point checked. Wrong looks like assuming a resealed panel or a rescheduled run fixed it without a confirming reading. Stop rule: any point still over the limit routes back to step 5's mitigation menu; the visit does not close on an assumed fix. Hazard: same as step 3, stay clear of moving components and the discharge path.
8. Document the full response and communicate the outcome to the customer and, where appropriate, the complainant, naming the boundary of what the shop can resolve. Acceptance: a written record filed and the customer briefed on the finding and any fix. Wrong looks like the shop promising to "make the neighbor happy" when the site already measures compliant, a promise it cannot keep and one that invites the same complaint at the next exercise cycle. Stop rule: the job does not close without the written record, whatever the finding. Where a site measures compliant and the complaint stands anyway, the record says so plainly and routes further recourse to the ordinance authority or HOA, not the shop.

The record this produces

The complaint as logged, the confirmed current limit and its source, the measured reading with load and time condition, the inspection finding, any repair or mitigation applied, the schedule check result, the post-fix re-measurement, and the customer and complainant communication. Filed against the original sound and setback commissioning record so the site's full compliance history is in one place, not scattered across separate visit notes.

Worked pass: a 2 AM exercise cycle and a perished panel seal

An HOA emails the customer citing a nighttime noise violation tied to the generator's Tuesday exercise cycle. The customer forwards it; office logs the complaint with the cited time, 2 AM, and schedules the tech to be on site for the next Tuesday run rather than an unrelated daytime visit.

Step 2 confirms the HOA's current covenant limit, 55 dBA at the property line during posted quiet hours of 10 PM to 7 AM, unchanged since install. Step 3 measures during the actual 2 AM cycle: 60 dBA at the property line, 5 dB over. Step 4's inspection finds the cause is at least partly mechanical: the enclosure access panel's gasket seal has perished and the panel sits slightly proud, letting sound escape at that seam. The tech replaces the gasket and reseats the panel. Because the repair addresses a genuinely degraded component, step 5's larger mitigation menu is not engaged this pass.

Step 6 is where this pass fails. The schedule check finds the exercise start time is 2 AM, squarely inside the HOA's 10 PM to 7 AM quiet hours, regardless of what the dBA level turns out to be. The stop rule fires: an exercise inside quiet hours gets moved, full stop. The tech reschedules the weekly run to 9 AM.

Step 7 re-measures under the new condition, the 9 AM run: the resealed panel and the rescheduled hour together bring the property-line reading to 54 dBA, under the 55 dBA limit, and the run now sits outside quiet hours entirely. Step 8 documents both fixes, briefs the customer on the gasket replacement and the schedule change, and sends a written summary the customer can forward to the HOA.

References

• See related: Sound attenuation and setback standard, for the distance-doubling calculation and mitigation-sizing method this procedure reuses rather than re-derives.
• See related: Hum or whine from alternator, bearing versus winding versus belt decision tree, for a close-range mechanical noise complaint from the owner rather than a neighbor.
• ISO 8528-10, for generator sound-level measurement methodology and reference distances.
• Locally adopted noise ordinance or HOA covenant document, confirmed current at the time of response rather than assumed unchanged from install.