The Court Cases Where Click-Through Acknowledgments Failed

Every company with a handbook runs an acknowledgment system, even if it is a signature sheet in a folder. What most of them have never done is ask whether that system would hold up the day it matters, in front of a judge, with employment counsel on the other side pulling at the record.

Courts have already answered that question four times. These cases, three from California’s appellate courts and one from the 8th Circuit, are where common acknowledgment practices went to die. They are worth reading not for the law, which your counsel owns, but for the pattern: in every one, the company had a record, and the record did not say the thing that mattered.

Sparks v. Vista Del Mar Child and Family Services (California, 2012)

The employee signed an acknowledgment of receipt of the employee handbook. Inside that handbook sat an arbitration clause the employer later tried to enforce. The court held it unenforceable: the acknowledgment never mentioned arbitration, and the handbook itself stated it was not a contract.

The failure: the record proved receipt of a book, not agreement to a clause. A signature that does not name the obligation is evidence of almost nothing about that obligation.

Esparza v. Sand & Sea, Inc. (California, 2016)

Similar setup, and the employer’s own paperwork did the damage twice over. The handbook’s welcome letter said it was “not intended to be a contract,” and the acknowledgment form even noted the employee had not read the handbook yet. No enforceable arbitration agreement.

The failure: the documents contradicted the claim. You cannot disclaim contractual force in the text and then ask a court to enforce that same text as a contract. An acknowledgment that admits non-reading undermines itself on its face.

Mendoza v. Trans Valley Transport (California, 2022)

The employer produced signed acknowledgment forms. The forms did not mention the arbitration policy at all. The court found no contract, express or implied.

The failure: same lesson a decade after Sparks, which tells you how common the practice remains. The record has to connect the person to the specific obligation, or it connects them to nothing.

Shockley v. PrimeLending (8th Circuit, 2019)

The modern one, and the reason “click-through” is in this post’s title. The company’s system auto-generated an acknowledgment when the employee clicked a link to the handbook. There was no evidence she ever opened the full text, and the court found no unequivocal acceptance, so no agreement.

The failure: the system recorded an event and called it consent. A click that opens a document is not a click that accepts its terms, and a record generated as a side effect proves the side effect.

The pattern, in one place

Four different companies and one autopsy. A record survives scrutiny when it carries four things together:

1. Identity: this specific person, verifiably.
2. The obligation, named: the record says what was agreed to, in the text the person saw, not “the handbook” as a container.
3. The version: which exact revision of the document, because the text changes and the record must not float.
4. Real assent: an affirmative act that unambiguously means acceptance, not an auto-generated event, and not a signature the paperwork itself undercuts.

And one structural lesson sits above all four cases: contract-weight obligations like arbitration terms, NDAs, and IP assignments do not belong inside the handbook behind a receipt signature. They belong in standalone documents with explicit agreement language and a real signature.

What this means for how you collect acknowledgments

If you run acknowledgments today, test your record against the pattern: pull one completed acknowledgment and ask whether it shows the exact attestation text the person saw, the version it covered, and an act that meant acceptance. If it is a checkmark in a spreadsheet or an auto-logged click, you have the Shockley record.

This is exactly why AllyMatter stores the attestation text itself on every acknowledgment record, binds every record to the exact version, timestamps the affirmative act, and keeps the record permanently, surviving the person’s departure. And it is why documents that are really agreements take an e-signature instead, as their own standalone documents, through the same system. Choosing between the two is its own decision.

We build software, not legal strategy. Which of your documents are contracts, and what these cases mean in your state, are questions for your employment counsel. What we can promise is that whichever answers they give, the record will hold.

Start your 30-day free trial. No credit card to start, and a 30-day money-back guarantee if you convert and change your mind.

Not ready for a trial? On annual plans, migration is on us: we’ll move your docs from SharePoint, Google Drive, Confluence, or Notion and have you running in about a week.