Real estate investor guide
Rental Property Tenant Damage and Chargeback Records: Evidence Checklist
Build fact-focused tenant-incident packets that stand on their own. This guide shows how to link an incident to the right unit and tenancy, reference the pre-incident condition without deciding responsibility, preserve dated observations and original media, store vendor estimates and invoices, index communications, and tie in ledger references. Use this to hand off clear, neutral records to a qualified reviewer.
Build a neutral incident record linking baseline condition, dated media, vendor support, factual messages, and ledger references. Preserve gaps and deliver a secure reviewer handoff.
Answer first
When something is damaged or out of expected condition, freeze the facts. Give the incident a unique ID linked to the exact unit and tenancy. Locate the move-in or earlier baseline materials, and bookmark them without drawing conclusions. Capture dated notes, photos, and video; keep original files unchanged. Collect vendor estimates, final invoices, and any payment confirmations. Index emails or messages that describe the facts or acknowledge observations. Add references (not calculations) for any charge or recovery entries in your accounting system. Flag open questions and unresolved items. Store everything in a structured folder with a brief index that ties each item to its source and date. Limit access to people who need to review it, and prepare a concise cover sheet so a qualified tax or legal professional can quickly understand what exists, where it came from, and what remains uncertain. This guide does not determine responsibility or tax treatment.
01Define a neutral incident evidence packet
An incident evidence packet is a focused bundle that captures what happened, when, and how it was documented—without deciding fault, normal wear, or financial outcome. Treat it as a factual snapshot that connects the event to the right place and time, preserves original material, and enables a qualified reviewer to evaluate next steps. The packet should be complete enough that someone who was not present can follow the trail from baseline condition to observations, vendor scopes, communications, and accounting references. Keep tone and contents neutral: observe, date-stamp, cross-reference, and flag open issues.
Checklist
– Create a unique incident ID and title (e.g., brief description and date).
– Write a two-sentence neutral summary (who observed, what was seen, when).
– Add links to the property, unit, tenancy, and lease references.
– Attach baseline condition references (move-in inspection, prior photos).
– Store dated observations, photos, and video in original form.
– Include vendor estimate(s), final invoice(s), and payment proofs, if any.
– Index communications that state facts or acknowledge observations.
– Add accounting ledger references for any charges or recoveries.
– Maintain a one-page index listing each item’s filename, date, and source.
– Note unresolved questions and where further evidence may be found.
02Link the incident to property unit and tenancy identifiers
A clear link prevents mix-ups when properties, roommates, or overlapping tenancies exist. Record the exact property and unit, match the incident window to the tenancy dates on the lease, and reference the accounting ledger that would reflect any charge or recovery entry. Use consistent internal IDs so later exports from your accounting system or document repository match the packet’s identifiers. Avoid over-collecting sensitive data; identify the tenancy confidently using neutral facts that appear on the lease and rent ledger without attaching superfluous personal details.
Checklist
– Property legal name and street address.
– Unit number or unique unit identifier.
– Internal property and unit IDs (if used).
– Lease identifier, tenancy start and end dates, and named occupants as on the lease.
– Rent ledger account or subaccount reference.
– Incident ID, creation date, and preparer’s name or initials.
– Cross-reference key: Incident ID ↔ Lease ID ↔ Unit ID ↔ Ledger ID.
– Map of where records live (folder path or repository link).
– Note if any identifiers are missing or inconsistent; flag for review.
03Record dated observations and original media
Capture what was observed, when, and by whom. Use clear, time-stamped notes that describe location, surface/material, apparent condition, and any immediate safety or containment steps taken. Photos and video are strongest when they are well-lit, include context and close-ups, and retain original metadata. Do not alter originals. If redaction is needed for sharing, create a labeled derivative copy. Consider logging who handled the files and when they were moved to storage to preserve an orderly chain of custody.
Checklist
– Observation log: date, time, observer’s name, exact location, and neutral description.
– Still photos: context shot(s), mid-range, and close-ups; include a measuring reference when helpful.
– Video: slow pan and detail clips; capture sound only if it adds factual context.
– Preserve original files with device-generated names and metadata; avoid editing.
– Record file properties: capture date/time, device, and any embedded location data.
– Optional: compute and store file checksums for originals.
– Store originals in a read-only folder; keep a working copy folder for annotations.
– Witness or vendor on-site notes limited to factual statements; include name and date.
– Note environmental conditions if relevant (e.g., wet floor, odor); keep neutral tone.
04Index communications and factual acknowledgments
Save communications that document facts: notice received, access granted, observation confirmed, or completion reported. Email threads, letters, and documented messages can show chronology and acknowledgment without weighing in on legal responsibility. Keep content organized by date and source; capture delivery receipts or read confirmations if they exist. Avoid retaining unnecessary sensitive information. If you store consumer report information elsewhere (e.g., application background materials), keep it out of the incident packet unless directly factual and necessary; handle such information with care consistent with applicable guidance.
Checklist
– Chronological log of relevant messages: date/time, sender, recipients, channel, and neutral summary.
– Copies of emails, letters, or messages that describe observations, access times, or completion notes.
– Delivery or read receipts when available.
– Photos or files attached to messages; save originals as separate items.
– Meeting or call notes: date, participants, and factual outcomes (avoid opinions).
– Consolidated timeline that references observation logs, vendor visits, and document dates.
– Note if any statements appear inconsistent; flag for review rather than conclude.
– Store sensitive data separately as appropriate; avoid duplicating personal information.
05Build the qualified-review handoff
A strong handoff helps a tax professional or attorney efficiently evaluate facts without sifting through unorganized files. Provide a short cover sheet, an index that cross-references each item, and read-only access to originals. Summarize what is in the packet, where it came from, and what is unknown. Keep conclusions out; pose questions. Include a high-level timeline and a quick locator for baseline materials, observations, vendor documents, communications, and ledger references.
Checklist
– Cover sheet: incident ID, property/unit, tenancy reference, two-sentence neutral summary.
– Timeline: key dates for observation, vendor estimate, invoice, communications, and any ledger entries.
– Contents index: file names, dates, sources, and brief descriptions.
– Baseline references: where to find move-in/prior condition materials.
– Observation media map: count of photos/videos, with folder paths.
– Vendor documents list: estimates, invoices, payments, and versions.
– Communications digest: factual acknowledgments and delivery receipts.
– Ledger locator: transaction IDs, dates, memos; note related entries.
– Open questions list and missing items.
– Access instructions and point of contact for follow-up questions.
Federal resources
Official sources
Use these public sources alongside qualified review when facts, timing, and records determine the result.
When the facts are more complex
Bring an organized set of facts to the next conversation.
A qualified review can begin with the records, questions, and transaction details already gathered.
Common questions
Frequently asked questions
What is the minimum incident record packet?
A minimal packet should let a reviewer see what changed, when, and how it was documented. At minimum: an incident ID and neutral summary; links to the specific property, unit, and tenancy; one or more baseline references; dated observation notes; original photos or video; a vendor estimate or invoice if obtained; a brief communications log; and ledger entry references (if any). Add an index so each item can be found quickly.
How should I reference prior move-in condition evidence?
Point to dated, original materials that show the same area or fixture before the incident. Examples include a signed move-in inspection checklist, prior inspection photos, or earlier maintenance records. Keep them unchanged and note their dates and sources. If you used a structured inspection form, store a clean copy and any acknowledgments. Do not infer responsibility in this section—just establish what “before” looked like.
What’s the best way to handle photos, videos, and original files?
Capture clear, well-lit images with context and close-ups. Preserve originals with their metadata intact; avoid editing. If you need to annotate or redact for sharing, create labeled copies and keep originals read-only. Record who took the media, when, and where it’s stored. Consider saving file checksums and keeping a backup. Store device-generated timestamps and any embedded location data as part of your record.
How do I manage multiple incidents during one tenancy?
Create a separate incident ID and folder for each event. Link all incidents to the same property, unit, and lease identifiers, and keep a master index that lists each incident with a short description and date. Avoid mixing photos or vendor documents across incidents; if a file applies to more than one, store it once and reference it from each packet. Maintain distinct timelines and ledger references.
What’s the difference between estimate and final invoice evidence?
An estimate reflects a proposed scope and anticipated costs at a point in time. A final invoice documents work performed, materials used, and amounts billed. Keep both when available, because they show the evolution from plan to completion. Store them as received, with dates and document numbers. If revisions or change orders occur, keep all versions in order and explain the sequence in your index.
How do I reference a charge in the ledger without making conclusions?
Record where the entry lives, not whether it’s correct. Capture the accounting system’s transaction date, internal ID, account name or code, and memo text. Include a screenshot or export of just the relevant entry if helpful. Link the entry to the incident ID in your index. If there are reversals, credits, or third-party recoveries, list their dates and IDs too. Leave calculations and determinations to a qualified reviewer.
How should communications and chronology be documented?
Maintain a simple timeline: who said what, when, and through which channel. Save emails, letters, or messages that state observable facts, access arrangements, or completion confirmations. Include delivery receipts or read confirmations if available. Keep call notes brief and factual. Avoid storing unnecessary sensitive details. Cross-reference each entry to supporting media, vendor documents, or ledger references so a reviewer can move from words to evidence.
What if baseline documents are missing?
Note the gap clearly in your index. Substitute the closest neutral references you have, such as a prior inspection covering nearby areas, purchase receipts, or earlier maintenance logs. Capture robust current observations with high-quality photos and video to strengthen “after” evidence. If you later locate baseline materials, add them without changing earlier files. Flag the absence and later discovery for a qualified reviewer to weigh.
How should I handle security and access for tenant-related files?
Limit access to individuals who need to review the packet. Use permissioned folders, strong authentication, and, where feasible, encryption. Store originals read-only and share redacted copies externally as needed. Keep consumer report information (like application background materials) separate and handle disposal securely consistent with applicable guidance. Back up your files and maintain a simple access log noting who can view the materials.
When is a qualified legal or tax review needed?
Consider requesting review when facts are disputed, insurance or third-party payments intersect with your books, documents appear inconsistent, large repairs span multiple periods, or you lack baseline evidence. A tax professional can advise how records may support reporting; legal counsel can address rights and responsibilities. This guide organizes evidence and flags questions; it does not decide outcomes or provide legal or tax conclusions.
This guide is educational. The application of tax rules depends on individual facts; verify current IRS guidance and consider a qualified tax professional before acting.