How should I handle a single email thread that mixes business and personal content?

A single email thread that blends work and personal content is common, and it raises a real question: which parts are records, and how do you treat them consistently? The guiding principle is that record status follows content and function, not the subject line or the folder a message happens to sit in. Any portion of the thread that documents an organizational activity, decision, transaction, or obligation is a record and must be retained accordingly — even if it shares a message with unrelated personal chatter.

Start by Classifying Content, Not the Whole Thread

Read the thread as a series of statements, not a single object. If even one message conveys business value — an approval, a commitment, a policy interpretation, a transaction — the thread contains a record. The presence of personal lines does not erase that obligation, and personal content does not become a record simply by riding along in the same conversation.

Practical Handling

• Preserve the record portion. Capture the thread (or the relevant messages) into your recordkeeping system so the business content is retained for its full retention period, with sender, recipients, dates, and attachments intact.
• Do not edit or delete to “clean it up.” Altering a message to strip personal lines can destroy context and undermine the integrity and authenticity of the record. Keep the thread as sent and received.
• Avoid mixing in the first place. Encourage staff to keep personal correspondence out of business threads and business accounts. Going forward, that single habit eliminates most of this problem.
• Apply the longest applicable retention. When a thread serves multiple business purposes, retain it under the longest relevant schedule until that period expires.

Why It Matters

Mixed threads frequently surface in audits, litigation discovery, and public-records or FOIA requests. If business content is destroyed because it was treated as “personal,” or if personal content is over-retained, both create risk. Consistent, content-based classification — applied through your retention schedule — keeps the organization defensible and the personal material from being swept up unnecessarily.

When in doubt, retain the thread as a record and let your schedule govern disposition. For related guidance, see the email and messaging topic hub.