Noise Complaint Scripts

Problem

Neighbor noise disputes often get stuck at two points: how polite the first message should be, and where to escalate if that fails. Hard confrontation can make the situation worse, while no action can miss the chance to build a usable record. noise-complaint-scripts addresses this by turning informal talks, property management complaints, 12345 hotline calls, and pre-legal notes into reusable communication templates.

How It Works

The skill runs through situation intake, strategy selection, script generation, and escalation planning:
- Intake: confirm noise type, time, frequency, and prior attempts so a footstep issue is not misread as construction or shared equipment.
- Strategy: choose a polite, formal, or legal-tier response based on severity and history, rather than always outputting the strongest tone.
- Output: generate spoken lines, written notices, property complaint letters, or hotline points, with usage context and escalation triggers.
- Escalation: if the current channel fails, map the next step to property, residents' committee, 12345, police, or mediation.

It may reference common rules from the Public Security Administration Punishment Law and Law on Prevention and Control of Environmental Noise Pollution, and reminds the user to keep time logs, recordings, and decibel notes where relevant. For engineers, this is less a legal advisor and more a structured template generator for complaint workflows.

Boundaries

It does not replace legal representation, certified noise measurement, or enforcement. Construction-site noise, commercial premises, and professional decibel testing need regulators or qualified labs. If the source is unknown, the neighbor is threatening, or the noise comes from shared facilities, the workflow should pivot to property management, police, or third-party mediation. Local time limits, renovation rules, and anonymous complaint options still matter, especially when avoiding an aggressive first message.