Records You Should Keep Before a Business Interruption Event Occurs
Key Takeaways
- Business interruption insurers calculate your payout based on lost net income — without records, that number is unprovable.
- Most BI claims disputes center on documentation gaps, not coverage disputes.
- Financial records should be updated and backed up off-site or in the cloud at least monthly.
- Your insurer will scrutinize 12–24 months of pre-loss financials to establish a baseline revenue figure.
- Payroll records, vendor contracts, and fixed expense logs are just as critical as income statements.
- A records management protocol in place before a loss dramatically shortens the claims timeline.
Summary
28 items · 45–90 minutes to audit and organize
Why Pre-Loss Records Are the Foundation of Every BI Claim
Business interruption insurance exists to replace income your business would have earned had a covered event never happened. That sentence sounds straightforward until you're sitting across from an adjuster who is asking you to prove — with verifiable financial data — exactly what your business would have earned. That hypothetical number is the heart of every BI claim, and your pre-loss records are the only evidence that can support it.
Insurers don't guess at your lost revenue. They reconstruct it from the financial paper trail you've maintained. If that trail is thin, contradictory, or simply missing, your payout will be reduced — or disputed entirely. Claims get denied far more often over documentation failures than over genuine coverage disputes. That's a correctable problem, and this checklist is how you correct it.
The goal isn't to have a filing cabinet full of paper. The goal is to have organized, current, and accessible records that let an adjuster — or a forensic accountant hired by your insurer — reconstruct your pre-loss financial picture with confidence. Every item on this list serves that specific purpose.
Note that while this checklist focuses on financial and operational records for BI purposes, your physical asset documentation belongs in a parallel file. See our guide to documenting commercial property before a loss for that companion process.
Tools and Systems You'll Need
Before working through the checklist below, confirm you have the right infrastructure in place to store, update, and access these records when it matters most — which may be immediately after a fire, flood, or other event that disrupts your physical operations.
Cloud Accounting Software (e.g., QuickBooks Online, Xero)
Generates and stores monthly P&L statements, expense reports, and balance sheets in a format adjusters and forensic accountants can readily interpret.
Secure Cloud Storage (e.g., Google Drive, Microsoft SharePoint, Dropbox Business)
Provides off-site, access-controlled storage for financial documents, contracts, and policy records that must survive a physical loss event.
Payroll Platform (e.g., ADP, Gusto, Paychex)
Archives detailed payroll records by pay period, including tax filings and benefits costs, in a format that supports BI wage loss calculations.
Document Management System (e.g., DocuWare, M-Files)
Organizes contracts, vendor agreements, and lease documents with version control and audit trails, making retrieval straightforward during a claim.
Password Manager (e.g., 1Password, Bitwarden Teams)
Stores access credentials for all record systems so authorized personnel can retrieve documents immediately without dependency on a single individual.
Forensic or CPA Accountant (on retainer or identified in advance)
Provides expert support in organizing pre-loss records and, after an event, in calculating and presenting your income loss claim to the insurer.
Cloud backup is non-negotiable. A records system that lives only on an on-site server is a records system that may be destroyed in the same event that triggers your BI claim. Redundancy isn't optional here.
The Complete Pre-Loss Records Checklist
Work through each group below. For every item, your standard should be: If my office were inaccessible tomorrow, could my accountant reconstruct this data from off-site records? If the answer is no, that item needs immediate attention.
Revenue and Income Records
Expense and Overhead Records
Payroll and Workforce Records
Insurance Policy Records
Operational and Continuity Records
Digital and Physical Record Storage
Don't Rely on Annual Tax Returns Alone
Many business owners assume their annual tax returns are sufficient evidence of income. They are not — at least not by themselves. Tax returns reflect annual aggregates and are often prepared months after the fiscal year ends. Adjusters need monthly granularity to account for seasonality, and they will look for consistency between your tax returns and your bank statements. Discrepancies between these sources are red flags that slow — or kill — a claim.
Undocumented Cash Transactions Are a Liability
If any portion of your revenue is received in cash and not fully reflected in your bank deposits and tax filings, you cannot claim that income in a BI loss. Insurers base payouts on verifiable records. Income that wasn't properly reported cannot be reconstructed. This is a hard boundary, and it's one reason businesses with informal cash handling practices consistently receive lower BI payouts than their actual losses.
Growth Projections Must Be Supported by Evidence
Claiming that your business was about to experience significant growth requires documentation prepared before the loss — not after. Signed contracts, executed letters of intent, and formal projections prepared by your accountant carry weight. Verbal agreements and retroactive estimates do not. If your business was genuinely on a growth trajectory, document it now.
Once you've completed your audit, compare your coverage limits against the revenue picture your records reveal. If your business has grown significantly since you last reviewed your policy, your current BI limit may be inadequate. The annual BI policy review checklist walks you through that assessment systematically.
How Insurers Actually Use These Records
Understanding how an adjuster or forensic accountant applies your records removes any temptation to treat this checklist as a bureaucratic exercise. Here's the mechanics:
Establishing the Revenue Baseline
The adjuster will typically look at 12 to 24 months of pre-loss revenue — monthly, not annual — to identify seasonal patterns. A restaurant that does 40% of its annual revenue in the summer and experiences a fire in June faces a very different calculation than one hit in February. Monthly P&L statements and bank statements, not annual tax returns alone, are what make this calculation accurate in your favor.
Separating Fixed from Variable Expenses
BI coverage typically pays for net income plus continuing fixed expenses — rent, loan payments, and minimum payroll you must maintain even with no revenue. Adjusters will parse your expense records to identify what stopped (variable costs like cost of goods) versus what continued (fixed overhead). Without a clean expense ledger with consistent categorization, this distinction becomes a negotiation rather than a calculation.
Projecting Forward
If your business was on a growth trajectory — a signed lease for a second location, a new contract with a major client — your records need to substantiate that trajectory. Signed contracts, executed letters of intent, and formal sales projections prepared before the loss carry evidentiary weight. Verbal agreements and after-the-fact estimates do not.
For a broader view of how to prepare your operations — not just your records — for a BI event, the complete BI claim preparation guide covers continuity planning, vendor communication, and the claim submission process itself.
Your BI Limit May Already Be Inadequate
Business interruption coverage limits are typically set at policy inception and don't automatically adjust as your revenue grows. If your business has grown meaningfully since you last reviewed your policy, your current BI limit may cap your payout well below your actual loss. Review your limit annually against your trailing 12-month gross revenue and — critically — against the restoration period your policy provides. A 12-month restoration period combined with an outdated revenue figure is a double exposure that most business owners don't discover until it's too late.
The Waiting Period Starts on the Day of the Loss
Most BI policies include a waiting period — commonly 48 to 72 hours — before coverage activates. This period is not negotiable after a loss, but it can be modified at policy inception. Review your waiting period now and confirm it's appropriate for how quickly your business would feel the revenue impact of a shutdown. A manufacturer with just-in-time inventory and a 72-hour waiting period may absorb the first three days of losses without any recovery.
Maintaining and Updating Your Records Over Time
A records audit you complete once and never revisit is only marginally better than no audit at all. Your business changes — revenue grows, expenses shift, employees are hired and let go, contracts are signed and fulfilled. Your records infrastructure needs to reflect the business as it exists now, not as it existed 18 months ago when you last thought about this.
Recommended Update Cadence
- Monthly: Back up financial statements, bank reconciliations, and payroll records to cloud storage.
- Quarterly: Update your fixed-expense schedule and review your vendor contracts file for any new or expired agreements.
- Annually: Conduct a full records audit against this checklist. Simultaneously review your BI coverage limits against your current revenue — your policy limit should reflect what your business earns today, not what it earned when you first bought the policy.
Building these updates into your existing accounting or operations calendar is the most reliable approach. Assign ownership to a specific person — an office manager, bookkeeper, or controller — rather than leaving it as a general responsibility.
Finally, make sure at least two people in your organization know where these records are stored and how to access them. A meticulously organized cloud drive that only the CFO can access creates a single point of failure at exactly the wrong moment.
All claims in this article are backed by peer-reviewed research. We follow strict editorial guidelines to ensure accuracy and reliability. Sources available on request from our editorial team.
