Skip to main content
← Field Notes

June 12, 2026

CEQA Document Delivery Dispute: Protect Your Paper Trail

If a client claims they never received a CEQA document, the burden usually falls on you to prove you sent it — and an email 'sent' folder rarely settles it, because it can't show what was delivered or whether it was opened. A tamper-proof delivery record with timestamps, recipient confirmation, and the exact file version sent is what resolves the dispute before it becomes a fee fight or a missed comment deadline.

If a client claims they never received a CEQA document, you — not the client — typically have to prove the send happened. An email "sent" folder doesn't do that: it shows the message left your outbox, not that the correct file arrived, opened, or reached the right person. The fix is a delivery record that timestamps each send, identifies the recipient, and locks the exact file version — so the dispute ends on facts instead of recollection.

What actually triggers a CEQA delivery dispute?

CEQA work runs on hard deadlines, and the disputes cluster around them. Public review periods for a Draft EIR and minimum review periods for a Negative Declaration are governed by the CEQA Guidelines and the Public Resources Code — confirm the exact periods and current section references before relying on them. When a lead agency or a project applicant says a draft, a comment response, or a Mitigation Monitoring and Reporting Program never landed, the question isn't really "did you do the work" — it's "can you show what you sent and when."

Three patterns repeat:

  • The version mismatch. You sent a draft. The client reviewed a different draft someone forwarded internally. By the time the discrepancy surfaces, the comment window is half gone, and each side blames the other.
  • The recipient gap. You emailed the project manager who left the firm three weeks earlier. The message sat in a dead inbox. Nobody at the client saw it until the deadline passed.
  • The "we never got it" at invoice time. The deliverable is disputed precisely because payment is attached to it. Denying receipt is a way to delay the check.

Why doesn't a sent email protect me?

Because a sent email proves intent to send, not delivery. It doesn't show the recipient opened the attachment, doesn't confirm the file was the final approved version, and doesn't survive scrutiny if the recipient's mail server silently dropped a large EIR attachment — which large CEQA files routinely trigger.

It also doesn't help that CEQA documents are frequently split across links, shared drives, and physical copies mailed to a clearinghouse. When the State Clearinghouse logs a submission date and your client logs a different one, your internal email thread is a weak tiebreaker. You need a record built to be read by a third party who wasn't in the room.

What does a defensible delivery record look like?

A record that holds up has four elements: a timestamp tied to the moment of delivery, a named recipient who can be matched to the engagement, the specific file (by version and hash, not just filename), and confirmation the recipient retrieved it. That last piece is what separates "I sent it" from "you received it."

This is the specific gap Mainstay closes. When you deliver a CEQA document through it, the platform locks the file version and produces a tamper-proof record of the send and the recipient's retrieval — so the "we never got it" claim meets a record neither side can quietly edit. You're not reconstructing a timeline from inbox screenshots months later; the record already exists, dated, and tied to the exact document.

How does delivery proof connect to getting paid?

Most CEQA engagements bill against deliverables — a percentage on Draft EIR submission, a percentage on the final, a milestone on the MMRP. When delivery is disputed, the milestone is disputed, and the invoice stalls. Smaller firms feel this immediately: a single contested milestone on a net-terms invoice is a real cash flow event, not a rounding error.

Triggering billing off a confirmed delivery record changes the conversation. Instead of "did you send the draft," the question becomes "here is the dated record of the version you retrieved on the 14th" — and the invoice clock starts on a fact. The same record that protects you in a dispute is the one that moves the receivable.

What should a small consulting firm do this quarter?

Three concrete moves:

  1. Stop relying on attachments for large documents. Use a delivery method that confirms retrieval, because large EIR files are exactly the ones that vanish silently.
  2. Tie every deliverable to a named, current recipient. Re-check the contact before each milestone send; staff turnover at clients and agencies is the quiet source of half these disputes.
  3. Keep the version locked. Match what you delivered to a single file you can produce on demand — by hash, not by "it should be the latest one in the folder."

The firms that don't get caught in a CEQA document delivery dispute aren't the ones with the best memories. They're the ones whose records were built to be read by someone else.

Mainstay coordinates the delivery and documentation of environmental compliance work — it is not a compliance advisor and makes no regulatory determination. Always confirm requirements with the relevant agency.

Sources

This post is for general informational purposes only. Mainstay coordinates the delivery and documentation of environmental compliance work — it is not a compliance advisor and makes no regulatory determination. Regulatory requirements vary by permit type, jurisdiction, and project conditions. Always confirm applicable requirements with the relevant agency or a qualified professional.