Your loan officer’s AI chat history is Exhibit A.

How routine credit questions become litigation evidence.

Republished from the September 2026 issue of Banking Law Today.

The workout officer types

“I told a borrower he needed to sell all his grain by the end of the week or we would foreclose on his operation. Could that statement give rise to lender liability?”

Bankers hear that AI conversations are discoverable and file the warning under legal trivia. Do not. A loan officer can create the borrower’s next exhibit simply by asking whether he has already gone too far.

Picture a farm borrower with a troubled credit and grain in storage. The officer demands a sale by Friday and threatens foreclosure. After the call, he wonders whether the ultimatum crossed a line. Before calling counsel, he types the question above.

The prompt records the officer’s own account: the demand, the deadline, and the threatened consequence. If the borrower later claims the bank forced a damaging sale, his attorney can compare that account with the call notes, grain-sale records, and the officer’s testimony. The bank has supplied a starting point in its own words.

The question may be more damaging than the answer. The officer does not have to ask AI to hide anything. A candid request for legal guidance can preserve facts the borrower would otherwise have to establish through documents and testimony.

The ultimatum does not establish liability by itself. The loan documents, default status, required notices, and the bank’s conduct matter. Where Farmer-Lender Mediation applies, the timing of enforcement matters too. Those are questions for counsel before the threat, not an AI reassurance afterward.

Suppose the chat continues: “He says selling now will lock in a loss, but I need the principal paid down this month. Does that change your answer?” The officer has added the borrower’s objection and his own objective to the record. The more context he gives the chatbot, the more context the other side may obtain.

The record cuts both ways

Protect the bank’s record

An ordinary business chat does not become privileged because the officer asks a legal question. A chat app is not bank counsel. Nor does an enterprise subscription, confidentiality setting, or “privileged” label settle the issue. Legal protection depends on the work and the circumstances in which it was created.

A discovery request can reach prompts, outputs, uploaded loan documents, exported conversations, and AI-created drafts copied into the file. Deleting the visible conversation may leave screenshots, downloads, audit data, and emails untouched. The record often lives in more than one place.

Do not let cleanup become the case

When litigation is reasonably anticipated, preserve relevant AI material along with the loan file. If records are lost because reasonable preservation steps were not taken, the court can impose corrective measures. Destruction intended to deprive the borrower of evidence can support adverse inferences or case-ending sanctions.

Stop deletion, preserve the account and device, identify where the output went, and involve counsel. Preservation does not concede that everything must be produced. It keeps that decision from being made for the bank by a missing record.

Do not fix a damaging chat by starting a second one: “Rewrite this so it cannot be used against us.” That instruction may become the next exhibit.

Use the borrower’s record

Consider the borrower who forms a new LLC, moves equipment and receivables into it, and leaves the debt behind six weeks before default. The paperwork calls it a routine reorganization.

He may have asked AI how to move those assets without making it look like he was avoiding the bank. In a fraudulent-transfer claim, intent is often assembled from timing, insider control, and the surrounding facts. A prompt may put that intent in plain English.

The chat does not prove the entire claim. It can explain why the transaction was structured that way and connect the new entity, moved equipment, and redirected payments into one chronology.

Ask your litigator to pursue the relevant AI histories. Identify the platforms and accounts, preserve uploads and outputs, and follow the drafts into emails and transaction documents. Expect the borrower to make the same requests of the bank.

The record starts now. The lawsuit comes later.

Supporting authorities for the web edition

Federal Rule of Civil Procedure 37(e) addresses lost electronically stored information that should have been preserved and cannot be restored or replaced. Measures under subsection (e)(1) require prejudice; adverse-inference and case-ending sanctions under subsection (e)(2) require intent to deprive another party of the information’s use. The rule does not make every deletion sanctionable.

In United States v. Heppner, No. 25 Cr. 503 (JSR) (S.D.N.Y. Feb. 17, 2026), Judge Rakoff rejected attorney-client privilege and work-product protection for the defendant’s self-directed exchanges with a public AI platform. The court considered the absence of counsel’s direction, the platform’s confidentiality terms, and whether the documents reflected counsel’s strategy. The ruling illustrates the risk discussed here; it does not decide protection for every lawyer-directed or enterprise AI workflow.

These source notes accompany the web edition and were not part of the original newsletter layout.

Contact Matthew

Matthew Bialick represents financial institutions in banking, creditors’ rights and commercial litigation. Contact him at 952-239-3095 or matthew@mjblawmn.com.