In the two previous posts, we explored the reasons collecting and preserving linked documents are such a discovery headache as well as best practices for both requesting parties and producing parties in addressing them.
Now, we turn to the practical matter of how to handle these documents once they enter the eDiscovery pipeline: particularly when processing Microsoft 365 linked documents for loading into Relativity. In our experience so far, 80 to 90 percent of the linked documents we’ve seen have come from M365 and Google Workspace – with probably 20 percent of that from Google Workspace (as discussed in our post last year).