Most people think of document search as a flat exercise: type a word, get back the documents that contain it. NetDocuments goes several layers deeper than that, and it’s worth understanding exactly how far, because it changes what you should expect when you search — and what you should expect opposing counsel or a records request to turn up.
The scenario
Picture this chain of custody:
- An email is sent with an attachment.
- That attachment is itself an email.
- The attached email has its own attachment — a Word document.
- That Word document contains the word “motion” somewhere in its body.
If you save the original outer email into NetDocuments and later run a text search for “motion,” NetDocuments will surface that email — even though the word “motion” never appears in the outer email’s subject, body, or visible text. It only exists three layers down, inside a document that’s attached to an email that’s attached to the email you saved.
Why this matters
NetDocuments’ text extraction and indexing engine doesn’t stop at the first layer of a file. When it processes an email with an attachment, it doesn’t just index the email text — it opens the attachment, extracts its text, and indexes that too. If that attachment happens to be another email with its own attachment, the engine repeats the process, extracting and indexing that nested content as well. The result is a fully searchable chain, no matter how many attachments deep the relevant text lives.
For legal teams, this has real consequences:
- Discovery and privilege review get more thorough. A responsive document buried inside a forwarded email chain won’t slip past a keyword search just because it’s nested.
- Due diligence and audits benefit the same way — a single search can surface a document that’s several attachment layers removed from the file someone actually thinks to open.
- False negatives become much less likely. If you’re relying on search to confirm a term doesn’t appear anywhere in a matter, nested-attachment indexing means you’re actually checking the whole chain, not just the top layer.
What this looks like in practice
In the example we ran across, a search for “motion” returned an email titled generically (nothing to do with the word itself) simply because an attached email carried its own attached Word document containing that term. From the search results screen, there’s no visual flag saying “this hit came from three layers deep” — the match just appears, and it’s worth remembering why it appeared before assuming the top-level document itself uses that language.
That’s a useful habit to build into review workflows: when a search result seems to have no obvious connection to your search term at the surface level, check what’s attached — and what’s attached to that.
The takeaway
NetDocuments doesn’t treat an email with an attachment as two separate, disconnected files. It treats the whole chain as one searchable unit, recursively extracting text from nested attachments so that a term buried several layers deep is still just as findable as one sitting in the subject line. If your firm relies on NetDocuments for discovery, compliance, or general recordkeeping, this recursive indexing is quietly doing a lot of work behind the scenes — and it’s worth knowing about before you assume a search has come up empty.
Have questions about how your firm’s NetDocuments environment is configured for search and indexing? Reach out or schedule a consultation.