Real estate investor guide
Rental Property Tenant Screening and Lease Records: File Checklist
A practical, evidence-first file index for tenant applications, consents, screening-report custody, signed leases, and addenda. This checklist focuses on factual documentation, version control, and secure storage, so a qualified tax or legal professional can review without guessing how files were created or handled. It emphasizes neutral records, custody notes, and clear cross-references. Guidance reflects conservative handling of consumer reports and general recordkeeping principles.
Index tenant screening and lease files by property, unit, and tenancy. Keep sensitive documents separate, preserve signed versions, record gaps, and prepare a secure, neutral review handoff.
Navigate this guide
- Define a factual tenant and lease file
- Create property, unit, tenancy, and document identity tags
- Separate sensitive screening materials from ordinary tenancy records
- Preserve application and consent artifacts without evaluating them
- Maintain a signed lease and addenda version index
- Use secure storage and access notes for sensitive material
- Handle missing, corrected, or transferred files without reconstructing decisions
- Build a qualified-review handoff index
Answer first
Start by naming the file set with consistent identity tags: property, unit, tenancy, and document. Gather the application and explicit consent authorizations and store any consumer reports separately with restricted access. Index the signed lease and addenda by date and version, and link to move-in, communications, and payments by reference, not duplication. Record how each document was obtained, where it lives, who can access it, and any change history. If something is missing, note the gap and the search steps taken. When a document is corrected or replaced, keep the original, add the new version, and write a short supersession note. If management or ownership changes, keep a dated custody transfer memo. Finish with a concise handoff index summarizing identifiers, inventory counts, storage locations, version notes, sensitive-material flags, and open questions. This structure supports an efficient, qualified review. It does not interpret screening outcomes or determine tax or legal results.
01Define a factual tenant and lease file
Treat the tenant and lease file as a neutral bundle of factual artifacts tied to one tenancy at one unit. It should answer: what documents exist, what each contains at a summary level (title and date only), where they are stored, and how they moved. The file should not evaluate applicants, interpret reports, or restate decisions. It simply inventories and links source materials so a qualified reviewer can trace documents and their custody.
Include only items that describe the tenancy’s paperwork lifecycle: application, consent, consumer report custody notes, signed lease, and signed addenda. Link other records (move-in, communications, payments) by reference so the main file remains a compact index.
Checklist
– State the file’s scope: application, consent, screening-report custody, signed lease, and addenda
– Note the tenancy period covered (start date; end date if applicable)
– List each included document by title, date, and version
– Provide storage location for each item (path, cabinet, or system ID)
– Record access constraints for any item with sensitive information
– Add a short file-level summary: identifiers, counts, and unresolved gaps
– Include a prepared-by line with date, plus contact for questions
02Create property, unit, tenancy, and document identity tags
Reliable identity tags prevent misfiles and streamline review. Use stable, unique tags that travel with every document and cross-reference. A property tag can mirror the deeded street address plus an internal code. A unit tag can reflect building/unit identifiers. A tenancy tag can pair the unit with the tenancy start date and a neutral sequential ID. A document tag identifies type, date, version, and source.
Keep a short legend explaining the tag scheme so anyone can read the file without guessing. Apply tags to file names, folder labels, index sheets, and custody notes. Ensure the same tags appear in both sensitive and ordinary folders without exposing sensitive content.
Checklist
– Property tag: e.g., “PROP-001 | 123 Main St, City ST”
– Unit tag: e.g., “UNIT-2B” (or parcel/subunit code)
– Tenancy tag: e.g., “TEN-2023-09-01-UNIT-2B-01”
– Document tag elements: type, date (YYYY-MM-DD), version (v1, v2), and source (e.g., “signed-by-both”)
– Create a tag legend stored at the root of the file set
– Apply tags to digital file names and physical folders
– Add tags to index sheets, custody logs, and transfer memos
– Verify tags appear consistently across all references
03Separate sensitive screening materials from ordinary tenancy records
Consumer reports and identity artifacts contain sensitive personal information. Keep them in a restricted, clearly labeled area separate from ordinary lease files. Limit access, document who can view them, and note where each sensitive item is stored. Store only what is necessary for a qualified review of documentation and custody. The Federal Trade Commission provides guidance concerning handling and disposal of consumer report information.
Ordinary tenancy records (lease, addenda, keys receipts) may be stored in a general tenancy folder. Keep cross-references between the sensitive and ordinary areas so reviewers can find items without mixing them.
Checklist
– Identify sensitive items: credit/background reports, report order confirmations, government ID images, SSN-containing materials, bank/paystub images, and screening portal exports
– Place sensitive items in a restricted folder or cabinet; note access roles
– Keep a sensitive-materials index with document titles, dates, and storage locations
– In the ordinary tenancy file, include only a pointer to sensitive items (no duplication)
– Add a brief note on security methods (e.g., locked cabinet, encrypted drive)
– Record disposal method references consistent with FTC guidance when appropriate
– Avoid embedding sensitive data in email threads or general notes
04Preserve application and consent artifacts without evaluating them
Keep the original rental application and explicit authorizations that permitted obtaining any consumer reports. Record how each artifact was collected (portal, email, paper), the date/time, and the source. If consent was recorded electronically, capture the system record showing acknowledgement, the time stamp, and any available IP or user ID. If related screening notices were sent, keep a factual copy or log entry for completeness, without evaluating requirements or outcomes.
Do not summarize, score, or interpret the application or reports here. Your aim is a clear trail from application and consent to the presence of sensitive screening documents, linked by date and source.
Checklist
– Save the final application submitted (unaltered), with submission date/time and source
– Save signed consent/authentication artifacts that permitted report ordering
– Keep order confirmations for any consumer reports and the vendor name
– Log the collection method (portal upload, email attachment, in-person)
– Preserve any screening-related notices sent (copy or log), with dates
– Maintain a short chain-of-custody note: who received each item and where it was filed
– Cross-reference application/consent to sensitive-report storage locations
05Maintain a signed lease and addenda version index
A clean version index prevents confusion over which lease and addenda govern a tenancy. Keep the fully executed lease as a distinct record and attach addenda as separate, clearly labeled items. When a lease is amended, renewed, or otherwise replaced, create a new version entry rather than overwriting the old one. Mark each document with dates, signers, and how it was executed (e.g., in-person wet signatures or an e-sign service identifier).
Include a supersession note when a later document replaces or modifies an earlier one. Keep all versions so a reviewer can follow the chronology.
Checklist
– List the executed lease as “LEASE—YYYY-MM-DD—v1—signed-by-both”
– Index each addendum separately with date and version (e.g., “ADDENDA—pet—YYYY-MM-DD—v1”)
– Note execution method and, if electronic, the platform’s transaction ID
– Record signers’ names exactly as they appear on the documents
– Create a supersession entry when a new lease or amendment applies
– Keep both original and revised documents; do not overwrite files
– Add cross-references to any related move-in or renewal communications
06Use secure storage and access notes for sensitive material
Sensitive documents call for heightened safeguards. Note, in plain language, how these files are secured and who has access. For digital records, this may include restricted folders, encryption-at-rest, unique user credentials, and activity logging. For physical records, this may include a locked cabinet in a controlled room. If sensitive items are later destroyed, document the method and date. The FTC publishes guidance on disposing of consumer report information and recommends reasonable measures for protection and disposal.
Keep the access notes brief and factual. Avoid embedding confidential content within the notes themselves.
Checklist
– Identify storage type for each sensitive item (physical/digital) and exact location
– Record permitted roles (e.g., owner, designated manager) rather than individual names when possible
– Note security methods (e.g., locked cabinet; encrypted server folder)
– Capture any change in access (date, reason, and by whom)
– Keep a simple access log for view/copy events when feasible
– If disposed, record method (e.g., shredding/pulverizing; secure deletion) and date
– Add a pointer to the organization’s security policy or handling guidelines
07Handle missing, corrected, or transferred files without reconstructing decisions
Files change. When something is missing, document the gap and the steps taken to locate it. When a document is corrected or re-signed, keep the original, add the corrected version, and write a supersession note explaining the relationship. If management or ownership transfers, create a custody memo that lists what moved, when it moved, and to whom custody transferred. These notes support a clean audit trail without attempting to recreate past judgments or screening conclusions.
Use short, dated memos for each variance so a qualified reviewer can understand the file’s evolution.
Checklist
– Missing item note: document title, expected date, search steps, and current status
– Corrected document entry: link old and new versions with a reason (e.g., typographical correction)
– Supersession tags: “superseded by [doc tag] on [date]”
– Transfer memo: items transferred, date/time, parties, and new storage locations
– Receipt acknowledgments when files change hands
– Do not delete superseded documents; keep them visibly linked
– Add open items to the handoff index’s “outstanding” section
08Build a qualified-review handoff index
End with a concise, one-to-two page handoff index. It should summarize identifiers, what exists, where it lives, what changed, and what needs attention. The purpose is to give a qualified reviewer the roadmap: property/unit/tenancy tags, inventory counts by document type, version highlights, sensitive-material flags, storage locations, and access points. Include brief custody notes, transfer memos, and any missing or pending items. Keep the language neutral and factual.
Attach the index at the root of the file set (both ordinary and sensitive folders may hold a copy without exposing confidential content). Update it when anything material changes.
Checklist
– Header: property tag, unit tag, tenancy tag, tenancy period
– Inventory: count of applications/consents, consumer-report items, lease/addenda versions
– Locations: paths, cabinets, and system IDs for each category
– Sensitive flags: list items held in restricted storage and access role notes
– Version highlights: which lease/addenda versions govern chronologically
– Custody notes: changes, transfers, and access log summary
– Outstanding items: missing documents, pending signatures, or confirmations
– Prepared-by, review-by, and last-updated dates
Federal resources
Official sources
Use these public sources alongside qualified review when facts, timing, and records determine the result.
When the facts are more complex
Bring an organized set of facts to the next conversation.
A qualified review can begin with the records, questions, and transaction details already gathered.
Common questions
Frequently asked questions
What are the minimum file index fields I should record?
At minimum, record property tag, unit tag, tenancy tag, tenancy period, and a document inventory with titles, dates, versions, and storage locations. Include a sensitive-materials flag for any consumer reports or ID images. Add a short custody note for how each item was obtained and by whom. Finish with outstanding items and a prepared-by/last-updated line so a qualified reviewer can assess scope, chronology, and where to find each record.
How do application records differ from signed-lease records in this file?
Application records show what was submitted and authorized before any lease was signed. Preserve the application, consent authorizations, order confirmations for consumer reports, and a short custody log. Store them separately from the executed lease. Lease records contain the fully signed agreement and addenda, tracked by date and version. Cross-reference the two groups with consistent property/unit/tenancy tags and a handoff index, but avoid mixing sensitive application materials into the lease folder.
Why separate sensitive screening reports from lease files?
Consumer reports and identity artifacts often contain highly sensitive information. Separating them reduces exposure, clarifies who can access them, and helps you document safeguards. Keep a pointer in the ordinary tenancy file and place the report and related items in a restricted area. The FTC publishes guidance on handling and disposing of consumer report information. Separation supports a clean review without revealing confidential data in general folders.
How do I handle multiple applicants on one tenancy?
Create one tenancy tag for the unit and period, then create a sub-index for each applicant’s application and consent materials. Keep each applicant’s sensitive items in their own restricted subfolder, linked to the same tenancy tag. The executed lease and addenda usually sit in a shared tenancy folder, with all signers listed exactly as on the documents. Your index should show counts and locations for each applicant’s records without evaluating or comparing them.
What’s the best way to track lease addenda and version history?
Index each addendum as its own document with a clear title, date, and version (e.g., “ADDENDA—parking—2024-01-15—v1”). When a lease is renewed or amended, create a new version entry and link it to the prior one with a supersession note. Do not overwrite older versions. Record signers, execution method, and storage location. A simple timeline in the handoff index helps reviewers see which documents govern chronologically.
What if the management company changes during a tenancy?
Prepare a dated custody transfer memo that lists the property/unit/tenancy tags, all document categories, and where each moved. Note the receiving party, storage locations, and any changes to access roles. Obtain and keep a receipt acknowledgment. Do not alter prior files; keep originals and add a transfer note in the handoff index. This preserves continuity and shows chain of custody without reinterpreting past records.
How should I securely store digital records?
Use restricted folders with unique user credentials, role-based permissions, and (where available) encryption at rest. Keep brief access notes and, if feasible, activity logs for view/copy events. Back up securely with limited access. Avoid emailing sensitive attachments; instead, store centrally and link by reference. When disposing of consumer report information, follow reasonable measures consistent with FTC guidance, such as secure deletion processes for digital media.
What if the consent or application document is missing?
Create a dated missing-item note that names the document, expected date, and search steps taken (e.g., portal logs, email, paper files). Link any indirect evidence of submission (receipt emails or portal confirmations). Do not recreate or backfill content. Add the gap to the handoff index’s outstanding items for a qualified reviewer to assess next steps. If needed, ask qualified counsel about options for addressing the gap prospectively.
What records should remain after the tenancy ends?
Keep the tenancy file intact with clear start/end dates. Archive the executed lease and addenda versions, application/consent artifacts, sensitive screening items (in restricted storage), and references to move-in/move-out condition and deposit disposition records. Update the handoff index to show the tenancy’s end date and where records are archived. When disposing of consumer report information, apply reasonable measures consistent with FTC guidance rather than leaving sensitive items in general storage.
When is a qualified legal or tax review needed?
Consider a qualified review when files include consumer reports, complex amendments or renewals, assignment or ownership transfers, missing or corrected documents, or cross-system custody questions. A review may also help when preparing returns or financial statements that rely on lease terms or tenancy timing. This guide organizes facts and custody notes; it does not determine legal or tax outcomes. Bring the handoff index so the reviewer can navigate quickly.
This guide is educational. The application of tax rules depends on individual facts; verify current IRS guidance and consider a qualified tax professional before acting.