The GC Says the Owner Hasn't Paid: What Records Should a California Subcontractor Organize?

# The GC Says the Owner Hasn't Paid: What Records Should a California Subcontractor Organize?

A common construction-payment sentence can stop a subcontractor cold:

• “We cannot pay you yet because the owner has not paid us.”

Sometimes that statement is part of a real project cash-flow problem. Sometimes it points to a contract clause. Sometimes it is connected to a disputed change order, retention hold, missing paperwork, lien waiver request, public-project funding issue, or an ordinary late-payment excuse.

Either way, the next step should not be panic. It should be a clean project record.

Before you rely on a deadline, send a legal threat, sign a waiver, record a mechanics lien, serve a stop payment notice, pursue a payment bond claim, or escalate the dispute, organize the facts that explain the project, the payment chain, and the amount owed.

This article is a records-first checklist for California subcontractors and suppliers facing an upstream-payment delay.

Start with the exact reason payment is being delayed

Do not leave the reason vague. Save the communication where the GC, customer, or upstream party explains why payment has not been made.

Common explanations include:

• The owner has not paid the GC.
• The lender has not released funds.
• The public entity has not processed the pay application.
• The architect or owner rejected part of the pay application.
• A change order is disputed.
• Retention is being held until project closeout.
• A lien waiver or release is required before payment.
• Backup paperwork is missing.
• The GC is waiting for payment from another tier.

Those facts can point in different directions. A missing invoice attachment is different from a disputed scope issue. Retention is different from a rejected change order. A private project is different from a public works project. A waiver request before cleared payment is different from a routine payment package.

The safest first move is to preserve the message and build the file around it.

Pull the contract before interpreting “pay when paid” language

If someone says payment depends on the owner paying first, find the contract provision they are relying on.

Look for language about:

• Payment timing.
• Pay-if-paid or pay-when-paid clauses.
• Conditions precedent to payment.
• Owner approval.
• Pay application procedures.
• Change order approval.
• Retention.
• Backcharges or setoffs.
• Dispute notice requirements.
• Lien waivers and releases.
• Claims, mediation, arbitration, venue, or attorney-fee provisions.

Do not assume the clause means what the GC says it means. Contract interpretation can be legally sensitive, especially when payment rights, statutory remedies, deadlines, and waiver language are involved.

For StreamLien's purposes, the important step is practical: save the signed contract, change orders, purchase orders, proposals, terms and conditions, and any emails that changed the deal.

Build the payment-chain timeline

A payment-chain dispute is easier to review when the dates are in one place.

Create a simple timeline with:

• Contract or purchase order date.
• First date labor, services, equipment, or materials were furnished.
• Key delivery dates.
• Pay application dates.
• Invoice dates.
• Change order request dates.
• Approval, rejection, or response dates.
• Payment dates and partial payment dates.
• Last furnishing or last work date.
• Notice dates, if any.
• Lien waiver or release dates.
• Date the GC first said the owner had not paid.
• Date the GC last promised payment.

That timeline helps separate three questions that often get mixed together:

1. What work or materials were provided? 2. What amount is unpaid? 3. What document or deadline might matter next?

Separate base contract, change orders, retention, and disputed amounts

A single unpaid balance may contain several buckets. Do not treat them all the same until the documents have been reviewed.

Break the balance into categories:

• Approved contract balance.
• Approved change orders.
• Pending or disputed change orders.
• Retention.
• Backcharges or claimed offsets.
• Materials stored but not installed.
• Final invoice amounts.
• Interest, fees, or collection charges.

For each bucket, save the support:

• Invoice or pay application.
• Signed change order or written approval.
• Field directive, RFI, email, or text approving extra work.
• Delivery ticket, daily report, photos, or time record.
• Payment history showing what has and has not been paid.
• Any rejection notice or explanation from the GC or owner.

This is especially important for unpaid change orders. Current California private-works payment-process coverage has made change-order records a timely topic, but public-facing content should avoid overpromising legal outcomes. The useful, low-risk takeaway is simple: disputed extras need a clean paper trail before escalation.

Confirm the project type before assuming the remedy

A subcontractor who is unpaid on a construction project may think first about a mechanics lien. But project type matters.

Your file should identify whether the project appears to be:

• Private residential.
• Private commercial.
• California public works.
• Federal project.
• Mixed or unclear.

Save the project address, owner information, public entity information if any, prime contractor information, lender information if known, and any bond information available.

Why this matters: different project types can point to different paperwork paths. A private mechanics-lien question is not the same as a public-works stop payment notice or payment-bond question. If the project type is unclear, that uncertainty should be flagged early instead of discovered after time has been lost.

Check preliminary notice records

If preliminary notice was required or sent, organize the proof before making assumptions about payment rights.

Save:

• The preliminary notice copy.
• Owner, direct contractor, construction lender, and other recipient information used.
• Mailing or service proof.
• Certified mail receipts, tracking, or proof of service.
• Date mailed or served.
• First furnishing date used for the notice.
• Any returned mail or address correction.

If no preliminary notice was sent, note that too. Do not guess about the consequences in public-facing copy or a demand letter. Missed or late notice issues can be legally sensitive and should be reviewed against the actual role, project type, dates, and facts.

Review lien waivers and releases before signing anything new

A GC may ask for a waiver, release, conditional waiver, unconditional waiver, progress waiver, final waiver, or closeout document before making payment.

Do not treat those documents as interchangeable.

Collect every waiver or release connected to the project and note:

• Who signed it.
• Which project it identifies.
• Which invoice, pay application, or period it covers.
• The through date.
• The amount stated.
• Whether it is conditional or unconditional.
• Whether payment actually cleared.
• Whether any exceptions or reservations were included.
• Whether another waiver is being requested before payment is received.

This is a major review flag. Signing the wrong payment document can create avoidable leverage and claim problems. If someone is asking for a release while also saying the owner has not paid, slow down and get the actual document reviewed.

Save communications without escalating too quickly

When payment is late, it is tempting to send an angry email or a lien threat immediately. Sometimes a stronger communication is appropriate. But first save the thread.

Create a communication folder with:

• Payment reminders.
• Promises to pay.
• “Owner has not paid” messages.
• Pay application comments.
• Change order rejections.
• Backcharge notices.
• Meeting notes.
• Text messages or field communications.
• Requests for waivers, releases, W-9s, insurance, payroll records, certified payroll, or closeout documents.

Then review whether the next communication should be a routine follow-up, document request, payment demand, intent letter, notice-related step, lien-related review, public-works route review, or attorney communication.

The wording matters. Public-facing threats, deadline statements, and legal conclusions should not be improvised.

Ask for the missing project-payment facts in writing

A calm records request can clarify the dispute without overcommitting legally.

Depending on the relationship and the documents, the subcontractor may need to ask for:

• Which pay application includes the subcontractor's work.
• Whether the owner approved or rejected that pay application.
• Whether the disputed amount is base scope, change order, retention, or backcharge.
• Whether payment has been received for any part of the subcontractor's work.
• What paperwork the GC claims is still missing.
• Whether a bond, lender, or public entity is involved.
• Whether the GC is requesting a conditional or unconditional waiver.
• When the GC expects to release payment.

Keep the request factual. The goal is to complete the file, not accidentally waive a position or make a legally loaded statement.

Know when to route the file for legal review

Some records are useful for ordinary admin follow-up. Others are legal-review triggers.

Flag the file for legal review before relying on:

• Pay-if-paid or pay-when-paid clause interpretation.
• Preliminary notice consequences.
• Mechanics lien eligibility or deadline calculations.
• Stop payment notice or payment bond claim timing.
• Public works vs private works classification.
• Unpaid change order rights.
• Retention release rights.
• Lien waiver or release effect.
• Demand letter language.
• Threats to record, serve, enforce, release, or foreclose a lien.
• Settlement, compromise, or release language.

StreamLien can help organize the facts, but final legal conclusions should be reviewed before customer reliance or external communications.

A practical checklist for the subcontractor's project file

Before escalating, organize these records:

• Signed contract, subcontract, purchase order, proposal, and incorporated terms.
• Change orders, change directives, RFIs, emails, and field approvals.
• Project address, owner, GC, lender, public entity, and bond/surety information if known.
• First furnishing, last furnishing, delivery, and work dates.
• Pay applications, invoices, continuation sheets, and backup.
• Payment history and unpaid-balance calculation.
• Retention calculation and closeout status.
• Preliminary notice copy and mailing/service proof.
• Lien waivers, releases, conditional/unconditional forms, and through dates.
• Communications about owner nonpayment, delayed funding, rejections, backcharges, and payment promises.
• Public/private/federal project classification notes.
• Any deadline, notice, or escalation concern that needs review.

The bottom line

When a GC says the owner has not paid, the right answer is not automatically “wait,” “file a lien,” or “send a threat.” The right first step is to organize the project record.

A clean file helps show what was agreed, what was performed, what was billed, what was paid, what remains unpaid, what notices were sent, what waivers were signed, what project type is involved, and what legal-review questions need attention.

That makes the next step more careful — whether it is a payment follow-up, document request, lien-related review, public-works payment route, waiver review, or attorney-reviewed escalation.

FAQ

Does “the owner has not paid” mean a subcontractor has no options?

Not necessarily. It depends on the contract, project type, payment-chain facts, notices, deadlines, waiver history, and applicable law. The safe first step is to organize the record and flag any pay-if-paid/pay-when-paid language for review.

Is pay-when-paid the same as pay-if-paid?

Do not assume they are the same. Contract language and enforceability questions can be legally sensitive. Save the exact clause, the full contract, payment history, and all related communications for review.

Should I sign a lien waiver if payment has not cleared?

Be careful. The effect can depend on whether the waiver is conditional or unconditional, what amount and through-date it covers, and whether payment actually cleared. Gather the document and get it reviewed before signing or relying on it.

What records should I collect if the GC says the owner has not paid?

Start with the contract, invoices, pay applications, change orders, payment history, preliminary notice records, waiver/release history, first and last furnishing dates, project type, owner/GC/lender/public entity information, and communications explaining the delay.

Does this issue change if the project is public works?

It can. Public-works payment routes may involve stop payment notices and payment bond claims rather than a private mechanics-lien path. Project type should be identified early and reviewed before selecting a document route.

Can StreamLien tell me exactly what deadline applies?

Deadline statements need review before customer reliance. StreamLien helps organize the facts needed for deadline review: project type, role, first/last furnishing, notice history, completion information, payment records, and document history.