A rejected pay app doesn’t just delay one check — it pushes your money a full billing cycle, which on most jobs means 30 more days of floating payroll and material. Most rejections are for the same handful of mechanical mistakes. This is the checklist that prevents them.

The short version

  • The schedule of values is negotiated once and governs every billing — break it down fine, front-load honestly, and know the billing cutoff dates cold.
  • Bill executed change orders as separate SOV lines, make the math tie to the GC’s log, and keep percent-complete numbers defensible.
  • Use California’s statutory lien waiver forms (Civil Code §§8132–8138): conditional waiver for a check, unconditional only after it clears — never before.
  • Retention on California public works is generally capped at 5%; once the GC is paid, your share is due within 7 days, and wrongful withholding accrues 2% per month.
  • Submit the same complete backup packet every cycle: certified payroll, lower-tier waivers, stored-material docs, and executed COs.

Before the job: set up the schedule of values right

Your schedule of values (SOV) is negotiated once and then governs every billing on the job. Two rules:

  • Break it down finer than you think you need. Big lump line items force you to argue percent complete; granular ones let you bill what’s visibly done. “Rough-in, floors 1–3” bills cleaner than “Rough-in.”
  • Front-load honestly. Weighting early activities (mobilization, submittals, layout) is normal and legitimate; inflating them invites an SOV fight and an auditor’s attention. What you want is an SOV that matches how your costs actually land.

Confirm the billing cutoff date and submission deadline at the preconstruction meeting and put them on the office calendar. Late pay apps often aren’t reviewed until the next cycle no matter how perfect they are.

The application itself

Most GCs want the AIA-style G702/G703 format or their portal’s equivalent. Every cycle, check:

  • Percent complete per line is defensible — your PM should be able to justify each number against field reports if asked
  • Stored materials are billed per the contract: on-site (or insured off-site with a bill of sale), documented with invoices, and listed separately
  • Change orders appear only after they’re executed, as their own SOV lines — burying CO work in base lines is how it gets double-questioned later
  • Retention is calculated at the contract rate and shown correctly against this period and to date
  • The math ties: previous applications + this period + retention = totals that match the GC’s log

California lien waivers: use the statutory forms

California is strict about waiver-and-release forms. Civil Code sections 8132–8138 prescribe four statutory forms — conditional and unconditional, each for progress and final payment — and a waiver that doesn’t substantially follow the statutory language is invalid, while an unconditional one signed before the money arrives is fully enforceable against you.

Working rules:

  • Exchange a conditional waiver for a check, an unconditional waiver only after it clears. That’s the entire system in one sentence.
  • Fill in the through date and exceptions carefully — disputed change orders and unbilled retention should be listed as exceptions, or the waiver may release them.
  • Collect the same waivers from your lower tiers and suppliers before releasing their money; the GC will demand them from you either way.

Retention and prompt payment

On California public works, retention is generally capped at 5 percent, and on private work whatever the contract says governs — but in both cases, state prompt-payment statutes put teeth behind the flow of money. Once the GC receives payment from the owner, your share is generally due within 7 days, and wrongfully withheld amounts accrue a 2 percent per month penalty plus attorney’s fees on the wrongfully withheld portion.

You don’t cite those statutes in a friendly email — but knowing them changes the tone of the unfriendly ones, and it tells you when a “we’re still waiting on the owner” story has expired.

The backup packet

Assemble the same packet every cycle so nothing is hunted for at the deadline: current certified payroll (on public work), lower-tier waivers, stored material documentation, executed COs billed this period, and updated as-builts or field reports if the contract requires them. One complete packet, submitted on time, every cycle — the GC’s payment reviewer learns your apps sail through, and that reputation is worth real days on every check.