Share
Tenant File Checklist for Landlords: What to Keep Together
A tenant file should tell the story of one tenancy from signed agreement to final move-out records. It is not the same as the general property file. The property file stores information that remains with the building—insurance, utilities, vendors, maintenance history, assets, and property documents. The tenant file stores documents tied to a specific leaseholder or tenancy.
Because tenant files can contain personal information, access should be more restricted than general maintenance or vendor records. Collect and retain only what is needed for legitimate management, legal, tax, insurance, or business purposes.
Quick tenant file checklist
- Signed lease and amendments
- Required disclosures and acknowledgements
- Tenant information sheet
- Emergency contact record
- Move-in condition report and photos
- Key and access handover record
- Important communication log entries
- Maintenance requests linked to the property history
- Renewal or extension documents
- Notices and delivery records where applicable
- Move-out condition records
- Deposit or final accounting documents where applicable
1. Start the file with the signed tenancy documents
Keep the fully executed lease and any addenda or amendments together. Drafts should be clearly separated from signed documents so there is no confusion about which version controls. If a renewal later changes dates or terms, preserve the original agreement and add the renewal rather than overwriting history.
The Lease Summary Sheet can provide a quick internal reference, but the signed agreement remains the source of truth.
2. Store required disclosures with proof of delivery
Federal, state, or local rules may require disclosures or informational documents. Keep the version provided to the tenant and any acknowledgement or delivery evidence your process requires. Do not assume the same disclosure package applies in every location.
Fair-housing rules also matter throughout tenant administration. HUD’s Fair Housing Act overview is a federal baseline, with additional state or local protections possible.
3. Keep current contact details separate from screening data
Once the tenancy begins, you need current phone, email, approved occupants, emergency-contact reference, and other operational details. Use the Tenant Information Sheet for current data rather than repeatedly opening an old application.
Screening materials can contain more sensitive information than routine tenancy administration needs. Limit access and retention according to legitimate business need and applicable law.
4. Add the move-in condition record
Keep the signed or acknowledged move-in inspection, schedule of condition, dated photos, and any pre-existing damage notes together. This becomes the baseline for later maintenance and move-out comparison.
Use the Move-In Inspection Checklist for the detailed condition workflow.
5. Keep access handover with the tenancy
The tenant file should show what keys, fobs, remotes, parking credentials, or tenant-specific digital access were issued at move-in. The ongoing master access history can remain in the property-side access log.
The Key Handover Checklist handles the specific event; the Key & Access Control Log tracks ongoing property access.
6. Use the communication log as an index
Important tenant communications should be retrievable, especially those tied to maintenance, access, notices, lease changes, complaints, or agreed actions. Do not print every text message and fill the file with noise. Use the Tenant Communication Log to summarize significant interactions and point to the original evidence.
7. Link maintenance requests to the property history
A tenant file can contain the request and communication trail, but the completed repair belongs in the property’s long-term maintenance history too. This prevents useful repair information from disappearing when the tenant file is archived.
For example, the tenant file may show when a leaking faucet was reported and access was scheduled; the property maintenance log should show what was repaired, by whom, and when.
8. Add renewal or extension documents chronologically
Keep every signed renewal, extension, amendment, and related communication in date order. Update the lease summary and expiration tracker after the renewal is complete.
The Lease Renewal Checklist manages the workflow before a new term is signed.
9. Close the file with move-out documentation
At tenancy end, add the move-out condition report, photos, key-return record, forwarding contact when lawfully obtained, required notices, and final financial or deposit documents. Then mark the file closed and move it to an archive according to your retention policy.
The Move-Out Process Checklist provides the broader end-of-tenancy workflow.
10. Protect tenant personal information
The FTC advises businesses to know what personal information they hold, keep only what they need, limit access, protect stored records, and securely dispose of information that is no longer required. Apply those principles to both paper and digital tenant files.
Do not leave tenant files in a shared vendor binder, unlocked vehicle, public cloud folder, or other location accessible to people without a legitimate need.
Use a simple active-file index
At the front of the tenant file, keep a one-page index showing the current lease, latest contact sheet, current emergency contact, move-in condition record, key handover, open maintenance issues, renewal status, and any unresolved documentation. The index should point to documents rather than duplicate them.
How this fits into the property file system
The tenant file is a restricted subfile inside the broader Rental Property File System. Permanent property history should survive tenant turnover, while tenancy-specific personal records can be archived separately.
The Property Management Binder can organize the property-side inspection, maintenance, inventory, emergency, and operating records that support the tenancy without exposing sensitive tenant data unnecessarily.
Keep formal notices distinct from routine communication
A communication log can show that a notice exists, but formal notices may have specific content, timing, and delivery rules. Store the actual notice and any proof of service or delivery in a dedicated subsection so an ordinary email thread is not mistaken for the controlling document.
Close and archive the file deliberately
When the tenancy ends, mark the file closed only after move-out records, access return, final communications, and required financial documents are complete. Record the archive date and retention category so old files are not kept indefinitely simply because no one knows when they can be reviewed or disposed of.
What should not be in a routine tenant file?
- Passwords or master access codes
- Full payment-card or bank login information
- Medical details not needed for a lawful process
- Subjective comments about personality or protected characteristics
- Unverified allegations written as established facts
- Duplicate copies of sensitive screening data with no ongoing need
A practical tenant-file order
Use a chronological front section for active tenancy documents and separate subsections for lease, move-in, contact and communication, access, maintenance requests, renewal, and move-out. A one-page index at the front can list the latest lease, current contact sheet, access record, and open issues.
FAQ
Should each tenancy have a separate file?
Yes. Separate files make leases, communications, access, renewals, and move-out history easier to understand and archive.
Should maintenance be stored in the tenant file or property file?
Store the tenant request and communication in the tenant file, and preserve the completed repair history in the property maintenance record.
Should old applications stay forever?
No single retention rule applies to every document. Keep records according to applicable law, legitimate business need, and your documented retention policy.
Can contractors access the tenant file?
Only information they legitimately need should be shared. Sensitive tenancy records should remain restricted.