Middle District of Florida eDiscovery, Collection and Production
Tampa eDiscovery That Follows the Records, Not the Address
A Tampa custodian's messages may sit in a Microsoft 365 tenant run from another state, a Teams channel owned by a former colleague and a personal phone that never touched the company network. Global Digital Forensics maps every one of those sources, collects them under a documented chain of custody and delivers a load whose counts reconcile to the manifest. When the collection method is questioned, the answer is already on paper.
The engagement
Source Mapping Comes Before Any Export
We work with counsel and the authorized system owners to identify every source, preserve the agreed data and document what each collection includes and excludes. The records decide the plan: a custodian who sits in Tampa may keep the relevant messages in a tenant run from elsewhere, a shared site owned by a former colleague or a chat application on a personal device, and the collection has to be built around where the data actually lives.
In the Middle District of Florida, ESI scope gets settled at the Rule 26(f) planning conference and in the case management report that Local Rule 3.02 requires within 40 days after a defendant appears, so we have the source map ready before that conference. The Tampa Division covers Hardee, Hillsborough, Manatee, Pasco, Pinellas, Polk and Sarasota counties, and the records almost never stay inside them. We confirm tenant ownership, administrator access and custodian availability first, then build the collection timetable backward from the court's dates. Call the Tampa office at (813) 305-7969 or the 24/7 hotline at (800) 868-8189 to start.
Preservation, collection, processing and production are separate steps, and we document each one on its own. A legal hold keeps data in place but produces nothing reviewable, and an export covers only the sources that were actually searched. Counsel sets the legal scope, privilege calls and production obligations; our record shows exactly what was done at every technical step and which items needed a different method. The first consultation is free.
If an account is scheduled for closure, that is the first source to map. Call (800) 868-8189 before the closure date rather than after.
Scope
Source mapping
We connect custodians to their mailboxes, shared sites, chat platforms, devices and business applications, including former accounts and sources owned by third parties, so nothing relevant is missed because nobody thought to ask who owned it.
Authorized collections
We agree on the date ranges, source locations, permissions and export methods with the legal team and the system owners, then record every failure and every source that needs a different acquisition approach rather than hiding it in an overall success count.
Processing and handoff
We apply the agreed filters and deduplication rules, preserve family relationships where the source supports them and reconcile the delivery with the collection manifest so the review team receives a load whose counts they can explain.
Evidence commonly reviewed
What a Tampa Collection Gathers
A Tampa collection typically gathers email and collaboration exports with their available metadata and attachments, endpoint files and authorized mobile collections including the relevant business messages, and the search definitions, export logs, exception reports, source identifiers and transfer records that show how each item reached the review set. Those process records matter as much as the documents, because they are what counsel will produce when the other side asks how the collection was done.
What you receive
Deliverables the Review Team Can Load
The engagement delivers a custodian and source map with the documented collection scope, collection manifests with hash records and an exception log, and review ready exports or load files prepared under the agreed specification with counts and processing notes. Each deliverable reconciles to the one before it, so a question about a count in the production can be answered from the manifest rather than from memory.
To see how a manifest reconciles to a production, read the national eDiscovery collections page before the first export.
A Collection Plan for Distributed Tampa Teams
Every collection begins by identifying the account: the custodian, the tenant, the mailbox or site identifier and the person authorized to grant access. We then check retention, asking about departed accounts, deletion settings, expiring links and sources that are no longer active, and we change no setting without the responsible owner and the legal team. A small authorized sample export tests attachments, message context, timestamps and the receiving platform's requirements before the full run, which is how the first full delivery loads cleanly.
Rolling collections are tracked by source, date window and batch identifier so later deliveries reconcile without losing their custodian associations. Exceptions are closed in the open: unavailable records, inaccessible containers and processing errors are identified in the exception log rather than absorbed into a success percentage, because the exception log is the document that protects the producing party when a gap is discovered later.
A chat export may reference a file stored elsewhere, and collecting the message alone may not preserve that file or the version that existed at the relevant time, so source mapping accounts for those relationships. Microsoft Purview adds cloud attachments, SharePoint document versions and full conversation threading to a review set only under premium eDiscovery licensing, so we confirm what the actual tenant can export before the plan depends on it.
Want the sample export run before the full collection is scheduled? Name the custodians and the receiving platform and the sample is where we begin.
Frequently asked
Targeted Collections, Privilege and the Handoff
Can collections be targeted rather than full device acquisitions?
Often, yes. The method depends on the question, the capabilities of the source and the preservation requirements in place. A targeted collection reduces unrelated data and review cost, and it must record its filters and the material it could not capture so the production can be defended later.
Does GDF decide what is privileged or legally responsive?
Counsel makes those calls. We apply documented technical criteria, run the processing and supply the counts, exceptions and field maps the review workflow needs, so every privilege and responsiveness decision rests on a documented population.
What should we confirm before a production handoff?
Confirm the receiving platform, the file formats, the metadata fields, the family handling, the numbering instructions and the exception process with the responsible review team, then validate a sample before the full delivery. A sample that loads cleanly is the cheapest insurance a production can buy.
National Methods and Neighboring Tampa Services
The national service page explains our eDiscovery collection methods and scope in detail.
Return to Tampa computer forensics and security services, or read Microsoft's own account of Purview eDiscovery capabilities.
Name the Custodians, the Platforms and the Deadline
Tell us who the custodians are, where their data lives, which review platform will receive it and when the production is due, and flag any account scheduled for closure. We confirm access and a secure delivery route before a single case record moves.
Prove the Load Works With a Sample Delivery
Bring the actual order, the custodian and source list, the requested date range, the receiving platform and the intended reviewers to the planning call. Provider permissions and licensing are confirmed for each source rather than assumed, because one export rarely covers every source. The manifest identifies each source, its requested range, the collection method, the item and family counts and the failed records, and the field map lists identifiers, custodians, timestamps with their time zone, parent and attachment links and any field the source did not supply.
A trial handoff checks natives, attachments, searchable text and field mapping with an authorized receiving reviewer before the full delivery. Hold configuration is recorded separately from collection, processing and production acceptance, and counsel owns the legal review decisions throughout. Where custodians or systems use different time settings, we preserve the original timestamps and document any normalization in the field map, and we compare source ranges with the requested period before the trial load.
The final exception register lists the missing fields or items and names who resolves each one: a clean sample confirms the format, and the register confirms the coverage. The court and Microsoft publish the references we work from: the Middle District of Florida Tampa Division page · Microsoft Purview eDiscovery capabilities and licensing.
The exception register is only useful if someone owns each line. Tell us who will receive the load and the register names them from the start.
Talk with an examiner
Send the Custodian List and the Deadline
Tell us the custodians, the platforms, the review destination and the production date. A senior examiner checks conflicts and calls you back with a collection sequence, and the request is handled in confidence.
Global Digital Forensics has supported law firms with collections and productions since 1992, with court tested examiners and 24/7 dispatch.
Start here
Give Your Tampa Review Team a Collection They Can Defend
On the first call a senior examiner walks through the custodians and platforms, tells you which sources to secure this week and lays out the collection sequence and timeline against the court's dates. The consultation is free and confidential.
Our 24/7 hotline is (800) 868-8189.
Reviewed by Joseph Caruso, Founder, CEO and CTO, CISSP. Last reviewed .