Short answer: A tenant interruption evidence packet should show what the building was like before the event, what happened, what tenant function was affected, what actions were taken, and when function returned. It should be useful to owners, brokers, claims teams, lenders, and asset managers without mixing physical facts with legal or coverage conclusions.
The packet is a timeline and evidence file.
Pre-Event Records
The best packet starts before the event:
- roof RUL and inspection date;
- roof, drain, scupper, gutter, and downspout photos;
- drainage maintenance records;
- prior leak log and closeouts;
- tenant-critical-space map;
- utility room and equipment map;
- emergency vendor list;
- deductible or retention summary;
- lender reporting requirements;
- business-continuity contacts.
Pre-event evidence reduces arguments about prior condition and preparedness.
Event Timeline
The event timeline should be factual:
| Timeline field | Example |
|---|---|
| First notice | who reported the issue and when |
| Weather or site condition | rain, wind, flood, access, outage, or other observed condition |
| Location | roof section, suite, room, utility, access point |
| Immediate action | shutoff, temporary protection, water extraction, tenant notice |
| Vendors called | time, response, scope |
| Photos taken | before mitigation, during work, after stabilization |
| Tenant function | what was impaired and for how long |
| Recovery milestone | when space, system, or access returned |
The timeline should avoid speculation. If causation is unknown, say it is unknown.
Tenant Function Evidence
A tenant interruption packet should explain the affected function:
- suite or area affected;
- percent of space impaired;
- equipment affected;
- customer, patient, resident, or employee access affected;
- inventory or contents affected;
- utility dependency;
- temporary relocation or workaround;
- reopening or return-to-function date.
This separates physical damage from operational consequence.
Cost Evidence
Cost records should be organized by category:
| Category | Evidence |
|---|---|
| Emergency response | vendor invoices, work orders, photos |
| Cleanup | extraction, drying, sanitation, disposal |
| Temporary operations | equipment, relocation, security, access control |
| Repair | scopes, estimates, invoices, approvals |
| Tenant coordination | communications and agreed actions |
| Retained loss | deductible, retention, owner-funded first response |
| Management time | internal response log if tracked |
Do not combine categories into one vague “storm cost” number.
Claims Boundary
Claims teams need facts. Policy interpretation, coverage, causation, exclusions, and valuation require the right professionals and the actual policy. A physical evidence packet should not pretend to decide those issues.
Its job is to preserve:
- condition;
- timeline;
- damage observations;
- mitigation;
- tenant impact;
- recovery steps;
- open questions.
Lending Boundary
Lenders may use the packet to understand reserves, NOI impact, borrower liquidity, covenant notices, collateral condition, and repair timing. The packet should show whether interruption was brief, contained, escalating, or unresolved.
For private credit, the retained-loss and recovery-timing sections are especially important. A small physical event can become a credit issue if liquidity is thin and tenant consequence is high.
El Nino And Climate Context
NOAA and WMO support El Nino preparedness in 2026. EPA supports heavier precipitation and runoff context. Those sources justify building evidence packets before event pressure. They do not establish that a specific water event was caused by El Nino.
Keep the source boundary clear.
The Bottom Line
A tenant interruption evidence packet is strongest when it is prepared before the event and updated during recovery. It should show condition, timeline, tenant function, mitigation, cost categories, retained loss, and recovery milestones in a way that multiple stakeholders can use.
Read next: water event documentation timeline, tenant interruption calculator, and claims causation and prior condition.
Sources and Scope
Source lanes include Ready.gov Business Continuity Planning, FEMA Hazus Flood Model Technical Manual, FEMA P-348 Protecting Building Utility Systems from Flood Damage, NOAA CPC ENSO Diagnostic Discussion, and WMO El Nino/La Nina Update May 2026. This article is not insurance, claim, legal, accounting, tax, engineering, credit, or investment advice.