Subpoenaed for a closing file: a New York primer

Real-estate files get subpoenaed for all sorts of reasons that have nothing to do with any mistake you made: a dispute between buyer and seller, a lender's claim, a divorce, a title fight, a fraud investigation involving someone else at the table. The demand lands on you because you have the records. What follows is a general map of the New York obligation, not legal advice for your specific matter — but knowing the shape of it turns an alarming envelope into a task with steps.

Don't ignore it — and don't over-comply either

The two failure modes are opposite. One is treating a subpoena as optional; it is not, and under New York practice a recipient who objects still has to say so in writing. The other is handing over the entire file, including privileged material, to make the problem go away. The correct path runs between them: read what is actually demanded, preserve everything, object where there are grounds, and produce what must be produced.

Read what is actually demanded

A subpoena duces tecum — a subpoena for documents — must specify a production time no less than 20 days after service and must describe each item or category with reasonable particularity (CPLR 3120). It can be issued on its own or joined with a subpoena to testify, and it can be satisfied by a custodian able to identify the records and testify to their origin, purpose, and custody (CPLR 2305(b)). When the subpoena comes from a party in a lawsuit and you are a non-party, it also generally must state the circumstances or reasons the disclosure is sought (CPLR 3101(a)(4)). Reading those requirements closely often narrows what you actually owe.

It is also worth confirming the basics before engaging with the substance: who issued the subpoena, in what proceeding, whether it was served properly, and whether it seeks documents, testimony, or both. Those threshold points shape every step that follows, and a defect in any of them can matter. Reading the demand as a document, not just a deadline, is the first real task.

Mind the clock, and object in writing

New York gives a recipient who objects a defined, short window: within 20 days of service, a person served with a document subpoena or notice must serve a written response stating the reasons for each objection with reasonable particularity (CPLR 3122(a)(1)). That is distinct from moving to quash or modify the subpoena, which is its own mechanism (CPLR 2304). The point for a busy practice is simple: calendar the dates the day the subpoena arrives, and make objections on paper and on time. An objection preserved is an argument you keep; silence forfeits it.

Common grounds for narrowing what you produce

Not every demand is enforceable as written, and New York gives a recipient real room to narrow one. Objections commonly rest on overbreadth (a request untethered to the actual dispute), relevance, undue burden, and, for a non-party, the requirement that the subpoena state the circumstances or reasons the disclosure is sought (CPLR 3101(a)(4)). A non-party generally should not have to shoulder the cost of another party's litigation, and can say so. None of this is a reason to stonewall — it is a reason to respond precisely: produce what is plainly discoverable, object with particularity to what is not, and, where the dispute is genuine, let the court resolve it on a motion to quash or for a protective order rather than by unilateral silence.

Handle privilege deliberately

A closing file often contains attorney-client communications and attorney work product. Those can be withheld, but New York requires a privilege log that states, for each withheld document, its type, general subject matter, date, and enough to identify it (CPLR 3122(b)). The Appellate Division has held that a log identifying documents by broad category rather than individually violates that rule absent party agreement or a court order (Joseph v. Rassi, 2024 NY Slip Op 04548 (2d Dep't 2024)). Two practical notes: the attorney-client privilege generally belongs to the client, so assertion and waiver are decided with the client; and a file that keeps privileged material separable as it is created turns the log into a short, mechanical exercise.

Because the privilege is the client's, a subpoena for a closing file is also a moment to communicate. The client — and sometimes other parties whose information is implicated — may need to know the demand exists, so that decisions about asserting privilege, seeking a protective order, or negotiating scope are made together and on time. Handling a subpoena in isolation is how waivers happen by accident.

Preserve first, produce second

The moment a subpoena is foreseeable — often before it arrives — the duty to preserve attaches. Once litigation is reasonably anticipated, routine destruction must stop and a litigation hold go in place, or spoliation sanctions can follow (VOOM HD Holdings LLC v. EchoStar Satellite L.L.C., 93 A.D.3d 33 (1st Dep't 2012)). Records are best left as they are — untidied, not re-exported or annotated. New York authenticates records through their regular-course origins (CPLR 4518) and, for electronic material, through testimony and circumstantial detail; altered or reconstructed files invite exactly the authentication fight you want to avoid.

When the file is years old

Many subpoenas arrive long after closing, which raises a practical question: what do you still have? New York's Rules of Professional Conduct require keeping the enumerated bookkeeping records — escrow and operating account records, retainer and compensation agreements — for seven years (RPC 1.15(d)). Beyond those, no single rule fixes how long the rest of the file must be kept, and the State Bar's guidance is to retain it well past the limitations periods that could bring it back into question. A portion destroyed under a genuine, routine retention policy applied before any duty to preserve arose is a materially different position from records lost to carelessness — one more reason a durable, complete record of each closing is worth keeping by default.

Why a sealed record turns weeks into hours

The reason a subpoena is stressful is rarely the law; it is the scramble. The file is spread across an email account, a document platform, a paralegal's folder, and a portal, and assembling it — while separating privilege and proving nothing changed — is the work. When the transaction already lives in one sealed, tamper-evident file with distribution logged and privileged material kept apart, the response is closer to retrieval than reconstruction.

That is what ClosingRecord is for. It does not decide what is discoverable, assert privilege, or give legal advice — those stay with you and your client. It keeps the underlying record complete, verifiable, and quick to produce. If you would rather build the file so this day is easy, start with the litigation-ready closing file, or open a complete sample transaction to see a sealed record firsthand.