Skip to main content

4th Cir. Document — Standing Order on Electronically Stored Information

High confidence· verified September 9, 2026Judge Preferences4th Jud. Cir., Standing Order on Electronically Stored Information — sha256-hashed 2026-07-25

A published requirement of Fourth Judicial Circuit Court (Fourth Judicial Circuit, Florida). Category: Judge Preferences. Cited as 4th Jud. Cir., Standing Order on Electronically Stored Information — sha256-hashed 2026-07-25. Verified against the official source (CC-P Civil & Criminal Procedures (Judge Brady) — PDF) on September 9, 2026.

Summary

40 verbatim requirements from Standing Order on Electronically Stored Information.

Applies to

Fourth Judicial Circuit (Duval, Clay, Nassau). Procedural information only; not legal advice.

Requirement

• Plaintiff shall serve this order upon counsel for Defendant within 20 days of the first appearance of counsel for Defendant and shall schedule a meet and confer with counsel for • At the meet and confer, both counsel for Plaintiff and Defendant shall be prepared to discuss in detail, and will actually discuss: a. • Stipulation or Agreed Order, the parties shall present their respective proposed orders to the Court for consideration within 15 days of the meet and confer. • Counsel for the Parties shall jointly prepare and file a short Notice of Compliance confirming they have met the requirements of paragraphs 1 and 2 of this order. • If the Report is filed within 15 days of the meet and confer, counsel for the parties need take no further action to comply with this Order, absent fuither motion by the parties or order of this Court. • If the Notice of Compliance is not filed within l5 days of the meet and confer, Plaintiff shall schedule a l5- minute Case Management Conference pursuant to 1.200(a) to address specific issues that have resulted in the lack of compliance. • Semantic synonyms shall mean without limitation code words, terms, phrases or illustrations, acronyms, abbreviations, or non-language alphanumeric associational references to relevant ESI, or information that may lead to relevant • Nothing in this protocol, or the subsequent designation of any search terms, shall operate to limit a party's obligations under the Florida Rules of Civil Procedure and applicable decisional authority to otherwise search for and produce any requested non-privileged relevant evidence, or information that could lead to relevant evidence. • Where structured data (e.g., data from a database) is requested, appropriate queries will be used to extract relevant data from any such database, which data shall match specified criteria, and returning specified fields, in a form and format that is verifiably responsive and readable by the use of commonly available tools. • If a producing party asserts that certain ESI is inaccessible or otherwise unnecessary or inadvisable under the circumstances, or if the requesting party asserts that, following production, certain ESI is not reasonably usable, the parties shall meet and confer with their respective technology experts to discuss resolving such assertions. • If the parties cannot resolve any such disputes after such a meet and confer has taken place, the issue shall be presented to the Court for resolution. • Unless otherwise agreed to in writing by a requesting party, ESI shall be produced in native data format, together with all associated metadata. • In such cases where production in native format is not possible or advisable (e.9., redacted documents), native format files shall be converted to static images and each page thereof saved electronically as a single page "TIFF" image that reflects how the source document would have appeared if printed out to a printer attached to a computer viewing the file. • Accompanying this TIFF shall be a multipage text (.TXT) file containing searchable text from the native file, and the metadata as discussed later in this document. • If voluminous TIFF production is anticipated, the parties shall meet and confer to determine how such production is to be made reasonably usable by the requesting party. • The parties shall meet and confer to the extent reasonably necessary to facilitate the import and use of the produced materials with commercially available document management or litigation support software. • Documents or records which either were originally generated or instantiated as ESI but now only exist in physical hard-copy format, or documents or records that were originally generated in hard-copy format shall be converted to a single page .TIFF file and produced following the same protocols set forth herein or otherwise agreed to by the parties. • For files or records not produced in their native format, each page of a document shall be electronically saved as an image file. • If a document consists of more than one page, the unitization of the document and any attachments and/or affixed notes shall be maintained as it existed in the original when creating the image files. • ESI with differing file names but identical hash values shall not be considered duplicates. • Exact duplicate shall mean bit-for-bit identicality with both document content together with all associated metadata. • Where any such documents have attachments, hash values must be identical for both the document-plus-attachment (including associated metadata) as well as for any attachment (including associated metadata) standing alone. • For files not produced in their native format, if an original document contains color, the producing party shall produce color image(s) for each such document if reasonably feasible. • For files not produced in their native format, each page of a produced document shall have a legible, unique page identifier ("Bates Number") electronically "burned" onto the TIF image in such a manner that information from the source document is not obliterated, concealed, or interfered with. • There shall be no other legend or stamp placed on the document image unless a document qualifies for confidential treatment pursuant to the terms of a Protective Order entered by this Court in this litigation or has been redacted in accordance with applicable law or Court order. • Any ESI produced in native data format shall be placed in a Logical Evidence Container that is Bates numbered, or the storage device (i.e., CD, USB, hard drive) containing such files shall be so Bates numbered. • Documents shall be produced on CD-ROM, DVD, external hard drive (with standard PC compatible interface), or such other readily accessible computer or electronic media as the parties may hereafter agree upon (the "Production Media"). • The documents contained on the media shall be organized and identified by custodian, where applicable. • For files not produced in their native format, text files for produced documents shall be produced reflecting the full text that has been electronically extracted from the original, native electronic files ("Extracted Text"). • The Extracted Text shall be provided in ASCII text format and shall be labeled and produced on Production Media in accordance with the provisions of paragraph II.H above, "Production Media." The text files will be named with the unique Bates number of the first page of the corresponding document followed by the extension ".txt." • Email attachments and embedded files must be mapped to their parent by the Document or Production number. • If attachments and embedded files are combined with their parent documents, then "BeginAttach" and "EndAttach" fields listing the unique beginning and end number for each attachment or embedded document must be included. • For files not produced in their native format, documents that present imaging or format production problems shall be promptly identified and disclosed to the requesting party; the parties shall then meet and confer to attempt to resolve the problems. • Notwithstanding anything contained herein to the contrary, a producing party shall not produce ESI in a format not requested or designated by the requesting party unless (i) the parties have met and conferred, and, having been unable to resolve such format production conflict at such meet and confer session, (ii) prior to referral to and resolution of such issue by the court. • If a party believes that responsive ESI no longer exists in its original format, or is no longer retrievable, the responding party shall explain where and when it was last retrievable in its original format, and disclose the circumstances surrounding the change in status of that ESI, including the date of such status change, the person or persons responsible for such state change, the reason or reasons such ESI is no longer retrievable in that format, and whether any backup or copy of such original ESI exists, together with the location and the custodian thereof. • The parties shall identifu a person ("Designated ESI Liaison") who is familiar with a party's: • The parties, including the designated ESI person(s), shall meet and confer to the extent necessary to discuss the back-up routine, application, and process and location of storage media, whether the ESI is compressed, encrypted, and the type of device or object in or on which it is recorded (e.g., whether it uses sequential or random access), and whether software that is capable of rendering it into usable form without undue expense is within the party's possession, custody, or control. • The receiving party seeking further information shall explain in writing the need for such information and state precisely each document (by Bates number) for which it seeks this information. • Within fourteen (14) days of such a request, the producing party must either (i) produce a full privilege log for the requested documents or (ii) challenge the request. • If a party challenges a request for further information, the parties shall meet and confer to try to reach a mutually agreeable solution.

Source of truth

Plaintiff shall serve this order upon counsel for Defendant within 20 days of the first appearance of counsel for Defendant and shall schedule a meet and confer with counsel for
Source health
Healthy · checked November 15, 2026
Effective date
—
Last verified
September 9, 2026benchpath-ocr-spacing-2026-09-14 | prior: benchpath-reverify-2026-09-08 (custody hash match) | prior: benchpath-p3-vision-recompose-2026-09-08

Reviewer note: Document sha256: 3e2b93e5173b1ba92eba360c01de310b0387e9f7fe32a2045186cd11b0dab2b6. Extracted from the document's own text layer. Text layer cleaned 2026-09-08 (Phase 3a): page markers removed; wording untouched. Text recomposed 2026-09-08 (Phase 3b): OCR/extractor artifacts corrected verbatim against the official print; wording unchanged. Verbatim from https://www.jud4.org/getContentAsset/87161c7b-3ad3-40bd-81bb-bd72f4fa65cd/135b97c9-84fa-4e82-b956-0fbccec4aa1f/Standing-Order-on-ESI-with-Exhibit-A.pdf?language=en, harvested 2026-07-25; whitespace normalised only. [moved from the text 2026-09-14]

Bond & Pretrial Release

Change history

  • July 16, 2026Monitor: CC-P Civil & Criminal Procedures (Judge Brady) — PDF unreachable (timeout or network error).
  • July 14, 2026Monitor: CC-P Civil & Criminal Procedures (Judge Brady) — PDF unreachable (timeout or network error).

Related rules

Judge PreferencesStatewide · Judge Eric N. Vitaliano

Judge Eric N. Vitaliano (E.D.N.Y.) — Practices and Rules: VI. PROCEDURE FOLLOWING NON-JURY TRIAL

Practices and Rules of Judge Eric N. Vitaliano, U.S. District Court for the Eastern District of New York, as the judge's own court page links it: section VI. PROCEDURE FOLLOWING NON-JURY TRIAL — verbatim from the judge's own document (official PDF, sha-custodied). Judge-specific requirement: applies in cases before this judge alongside the Local Rules and the federal rules.

High confidence· verified November 3, 2026
Judge PreferencesStatewide · Judge Eric R. Komitee

Judge Eric R. Komitee (E.D.N.Y.) — Practices and Rules (CV): I. COMMUNICATIONS

Practices and Rules (CV) of Judge Eric R. Komitee, U.S. District Court for the Eastern District of New York, as the judge's own court page links it: section I. COMMUNICATIONS — verbatim from the judge's own document (official PDF, sha-custodied). Judge-specific requirement: applies in cases before this judge alongside the Local Rules and the federal rules.

High confidence· verified November 3, 2026
Judge PreferencesBroward County · Judge Corey B. Friedman

Seventeenth Cir. — Judge Corey B. Friedman: Judge preferences

1 verbatim requirement on judge preferences.

High confidence· verified September 9, 2026Seventeenth Judicial Circuit (pp. https://www.17th.flcourts.org/division-mn/) — captured and sha256-hashed 2026-07-24
Judge PreferencesStatewide · Judge Eric R. Komitee

Judge Eric R. Komitee (E.D.N.Y.) — Practices and Rules (CV): II. ELECTRONIC CASE FILING (ECF)

Practices and Rules (CV) of Judge Eric R. Komitee, U.S. District Court for the Eastern District of New York, as the judge's own court page links it: section II. ELECTRONIC CASE FILING (ECF) — verbatim from the judge's own document (official PDF, sha-custodied). Judge-specific requirement: applies in cases before this judge alongside the Local Rules and the federal rules.

High confidence· verified November 3, 2026