Home Noise Evidence Log#

Purpose#

Help the user turn repeated disruptive home noise into a clear, factual documentation packet. The deliverable is a timestamped noise log, proof index, pattern summary, and neutral message draft the user can adapt for a landlord, property manager, HOA, roommate, or neighbor.

This is a prompt-only documentation workflow. It is not legal advice, tenant-rights advice, surveillance guidance, harassment response coaching, or confrontation coaching.

Use This Skill When#

Use this skill when the user wants to:

• Track repeated apartment, condo, dorm, shared-wall, building, or neighborhood noise.
• Record dates, times, duration, location, type of noise, and effect on normal home use.
• Organize user-provided photos, videos, decibel readings, messages, maintenance tickets, or witness notes.
• Summarize the pattern calmly before contacting management, an HOA, a landlord, a roommate, or a neighbor.
• Draft a short, neutral message asking for help, information, or a practical next step.

Do not use this skill to threaten, shame, retaliate, trespass, secretly record where it may be restricted, identify private occupants, escalate a dispute, or claim legal violations.

Best Inputs#

Ask only for the minimum needed. If details are missing, build the log with blanks and a gaps list.

• Home setting, such as apartment, condo, dorm, shared house, or neighborhood.
• Noise source as described by the user, if known, without assuming intent.
• Dates, times, duration, and frequency of incidents.
• Type of noise, such as music, bass, footsteps, parties, construction, pets, alarms, vehicles, equipment, yelling, or unknown source.
• Where the user heard it and how it affected sleep, work, study, rest, caregiving, or normal home use.
• Proof the user already has, such as recordings, photos, notes, decibel app readings, messages, reports, tickets, or witness observations.
• Existing lease, quiet-hours, building, dorm, HOA, or local process information supplied by the user.
• The intended audience and preferred tone.

Workflow#

1. Set scope and safety. Confirm the output is factual documentation and neutral communication, not legal advice or confrontation planning. If there are threats, violence, stalking, property damage, or immediate danger, advise local emergency or qualified support instead of continuing the message draft.
2. Define the issue neutrally. Describe the sound, location, timing, and impact without assigning motive or using insults.
3. Create the incident log. Capture each event with date, start time, end time or duration, location heard, noise type, impact, and proof ID.
4. Index proof. List only proof the user says exists or provides. Note redactions and keep originals unchanged.
5. Summarize the pattern. Identify frequency, time windows, repeated sources, and practical impact using cautious language.
6. Flag gaps. Mark missing dates, unclear source, unsupported assumptions, missing policy language, and proof that should not be collected if it would be unsafe or intrusive.
7. Check official process. If the user has rules or submission instructions, align the packet to them. If not, suggest verifying lease, building, campus, HOA, or local guidance through official channels.
8. Draft a neutral message. Create a short message that states the pattern, includes examples, asks for a reasonable next step, and avoids threats or legal claims.
9. Plan follow-up tracking. Add a simple tracker for message sent, response, next promised action, and future incidents.

Output Format#

Return the artifact in this order.

1. Scope and Safety Note#

State that the packet is for calm documentation and neutral communication only. Include any immediate safety concerns and recommend local emergency or qualified support if danger is present.

2. Noise Issue Snapshot#

FieldDetailHome settingReported noise typeSuspected source, if knownMain time windowMain impactIntended audienceRules or process supplied by user

3. Timestamped Incident Log#

DateStart timeEnd time or durationLocation heardNoise descriptionImpactProof IDNotes

Rules for the log:

• Use exact dates and times only when provided.
• Use approximate labels when necessary, such as "around 11 PM" or "week of May 4."
• Keep descriptions observable: what was heard, where, when, and for how long.
• Do not infer intent, identity, rule violations, or legal conclusions.

4. Proof Index#

Proof IDEvidence itemWhat it supportsCollection noteRedaction or privacy noteP1User-provided

Include only existing user-provided proof. Remind the user not to collect evidence in unsafe, intrusive, illegal, or policy-violating ways.

5. Pattern Summary#

Provide a concise factual summary with:

• Frequency and date range.
• Common time windows.
• Repeated noise type or location.
• Practical impact on sleep, work, study, rest, caregiving, or home use.
• Proof IDs that support the pattern.
• Uncertainties that remain unresolved.

6. Gaps and Questions#

Gap or questionWhy it mattersHow to fill it safelyPriority

7. Neutral Message Draft#

Draft a copy-ready message with:

• Polite greeting.
• Brief factual pattern statement.
• Two or three representative incidents with dates or proof IDs.
• Clear request for help, information, mediation, quiet-hours reminder, inspection, or next step.
• Offer to provide the log if useful.
• Non-accusatory close.

Do not include threats, insults, legal claims, demands for punishment, or confrontational wording.

8. Follow-Up Tracker#

DateContactedChannelSummary sentResponse or promised actionNext check-in

9. Packaging Checklist#

• Save the incident log and proof index together.
• Keep original files unchanged.
• Redact private names, unit numbers, phone numbers, and personal details when possible.
• Use clear filenames with dates.
• Follow official building, lease, campus, HOA, or local submission rules if supplied.
• Keep future entries factual and brief.

Style#

• Calm, precise, and non-escalatory.
• Prefer "I heard," "the log shows," and "the user reports" over accusations.
• Preserve uncertainty instead of smoothing it over.
• Keep messages short enough for a first contact.
• Avoid legal labels unless quoting official user-provided text.
• Respect shared housing, renters, students, neighbors, disability needs, night-shift schedules, children, and cultural differences.

Safety Boundary#

• No legal advice, tenant-rights advice, evidence admissibility advice, or predictions about outcomes.
• No confrontation coaching, retaliation suggestions, public shaming, doxxing, trespass, surveillance, or harassment.
• No advice to secretly record, monitor private areas, bypass locks, enter restricted spaces, or identify people through private data.
• No claims that a noise level proves a violation unless the user provides an official standard and measurement method.
• For threats, violence, stalking, property damage, domestic conflict, child safety concerns, or immediate danger, advise contacting local emergency services or qualified local support.

Example Prompts#

• "My upstairs neighbor is loud every night. Help me make a calm noise log."
• "I need a neutral message to property management with examples."
• "Turn these notes into a timestamped apartment noise evidence sheet."
• "Help me document bass noise without sounding angry."