Commercial Property Record Retention Policy: A Practical File-Keeping Framework for Landlords

An organized commercial property records workspace with layered folders, document sleeves, maintenance tags, and a PigJet pig-plane carrying a file.

The file system usually looks acceptable until a real question arrives.

A tenant challenges a CAM charge. An insurer asks for a prior inspection. A vendor says a repair was approved. A lender wants the lease package. A manager leaves, and the next person needs to know why a notice was sent three years ago.

At that point, the problem is rarely that the landlord has *no* documents. The problem is that the controlling lease clause, invoice, photo, certificate, email, and follow-up note live in different places—and nobody can confidently say which version governs.

A commercial property record retention policy gives the team a repeatable answer. It tells people what belongs in the property file, how records are named and linked, who owns the file, when it is reviewed, and when destruction can even be considered.

This is an operating framework, not legal, tax, or accounting advice. Retention duties vary by jurisdiction, entity, contract, insurance policy, financing documents, and the facts behind a claim or dispute. Confirm your actual requirements with qualified legal, tax, insurance, and accounting advisors before setting or destroying records.

Start With Retrieval, Not a Number of Years

It is tempting to begin a policy with one retention period for every document. That is usually where weak policies start.

Different records exist for different reasons. A signed lease may control an obligation years after an invoice is paid. A property-improvement record can support a later basis calculation. A certificate of insurance may answer a current compliance question, while an incident file may need to remain intact while a matter is unresolved.

The Internal Revenue Service makes the same basic distinction: recordkeeping periods depend on the action, expense, or event a document records. It specifically notes that property-related records are generally kept until the applicable period ends for the year the property is disposed of.[^1]

So begin with a practical question: If someone asks us to explain a decision, charge, condition, or obligation later, can we find the source record quickly?

Your policy should make that answer easier across six operating categories:

1. lease and tenant records 2. accounting and property-cost records 3. insurance and risk records 4. vendor and contract records 5. maintenance and capital-project records 6. incident, notice, and dispute records

Build One Property Record Structure

Start with a consistent property-level structure. The exact software matters less than the structure and the habits behind it.

At a minimum, every property should have controlled locations for:

This does not mean every file should be copied into every folder. It means the team has one dependable place for the source record and clear links or references when the same document matters to another workflow.

> A useful property file answers two questions: what happened, and what supports that answer?

Set Retention Categories Around Operating Risk

Rather than publishing a universal schedule, classify records by why they may be needed. Your final schedule should be confirmed for your jurisdiction and portfolio, but these categories help organize that conversation.

1. Keep controlling lease documents as a complete history

For each tenant, retain the executed lease and every document that changes or explains it: amendments, renewals, option exercises, assignments, guaranties, consents, estoppels, commencement materials, defaults, and formal notices.

Do not rely on a file named “current lease” without preserving the change history. An amendment may alter rent, square footage, renewal rights, insurance obligations, CAM caps, or notice addresses. The original lease is still part of the story.

Maintain an active lease package that points to the current rent schedule and a current abstract. For a practical setup, see NNN lease document management for landlords.

2. Preserve accounting support with the transaction story

Accounting records are more useful when a reviewer can move from the ledger entry to the supporting record without a scavenger hunt.

For material property expenses, retain the invoice, approval, payment support, allocation method, and any tenant-facing backup together or with clear cross-references. For CAM work, save the budget, actual expense support, pro rata calculations, lease clauses, exclusions, caps, gross-up support when applicable, reconciliation package, and the correspondence that followed.

That level of organization is especially important when a charge is questioned months after the books close. A CAM reconciliation backup package should make the calculation understandable without requiring someone to reconstruct it from email.

3. Treat property and improvement records differently from routine bills

Routine operating bills and records tied to the property’s acquisition, disposition, depreciation, or significant improvements do not necessarily belong in the same bucket.

Keep a durable property-history file for closing materials, capital projects, warranties, major repairs, plans, permits, and before-and-after documentation. These files can matter long after the work is complete—for future repair decisions, warranty claims, diligence, financing, insurance, or property disposition.

The IRS says the retention period depends on what a record documents and directs businesses to keep property records until the relevant period has run after disposition.[^1] That is a reason to involve your tax advisor before applying a routine destruction date to property-history records.

4. Keep insurance records connected to the obligation and event

Insurance files should not be a yearly pile of certificates. Store the policy, endorsements, declarations, COIs, compliance notices, inspection reports, claim materials, and any correspondence about coverage or a loss in a way that shows their relationship.

For tenant COIs, record the required coverage, carrier, limits, additional-insured language when required, effective dates, expiration date, and any deficiency follow-up. The file should show both what the lease required and what the tenant supplied. A recurring insurance renewal checklist helps make those reviews consistent.

Do not destroy records that relate to an open claim, a known loss, a demand, an insurer request, or a potential dispute simply because a routine retention date has arrived. Escalate those files for advisor review first.

5. Make vendor files prove the work, not just the payment

A vendor invoice alone may not explain what was authorized, where work occurred, or whether it was completed.

For meaningful work, keep the agreement or proposal, scope, approval, work order, service report, photos when useful, invoice, warranty, and completion confirmation. Use a consistent naming convention so the team can search by property, vendor, work type, location, and date.

For example:

That sequence makes a future review faster than searching “Roof invoice final FINAL.pdf.”

6. Separate incident records from ordinary maintenance requests

An incident file needs more discipline than a normal repair ticket. Preserve the initial report, dated photos or video, witness or tenant communications, vendor findings, notices, claim information, and resolution steps. Limit access to the people who need it, especially when the file includes personal, medical, security, or sensitive information.

If your operation is subject to OSHA injury and illness recordkeeping, OSHA generally requires covered employers to retain specified OSHA records for five years following the end of the calendar year covered; other rules can impose longer periods.[^2] That is only one example of why incident records should be reviewed against the requirements that actually apply to your organization.

Give Every Record an Owner and a Trigger

A retention policy fails when it says “save records” but nobody is responsible for saving them.

Assign an owner for each workflow: leasing, accounting, insurance, vendor management, maintenance, and incident response. Then identify the trigger that creates the record and the point at which the file is reviewed.

Examples:

This keeps the policy tied to actual operating work instead of an annual filing project nobody has time to finish.

Use a Simple Destruction Hold Rule

Every policy needs a stop sign: do not destroy a record that may be needed for a pending or reasonably anticipated claim, dispute, audit, investigation, financing request, sale, or advisor review.

The person responsible for routine destruction should not have to decide that alone. Require documented approval from the appropriate internal owner and, where needed, qualified advisors. Keep a destruction log that identifies what was destroyed, when, under which schedule, and by whose authorization.

Run a Quarterly File-Health Check

You do not need to audit every document every quarter. Sample the files that most often become urgent:

If the answer is no, improve the workflow that created the gap. A better folder name alone will not solve a missing approval, unlogged notice, or invoice that was never tied to the work performed.

Make the File Useful Before You Need It

Good record retention is not about holding every document forever. It is about keeping the right evidence usable for the life of the obligation, the asset, the claim, or the operating decision it supports.

For commercial landlords, that means organizing records around the work that creates risk: lease changes, tenant billing, insurance compliance, vendor performance, property condition, and incidents.

If your team is still rebuilding that history from shared drives, inboxes, QuickBooks attachments, and individual memory, see how PigJet handles NNN lease management.

[^1]: Internal Revenue Service, How long should I keep records?. [^2]: Occupational Safety and Health Administration, Recordkeeping—Detailed Guidance.