Skip to content
  • News & Events
  • Careers
  • Contact
Home Logo
  • Solutions
    • Solutions
    • eDiscovery
      • eDiscovery Cost Calculator
      • Early Case Assessment
      • Processing
      • Web Hosting
      • Data Analysis
      • Consulting
      • Expert Witness & Technical Consulting
      • Multi-Language Litigation
      • eDiscovery for Government Agencies
    • Document Review
      • Incident Response Review
    • Digital Forensics
      • Evidence Collection & Preservation
      • Forensic Expert Services
      • Data Forensic Process
      • Accredited Lab & Facilities
      • Forensic Testing & Validation
    • Cyber Security
      • Incident Response
      • Penetration Testing & Ethical Hacking
      • Vulnerability Assessments
    • Court Reporting Services
    • Record Retrieval & Subpoena Services
      CA & TX
      • Subpoena Domestication
    • Traditional Services
    • Contract Legal Staffing & Legal Recruiting
  • Technology
    • Technology
    • Array In-House Solutions
      • Platform Intelligence
      • Review Intelligence
      • Testimony Intelligence
      • Acumen
    • Strategic Partnerships
  • Experience
    • Experience
    • Our Team
    • Locations
    • Company Timeline
    • Testimonials
  • Insights
  • Solutions
    • Solutions
    • eDiscovery
      • eDiscovery Cost Calculator
      • Early Case Assessment
      • Processing
      • Web Hosting
      • Data Analysis
      • Consulting
      • Expert Witness & Technical Consulting
      • Multi-Language Litigation
      • eDiscovery for Government Agencies
    • Document Review
      • Incident Response Review
    • Digital Forensics
      • Evidence Collection & Preservation
      • Forensic Expert Services
      • Data Forensic Process
      • Accredited Lab & Facilities
      • Forensic Testing & Validation
    • Cyber Security
      • Incident Response
      • Penetration Testing & Ethical Hacking
      • Vulnerability Assessments
    • Court Reporting Services
    • Record Retrieval & Subpoena Services
      CA & TX
      • Subpoena Domestication
    • Traditional Services
    • Contract Legal Staffing & Legal Recruiting
  • Technology
    • Technology
    • Array In-House Solutions
      • Platform Intelligence
      • Review Intelligence
      • Testimony Intelligence
      • Acumen
    • Strategic Partnerships
  • Experience
    • Experience
    • Our Team
    • Locations
    • Company Timeline
    • Testimonials
  • Insights
  • News & Events
  • Careers
  • Contact

Get Started

Get Started

Insights Articles

  • Insights
  • Articles
eDiscovery

Slack and Teams Collections: What Legal Teams Should Confirm Before Discovery Starts

| November 17, 2026

 

Slack and Microsoft Teams data can contain critical evidence, but collecting messages is only part of the challenge. Before starting Slack eDiscovery or Teams eDiscovery, legal teams should confirm which custodians, channels, conversations, attachments, and metadata are in scope, how retention policies affect available data, and whether the collection method preserves the context needed for review.

These details matter because collaboration data rarely exists as a simple series of standalone messages. Threads, reactions, timestamps, shared files, and permissions can all influence how reviewers interpret a conversation. If collection requirements are not established early, teams may face missing context, additional collection work, unexpected costs, or delays during review.

A structured pre-collection checklist can help legal teams identify potential gaps before collection begins.

 

Slack and Teams Collection Checklist: What to Confirm First

Before collection begins, use this checklist to align your legal team, IT, and eDiscovery provider on the data in scope, potential limitations, and requirements for review.

1. Custodians and data ranges

Identify the relevant custodians and define the date range for collection. Confirm how former employees, inactive accounts, and changes to the custodian list will be handled.

2. Channels, workspaces, and direct messages

Determine which public and private channels, teams, one-to-one messages, and group chats are relevant to the matter. Confirm that the proposed collection method can access each in-scope data type.

3. Retention and preservation 

Review applicable retention policies and determine whether relevant messages may have been deleted or expired. Identify any preservation steps that need to happen before collection begins.

4. Threads and conversation context

Confirm whether parent messages, replies, and thread relationships will be preserved. Ask how the collection method handles reactions, edited messages, and other available details that may help reviewers interpret a conversation.

5. Attachments and cloud file links

Determine whether relevant files are uploaded directly to the platform or linked from a cloud storage location. Confirm whether linked files can be collected and associated with their original messages so reviewers have the context they need.

6. Timestamps and metadata 

Establish which timestamps, participant details, message identifiers, and other metadata will be captured. Confirm how time zones and message chronology will be represented to help reviewers reconstruct events accurately.

7. Permissions and access

Identify the administrative permissions, account access, and approvals required to collect the relevant data. Address any restrictions that could limit collection or delay the process.

8. Export format and review readiness

Confirm the expected output format and whether the collected data will be searchable and compatible with the intended review platform. Determine how conversations, threads, and attachments will be presented to reviewers.

9. Validation and reporting

Ask how collection completeness will be assessed and potential gaps documented. Confirm what reporting will be available to help the team understand collection results and address any identified limitations.

10. Scope, cost, and timeline

Discuss what could require additional collection, processing, or review work, including newly identified custodians, data sources, or separate collection of linked documents. Establish how scope changes will be communicated, evaluated, and approved before additional work proceeds.

 

What Legal Teams Should Know About Slack eDiscovery and Teams eDiscovery

Although Slack and Microsoft Teams both support workplace communication, their data structures, administrative controls, and available collection options are not identical. Avoid assuming that a process used for one platform will work the same way for the other.

Retention policies and deleted messages

Retention settings can determine how long messages remain available and what happens when users delete or edit content. Administrative policies, legal holds, and other platform configurations may also affect what can be collected.

Before collection starts, confirm the organization's applicable retention policies, whether relevant data is still available, and whether preservation steps are needed. Coordinate with the appropriate administrators and counsel rather than assuming that a standard export will recover historical or deleted content.

Timing matters. If relevant messages may be expiring, escalate the preservation question promptly.

Threads, replies, reactions, and timestamps

A message viewed in isolation may tell only part of the story. Replies may clarify its meaning, reactions may provide additional context, and timestamps can help establish the sequence of events.

Ask how the collection process represents threaded conversations and whether parent messages, replies, reactions, edits, and available metadata will be preserved. Confirm the treatment of time zones and timestamps so that communications can be placed accurately in a timeline.

Not every collection method captures every element. Establish what is available, what will be included, and what limitations need to be documented.

Attachments and cloud file links

A chat message may contain an uploaded file, a link to a cloud-hosted document, or a reference to content stored elsewhere. These are not necessarily equivalent from a collection perspective.

Confirm whether files are collected directly with the conversation or remain in a separate cloud location. For linked files, determine whether the collection process can automatically retrieve the underlying content, preserve the relationship between the message and file, and account for relevant versions or access restrictions.

Permissions, exports, and review readiness

Collection depends on the access available to the people and tools performing it. Confirm the necessary administrative permissions, account access, approvals, and any restrictions that could affect collection.

Then review the expected output. Will conversations be searchable? Will messages remain associated with the correct participants and timestamps? Can reviewers follow threads and identify related attachments? Are the resulting files compatible with the intended review platform?

These questions help connect collection decisions to downstream processing, hosting, analysis, and review rather than treating collection as an isolated task.

 

What Can Go Wrong When Collaboration Data Collection Starts Without a Plan?

Even when a collection appears complete, gaps can emerge once the data reaches review. Common issues include:

  • Missing conversations: Relevant direct messages, private channels, group chats, or custodians were not included in the original scope.
  • Lost conversational context: Messages are exported without clear thread relationships, replies, reactions, or other available context.
  • Unavailable historical data: Retention settings or prior deletions mean some messages are no longer accessible.
  • Disconnected attachments: Messages contain cloud links, but the linked files are not collected or cannot be matched to the right conversations.
  • Inconsistent timelines: Timestamps or time-zone handling make it difficult to reconstruct the order of events.
  • Unexpected collection costs: Additional custodians, data sources, or collection methods are needed after review has begun.
  • Review delays: Data arrives in a format that requires additional processing, validation, or manual reconstruction.

 

Some limitations cannot be reversed. For example, a collection process cannot guarantee recovery of content that is no longer available. The goal is to identify known risks early, document limitations, and make informed decisions about preservation and collection. 

 

Questions to Ask Before Slack or Teams Collection

Before authorizing a collection, legal teams should be able to answer the following questions with their IT team and eDiscovery provider:

  1. What data types are in scope? Confirm custodians, channels, direct messages, group chats, date ranges, and relevant workspaces.  
  2. How will retention and preservation be handled? Identify applicable policies, potential deletion risks, and any preservation steps required.  
  3.  What context and metadata will be captured? Ask about threads, replies, reactions, edits, timestamps, participant details, and message identifiers.  
  4.  How will attachments and cloud links be handled? Determine whether linked files can be collected, associated with their messages, and validated.  
  5.  What access and permissions are required? Identify who must authorize collection and whether account or administrative restrictions could affect the results.  
  6.  How will the results be validated? Ask what checks will be performed, what reporting will be available, and how collection gaps will be communicated.  
  7.  Will the output support review? Confirm the expected format, processing requirements, searchability, and ability to preserve conversational context. 
  8.  What could change the scope, cost, or timeline? Discuss assumptions, limitations, additional collection needs, and how changes will be approved. 

A clear plan does not eliminate every challenge, but it gives the team a shared understanding of what is being collected, why it matters, and how potential gaps will be addressed. For additional guidance on evaluating service providers, see Array's eDiscovery provider guide.

 

Frequently Asked Questions

What should legal teams confirm before Slack eDiscovery?

Confirm the relevant custodians, channels, direct messages, date ranges, retention settings, threads, attachments, metadata, permissions, and collection method. Also establish how completeness will be validated and how the collected data will be prepared for review.

Is Teams eDiscovery different from Slack eDiscovery?

Yes. Although both platforms support workplace conversations, their data structures, administrative controls, retention configurations, and collection options can differ. Legal teams should confirm platform-specific capabilities and limitations rather than assuming the same collection approach will capture the same information from both.

Are Slack and Teams messages enough, or should attachments be collected too?

The answer depends on the scope and relevance of the matter. If messages reference documents stored in cloud platforms, those files may contain important evidence. Teams should determine whether relevant attachments or linked files must be collected and how their relationships to the original messages will be preserved.

Can deleted Slack or Teams messages be recovered?

Not always. Recovery depends on factors such as retention policies, deletion behavior, available records, administrative settings, and the collection method. Legal teams should assess preservation needs promptly and confirm what data remains available before assuming it can be recovered.

Why does conversation context matter in chat discovery?

A standalone message may be ambiguous without its replies, surrounding discussion, reactions, or related files. Preserving available context helps reviewers interpret communications accurately and understand how a conversation developed.

 

Prepare Collaboration Data for Discovery

Slack and Teams collections require more than gathering message content. Legal teams need to understand the scope, access requirements, retention settings, related files, metadata, and review needs before collection begins.

Array provides end-to-end eDiscovery services, including data identification, preservation, collection, processing, hosting, analysis, review, and production. We work with legal teams to develop collection approaches tailored to the matter, helping identify potential gaps and prepare data for the next stage of discovery.

Connect with Array to learn more about modern data collection and planning for collaboration data discovery. You can also explore our guides on cloud file links and modern attachments to understand how linked content can affect collection and review.

Johanna Whippen; Solutions Architect

With her 10+ years of eDiscovery experience, Johanna has developed an advanced expertise in working at the intersection of IT and Legal to identify and mitigate risk points relating to information governance and data preservation, consult on best practices, and liaise between legal and technical stakeholders. Taking a delivery-driven approach, Johanna regularly consults with corporate legal and law firm clients on best practices and innovative solutions to meet immediate needs and exceed long-term goals.  

Share this post

Keep reading

 Second Requests: Why Knowing Your Data Matters Before Collection Begins
eDiscovery

Second Requests: Why Knowing Your Data Matters Before Collection Begins

Nov 16, 2026, 12:11:17 PM

When a Second Request arrives, one of the first questions legal teams ask is, "What data do we need...

 5 Questions to Ask When eDiscovery Costs Change Mid-Project
eDiscovery

5 Questions to Ask When eDiscovery Costs Change Mid-Project

Nov 12, 2026, 11:24:13 AM

Even with careful planning, an eDiscovery project can cost more than initially expected. Data...

 What Drives eDiscovery Costs Up Mid-Project?
eDiscovery

What Drives eDiscovery Costs Up Mid-Project?

Nov 10, 2026, 9:00:02 AM

eDiscovery costs can increase mid-project when the scope of discovery changes, additional data...

Frame 35

People.
Process.
Excellence.

Lets Talk
  • QUICK LINKS
  • Solutions
  • Technology
  • Experience
  • Insights
  • Careers
  • News & Events

Stay Current. Stay Competitive. Stay Informed.

SOC 2
Privacy Policy Terms & Conditions Report Abuse
All Rights Reserved. ©2025 Array Trust Array