The asymmetric clock

Behind the curtain: The speed gap is a resource gap. The employer has a legal department; the worker has twenty-one days and a personal email address. That structural asymmetry, not any individual’s bad faith, is what the three California rules are designed to balance.

A fictional example

This is a made-up story. Jordan is leaving Totally Normal Corp., and two emails sit on the same thread with the same HR coordinator.

The first email. Jordan asks when the final paperwork will arrive. Two minutes later, the e-signature envelope with the release is in Jordan’s inbox.

The second email. A month later Jordan asks for the pay statement behind the final deposit. The statement arrives three days later, after a reminder.

Same thread, same people, minutes in one direction and days in the other.

The documents themselves can add to the picture. A PDF pay statement often carries an embedded creation date. When that date is days earlier than the day it was finally sent, the file shows it existed and was simply not sent until the worker pushed.

Why this is worth naming

Nobody is obliged to answer email quickly, and the point is not rudeness. The point is that speed reveals priority: the thread is a permanent record of what was prioritized.

That record has two uses. The first is practical: once you see the pattern, you stop waiting politely and start sending dated statutory requests. The second is evidentiary: if a dispute develops later, the cadence of a thread is objective, timestamped, and very hard to argue with.

The habit that protects you

From the day you are told, move every important request into writing, and give each one a clock:

I am requesting a complete copy of my executed separation agreement, including all exhibits and the signing certificate, under Labor Code 432. I am separately requesting my personnel records under Labor Code 1198.5 and my payroll records under Labor Code 226. Please confirm receipt of this request today, [date].

You will often get a faster answer simply because the email now has statutory words in it and gets routed differently. And if you do not, the clock is running and it is documented.

See the records request letter for a version you can send as is.

The ideal

In the ideal process, clocks run at the same speed in both directions. A document the employer needs signed gets a statutory period measured in days. A document the worker has requested under a statute (the executed agreement, the pay statement, the personnel file) gets produced inside the deadline that statute already sets, without escalation. You can check this from your own inbox: compare the timestamp on anything you were asked to sign with the timestamp on anything you asked to receive.

Why it works

Delay is cheap for a repeat player and expensive for a one-shotter, in Galanter’s terms (1974). The employer runs this process on a schedule it controls, with staff whose job continues next month. The worker’s clocks are unforgiving and personal: a revocation window, a COBRA election deadline, a benefit month ending. Scarcity research (Mani and colleagues, Science, 2013) explains why slow answers compound the harm. Each unanswered request stays in the worker’s head, using up the attention needed for the decisions that cannot be postponed.