An email retention policy defines which messages and attachments an organization keeps, why it keeps them, when the retention clock starts, and what happens when the period ends. It also defines when ordinary deletion must stop because information needs to be preserved.
“Keep everything” and “delete after a fixed number of years” both avoid the real question: what record does this message contain? A receipt, an employment decision, a customer’s signed acceptance, and a lunch invitation do not automatically deserve the same treatment.
This guide is an operational planning framework. The legal examples are explicitly U.S. federal and UK examples, not a schedule for every organization. Have the responsible records, privacy, and legal advisers approve the applicable requirements before turning on deletion.
Retention, backup, and a legal hold do different jobs
On a small screen, scroll the table sideways to read all columns.
| Control | Purpose | What it does not establish |
|---|---|---|
| Retention schedule | Define how long a class of record is kept and the event that starts the period. | That the email system actually enforces the written rule. |
| Backup | Recover data or a service after a loss or disruption. | That each record can be found, preserved, or deleted according to a schedule. |
| Preservation or legal hold | Suspend ordinary disposal for information within a defined matter or obligation. | That every mailbox must be kept forever or that all unrelated data is in scope. |
| Archive or export | Move or copy information into another storage or retrieval arrangement. | A retention policy, complete evidence, or a tested restore by itself. |
A user deleting a message may remove it from their visible mailbox while a compliance system retains a copy. Conversely, an exported folder may lose relationships or omit linked documents. Describe which copy is authoritative and which controls govern each location.
Build the schedule around records and triggering events
Inventory the information first: individual and shared mailboxes, archived accounts, local exports, mobile copies, attachments, and messages copied into CRM or ticketing systems. Identify the business purpose and owner of each record category. A link in a message does not necessarily preserve the linked document or the version the recipient saw.
The IRS record-retention guidance illustrates why one number is inadequate. U.S. tax-record periods depend on the event and circumstances, and other reasons can require keeping a record longer. Those tax rules do not create a blanket rule for all business email.
For personal data subject to the UK GDPR, the ICO’s storage-limitation guidance explains that retention must be justified by purpose rather than a universal period. Consider both obligations to preserve information and obligations to avoid unnecessary retention.
On a small screen, scroll the table sideways to read all columns.
| Field | Example question |
|---|---|
| Scope | Does this cover contract acceptance emails, attachments, and later amendments? |
| Authority and purpose | Which applicable requirement or documented business need supports retention? |
| Trigger | Does time run from sending, case closure, contract termination, or another event? |
| Period and review | Who approves the duration, and when is that decision reviewed? |
| System and owner | Where is the authoritative record and who maintains the rule? |
| Disposal and exceptions | How is disposal checked, and how do holds suspend it? |
A policy that says “retain for six years” but omits the trigger is incomplete. Six years from the message date and six years after a contract ends can produce very different results. Use explicit event definitions and document how the event enters the system.
Give preservation a clear escalation route
In U.S. federal civil litigation, Federal Rule of Civil Procedure 37(e) addresses certain losses of electronically stored information that should have been preserved in anticipation or conduct of litigation. The rule’s conditions matter; it is not an instruction to retain every message indefinitely.
Have a named legal or records owner decide the scope of a preservation obligation and communicate it to administrators and affected staff. Record the relevant people, systems, date ranges, and subject matter. Confirm that automated deletion, account closure, and backup rotation will not undermine the required preservation. Staff need an escalation route before ordinary cleanup destroys potentially relevant material.
Translate the policy into settings, then test the result
Microsoft Purview distinguishes retention policies applied at container level from labels applied to individual items. Its retention-settings documentation also distinguishes retaining, deleting, and retaining then deleting, with different choices for when a period begins. Features, licensing, workloads, and overlapping rules affect the outcome.
- Map each approved category to its supported system control. Record any gap requiring another process.
- Test on nonproduction records with known dates and content. Include a message with an attachment and one with a link.
- Check retrieval after a user deletes a message, after an account is deactivated, and while a hold applies.
- Test what happens when multiple policies apply and when a hold is released. Include separately stored copies.
- Confirm the required propagation and processing time. A configured expiration date does not guarantee immediate removal.
- Document evidence of the test and obtain operational approval before broad enforcement.
Explain the behavior to staff in plain language: where to file records, what “delete” does, and who handles a preservation question. Revisit settings after migrations, license changes, new messaging tools, or a change in business activity.
Write a policy people can operate
Download the annotated email-retention worksheet (plain text). It includes scope, responsibility, a repeatable category record, hold handling, disposal review, and test evidence. Retention durations are intentionally left for your organization to determine; the worksheet is not a preapproved legal policy.
AI can suggest categories for review or help find inconsistencies in a draft schedule. It should not invent retention periods, decide that a hold has ended, or serve as the sole basis for deletion. Validate classification on known records and retain a route for ambiguous cases. A wrongly deleted record can be much harder to remedy than a mislabeled one.