Legal Document Formatting Guidelines: Rules & Checklist
Legal Document Formatting Guidelines: Rules & Checklist
Legal content overseen by Nathan Walter, Esq., attorney licensed in California (State Bar No. 313299).
A defense team reusing a template from the last matter has to know which settings are rules and which are habits. Legal document formatting guidelines start with the rule that governs the court and the document, and font, margin and numbering choices follow from it.
This article covers how to find that rule, how requirements change with the document type, and a Word checklist for the review before service or filing. The examples come from the Federal Rules of Civil Procedure (FRCP), the Federal Rules of Appellate Procedure (FRAP) and the California Rules of Court.
It is written for teams that prepare federal discovery responses and other litigation papers, including discovery workflows for defense firms.
Legal document formatting guidelines start with the governing rule
For each formatting setting, identify its authority: a governing rule, statute, order or applicable filing instruction. Record firm preferences separately, and do not treat a template setting carried over from an earlier matter as proof of a court requirement.
Identify the court, document and destination
Three facts decide which rules to look up:
- Court: a federal district court, a federal court of appeals or a state court, and which one.
- Document: a pleading, a discovery response, a brief or a motion.
- Destination: service on another party, filing with the court or a document production.
The same Word file can face different requirements at each stage, and a template accepted in one court says nothing about another.
Build a source-backed checklist
For each document class your team prepares, record:
- The official URL of the rule, local rule or order.
- The subsection that states the requirement.
- The effective date or version you checked.
- The exact setting, with any exception the rule states.
Keep firm preferences on a separate list. A prior accepted filing is not authority for a setting, because the court, judge or document type may have been different.
Find the rules that apply to this document
Check national rules, local rules and case orders
For civil proceedings in the federal district courts, the FRCP provide the national procedural rules, and districts may adopt local rules governing their practice. FRCP 83(a)(1) says that “a local rule must be consistent with—but not duplicate—federal statutes and rules adopted under 28 U.S.C. §§2072 and 2075.” A local rule therefore sits alongside the national rules and has to be consistent with them.
Individual judges can also regulate practice. Under FRCP 83(b), “a judge may regulate practice in any manner consistent with federal law, rules adopted under 28 U.S.C. §§2072 and 2075, and the district’s local rules.” For formatting, the places to look are the court’s local rules, any standing order from the assigned judge, any case-specific order and the court’s electronic filing instructions.
Recognize that state requirements differ
State courts set their own formatting rules, and those can differ from the federal rules on the same point. Three California Rules of Court show how specific they can be:
- Font size, Rule 2.104: “Unless otherwise specified in these rules, all papers filed must be prepared using a font size not smaller than 12 points.” That is a minimum with an exception, not an exact size for every paper.
- Margins, Rule 2.107: “The left margin of each page must be at least one inch from the left edge and the right margin at least 1/2 inch from the right edge.”
- First page, Rule 2.111: the first page must have, “in the first 2 inches of space between lines 1 and 7 to the right of the center of the page, a blank space for the use of the clerk,” and, “on line 8, at or below 3 1/3 inches from the top of the page, the title of the court.”
Rule 2.111 lists further first-page items beyond these two. Under Rule 2.100(b), this chapter governs papers to be filed in California trial courts. Do not carry these settings into another court or document class without checking its rules.
Match the format to the document class
Pleadings: captions and numbered paragraphs
FRCP 10(a) provides that “every pleading must have a caption with the court’s name, a title, a file number, and a Rule 7(a) designation.” It also says that “the title of the complaint must name all the parties; the title of other pleadings, after naming the first party on each side, may refer generally to other parties.”
FRCP 10(b) adds that “a party must state its claims or defenses in numbered paragraphs, each limited as far as practicable to a single set of circumstances.” For those claims or defenses, bullets do not replace the numbered paragraphs the rule requires. Use automatic numbering as a drafting aid, then recheck the sequence after moving paragraphs.
Rule 10 addresses pleadings, but document labels do not settle every form requirement. FRCP 7(b)(2) states: “The rules governing captions and other matters of form in pleadings apply to motions and other papers.” Check that provision along with the rules governing the particular document.
Discovery responses: keep each answer tied to its request
For interrogatories, FRCP 33(b)(3) states that “each interrogatory must, to the extent it is not objected to, be answered separately and fully in writing under oath.” Under FRCP 33(b)(5), “the person who makes the answers must sign them, and the attorney who objects must sign any objections.” For a practical review of interrogatory answers and signatures, keep each answer visibly tied to its interrogatory and check the required signatures: the person making the answers signs them, and an attorney who objects signs the objections. Placing each answer below its interrogatory is a layout choice, not a format prescribed by these subsections.
For requests for production (RFPs), FRCP 34(b)(2)(B) provides that “for each item or category, the response must either state that inspection and related activities will be permitted as requested or state with specificity the grounds for objecting to the request, including the reasons.” Placing each response directly after its request number makes that item-by-item check straightforward. The rule does not prescribe a typeface or a method of reproducing the request text. The response side is covered in more detail in requests for production.
Review the written response separately from the documents to be produced. For electronically stored information, check the requested form, any form objection stated under Rule 34(b)(2)(D), and any stipulation or court order before converting files.
Briefs: use the correct briefing rules
Briefs in the federal courts of appeals follow FRAP 32. It is one example of a document-specific rule and is not a formatting rule for district-court motions. FRAP 32(a)(4) provides:
- “The brief must be on 8 1/2 by 11 inch paper.”
- “The text must be double-spaced, but quotations more than two lines long may be indented and single-spaced. Headings and footnotes may be single-spaced.”
- “Margins must be at least one inch on all four sides. Page numbers may be placed in the margins, but no text may appear there.”
FRAP 32(a)(5) permits “either a proportionally spaced or a monospaced face.” Under 32(a)(5)(A), “a proportionally spaced face must include serifs, but sans-serif type may be used in headings and captions. A proportionally spaced face must be 14-point or larger.” Under 32(a)(5)(B), “a monospaced face may not contain more than 10 1/2 characters per inch.” Under FRAP 32(a)(6), “case names must be italicized or underlined.”
These are federal appellate-brief requirements, not a universal template. FRAP 32(e) also permits a court of appeals, by local rule or an order in a particular case, to accept documents that do not meet all of Rule 32’s form requirements.
Apply the verified settings in Word
Word’s menus differ between versions and platforms, so what follows is a workflow and not a legal requirement.
Set page layout and paragraph styles
Set the verified paper size and margins in the document’s page layout, then check the font and paragraph spacing for each type of text. Inspect body text, quotations, headings, footnotes and the caption separately. FRAP 32(a)(4) permits single-spaced headings and footnotes and allows quotations more than two lines long to be indented and single-spaced; it otherwise requires double-spaced text.
In Word for Windows, applying heading styles to body headings makes them appear in the Navigation pane. Treat that as a drafting aid and check filing requirements separately.
Control numbering and page sections
Use automatic numbering and automatic page numbers, then inspect these settings separately:
- paragraph-list numbering, including any intended restarts;
- page-number starting values in each section;
- header and footer links to the previous section;
- the header, footer and page number displayed on each section’s first page.
Microsoft explains how to set page-number formats and starting values by section. Its Link to Previous guidance distinguishes linked header and footer types, while Different First Page allows separate first-page treatment. If a rule or court instruction specifies where page numbers go, enter that setting and compare it against the printed or exported pages.
Check citations and cross-references
Update fields and cross-references, along with any table of contents or table of authorities the document needs, then compare them with the visible pages. Check each citation to a rule or record against its source, and add any court-specific citation requirement to the checklist from the first section.
Review the release copy without changing the evidence
A working draft may contain edits, comments and revision information. The version that leaves the firm is a release copy, and it should be a separate file from any original or client evidence.
Resolve draft markup on a copy
Accepting or rejecting tracked changes is a drafting decision, and hiding markup on screen is a separate action. On a copy of the file, resolve the edits the attorney has approved, read any comments and look for hidden text before release. Microsoft’s Document Inspector guidance recommends inspecting a copy because removed data cannot always be restored; its checks also have limits. Do not run a blanket cleaning step over the original file, a client’s documents or a native production. The attorney decides what may be removed, and the governing production requirements come first.
Keep production-format decisions separate
Production form is set by the rules and by the parties. Under FRCP 34(b)(1)(C), a request “may specify the form or forms in which electronically stored information is to be produced.” Under 34(b)(2)(D), “if the responding party objects to a requested form—or if no form was specified in the request—the party must state the form or forms it intends to use.” Under 34(b)(2)(E)(ii), “if a request does not specify a form for producing electronically stored information, a party must produce it in a form or forms in which it is ordinarily maintained or in a reasonably usable form or forms.” Those procedures apply, in the words of 34(b)(2)(E), “unless otherwise stipulated or ordered by the court.”
Converting files or stripping metadata is therefore a production-form decision to check against the request, any agreement and any order. See how to organize discovery documents for production for the document side of that work.
Run a final document-to-PDF check
Compare the exported file with the approved draft
These checks are technical, not jurisdictional requirements. Run them on the file you will send, since export can change how a document looks:
- Read the caption and first page of the exported file.
- Confirm the page sequence and that no page is missing.
- Look for broken cross-references, clipped text and changed fonts or page breaks.
- If redactions are involved, arrange a separate review of the release copy using the redaction tool’s documented checks; this formatting checklist is not a redaction-validation procedure.
- Test whether the text can be selected and searched, rather than assuming it can.
Confirm destination requirements and sign-off
Check the court’s or recipient’s file specifications, the filename convention for the matter, and any signature or verification the document needs. A filename pattern and version labels are the team’s own convention unless an instruction says otherwise. The attorney responsible for the document gives the last review.
Draft editable discovery responses with Briefpoint
Briefpoint drafts responses and objections to interrogatories, requests for production and requests for admission. The output is editable discovery response drafts in Microsoft Word, and attorneys keep final review.
Because the draft arrives in a Word file your team can edit, the document-class checks, the style settings for the governing rule and the PDF comparison all happen in the file the attorney is already reviewing. Your team remains responsible for identifying the governing formatting requirements and reviewing the draft before release.
For the handoff, keep the rule checklist beside the editable draft. Record which document class you reviewed, which settings you checked and which release copy the attorney approved. That gives the next reviewer a specific file and checklist to compare, rather than an unexplained template.
Book a demo to see Briefpoint’s editable Word discovery responses.
See Briefpoint in action:
FAQs About Legal Document Formatting Guidelines
Can I reuse a legal document template from another case?
A template can be a starting point, but its settings need checking against the court and document in the new matter. FRAP 32’s 14-point minimum for proportionally spaced faces and California Rule 2.104’s 12-point minimum, unless otherwise specified, illustrate why scope and exceptions matter. A fresh-matter checklist of court, document, destination, rule subsection and exact setting separates firm preferences from rule requirements.
Why does numbering change when I paste text into Word?
Pasted text can bring source formatting or adopt the destination list’s numbering, depending on the paste option. Microsoft’s paste guidance distinguishes Continue List from New List, which keeps the inserted items’ original sequence. Compare the source and destination styles, inspect the chosen option, and recheck any numbered claims or defenses required by FRCP 10(b).
Does hiding tracked changes remove them from a Word file?
No. Microsoft explains that No Markup only temporarily hides tracked changes; removing them requires accepting or rejecting them. A file may also hold comments and other revision data, so review a copy for markup before release. The attorney decides what may be removed under the governing production requirements.
Why does a legal document look different after PDF export?
Font substitution is one possible reason a PDF looks different. Microsoft’s Word-to-PDF guidance explains that a PDF reader might substitute another font when a font cannot be embedded and the bitmap-text option is not selected. Compare the exported file with the approved draft, checking the caption, page sequence, footnotes and clipped text rather than assuming the export preserved every detail.
Can court papers be submitted electronically instead of on paper?
Check the requirements for the specific court and document rather than treating electronic submission as an automatic option. For a federal civil matter, consult the court’s filing instructions alongside the governing rules and orders. FRCP 83 requires consistency with federal law and rules; it does not itself answer whether your particular paper must or may be filed electronically.
The information provided on this website does not, and is not intended to, constitute legal advice; instead, all information, content, and materials available on this site are for general informational purposes only. Information on this website may not constitute the most up-to-date legal or other information. This website contains links to other third-party websites. Such links are only for the convenience of the reader, user or browser. Readers of this website should contact their attorney to obtain advice with respect to any particular legal matter. No reader, user, or browser of this site should act or refrain from acting on the basis of information on this site without first seeking legal advice from counsel in the relevant jurisdiction. Only your individual attorney can provide assurances that the information contained herein – and your interpretation of it – is applicable or appropriate to your particular situation. Use of, and access to, this website or any of the links or resources contained within the site do not create an attorney-client relationship between the reader, user, or browser and website authors, contributors, contributing law firms, or committee members and their respective employers.
READ MOREAI for Lawyers and How It Affects the Future of the Industry
7 Best Ways to Use AI for Legal Discovery
How to Organize Discovery Documents for Production
How to Organize Discovery Documents for Production
Legal content overseen by Nathan Walter, Esq., attorney licensed in California (State Bar No. 313299).
Here is how to organize discovery documents for production: keep your preserved originals, review copies and released productions in separate places, give every document a stable ID, and map each responsive file to the requests it answers. The production then comes from a set you can identify, not from whatever sits in a working folder.
This guide covers federal civil practice under the Federal Rules of Civil Procedure (FRCP).
It is written for discovery workflows for defense firms: litigation teams, paralegals and litigation-support staff handling client records and incoming productions. It walks through five steps and ends with a handoff manifest.
How to organize discovery documents under federal rules
The federal rules set outcomes. They do not prescribe a filing system, so build your internal method around what the rules require and keep the method distinct from the requirement.
Choose the production method before building the export
Scope comes first. Under Rule 26(b)(1), unless limited by court order, parties may obtain discovery regarding “any nonprivileged matter that is relevant to any party’s claim or defense and proportional to the needs of the case.” Collecting a file does not make it producible, so your organization needs a place to record what was reviewed and what was found responsive.
A request for production (RFP) reaches items “in the responding party’s possession, custody, or control,” and Rule 34(a)(1) lists electronically stored information (ESI) such as writings, photographs, sound recordings and images. A search of one local drive does not by itself answer whether a source falls within that standard.
Then comes presentation. Unless otherwise stipulated or ordered by the court, Rule 34(b)(2)(E)(i) says a party “must produce documents as they are kept in the usual course of business or must organize and label them to correspond to the categories in the request.” Those are two alternatives. A folder assembled for the litigation may not reflect how the documents were kept in the usual course of business, so a team relying on the first alternative needs to know how the source was actually kept.
A request-by-request map is an internal control. The rule does not require request-by-request Bates ranges, and Bates numbers (unique page identifiers) alone do not show that a production complies. For more on the requests themselves, see our guide to requests for production.
State rules
This guide covers federal practice. State rules and local rules may differ, and a stipulation or court order can change the procedure in any matter. For a state-specific process on a different discovery device, see responding to interrogatories in California.
1. Preserve source files and record each intake
Start with an intake register for the matter. Each time documents arrive, whether from a client, a custodian, a records vendor or the other side, record one row before anyone works on the files.
Create an intake register
Record these fields at intake:
- Source and custodian: who or what system the documents came from.
- Received date and method: email, secure portal, drive or paper.
- Original name and path: exactly as received, in its own field.
- Document ID: your internal identifier, assigned at intake.
- Existing production numbers: any Bates numbers already on documents from another party.
- Physical location: for paper, so the original can be found after scanning.
Keep native files and original source sets in a preserved folder that nobody works in. Review happens on copies. Keep the paper original after it is scanned.
Separate incoming from outgoing material
Treat client collections, opposing productions and your own production copies as three different kinds of material. Documents received from another party keep the production numbers they arrived with. If you need your own identifier, add it in a cross-reference column rather than restamping what the other side produced.
If ESI “that should have been preserved in the anticipation or conduct of litigation is lost because a party failed to take reasonable steps to preserve it” and it cannot be restored or replaced through additional discovery, Rule 37(e) allows the court to act. On a finding of prejudice, measures are limited to those “no greater than necessary to cure the prejudice.” Adverse presumptions, adverse-inference instructions, dismissal or default require a finding of intent to deprive. Deletion decisions belong to the responsible attorney.
2. Build working folders and consistent names
Organize files by matter, then by stage. Keep the structure shallow enough that anyone on the team can find a file, and add a folder only when it has a job.
Separate originals, review and released productions
A workable top level for one matter:
- Requests received, and responses (drafts and served versions in separate subfolders)
- Collected originals, read-only
- Review copies
- Restricted review, for items under privilege review
- Production batches, one subfolder per release
Outgoing folder names do not replace source context. A file in a production batch should still trace back to its intake row.
Use stable IDs rather than “final-final”
Pick one naming format and apply it to every working copy: matter, document type, date and internal ID, as in MAT042_Email_2026-02-14_DOC00127.pdf. The internal ID is what stays constant when a file moves between folders. Keep the source filename in the intake register, and do not rename the originals.
One team role, such as a litigation-support lead, maintains the index, and the attorney controls release. Limit access by role. That is a workflow safeguard that helps keep review material out of production folders. It is not a guarantee that privilege is preserved.
Use your firm’s approved encrypted sharing tools for sensitive discovery files. Keep backups and periodically test restoration so the team can recover its preserved sources and released sets.
3. Map responsive files to request categories
Review turns collected files into a set you can describe. Our overview of legal document review covers the review workflow itself; this section covers the records that workflow feeds.
Keep document and request records distinct
A request can have many responsive documents, and one document can answer several requests, so a folder cannot hold the answer by itself. Keep two kinds of record instead.
The document record carries the document ID, custodian, review status, associated request numbers, privilege decision state, production batch and Bates or native identifier. Review status takes one of four values: unreviewed, responsive, nonresponsive or privilege decision pending.
The request record carries the request number or category, its search status and any exceptions. Search status takes values such as search pending, search completed or no responsive material located. That last value belongs on the request record, not on a document row. It records that a search was done, which is different from a certification that nothing exists.
A defense-firm request-to-document example
These examples are invented. A defense firm is responding to a plaintiff’s first set of requests for production in a warehouse-injury case, and its client is “Acme.”
RFP set 1, no. 7
Batch P01
Responsive range: ACME000101–ACME000108
Context: Inspection records; entry on ACME000104.
RFP set 1, no. 12
Batch P01
Responsive range: ACME000104–ACME000106
Context: Same pages as no. 7, produced once.
RFP set 1, no. 15
Batch P01
Responsive file: DOC00342, native spreadsheet.
Context: Image cross-reference added if the governing protocol calls for images.
The first two entries show one set of pages answering two requests without a second copy in a second folder. The third entry points to a native file by its internal ID.
The index supports the written response and does not replace it. Rule 34(b)(2)(B) governs what the response must say, and the index is not a privilege log either. The example is also an internal view: attorney notes, privilege-review drafts and unreleased documents stay out of anything built from it for the other side.
4. Separate privilege decisions and confirm ESI form
Maintain a restricted withholding track
Keep documents with a pending privilege decision in the restricted review folder, outside any production queue. Under Rule 26(b)(5)(A), a party that withholds otherwise discoverable information as privileged or as trial-preparation material must expressly make the claim and describe the nature of what was withheld “in a manner that, without revealing information itself privileged or protected, will enable other parties to assess the claim.”
Under Rule 34(b)(2)(C), an objection “must state whether any responsive materials are being withheld on the basis of that objection,” so the withheld set has to be identifiable. Internal privilege tags are working notes. They are not a served privilege log, and whether a particular record is protected is a question for counsel.
Record the form each file will take
Under Rule 34(b)(2)(D), if the responding party objects to a requested form for ESI, or if the request specifies none, the party “must state the form or forms it intends to use.” Unless otherwise stipulated or ordered, Rule 34(b)(2)(E)(ii)–(iii) adds two points: if a request does not specify a form, ESI must be produced in a form or forms in which it is ordinarily maintained or in a reasonably usable form or forms, and the same ESI need not be produced in more than one form.
A form field on each document record keeps this from being decided by filename convenience. Capture the requested form, any objection and intended form, the governing stipulation or order, and the native ID. Nothing in these provisions means every file becomes a PDF or that native production is always required. Where the parties negotiate the details, see our guide to creating an ESI protocol.
5. Assemble the production handoff
Create a batch manifest
The manifest is the organizational output of this process. For each batch, record the batch ID and date, each produced filename, and its Bates range or native identifier. If you organize and label by request category, add the approved category labels. Stamping and numbering conventions are covered in Bates numbering best practices.
Inspection records
Batch P01 — PDF
Produced filename: inspection.pdf
Bates range: ACME000101–ACME000108
Warehouse schedule
Batch P01 — native spreadsheet
Produced filename: schedule.xlsx
Native ID: DOC00342
Keep release records separate from review notes
Retain the copy that was released and a record of its delivery. Later batches get their own identifiers and never overwrite the earlier release.
If later-located material changes the picture, Rule 26(e)(1) applies. A party that has responded to a request for production must supplement or correct its response “in a timely manner if the party learns that in some material respect the disclosure or response is incomplete or incorrect,” if the additional or corrective information has not otherwise been made known to the other parties during the discovery process or in writing, or as the court orders. The rule does not set one number of days.
For the final attorney review of responses and production, use the discovery checklist.
Common discovery organization mistakes
Habits that undercut an organized set:
- Moving originals into production folders, so the preserved set changes.
- Losing the source ID when a file is renamed for production.
- Using one status field for both document review and request search.
- Leaving unresolved privilege candidates in a batch folder.
- Treating the index as proof that every responsive document was found.
Find and cite responsive documents with Briefpoint
Briefpoint drafts responses and objections to interrogatories, requests for production and requests for admission. The output is editable in Microsoft Word, so the attorney can revise a draft against your organized record before anything is served, and attorneys keep final review.
Autodoc finds responsive documents, adds page-level Bates citations and builds a Bates-numbered production package. Once your team has organized its sources and request categories, that gives the reviewing attorney page references to check against the index and the manifest. The index, the folder structure and the decisions about form and privilege remain with your team and the responsible attorney.
During that review, compare each cited page with the source record and keep any unresolved document question open for the responsible attorney.
Book a demo to see how Briefpoint supports discovery drafting and production preparation.
Watch the Briefpoint demo:
FAQs About How to Organize Discovery Documents
Can I use Excel to organize discovery documents?
Yes, as an index. A spreadsheet can hold document IDs, custodians, review status, request numbers and batch identifiers, but it does not replace a repository for the files, and it does not show that a production complies with Rule 34. Store document IDs as text so an ID such as 00127 keeps its leading zeros, and control who can edit the current version.
How do I keep emails and attachments connected during discovery?
Give each email and each attachment its own document ID, then tie them together with a shared family ID or parent and child fields rather than similar file names. An attachment may need its own review decision, so it gets its own row. If an attachment cannot be located or opened, record it as an exception for attorney review.
Should I organize discovery documents chronologically or by custodian?
Neither has to be the master structure. Keep one copy of each document and treat date and custodian as sortable fields, so the same set can be viewed either way without duplicates. Record the source even when you sort by date. If a document’s date is unknown, enter “unknown date” instead of guessing, so a later reviewer can tell an estimate from a fact.
How should I track audio and video files in a discovery index?
Give each recording a stable file ID, its original filename, its source location and, where useful, a duration or time-stamped segment reference. Rule 34(a)(1)(A) lists sound recordings and images among the items a request may reach, but page-level Bates numbers usually do not fit them, so a file-level identifier does the work. How much detail to index is a workflow choice.
The information provided on this website does not, and is not intended to, constitute legal advice; instead, all information, content, and materials available on this site are for general informational purposes only. Information on this website may not constitute the most up-to-date legal or other information. This website contains links to other third-party websites. Such links are only for the convenience of the reader, user or browser. Readers of this website should contact their attorney to obtain advice with respect to any particular legal matter. No reader, user, or browser of this site should act or refrain from acting on the basis of information on this site without first seeking legal advice from counsel in the relevant jurisdiction. Only your individual attorney can provide assurances that the information contained herein – and your interpretation of it – is applicable or appropriate to your particular situation. Use of, and access to, this website or any of the links or resources contained within the site do not create an attorney-client relationship between the reader, user, or browser and website authors, contributors, contributing law firms, or committee members and their respective employers.
READ MOREUnderstanding eDiscovery Costs and How to Manage Them
What Happens During the Litigation Process?
Sample Response to Request for Production of Documents
Sample Response to Request for Production of Documents
Legal content overseen by Nathan Walter, Esq., attorney licensed in California (State Bar No. 313299).
Under FRCP 34(b)(2)(B)–(C), a federal response must address each item or category by permitting inspection as requested or stating specific objection grounds and reasons. An objection must say whether responsive materials are withheld on that basis. If you elect to produce copies, production must finish by the requested inspection time or another reasonable time specified in the response.
This sample response to request for production of documents walks through six federal patterns, with the rule behind each sentence.
For background, see federal requests for production and written discovery responses.
What a federal production response must say
A request, a written response and the production itself are three separate events. The written response says what will be produced, what is objected to and what is withheld. The production is the delivery of documents or electronically stored information (ESI).
Under Federal Rule of Civil Procedure (FRCP) 34(a)(1), a party may request items “in the responding party’s possession, custody, or control.” The request must fall within the scope of Rule 26(b). That scope covers any nonprivileged matter that is relevant to a party’s claim or defense and proportional to the needs of the case, weighing factors such as the amount in controversy, the parties’ relative access to information and whether the burden outweighs the likely benefit (FRCP 26(b)(1)).
For the requesting side, see these examples of document requests.
Match each response to the request
FRCP 34(b)(2)(B) requires a response “for each item or category.” The response must either state that inspection and related activities will be permitted as requested or state with specificity the grounds for objecting, including the reasons. A party may say it will produce copies instead, and production must then be completed by the time stated in the request or another reasonable time specified in the response.
Under Rule 34(b)(2)(C), an objection must state whether any responsive materials are being withheld on the basis of that objection. An objection to part of a request must specify the part and permit inspection of the rest.
A practical skeleton follows. It is a drafting habit, not a form the rule prescribes:
- Restate the request number.
- State what will be or has been produced, with Bates references (page-level identifiers stamped on each produced page).
- If objecting, state the specific ground and the reasons.
- State whether responsive materials are withheld on that objection.
- State when production is or will be complete.
Separate confidentiality from privilege
Confidentiality and privilege are different things in the rules. A privilege or trial-preparation protection is asserted under FRCP 26(b)(5)(A): the party must expressly make the claim and describe what was withheld so that other parties can assess the claim without learning the protected content.
Confidentiality is addressed through protective measures. Under FRCP 26(c)(1), a party may move for a protective order, and the court may issue one for good cause, including one requiring that a trade secret or other confidential commercial information be revealed only in a specified way (Rule 26(c)(1)(G)). The rule text does not make “confidential” a stand-alone reason to withhold documents.
Federal response and production deadlines
The written response, the delivery of copies and a stipulated extension are governed by different parts of the rules.
| Event | Timing | Authority |
|---|---|---|
| Written response to a request | Within 30 days after service | FRCP 34(b)(2)(A) |
| Response to an early request delivered under Rule 26(d)(2) | Within 30 days after the first Rule 26(f) conference | FRCP 26(d)(2); 34(b)(2)(A) |
| Completing production of copies | By the inspection time in the request, or another reasonable time specified in the response | FRCP 34(b)(2)(B) |
| Different response time | As stipulated under Rule 29 or ordered by the court | FRCP 34(b)(2)(A) |
| Stipulation that interferes with discovery, motion or trial dates | Needs court approval | FRCP 29(b) |
More time requires the right mechanism
Rule 34(b)(2)(A) says a shorter or longer response time may be stipulated under FRCP 29 or ordered by the court. Rule 29(b) adds that a stipulation extending the time for any form of discovery must have court approval if it would interfere with the time set for completing discovery, for hearing a motion, or for trial.
A separate question is when production is completed. Rule 34(b)(2)(B) lets the response specify another reasonable time for completing production. That is not a way to postpone the written response itself, and any scheduling order still applies. The rules set no automatic grace period.
Sample response to request for production of documents
The following examples are invented and illustrate federal response drafting; they are not court-approved forms. Bates ranges and dates are made up.
1. Full production with Bates references
Employment case, plaintiff responding. Request No. 1: Produce Plaintiff’s offer letter and signed employment agreement.
Response to Request No. 1: Plaintiff produces the responsive documents in Plaintiff’s possession, custody, or control at PLA000001–PLA000012. Production in response to this request is complete. No responsive materials are withheld.
The response names the location and says production is complete. It uses the present tense because the documents go out with it. Bates numbering is a common practice, not a Rule 34 requirement. The authority is FRCP 34(a)(1) and (b)(2)(B).
2. Partial production with a withholding statement
Employment case, plaintiff responding. Request No. 4: Produce all communications concerning any job application Plaintiff submitted at any time in the last ten years.
Response to Request No. 4: Plaintiff objects to this request to the extent it seeks communications about applications outside the period from January 1, 2024 to the present. Plaintiff objects that earlier applications concern unrelated positions and do not bear on the pleaded claims or defenses. Collecting those communications would require restoring eight years of archived accounts, imposing expense disproportionate to their likely benefit in this case. Plaintiff is withholding communications about applications submitted before January 1, 2024 on the basis of this objection. Plaintiff produces all other responsive communications at PLA000013–PLA000045. Production in response to this request is complete.
This pattern follows Rule 34(b)(2)(C): the objection names the part challenged and says what is held back, and the rest is produced. The example assumes the stated relevance and retrieval facts support the objection; the lost-wage period alone does not establish the proper discovery boundary under Rule 26(b)(1). This objection does not involve privilege.
3. A specific objection followed by production
Employment case, employer responding. Request No. 7: Produce payroll records for Plaintiff, in image-only PDF form.
Response to Request No. 7: Defendant objects to the requested form of production. The payroll records are kept as spreadsheets, and converting them to image-only PDFs would remove the formulas and sortable data that make them usable. Defendant will produce the records in native XLSX format, identified as DEF-PAY001 through DEF-PAY003, on November 18, 2026. No responsive materials are withheld on the basis of this objection.
Rule 34(b)(2)(D) permits an objection to a requested form for ESI, and when a party objects it must state the form it intends to use. Here the objection is about format only, and the response says plainly that nothing is being held back. Native files are not Bates-stamped page by page the way images are, so the response identifies them by file designation. The form can still be resolved by agreement or court order.
4. No responsive documents after a search
Personal injury case, plaintiff responding. Request No. 3: Produce all photographs Plaintiff took on the date of the incident.
Response to Request No. 3: Plaintiff searched the photo library on Plaintiff’s phone, Plaintiff’s cloud photo account and Plaintiff’s paper files for photographs taken on the date of the incident. Plaintiff located no responsive documents in Plaintiff’s possession, custody, or control. No responsive materials are withheld on the basis of any objection.
A response like this should describe the search actually done, and it fits only once the search is finished. It does not mean the photographs never existed. Rule 34 does not prescribe the phrase “diligent search.”
If the party later learns the response is incomplete or incorrect in a material respect, FRCP 26(e)(1) requires a timely supplement, unless the correct information has already been made known to the other parties during discovery or in writing. The authority for the response itself is Rule 34(a)(1) and (b)(2)(B).
5. Privileged documents identified in a log
Employment case, employer responding. Request No. 9: Produce all communications concerning the decision to terminate Plaintiff.
Response to Request No. 9: Defendant produces non-privileged responsive communications at DEF000101–DEF000140. Defendant is withholding three communications on the basis of the attorney-client privilege and expressly asserts that privilege as to them. Those communications are described in entries 1 through 3 of the privilege log served with this response.
Rule 26(b)(5)(A) requires an express claim and a description of the nature of what was not produced, one that lets the other parties assess the claim without revealing privileged information. The hypothetical assumes counsel has reviewed those three items and concluded they are privileged.
The rule does not prescribe a log format, and a case order may set its own expectations.
6. Rolling production with a stated end date
Business records case, employer responding. Request No. 12: Produce all monthly equipment inspection records for the Springfield facility.
Response to Request No. 12: Defendant will produce responsive records on a rolling basis. Defendant produced the first batch on November 18, 2026 at DEF000201–DEF000260. Defendant will produce a second batch on November 25, 2026, and production will be complete no later than December 2, 2026.
The records are kept in both active and archived systems, and the archived records must be retrieved from offline storage. No responsive materials are withheld on the basis of any objection.
The unproduced batches are scheduled production, not withholding. The response gives dates and a concrete reason for the schedule (archived records in offline storage). Dates alone would not show that the schedule is reasonable. The sample assumes the schedule fits the scheduling order and has been agreed to; real wording should identify any actual stipulation or order.
Rule 34(b)(2)(B) allows completion by the inspection time or another reasonable time specified in the response. An extension of the written-response deadline runs through Rule 34(b)(2)(A) and Rule 29(b), and a message saying “we need 14 more days” is not a stipulated extension.
Check the documents against the written response
Before service, the documents and the written response should say the same thing. This checklist is a drafting aid, not a list of rule requirements:
- Bates ranges: confirm each range in the response matches files that actually exist in the production.
- Form and organization: check the applicable stipulation or order. Otherwise, Rule 34(b)(2)(E)(i) requires documents as kept in the usual course of business or organized and labelled to the request categories. State the ESI form where Rule 34(b)(2)(D) requires it.
- Withholding: confirm every objection says whether materials are withheld on it, and every redaction or withholding has a stated basis.
- Privilege entries: confirm each item described in the response appears in the log.
- “Subject to” language: “subject to and without waiving” should not leave the reader unable to tell whether documents are withheld.
- Incomplete search versus none found: keep them separate. “No responsive documents” should follow a completed search, not stand in for one still underway.
- Supplementation: note the Rule 26(e)(1) duty to supplement.
A cover letter can be a convenient way to transmit a production, but it does not replace the item-by-item response. For help with file organization, see how to organize discovery documents.
State rules
These examples apply the Federal Rules of Civil Procedure. They are not state-specific forms, and state courts have their own requirements that must be checked separately.
For two state-level guides, see responding to requests for production in Texas and Florida requests for production.
Draft production responses with Briefpoint
Briefpoint drafts responses and objections to requests for production, interrogatories and requests for admission. Output is editable in Microsoft Word, and attorneys keep final review of every response before it is served.
For document-heavy requests, Autodoc finds responsive documents, adds page-level Bates citations and builds a Bates-numbered production package. Client Bridge sends clients plain-language questions through a secure link so they can answer and upload documents for attorney review.
Briefpoint supports all 50 states and 98 federal courts. Whether a particular objection, privilege claim or production schedule is appropriate remains the attorney’s decision. During final review, compare each draft response with the request, the records selected for production and any stated withholding.
Book a demo to see Briefpoint’s discovery-response workflow.
Watch the Briefpoint demo:
FAQs About a Sample Response to Request for Production of Documents
How do you respond to a request for production of documents?
Respond in writing to each item or category by stating that production or inspection will be permitted, or by stating specific grounds and reasons for objecting. Under FRCP 34(b)(2)(B)–(C), each objection must say whether responsive materials are withheld. The written response is separate from the documents themselves, which must be produced by the stated completion time.
How long do you have to respond in federal court?
Ordinarily 30 days after being served, under FRCP 34(b)(2)(A). For an early request delivered under Rule 26(d)(2), the 30 days run from the first Rule 26(f) conference. The parties may stipulate to a different time under Rule 29, or the court may order one. Completing production can follow a separate reasonable date stated in the response.
What do you say if you have no responsive documents?
State accurately that no responsive documents were located in your possession, custody, or control after the search you describe, and that nothing is withheld on an objection. Use that wording only once the search is finished. If the response proves materially incomplete or incorrect, FRCP 26(e)(1) requires a timely supplement, subject to the rule’s exception for information already made known.
How do you identify documents withheld as privileged?
Expressly make the privilege claim and describe the nature of the withheld documents so the other side can assess the claim without seeing protected content, as FRCP 26(b)(5)(A) requires. A privilege log is a common way to do this, but the rule does not set a fixed template. Local rules or case orders may add expectations.
Can you ask for more time or produce documents in batches?
You can seek a stipulated extension of the response time under FRCP 29, subject to court approval if it would interfere with discovery, motion or trial dates. Separately, a response may specify another reasonable time to complete production under Rule 34(b)(2)(B). State a firm completion date.
The information provided on this website does not, and is not intended to, constitute legal advice; instead, all information, content, and materials available on this site are for general informational purposes only. Information on this website may not constitute the most up-to-date legal or other information. This website contains links to other third-party websites. Such links are only for the convenience of the reader, user or browser. Readers of this website should contact their attorney to obtain advice with respect to any particular legal matter. No reader, user, or browser of this site should act or refrain from acting on the basis of information on this site without first seeking legal advice from counsel in the relevant jurisdiction. Only your individual attorney can provide assurances that the information contained herein – and your interpretation of it – is applicable or appropriate to your particular situation. Use of, and access to, this website or any of the links or resources contained within the site do not create an attorney-client relationship between the reader, user, or browser and website authors, contributors, contributing law firms, or committee members and their respective employers.
READ MORE







