How do we resolve it when two offices have conflicting retention rules for the same email thread?

When two offices apply different retention rules to the same email thread, the conflict is usually not a contradiction to “average out” — it is a signal that the thread serves more than one business purpose. The guiding principle is straightforward: a record is kept as long as the longest applicable requirement demands. You do not delete to satisfy the shorter rule while another office still has a legitimate, schedule-based need to retain.

Start by identifying the record, not the message

The same email can be a copy in one office and the official record in another. Determine which office holds the record copy (the version of record) and which holds a reference or convenience copy. Reference copies can typically be disposed of when no longer useful; the record copy is governed by the retention schedule. Often the apparent conflict disappears once you confirm only one office actually owns the record.

Apply the longest-retention rule

If the thread genuinely qualifies as a record in both offices under different schedule items, retain it for the longest of the applicable periods, then dispose only when every requirement has lapsed. Retention minimums are floors, not ceilings, so honoring the longer period satisfies both. Document which schedule item drove the final disposition date.

Resolve overlapping schedule items

• Map each office’s rule to the specific records schedule item and the function it covers.
• Check whether one item is more specific (program-specific) and one more general; the more specific, function-aligned classification usually controls.
• Watch for legal holds: any hold for litigation, audit, FOIA, or investigation overrides routine disposition until lifted.

Escalate and govern the outcome

Disagreements that cannot be settled by the rules above belong with the records officer or an information-governance committee, not with the individual mailbox owners. Record the decision, the rationale, and the controlling authority so the same thread is handled consistently next time. For broader guidance on managing message-based records, see the email and messaging topic hub.

A consistent, documented classification practice — assigning each thread to the right function up front — prevents most of these conflicts from recurring.