WalkingPDF

guide

How to write a deficiency letter for a document production

A deficiency letter states what is wrong with a production, where exactly it is wrong, and what you want done about it. Every item needs four things: the observation, the page reference, the request, and a date. Anything that cannot be pointed at a page does not belong in the letter.

What the letter is for

It is not a complaint and it is not a motion. Its job is to put the other side on notice of specific defects, in a form that can be attached to a motion later without being rewritten. That means it has to be specific enough to be answered and calm enough to be answered without a fight.

The letter also protects you. A defect raised in writing, with a date, is the difference between a meet-and-confer that resolves in a week and one that begins with "we were never told".

Four things every item needs

  1. What was observed

    One sentence, mechanical, no adjectives: the production does not contain Bates numbers ABC000118 through ABC000121.

  2. Where it is

    The numbers, the file, the page - whatever a reader needs to open the set and see it without asking you. A defect you cannot locate is a defect they can deny.

  3. What you are asking for

    Produce the missing pages, re-stamp the range, supply the load file, or confirm in writing that the pages do not exist. One ask per item, not a paragraph of alternatives.

  4. By when

    A date. Without one the letter is a description of a problem rather than a request, and the response it earns is silence.

A structure that holds up

  • Open with the production you are responding to: date served, Bates range, and how it was transmitted. That paragraph is what makes the letter admissible in a later argument about what was produced and when.
  • Then the items, numbered continuously, grouped the way a reviewer works a set: load file first, then numbering, then text and images, then families, then redactions. A letter that jumps between categories reads as a list of grievances.
  • Close with the ask as a whole: a supplemental production by a stated date, and a written response to any item you cannot cure.

The sentences that get a response

Write "the production does not appear to contain" rather than "you failed to produce". The first describes what you received; the second asserts an intention you cannot prove, and it invites a reply about your tone instead of the missing pages.

Keep the counts. "Fourteen pages are missing across three ranges" is harder to answer than "there are gaps", and it is the sentence that survives into a declaration.

What to leave out

  • Findings that are information rather than defects - a blank page, a stamp in the text layer. They are true and they invite an argument instead of a fix, and each one makes the real items look weaker.
  • Anything you have not located by number. "Some documents appear to be missing" cannot be answered and will not be cured.
  • A demand for sanctions in a first letter. It converts a cure into a negotiation about whether you were reasonable.

Getting the list without writing it by hand

The work in a deficiency letter is not the prose, it is the inventory: which numbers are missing, which rows point at nothing, which pages have no text, which redactions still hold text. Done by hand on a thousand-page set, that inventory takes a day and misses the joins between volumes.

The check produces that list mechanically, and the deficiency report writes it in the receiver's voice - what was observed, exactly where, and what to ask for, phrased per rule family because "re-stamp the pages" is the producer's instruction and "ask them to re-stamp and re-serve the range" is yours. It arrives with the same order as the audit; there is no second charge for the same set.

Build the list before you write the letter

Upload the production you received. The findings become a numbered inventory with page references, and the deficiency report states each one as an observation, a location and a request - the three things every item in the letter needs.

The verdict, the file list and the worst findings are free and stay free. The inventory, deficiency report and certificate unlock on payment, from $49 for a set up to 1,000 pages. The three sizes.

Frequently asked questions

How long should a deficiency letter be?

As long as the defects require and no longer. One page is normal for a production with three problems; a twenty-seven-page letter about four missing pages mostly teaches the reader that you are not going to be reasonable, which is the opposite of what the letter is for.

Should the letter cite rules or cases?

Only the ones you are prepared to brief. A letter that asserts a violation invites a reply about the authority; a letter that states a mechanical fact and asks for a cure is much harder to refuse and does not commit you to a position you have not researched.

What if the other side says the pages never existed?

That is a cure, and it should be in writing. Ask them to confirm it expressly, so the record shows either the pages or the statement that there are none - which is what a later motion is actually about.

Can I send the deficiency report itself as the letter?

It is written to be attached, not sent bare: it has the items, the page references and the asks, but the covering paragraph identifying the production, the date served and the deadline is yours to write. Most people use the report as the body and add a page of cover.

Keep reading

guide How to QC an incoming production A production you receive has to load, read and reconcile before anyone can review it. These twelve checks run in the order that surfaces the expensive failures first: does the load file import, does every row have an image, does the numbering hold, and is every page searchable. Run them before the review clock starts, not after. guide Privilege log template, and the columns a reviewing party needs A privilege log needs six things for every withheld document: the Bates range it covers, the document type, its date, its author, its recipient, and the basis for withholding. A log missing any of them invites a challenge that has nothing to do with whether the document is actually privileged. guide How to find a missing Bates number before the set is served A Bates gap is a number that should exist in the sequence and does not. Most gaps are invisible on screen, because the pages either side of the hole look continuous. The reliable way to find one is to read the stamp off every page and compare what is there against the range each file claims to cover. tool Check a PDF for production defects Upload one PDF and get a plain-language result for each production check: text layer, Bates gaps, duplicate Bates numbers, extractable stamp text, page size and rotation drift, redaction leakage, and whether the file opens at all. No account or email address is needed, and the uploaded file is checked in a temporary directory and discarded. guide Why Bates numbers land in the wrong order across files When you number a folder of PDFs in one pass, the numbering follows the order the files were added, which is usually alphabetical by filename - and neither the filename order nor the file-modified order is the order a production is served in. The sequence is still continuous, so nothing looks wrong until a receiving party reads the set. The check that catches it compares the Bates range of each file against the order the files are meant to appear. guide Why Bates numbers show up in keyword search A stamp is either an image drawn on the page or text added to the content stream. When it is text, it stays in the text layer, and every keyword search for that number or for a stray date inside it returns the page. Receiving parties use stamped numbers as identifiers, so a searchable stamp quietly pollutes their results - and in the worst case leaks a number into a privilege log as if it were document content.