A good attachment can
- Give a landlord or caseworker one readable incident summary
- Keep a date, duration, notes, and reference metrics together
- Link a later follow-up to the right event
- Make limitations visible instead of hiding them
Illustrative sample · not a real incident
The report turns one selected incident into a readable summary. It preserves context; it does not certify a measurement, identify a source, submit a complaint, or determine a legal violation.
Download the illustrative PDFThe illustration and downloadable file use invented demo values. Actual fields and layout can vary by incident and app version.
Field guide
A clear report separates what the phone recorded, what the user observed, and what remains unknown.
The incident’s start, end, and duration
Optional location context plus the room and conditions you note
A neutral description of what you observed
Selected weighting, average/maximum reference values, and measurement context
Whether local audio or other supporting media exists
Input-route, overload, integrity, and non-certification notices where relevant
A SHA-256 digest covering selected report data; not a legal certification
A good attachment can
It does not