PromptBase
PromptBase SelectGet Select
Close icon
General
Home
Marketplace
Create
Hire
Login
Chat
Sell
Explore

Prompt Details

Model
Chat - (gpt-5.6)
Token size
1,132
Example input
[YOUR_ROLE]: I am the resident in unit 3B reporting recurring noise from the unit above me to the property manager. [INCIDENT_NOTES]: Aug 28, 11:42 p.m.–12:18 a.m.: bass-heavy music and repeated shouting heard in bedroom; 36 minutes; phone audio recorded at 11:51 p.m.; woke me. Aug 31, 12:07–12:44 a.m.: bass and furniture scraping; 37 minutes; two short phone videos; could not return to sleep for about an hour. Sep 3, 10:55–11:20 p.m.: loud music; 25 minutes; no recording; interrupted sleep. Sep 6, 1:14–1:39 a.m.: music and several heavy impacts; 25 minutes; audio at 1:19 a.m.; woke me before an early shift. [COMMUNICATION_HISTORY]: I emailed management on Sep 1 with the Aug 28 and Aug 31 notes and links to the two videos. They replied that they would remind the building about quiet hours. I did not contact the neighbor directly because the hallway interaction I saw on Aug 30 involved intoxicated guests and felt unsafe. Noise continued on Sep 3 and Sep 6. [LEASE_OR_BUILDING_RULES]: House rules: “Quiet hours are 10:00 p.m. to 7:00 a.m. Residents must avoid amplified music or other sound that unreasonably disturbs neighboring units during quiet hours.” [DESIRED_OUTCOME]: I want management to acknowledge the recurring pattern, tell me what documented next step they will take, and ask me for any specific evidence they still need.
Example output
## 1. Situation frame The resident of unit 3B is updating the property manager about recurring late-night sound from the unit above after an earlier building reminder did not resolve it. The desired outcome is a documented management response that states the next step and any further evidence required. ## 2. Incident ledger | ID | Date and time | Duration | Direct observation | Source available | Immediate impact | Confidence | |---|---|---:|---|---|---|---| | I1 | Aug 28, 11:42 p.m.–12:18 a.m. | 36 min | Bass-heavy music and repeated shouting heard in bedroom | Personal observation; phone audio at 11:51 p.m. | Woke resident | Confirmed | | I2 | Aug 31, 12:07–12:44 a.m. | 37 min | Bass and furniture-scraping sounds | Personal observation; two short phone videos | Interrupted sleep; about one hour to return to sleep | Confirmed | | I3 | Sep 3, 10:55–11:20 p.m. | 25 min | Loud music | Personal observation; no recording | Interrupted sleep | Partial | | I4 | Sep 6, 1:14–1:39 a.m. | 25 min | Music and several heavy impacts | Personal observation; phone audio at 1:19 a.m. | Woke resident before an early shift | Confirmed | The recordings are reported as available; their contents have not been independently inspected here. ## 3. Fact-versus-inference audit **Supported facts** - Four dated incidents occurred within ten days, all during supplied quiet hours (I1–I4). - Music was reported in three incidents and bass-heavy music in one; sleep was affected each time (I1–I4). - Recordings are reported for three incidents (I1, I2, I4). - Management received an earlier report and said it would issue a building reminder; two later incidents were recorded after that reply. **Plausible but unverified interpretations** - The unit above is the source. Sound was perceived as coming from above, but building transmission has not been ruled out. - The Sep 3 event was the same source and activity as the recorded events. **Claims made by others** - Management stated that it would remind the building about quiet hours. The prompt does not establish when or how that reminder was delivered. **Contradictions or timeline conflicts** - None in the supplied record. ## 4. Pattern map - **Quiet-hours recurrence:** 4/4 incidents occurred between 10:00 p.m. and 7:00 a.m. (I1–I4). - **Music component:** 4/4 incidents include music or bass (I1–I4). - **Sleep impact:** 4/4 incidents woke the resident or interrupted sleep (I1–I4). - **Continued after first report:** 2/4 incidents occurred after management's Sep 1 response (I3–I4). **Evidence strength: Usable.** Multiple dated incidents share a bounded time window, sound type, and impact, and three have reported source files, supporting a specific request for management process rather than a conclusion about motive or punishment. ## 5. Fair-reading check | Alternative not ruled out | Distinguishing observation | |---|---| | Sound may travel from another unit or common area | Note whether the sound is strongest at a shared wall, ceiling, hallway, or window during the next event | | Some heavy impacts may be separate from the music | Record start and stop times for music and impacts independently rather than grouping them automatically | | A building or mechanical source could contribute to low-frequency bass | Ask management whether similar reports exist and whether building equipment operates during the same window | Property management is the appropriate recipient because there is a repeated record, prior contact did not resolve the issue, and direct contact is described as unsafe. ## 6. Resolution brief - **Observed:** Four quiet-hours incidents in ten days involved music or bass and disrupted sleep; three have reported recordings, and two occurred after management's first response (I1–I4). - **Impact:** The resident was awakened or had sleep interrupted on all four occasions, including before an early shift. - **Request:** Please confirm what documented management step will follow this repeated pattern and identify any additional incident details or file format needed. - **Success check:** Progress is a written reply naming the next step, responsible contact, and evidence needed, followed by no comparable quiet-hours event during a defined observation period. Supplied rule text: “Quiet hours are 10:00 p.m. to 7:00 a.m. Residents must avoid amplified music or other sound that unreasonably disturbs neighboring units during quiet hours.” This brief does not determine whether management will find a violation. ## 7. Ready-to-send message **Subject: Follow-up record of recurring quiet-hours noise** Hello, I am following up on my Sep 1 report because the same late-night pattern continued after the building reminder. I have now logged four incidents between Aug 28 and Sep 6, all during the building's 10:00 p.m.–7:00 a.m. quiet hours. The latest was Sep 6 from 1:14 to 1:39 a.m.; music and heavy impacts woke me before an early shift. I also have time-stamped phone files for three of the four incidents. Could you please confirm the next documented step management will take and tell me whether you need a particular log format or the original files? Because direct contact has felt unsafe, I would like communication to remain through management. Thank you. I can send the incident ledger and source links in the format you prefer. ## 8. Next capture plan 1. **Exact source location:** Note where each sound is strongest. This helps distinguish the unit above from building transmission; record the room and direction in one line during the next incident. 2. **Separate sound timelines:** Track music and impacts independently. This prevents unrelated sounds from being merged; note separate start and stop times. 3. **Management response details:** Preserve the date and exact wording of each reply. This establishes what follow-up was promised; keep the original email thread unchanged. Keep original recordings and messages unchanged; this brief is an organizing layer, not a replacement for source material.
GPT

Apartment Noise Evidence Brief

Add to Cart
PromptBase Select
Get this prompt + 9 more with Select$14 your first month, then $19/mo$14 first month, then $19/mo
View Select
Instant accessInstant access
Usage rightsCommercial use
Money-back guaranteeMoney‑back
By purchasing this prompt, you agree to our terms of service
GPT-5.6
Tested icon
Guide icon
4 examples icon
Free credits icon
Turn scattered noise notes and messages into a calm, decision-ready apartment brief—not an angry complaint letter. Get a dated incident ledger, fact-versus-inference check, recurring-pattern summary, evidence gaps, a proportionate request, and a ready-to-send message for a neighbor or property manager. Works whether you are reporting noise or responding to vague complaints. Built for renters who need clarity and a practical next step without invented facts or legal theater.
...more
Added over 1 month ago
Report
Browse Marketplace