Tampa | Litigation collection support
Tampa eDiscovery Collections
Collect the right records, document the gaps and give the review team a usable handoff. Plan the sources and delivery requirements before exports begin.
The engagement
What the eDiscovery Collections engagement covers
A Tampa business matter may involve a local custodian, a remotely managed Microsoft 365 tenant and mobile messages held on personally owned devices. The collection plan has to follow the records, not just the office address. GDF works with counsel and authorized system owners to identify sources, preserve agreed data and document what each collection includes.
For litigation in the Middle District of Florida, the case schedule and counsel's instructions guide technical preparation. The Tampa Division serves several surrounding counties, but the courthouse does not determine where electronic records reside. We establish tenant ownership, administrator access and custodian availability before committing to a collection sequence.
Preservation, collection, processing and production are separate steps. A legal hold does not automatically create a usable export, and a successful export does not prove that every relevant source was searched. Counsel determines legal scope, privilege and production obligations; GDF documents the technical execution and limitations.
Scope
Source mapping
Connect custodians to mailboxes, shared sites, chat platforms, devices and business applications, including former accounts and third-party owners.
Authorized collections
Agree date ranges, source locations, permissions and export methods. Record failures and sources that require a different acquisition approach.
Processing and handoff
Apply agreed filters and deduplication rules, preserve family relationships where available and reconcile the delivery with the collection manifest.
Evidence commonly reviewed
Evidence reviewed
- Email and collaboration exports with available metadata and attachments.
- Endpoint files and authorized mobile collections, including relevant business messages.
- Search definitions, export logs, exception reports, source identifiers and transfer records.
What you receive
Deliverables
- A custodian/source map and documented collection scope.
- Collection manifests, hash records and an exception log.
- Review-ready exports or load files under the agreed specification, with counts and processing notes.
A collection checklist for distributed Tampa teams
- Identify the account: Record the custodian, tenant, mailbox or site identifier and the person authorized to grant access.
- Check retention: Ask about account departures, deletion settings, expiring links and sources that are no longer active. Do not change settings without the responsible owner and counsel.
- Test the export: Use a small authorized sample to check attachments, message context, timestamps and the receiving platform's requirements.
- Track rolling collections: Record the source, date window and batch identifier so later deliveries can be reconciled without losing custodian associations.
- Close the exceptions: Identify unavailable records, inaccessible containers and processing errors rather than hiding them in an overall success count.
A chat export may reference a file stored elsewhere. Collecting the message alone may not preserve that file or the version available at the relevant time. Source mapping should account for those relationships. Microsoft Purview capabilities also depend on the source, permissions and licensing in the actual tenant; a product name is not a guarantee of complete coverage.
Frequently asked
Questions about Tampa eDiscovery Collections
Can collections be targeted rather than full-device acquisitions?
Often, yes. The method depends on the question, source capabilities and preservation requirements. Targeted collection reduces unrelated data but must record its filters and the material it could not capture.
Does GDF decide what is privileged or legally responsive?
No. Counsel directs those decisions. GDF can apply documented technical criteria and provide processing information to support the review workflow.
What should we confirm before a production handoff?
Confirm the receiving platform, file formats, metadata fields, family handling, numbering instructions and exception process with the responsible review team. Validate a sample before the full delivery.
Plan the custodians, sources and collection deadline
Identify the custodians, source platforms and intended review destination. Share the collection timetable and any account scheduled for closure. Confirm access and secure delivery arrangements before sending case records.
Talk with an examiner
Discuss the matter and the next step.
Call to discuss timing, scope and the safest way to share information. Do not send evidence or credentials by email.
24/7 hotline: 1-800-868-8189