Skip to content

Records governance research

Record Retention and Litigation Holds in Property Management

No single federal period is the direct numeric answer for this source review. No single federal retention period applies to every property management record. A defensible program classifies records, assigns a retention trigger and owner, and suspends ordinary deletion when litigation or an investigation is reasonably anticipated.

| Updated 2026-10-22 | 2,369 words

Record Retention and Litigation Holds in Property Management
Table of contents

Record retention and litigation holds

No single federal period

U.S. retention duties depend on the record class, jurisdiction, contract, and anticipated litigation

Key takeaways

  • Do not adopt one retention number for every property record. Classify the record, identify the legal or business trigger, and document the rule.
  • A litigation hold is an instruction to preserve, not a promise that every file is relevant. Name the custodians, systems, date range, and suspension steps.
  • Keep the retention schedule, hold notice, acknowledgment, collection log, and release decision together so another reviewer can reconstruct the sequence.
  • Route legal questions about scope, preservation, and release to qualified counsel. An administrative assistant can execute a hold but should not decide its legal sufficiency.

Key statistics and definitions

Record class

Leases, applications, maintenance files, financial records, and personnel files follow different rules

Trigger event

A retention clock starts from a defined event such as lease end, case closure, or tax period

Hold notice

A hold suspends ordinary deletion once litigation or an investigation is reasonably anticipated

Methodology

This review treats record retention and litigation holds as separate controls. It examines the record class, the trigger event, the retention period, the source system, the custodian, and the disposal or preservation evidence. The unit of analysis is a record class within a property management workflow, not an individual document standing alone.

The external sources were selected for their direct relevance to records governance. NARA provides records management concepts, the Federal Rules address preservation and sanctions in federal civil cases, and Rule 37 provides the specific text on failure to preserve electronically stored information. HUD, the FTC, NIST, the SBA, and the IRS supply context for housing, privacy, security, business recordkeeping, and tax records. None of those sources establishes a universal private-sector retention period.

The operating recommendations are editorial. They translate the source material into a schedule and hold procedure that a property manager can test. They do not replace legal advice, a jurisdiction-specific retention requirement, a contract, or a tax rule. A qualified professional should review the schedule and any hold with legal effect.

The review does not measure a company's compliance or estimate the cost of a claim. It tests whether a record class and a hold can be reconstructed from retained evidence. A finding that a step is missing is a process observation, not a legal conclusion.

The direct answer: a retention schedule and a hold solve different problems

A retention schedule answers a routine question: how long does this class of record stay in the ordinary course? A litigation hold answers an exception question: which records must stop following the ordinary deletion rule because a dispute, claim, or investigation is reasonably anticipated? Treating the two as one policy creates gaps in both directions. A schedule can authorize deletion of a record that should have been preserved, while a hold can become so broad that the team keeps everything and manages nothing.

For a property management company, the practical unit is the record class, not the file cabinet. A lease file, an applicant screening file, a maintenance photo set, an owner statement, a vendor tax form, and a personnel file have different triggers and different reviewers. The schedule should name the class, the trigger event, the minimum retention period, the system of record, the owner, and the disposal method. If the team cannot state those fields, it does not yet have a schedule.

The hold is a separate instruction layered on top. It should identify the matter, the custodians, the systems, the date range, the types of records, and the steps that must stop. It should also name who can answer questions, who confirms preservation, and who authorizes release. That structure lets an assistant execute a defined task without deciding whether a record is relevant or privileged.

What federal records guidance does and does not require

The National Archives publishes records management guidance for federal agencies, not a universal retention schedule for private property managers. Its value to a private company is methodological: identify records, assign responsibility, control the lifecycle, and document disposal. It does not replace state real estate rules, local housing requirements, tax rules, or the company's own contracts.

The Federal Rules of Civil Procedure matter when a case is in federal court. Rule 37 addresses the failure to preserve electronically stored information and the sanctions that can follow. The rule does not create a single retention period for leases or maintenance photos, and it does not tell a property manager what to keep before a case exists. It reinforces a simpler operational point: once preservation is required, a routine deletion process can become a serious problem if nobody suspends it.

HUD's fair housing guidance, the FTC Safeguards Rule, NIST privacy guidance, SBA recordkeeping advice, and IRS recordkeeping guidance each address a different slice of the problem. Fair housing records may be relevant to a complaint. Safeguards and privacy guidance affect how records are protected and accessed. Tax rules affect financial records. A property manager should map each external requirement to a record class and a responsible owner rather than blending them into one generic retention number.

Why property management records need a class-based schedule

Property management produces records in several distinct streams. Leasing creates applications, screening reports, consent records, adverse action notices, leases, addenda, and renewal documents. Operations creates work orders, vendor assignments, inspection reports, photos, permits, and completion evidence. Accounting creates rent ledgers, owner statements, invoices, bank reconciliations, deposits, and tax forms. Resident service creates complaints, accommodation requests, notices, and communication logs.

Those streams have different retention logic. A maintenance photo may be needed to support a repair, a warranty claim, an insurance claim, or a later condition dispute. An applicant screening record may be governed by consumer reporting rules and a defined adverse action process. An owner statement may need to reconcile to a tax year. A personnel file follows employment rules. A single 'keep everything for seven years' rule is easy to write and hard to defend because it ignores the trigger and the purpose.

A class-based schedule also makes deletion safer. The team can dispose of a class only after the trigger, the minimum period, and any hold check are complete. The disposal record should show the class, the date range, the authority, the method, and the reviewer. That record is as important as the retention period because it shows the company followed its own rule.

The four duties in a litigation hold

A workable hold has four duties. The first is to recognize the trigger. A demand letter, a fair housing complaint, a personal injury claim, a vendor dispute, a security incident, or a regulatory inquiry can all create a preservation obligation. The team does not need to decide the merits of the claim to recognize that preservation may be required. It needs a route to counsel or management quickly.

The second duty is to suspend deletion. That means more than sending an email. The team should identify the systems and custodians that may hold relevant records, confirm that auto-deletion and retention jobs are paused where appropriate, and instruct people not to delete, edit, or remove files. The suspension should cover paper, email, shared drives, property management software, photos, text messages used for business, and vendor portals where the company controls the record.

The third duty is to preserve and collect. The hold log should record what was collected, from whom, when, and in what form. Keep the original file where possible and create a working copy for review. Do not let an assistant decide that a record is irrelevant or privileged. The assistant can collect the identified categories and escalate questions.

The fourth duty is to document and release. The file should show the hold notice, acknowledgments, collection steps, any changes in scope, and the eventual release. Release should come from the authorized person, not from an assistant who assumes the matter is over. If some records remain under a separate obligation, the release record should say which ones and why.

Sampling a retention and hold file

A useful sample starts with the schedule, not with a random folder. Select one record class and trace a record from creation to disposal. Confirm the trigger event, the retention period, the system of record, the owner, and the disposal authority. Then select a second record from the same class that should still be active. The reviewer should be able to explain why one was kept and the other was eligible for disposal.

For a hold, select one matter and trace the notice, acknowledgment, collection, and release. Check whether the systems named in the notice match the systems that actually held records. Check whether the date range is stated and whether later custodians were added when the matter expanded. A hold that exists only as an email with no collection log is difficult to verify.

The sample should include an exception. Choose a record that was almost deleted, a custodian who did not acknowledge, or a system that was missed on the first pass. The point is not to grade individuals. The point is to find where the process depends on memory. Those are the places to add a checklist, a system control, or a named backup.

Implementation sequence for a property portfolio

Start with an inventory. List the systems that hold property, resident, applicant, owner, vendor, financial, and personnel records. For each system, name the administrator, the retention capability, the export method, and the access rules. Include shared drives and local folders that people use for working copies, because those are often outside the formal retention tool.

Next, define a small number of record classes. A first pass might use leasing, screening, maintenance and inspections, resident service, financial and owner, vendor, and personnel. For each class, write the trigger, the minimum period, the source system, the owner, and the disposal method. Mark the classes that require legal or tax review. Do not publish a period you cannot support.

Then write the hold procedure. Include the trigger examples, the person to notify, the notice template, the systems to check, the collection log, the escalation path, and the release authority. Assign a backup for each step. Test the procedure with a tabletop exercise before a real matter arrives.

Finally, train the people who create records. A retention program fails when the team stores the only copy in a personal inbox or a text thread. Give residents and vendors an approved channel, give staff a clear naming and filing rule, and review a sample each quarter. The goal is not a perfect archive. It is a record that another authorized person can find and understand.

Privacy, vendor records, and access boundaries

Retention and privacy pull in opposite directions if the team treats them as separate projects. Keeping records longer increases the data at risk. Deleting too early destroys evidence and operational history. The resolution is to keep the minimum needed for a defined purpose, protect it with role-based access, and document why it remains. NIST privacy guidance and the FTC Safeguards Rule both point toward defined roles, controls, and accountability rather than unrestricted storage.

Vendor records deserve their own line in the schedule. A vendor file may include a W-9, insurance certificate, contract, license, background check, access credential record, invoice, and performance notes. Each item has a different trigger. A certificate that expires is not the same as a contract that ends. A tax form follows a tax year. An access credential should be deactivated when the work ends, even if the vendor file remains for accounting.

Access should follow the task. A coordinator who updates a maintenance log does not need the entire applicant screening file. An accounting reviewer may need the invoice and ledger but not the resident's medical accommodation record. Use named accounts, least privilege, and an access log. When a hold is active, do not broaden access casually. Add reviewers only through the approved process.

Conclusion: make the hold reproducible

A retention schedule is a set of decisions about what to keep and why. A litigation hold is a controlled exception that stops ordinary deletion when preservation is required. Neither works as a vague instruction to 'keep important records.' Both need a class, a trigger, an owner, a system, and a review step.

The test is reproducibility. Give the file to a reviewer who did not handle the matter. Can that person identify the record class, the retention rule, the hold notice, the systems searched, the records collected, and the release authority? If the answer depends on the memory of one manager, the program is not yet operational. Fix the record before the next claim, not after.

Reference table

Record classTypical retention triggerControl question
Lease and occupancy fileLease end or final dispositionWhat agreement, notices, and addenda must remain together?
Applicant and screening fileDecision date or required retention periodWhich consumer report, consent, and adverse action records apply?
Maintenance and inspection fileWork completion, unit turn, or claim closureWhich photos, work orders, invoices, and safety records support the decision?
Financial and owner recordsTax year, statement period, or account closureWhich ledger, bank, invoice, and distribution records reconcile?
Personnel and vendor filesSeparation, contract end, or tax yearWhich eligibility, tax, insurance, and performance records belong in the file?

Sources

  1. National Archives, Records Management Accessed 2026-10-22.
  2. U.S. Courts, Federal Rules of Civil Procedure Accessed 2026-10-22.
  3. Cornell Legal Information Institute, Federal Rule of Civil Procedure 37 Accessed 2026-10-22.
  4. HUD, Fair Housing Act Overview Accessed 2026-10-22.
  5. FTC, Safeguards Rule and Gramm-Leach-Bliley Act Accessed 2026-10-22.
  6. NIST, Privacy Framework Accessed 2026-10-22.
  7. SBA, Manage Your Business Accessed 2026-10-22.
  8. IRS, Recordkeeping for Small Businesses Accessed 2026-10-22.

Frequently asked questions

Is there a federal retention period for property management records?

There is no single federal period that covers every record in a property management company. Retention depends on the record type, jurisdiction, contract, program rules, tax obligations, and anticipated litigation. Build a class-based schedule and confirm it with qualified counsel.

When should a litigation hold start?

Start when litigation or an investigation is reasonably anticipated, not only after a complaint is filed. The hold should identify the matter, custodians, systems, date range, preservation steps, and the person responsible for oversight.

Can a virtual assistant execute a litigation hold?

A trained assistant can send approved notices, collect acknowledgments, preserve identified files, and maintain the hold log. Counsel and management decide the scope, legal sufficiency, and release. The assistant should escalate any question about relevance or privilege.

What should the hold release record show?

Record the matter, the date the hold is released, the authority for release, the records returned to the normal schedule, and any records that remain preserved. Do not release a hold informally through a chat message.

  • Property management records retention and disposition audit

    By retention class, this study checks whether selected record series retain the retention rule, trigger event, legal hold status, destruction authorization, and destruction certificate at the September 18 cutoff. A retention schedule on a shelf does not prove records were kept or destroyed correctly. The result measures disposition control, not legal sufficiency or the accuracy of the underlying records.