The Potemkin Client File: A Forensic Diagnostic

Quick Answer

A Potemkin client file is a client file assembled on demand — usually in response to a written file request or a court-ordered production — rather than maintained contemporaneously during the representation. The term references the Potemkin village: a facade built for inspection.

The diagnostic is in the PDF metadata. A file genuinely maintained across months of representation carries heterogeneous fingerprints: Microsoft Word, the court's electronic filing system, scanner output, email print exports, bankruptcy practice software. A file assembled in one sitting carries a single browser-engine fingerprint — Chrome, Skia/PDF, PDFium, Safari, or Edge — and creation timestamps clustered in a single short window.

What "Potemkin File" Means in Practice

In a properly-run representation, a client file is built as work happens. The engagement letter is signed in Word and saved. Schedules are drafted in bankruptcy software (Best Case, NextChapter, etc.) and filed through the court's electronic filing system. Hearing notes are taken in the firm's matter-management product. Correspondence accumulates in an email client. Creditor letters arrive in paper or PDF from third parties and get scanned. Every document carries its own origin fingerprint, and creation timestamps are scattered across the timeline of the representation.

A Potemkin file inverts this. When the firm receives the request, no real file exists in the form requested. So a staffer opens a browser, navigates to PACER (or another public source), prints filed documents to PDF using the browser's print function, and stacks them together as a "production." Every PDF in the stack carries the same browser-engine signature. The creation timestamps cluster within minutes of each other. The original drafts, the intake notes, the email correspondence, the worksheets, the supervisor reviews — none of which exist in a unified file — are silently omitted.

The result looks like a file production. The metadata says it is a fresh export of public records, not a record of the representation.

The Legal Stakes

A Potemkin file production is not a clerical issue. It implicates multiple rule clusters at once, each with independent consequences:

ABA Model Rule 3.4(a) - Fairness to Opposing Party and Counsel

Substituting fabricated assembly for missing originals — or concealing the absence of an original file by producing a substitute that looks complete — falls within Rule 3.4(a)'s prohibition. Every state has a substantively identical rule.

ABA Model Rule 1.16(d) - Surrender of Client Property

Rule 1.16(d) requires surrender of the file, not a reconstruction of it. Producing a substitute is non-compliance, not compliance. See our client file guide for the full Rule 1.16(d) framework.

Federal Rule of Bankruptcy Procedure 9011

Documents signed and filed in bankruptcy court must be supported by reasonable inquiry into the facts. A reconstructed file presented as the original — particularly one used to support filed pleadings — can implicate Rule 9011's certification standard.

18 U.S.C. Section 1519 (federal obstruction)

Bankruptcy proceedings are matters within federal jurisdiction. Fabricating records "in contemplation of" a federal proceeding triggers Section 1519. This is a criminal statute. The U.S. Trustee Program and the Department of Justice have prosecutorial authority.

11 U.S.C. Section 329 (fee review)

A firm that cannot produce a contemporaneous file documenting the work performed has difficulty defending the fees it was paid for that work. See section329.org for the fee-disgorgement framework.

The Forensic Fingerprints

Three signals, in combination, distinguish a Potemkin file from a real one:

1. Browser-engine Creator/Producer fields

Every PDF carries metadata identifying the software that created it. Documents produced through a web browser's "print to PDF" function carry distinctive signatures:

Browser	Typical Creator	Typical Producer
Google Chrome	Chrome (version)	Skia/PDF m(version)
Microsoft Edge	Microsoft Edge (version)	Skia/PDF m(version)
Mozilla Firefox	Mozilla/5.0 (engine string)	PDF Library or built-in
Safari (macOS)	Safari (version) or WebKit	WebKit or CoreGraphics
Embedded PDF viewer (PDFium)	(various)	PDFium

By contrast, documents drafted in a firm typically carry Producer fields like Microsoft® Word (version), Adobe Acrobat (version), or bankruptcy practice products. Court-filed documents downloaded from PACER carry the court's filing-system fingerprint. Scanned documents carry scanner-vendor producers (TWAIN drivers, Canon/HP/Brother). Heterogeneity across these fingerprints is the signature of an actual working file.

2. Tight assembly window in creation timestamps

Plot the CreationDate for every PDF in the production on a timeline. A file that was built across months of representation shows scattered timestamps spanning the engagement. A Potemkin file shows clustering within a narrow window — sometimes under an hour — that immediately precedes the production date.

3. ModDate ≈ CreationDate

PDFs that have been edited over time typically show a ModDate distinct from the CreationDate. Documents produced in a single export from another source typically show ModDate equal to or near-equal to CreationDate. Across an entire production, a uniform ModDate = CreationDate pattern is consistent with single-session generation.

What a Real, Contemporaneous File Looks Like

For contrast, here is the metadata signature a legitimately-maintained bankruptcy file typically shows:

• Engagement letter: Microsoft Word producer, creation date matching the start of representation, ModDate showing client signature event.
• Voluntary petition and schedules: producer is the bankruptcy practice product (Best Case, NextChapter, ECF) or the court filing system; creation dates match the actual filing event.
• Plan documents and amendments: same producer family, creation dates corresponding to drafting and filing events.
• Trustee correspondence: mixture of producers — the firm's outgoing emails carry one signature; trustee responses carry the trustee's filing-system or office producer.
• Creditor letters: scanned-document signatures; creditor exhibits often retain Acrobat or third-party producers.
• Pay stubs and tax returns: typically scanned or downloaded from third-party payroll/IRS systems; carry third-party producers.
• Hearing notes: often handwritten and scanned, or typed in the firm's matter-management product.
• Internal worksheets (means test scratch, plan feasibility, etc.): producer reflects whatever spreadsheet or analytical tool the firm uses.

Heterogeneity over time is the signature of representation. Uniformity in a single short window is the signature of assembly.

How to Audit Your Own File (Step by Step)

1. Preserve everything immediately. Make a forensic copy of every PDF to a separate drive without opening the originals. Opening a file can update access timestamps. Keep originals untouched.
2. Inspect metadata on each PDF. Open the copy in Adobe Acrobat Reader (free). Use File > Properties. Record the Creator, Producer, Created, and Modified fields. A spreadsheet works well for this.
3. Plot the Creation dates on a timeline. Real files span the representation. Potemkin files cluster within hours.
4. Group by Producer. Count how many distinct Producer fingerprints appear. A real bankruptcy file production typically shows 5-15+ distinct Producers across the file. A Potemkin file shows 1-3.
5. Spot-check externally-sourced documents. Creditor letters, IRS transcripts, pay stubs, and bank statements should carry their own third-party producers. If everything in the production carries the firm's browser fingerprint, externally-sourced documents have been re-printed through the same browser — not preserved in native format.
6. Compare to your expectations. Did you sign an engagement letter the firm drafted in Word? It should appear in the production with a Word producer. Did the firm email you? Those emails should appear in their native email-export form. Documents missing from the production tell you what the firm did not preserve.
7. Save screenshots of every diagnostic metadata pane. Filename, full metadata, and date of inspection. These become exhibits.

Free Tools for the Audit

You do not need expensive forensic software. The signal is in fields every PDF reader can display:

• Adobe Acrobat Reader (free, all platforms): File > Properties shows Creator, Producer, Created, Modified. Easiest for non-technical users.
• Built-in OS tools: Windows right-click Properties > Details; macOS Finder Get Info. Limited but free and zero-install.
• Web browsers: open the PDF and check the viewer's document info pane (varies by browser).
• Command-line: pdfinfo (part of Poppler, free, available on Windows/macOS/Linux). One command prints all metadata: pdfinfo your-file.pdf.
• Command-line: exiftool (free, cross-platform). Exhaustive metadata including XMP fields: exiftool your-file.pdf.

Common Innocent Explanations - and Why They Usually Fail at Scale

A firm faced with these findings will sometimes offer innocent explanations. They are worth considering:

"We re-exported everything to consolidate the file."

Sometimes a firm consolidates documents into a single output for a production. But re-export to PDF does not have to use the browser print function — firms with practice-management software typically have built-in export tools that preserve the original producers in the XMP metadata. Browser re-export specifically destroys the original signatures. The choice of method is significant.

"We always print everything through the browser."

Possible for very small firms. But this defense undermines the firm's competence claim: it concedes that the firm never had a file in any other form, which in a complex bankruptcy representation is itself a problem under Model Rule 1.1 (competence) and Rule 1.3 (diligence).

"PACER documents naturally carry browser fingerprints."

PACER documents downloaded directly carry PACER's filing-system fingerprint, not a browser's. Documents that carry a browser fingerprint were viewed in the browser first and printed to PDF — an extra, post-hoc step. Documents whose original source was PACER but that now carry only browser fingerprints have lost their authenticating chain.

"The dates cluster because we exported everything for you at once."

This explanation accepts the diagnostic. The clustering proves the file was generated for production, not maintained during representation. That is exactly the Potemkin-file claim.

What to Do If You Find These Signals

1. Preserve and document. Forensic copies, metadata screenshots, dated inspection notes.
2. Send a preservation letter to the firm noting your forensic findings and demanding preservation of all original drafting files, intake records, matter-management notes, email correspondence, and internal worksheets. See our spoliation duty page.
3. File a bar complaint under your state's Rule 3.4(a), Rule 1.16(d), and Rule 1.1 equivalents. The forensic findings give the disciplinary body a deterministic record to evaluate. See our bar complaints guide.
4. If the case is still active in bankruptcy court, notify the U.S. Trustee assigned to your case. The USTP has independent investigative authority and can refer matters to the Department of Justice under 18 U.S.C. Section 1519 in appropriate cases.
5. Consult a legal malpractice attorney. The forensic record dramatically strengthens any case. Most malpractice attorneys offer free initial consultations and work on contingency.
6. Consider a Section 329 fee review. A firm that cannot produce a contemporaneous file documenting its work has difficulty defending the fees it was paid. See section329.org.

Why the Bar Doesn't Already Catch This

State disciplinary bodies generally investigate in response to complaints, not proactively. PDF metadata forensics is not a routine part of bar discipline workflows. Most clients do not know that a "complete file production" in PDF form preserves evidence of how the file was assembled.

The result is that this category of non-compliance has historically been under-detected. A firm operating a high-volume, paralegal-driven workflow that never builds individual client files can avoid disciplinary scrutiny — not because the conduct is permissible, but because the diagnostic is not yet standard practice.

This page exists so any client can run the same audit a forensic expert would run, using only free tools, and document findings before filing a complaint. The methodology is intentionally public and reproducible.

Related guides on this site: why won't my lawyer give me my client file · spoliation duty · bar complaints · check your attorney · malpractice damages

External authorities: ABA Model Rule 3.4 · 18 U.S.C. § 1519 · FRBP 9011 · U.S. Trustee Program