Published October 27, 2026.
Renewal files accumulate offers, notices, delivery receipts, signature certificates, and correspondence. The question of how long to keep them usually arrives in two forms: a former resident asks for a document, or an auditor asks why a file was destroyed. A retention schedule answers both, but only if it is specific about the record type and the source of the rule.
Four record categories
The first category is the lease itself and its amendments. Retention here is often tied to the tenancy and to the statute of limitations for contract claims, which varies by state. The signed lease, the addenda, and the final renewal terms belong together.
The second category is the renewal offer and the resident's response. These records show what was offered and what was accepted. Keep the offer version, the response, and the expiration date.
The third category is delivery evidence: postmark, carrier scan, portal confirmation, or in-person acknowledgment. This is the record that proves notice was served. It should stay with the notice version it supports.
The fourth category is program records. Voucher files, tax credit certifications, and other assisted-housing files can have retention requirements set by the program or the funding agreement, which may be longer than the general business schedule.
Why one period does not fit all
A single retention period applied to every document produces two failures. It destroys delivery evidence too early, or it keeps routine correspondence longer than necessary. The schedule should be built by record type, with the source of the period recorded next to it.
Where a program requirement and a state requirement differ, the longer period usually governs the file, but that decision belongs to the property's compliance or legal reviewer. The coordinator's job is to make the conflict visible.
Keeping delivery evidence usable
Delivery evidence is only useful if it can be matched to the document it proves. Name the file with the unit, the notice type, and the date. Store the evidence in the same folder as the notice, or link to it from the notice record.
A folder of unlabeled carrier receipts is not a retention system. It is a pile that happens to be old.
Destroying records deliberately
Destruction should be a scheduled, documented action, not a cleanup when storage fills up. Record what was destroyed, the date, the schedule authority, and the person who approved it. Apply a hold when a dispute, a complaint, or a legal matter is open, and record the hold.
If the property uses a vendor for storage or destruction, keep the vendor's certificate with the destruction log.
Access requests during the retention period
A former resident may request a copy of a lease or a notice. The response should come from the retained file, not from a reconstruction. That is one reason to keep the executed version and the delivery evidence rather than only a summary in the property system.
Route requests that involve protected information through the property's privacy process rather than emailing documents from a personal account.
A workable schedule format
For each record type, list the retention period, the trigger that starts the period, the source, the storage location, and the destruction method. The trigger matters as much as the period: a lease retained for seven years after expiration is different from one retained for seven years after the last amendment.
Review the schedule annually and when a property changes program status. Record the review even when nothing changes.
Limits
This review describes the categories and the method. It does not state a retention period for any jurisdiction or program. Those periods come from statutes, regulations, and funding agreements, and they change.
The sources cited are public references for orientation. A property with a specific question should consult its compliance reviewer or counsel.