By Reviewed against the Receipts.law precedent corpus · Published 2026-05-16

Palmer v. Hoffman and the Business-Records Exception

Q: Does Palmer v. Hoffman apply to all employment documents?

No. Palmer applies only to documents offered as business records under FRE 803(6). Routine operational records like timesheets, payroll logs, and attendance systems typically qualify as business records because they're created for operational purposes. Palmer targets documents created about the business in anticipation of legal claims rather than documents created by the business to conduct its operations.

Q: What if the employer has a policy requiring documentation of all complaints?

A policy requiring documentation doesn't change the Palmer analysis if the documentation is created for litigation purposes rather than operational ones. Courts distinguish between records made to run the business (which qualify) and records made to defend against claims (which don't), regardless of whether the employer has formalized the litigation-prep process into a written policy.

You've just received your employer's production in response to your EEOC charge.

Buried in the stack: a memo from HR labeled "Incident Summary—[Your Name]." It's dated two weeks after you complained about discrimination. It paints you as insubordinate, hostile, disruptive.

The problem? You know for a fact that memo didn't exist until after you filed your complaint. It wasn't created in the ordinary course. It was assembled to justify the termination they'd already decided on.

That's where Palmer v. Hoffman comes in. The 1943 Supreme Court decision that draws a bright line between records made during business operations and records made to prepare for a fight.

In this article, you'll learn:

What makes a document qualify under the business-records exception to hearsay
Why the Palmer test excludes litigation-prep documents even when the business routinely creates them
How federal courts apply the doctrine to weed out post-hoc HR justifications

What the Business-Records Exception Actually Covers

Close-up photo of a professional business ledger or logbook with handwritten entries and timestamps, photographed on an

Federal Rule of Evidence 803(6) creates a hearsay exception for records "made at or near the time by—or from information transmitted by—someone with knowledge" if "keeping the record was a regular practice of that activity."

The rationale is simple: businesses rely on accurate records to function. When a shipping log records a delivery, when a payroll system logs a clock-in, when a sales database captures a transaction, those entries carry inherent reliability because the business depends on their accuracy.

But here's the thing:

Not every document a business creates qualifies.

The exception has four foundational requirements. The record must be made (1) at or near the time of the event, (2) by someone with knowledge or from information transmitted by someone with knowledge, (3) kept in the regular course of business, and (4) made as a regular practice of that business activity.

Element three is where Palmer v. Hoffman, 318 U.S. 109 (1943), draws the line.

Key takeaway: A document created about business operations is not the same as a document created during business operations. The distinction matters for admissibility.

The Palmer v. Hoffman Test

Palmer v. Hoffman involved a wrongful-death suit arising from a train-truck collision. The railroad's engineer prepared a written statement describing the accident. The railroad attempted to introduce the statement under the business-records exception, arguing that the company routinely required engineers to file such statements after every accident.

The Supreme Court rejected the argument.

Justice Douglas, writing for the majority, held that the statement was "not made in the regular course of business" within the meaning of the statute. The statement was "dripping with motivations to misrepresent" because it was created with an eye toward litigation.

The regularity of the practice didn't cure the litigation purpose.

Even though the railroad made such statements after every accident, the statements were prepared to build a defense, not to document operations. That disqualified them from the exception.

Now, here's where it gets important:

The Palmer rule doesn't require proof of subjective bad faith. The test isn't whether the person drafting the memo intended to lie. The test is whether the document was made in anticipation of litigation rather than as part of the activity itself.

Watch for: Documents created after an employee complains or files a charge almost always fail the Palmer test. The timing alone indicates litigation purpose, regardless of what the employer claims about "routine practice."

How Courts Apply Palmer to Employment Records

Professional overhead shot of a desk with calendar pages showing different dates, sticky notes with timestamps, and docu

Employment cases generate a particular species of post-hoc documentation. After an employee complains about discrimination or reports misconduct, HR suddenly "discovers" performance problems that were never documented before.

Memos appear. Incident reports materialize. Performance-improvement plans get backdated (or at least backdated in effect, by summarizing events from weeks or months earlier without contemporaneous support).

Federal courts apply Palmer to exclude these records when the employer tries to use them as evidence of legitimate reasons for termination.

The analysis turns on three factors:

Timing. Was the document created before or after the protected activity? A performance writeup dated three days after the employee filed an EEOC charge is functionally a litigation document, not a business record.

Routine practice. Did the employer consistently create similar records for all employees in similar circumstances, or only for this employee after they became legally problematic? If the employer never documented similar conduct by other employees, the record fails the regular-practice prong.

Operational necessity. Does the business need this record to function, or does it exist solely to justify a personnel decision under legal scrutiny? A daily timekeeping log serves operational needs. A retrospective memo summarizing three months of alleged attitude problems does not.

But it gets better:

Even if the document is excluded as a business record under 803(6), it may still be admissible as a party-opponent admission under FRE 801(d)(2)(D). The difference is procedural, not substantive—but it matters for burden-shifting.

When the employer offers the document as a business record, the document carries a presumption of reliability. The employee must affirmatively rebut it.

When the same document comes in only as an admission, it's treated as the employer's self-serving statement. No presumption. And the fact that the employer needed to create the document after the charge can itself become evidence of pretext.

1 of 1 indexed cases citing Palmer v. Hoffman in the employment-retaliation context resulted in outcomes favorable to the employee.

Why Litigation-Prep Records Undermine Credibility

Here's what employers miss when they assemble post-charge justification files:

The absence of a record can be more powerful than its belated presence.

If an employee's conduct was truly problematic enough to warrant termination, a functioning business would have documented it when it happened. Managers don't wait three months to write up safety violations. HR doesn't ignore repeated insubordination until after the employee files a complaint.

When the employer produces a memo dated five days after the EEOC charge, the memo itself becomes evidence of pretext. The timing proves the employer wasn't documenting performance problems—it was documenting a legal defense.

Palmer gives courts a doctrinal tool to exclude that evidence or, at minimum, strip it of the reliability presumption that business records ordinarily enjoy.

And that shifts the burden back where it belongs: on the employer to prove, with contemporaneous evidence, that the adverse action had a legitimate basis unrelated to the protected activity.

Pro tip: The absence of contemporaneous documentation is admissible circumstantial evidence of pretext. If your employer never wrote you up before you complained, that gap is part of your case—not a weakness in it.

The Intersection With Spoliation Doctrine

Photo of file cabinet drawer partially open showing gaps between folders where files are missing, alongside intact organ

The Palmer doctrine intersects with the duty to preserve evidence under Zubulake v. UBS Warburg and similar spoliation precedents. (For a full treatment of preservation obligations, see Zubulake and the Duty to Preserve in Employment Cases.)

When an employer destroys or fails to preserve documents that would have been made in the regular course of business, spoliation inference allows the factfinder to assume those documents would have been unfavorable to the employer.

But when the employer creates documents that were not made in the regular course, Palmer treats them as inherently suspect.

The two doctrines work together. Missing contemporaneous records + manufactured post-hoc records = a pattern that supports pretext.

Now, here's the wrinkle:

Some employers try to cure the Palmer problem by implementing policies requiring documentation of all disciplinary events "for legal-compliance purposes." They argue that because the policy makes litigation-prep documentation routine, the records qualify as business records.

Courts generally reject this argument. The purpose of the document—building a litigation defense—doesn't change just because the employer made litigation-prep part of its regular practice. Palmer looks to the nature of the activity documented, not the employer's internal characterization of the documentation process.

In real cases: Courts have excluded "compliance files" created after protected activity even when the employer had a written policy requiring such files. The policy doesn't transform litigation prep into ordinary-course business activity.

What Palmer Means for Your Evidence Strategy

If you're building a retaliation case, the Palmer doctrine gives you two lines of attack against the employer's proffered legitimate reasons.

First, challenge foundation. When the employer offers a post-complaint memo or writeup, object on hearsay grounds. Force the employer to lay foundation for the business-records exception. If the employer can't show the record was made in the ordinary course rather than in anticipation of litigation, the court excludes it or admits it only as an admission.

Second, use timing as circumstantial evidence. Even if the document comes into evidence, its late creation supports an inference of pretext. Employers with legitimate reasons document them when they happen. Employers manufacturing reasons document them after the complaint.

The absence of pre-complaint documentation, combined with the sudden appearance of post-complaint documentation, tells a story. Palmer gives that story doctrinal weight.

And here's the practical reality:

Most employment cases settle before trial. Discovery fights over Palmer objections force employers to confront the weakness of their post-hoc justifications early in the case. When the employer realizes its "performance file" won't survive a motion in limine, settlement value shifts.

Common Misconceptions About Palmer

Three myths about Palmer v. Hoffman circulate in employment litigation:

Myth 1: Palmer only applies if the employer acted in bad faith. Not true. The test is objective. A document prepared in anticipation of litigation fails the business-records exception regardless of the drafter's subjective intent or honesty.

Myth 2: Regular practice cures litigation purpose. Also false. The fact that the employer routinely creates litigation-prep documents doesn't transform them into ordinary-course business records. Palmer rejected exactly this argument.

Myth 3: Palmer exclusion means the evidence disappears. No. The document may still come in as a party admission. The difference is that it loses the reliability presumption and can be used as evidence of the employer's reactive, defensive posture.

Understanding these distinctions matters because employers and their counsel often mischaracterize Palmer to avoid its application.

Frequently Asked Questions

Does Palmer v. Hoffman apply to all employment documents?

No. Palmer applies only to documents offered as business records under FRE 803(6). Routine operational records like timesheets, payroll logs, and attendance systems typically qualify as business records because they're created for operational purposes. Palmer targets documents created about the business in anticipation of legal claims rather than documents created by the business to conduct its operations.

Can an employer cure a Palmer problem by backdating documents?

No, and attempting to do so creates additional legal risk. Backdating or altering documents to make them appear contemporaneous can trigger spoliation sanctions, fraud allegations, and adverse-inference instructions. Courts can and do examine metadata, email timestamps, and document-creation logs to verify when records were actually made.

What if the employer has a policy requiring documentation of all complaints?

A policy requiring documentation doesn't change the Palmer analysis if the documentation is created for litigation purposes rather than operational ones. Courts distinguish between records made to run the business (which qualify) and records made to defend against claims (which don't), regardless of whether the employer has formalized the litigation-prep process into a written policy.

Does Palmer apply in administrative proceedings like EEOC investigations?

The Federal Rules of Evidence don't formally apply in EEOC proceedings, but the Palmer principle—that litigation-motivated records are inherently less reliable than operational records—often influences how investigators weigh evidence. A memo created after the charge is filed carries less weight than contemporaneous documentation, even in an administrative context.

If a document is excluded under Palmer, can I still use it to show the employer's motive?

Yes. Even if a document is excluded as a business record under 803(6), it may be admissible for non-hearsay purposes—such as showing the employer's state of mind, the timing of the employer's response to protected activity, or the absence of contemporaneous documentation. The document's existence and timing can themselves be circumstantial evidence of retaliatory motive.