Lien waivers — the four California forms and when each is safe to sign

Every pay cycle, someone upstream asks you to trade lien rights for payment. California scripts that trade precisely: four statutory forms, Civil Code §8132–§8138, one for each cell of a two-by-two — and the statute's exact language is required, so a GC's "custom" waiver that deviates is asking for more than the law does. The whole game is knowing which cell you're in.

The matrix

Progress paymentFinal payment
Conditional — effective only when the payment actually clears§8132 — sign with the pay app§8136 — sign with the final invoice
Unconditional — effective the moment you sign, paid or not§8134 — only after the progress check cleared§8138 — only after final payment cleared

Read it as a rule of motion: requests travel conditional; receipts travel unconditional. You hand over a conditional waiver to get a payment moving; you hand over an unconditional one only to evidence money already in the bank.

The one rule that matters

Never sign an unconditional waiver for money you haven't received. An §8134/§8138 waiver is effective on signature — if the check bounces, funding hangs, or the GC nets something against it, your lien rights for that period are gone anyway. The conditional forms exist precisely so nobody ever has to do this; a GC who insists on unconditional before funding is asking you to finance their risk. The counter is simple and standard: "conditional now, unconditional when it clears."

Watch the details on each waiver: the through date (work after it isn't covered — on a progress waiver it should match the pay app period), the exceptions box (list disputed change orders and unbilled extras so the waiver doesn't swallow them), and the amount.

The cycle in practice

  1. Pay app goes in → §8132 conditional progress rides with it (the GC's submission checklist almost always demands it).
  2. Payment clears → §8134 unconditional progress for that period, usually handed over with the next month's application.
  3. Retainage and final billing§8136 conditional final with the request; §8138 unconditional final only once the last dollar — retention included — has cleared.

Waivers waive the lien; your preliminary-notice and deadline clock is a separate machine that keeps running regardless — a perfect waiver file doesn't save rights you lost by missing a notice.

Common mistakes

  • Signing the GC's non-statutory form unread. If it doesn't track the statutory text, it can waive more than the payment covers — stop-notice rights, claims, retention.
  • Unconditional finals to "speed up" retention. The order is money, then §8138. Always.
  • Through dates past the period. A progress waiver dated through today covers this week's work the pay app didn't bill. Match it to the application period.

See also

This is how STrOp works

The data flows you read about here are how the platform threads bid, execution, billing, and closeout. Single pipeline. No re-keying.

Request beta access →

Last updated 2026-08-20.