How should the parties agree on production formats and metadata fields in an ESI protocol or meet-and-confer?

Production formats and metadata fields are easiest to resolve early, before either side has spent money collecting or processing data. In US federal civil litigation, the rules encourage parties to confer about the form of production near the outset of a case, and many courts expect a written ESI protocol memorializing those agreements. Practices vary by jurisdiction, so confirm what your court, state, or country requires before relying on any single approach. For broader background, see e-discovery.

Decide the form of production

Discuss form by data type rather than picking one format for everything. Common questions to settle:

• Native vs. near-native vs. image plus load file. Spreadsheets, databases, and audio often need native or near-native formats to remain usable; many documents are produced as images with extracted text.
• Searchable text. Whether each document includes extracted or OCR text so the receiving party can search it.
• Bates numbering and redactions. How documents are labeled and how privileged or sensitive material is withheld or masked.

Agree on metadata fields

Rather than demanding “all metadata,” name the specific fields each party will produce and the format for each. Frequently negotiated fields include custodian, file name, file path, author and recipient fields, sent and received dates, last-modified date, file type, and a hash value for deduplication and integrity. Agree on date and time formats and a consistent time zone to avoid downstream confusion.

Address handling and edge cases

A strong protocol also covers items that cause disputes later:

• De-duplication and email threading approaches.
• Treatment of embedded files, attachments, and modern collaboration or messaging data.
• How parent-child relationships (an email and its attachments) are preserved.
• Privilege logging and procedures for clawing back inadvertently produced material.

Keep it collaborative and documented

Approach the meet-and-confer as cooperative problem-solving, not posturing. Bring IT or a technical advisor who understands your systems, and put the agreement in writing so both sides and the court can rely on it. Proportionality matters: tie requested formats and fields to what the case actually needs, and revisit the protocol if new data sources surface.