Lower-Tier Contractor and Supplier Claims

The lower-tier claim usually starts with a sentence that sounds harmless.

"We did the saw-cutting for your concrete sub, and they still owe us."

Or:

"Your roofing sub assigned payment to us for the materials."

Or:

"We are sending this notice to protect our rights. We are a sub-subcontractor on the project."

If you are the GC or an upper-tier trade, you may think the answer is simple: "I did not hire you."

Sometimes that is the right starting point. It is not the whole answer.

A sub-subcontractor or supplier usually does not have a simple breach-of-contract claim against the GC or upper-tier contractor just because it worked on the project or shipped materials to it. But lower-tier parties can still reach an upper tier through payment bonds, lien statutes, trust-fund statutes where they apply, third-party beneficiary language, assignments, joint-check agreements, direct-payment promises, warranty pass-throughs, and sloppy flow-down clauses.

The trap is not that every sub-sub can sue every upper-tier contractor. The trap is believing they never can.

If you are building that file from scratch, start with the construction document catalog and keep the core forms simple: a clean construction contract agreement, a tight statement of work, written work orders, current daily reports, pay applications, properly matched lower-tier lien waivers, and proof of payment. If the file is loose, the lower-tier party has room to make arguments you could have avoided.

Start with the payment chain

On a small commercial buildout or residential remodel with specialty trades, the chain may look like this:

The contract line is not the same as the risk line.

The GC may have no direct contract with the sub-sub, and an upper-tier trade may have no direct contract with the supplier below its own sub. Still, the upper tier may receive a lien notice, a state bond claim, a direct-payment request after the first-tier sub falls behind, or an assignment notice saying a specific invoice has been assigned. On a federal job, the prime can also receive a Miller Act notice from a qualifying lower-tier claimant.

The right response is not a text argument. The right response is a paperwork audit.

Pull the signed subcontract, any lower-tier subcontract approval, the purchase order, project specifications, pay applications, transmittals, submittal register, delivery tickets, lien waivers, bond information, and the latest customer statement of account. Then figure out what legal lane the lower-tier party is using.

The six lanes that let a lower-tier claim move upward

Do not treat every letter from a sub-subcontractor the same way.

That table is why "we have no contract" is incomplete. It may defeat one claim and leave five others untouched.

Assignment is not magic, but it is not nothing

An assignment is a transfer of a right. On a job file, the common versions are:

• assignment of invoice proceeds;
• assignment of a subcontract payment application;
• assignment of a purchase-order receivable;
• assignment of a claim after a dispute;
• assignment of warranty rights;
• assignment of lien or bond claim proceeds where state law allows it.

The assigned right usually cannot be better than the right the assignor had. If the first-tier subcontractor is not owed money because the work is defective, incomplete, overbilled, or offset by backcharges, the assignee may inherit that problem.

But assignment still matters because it changes who is asking for the money and where payment must be sent. If the electrical sub assigns its next $18,000 draw to the switchgear supplier and the GC acknowledges that assignment, the GC cannot casually pay the electrical sub and assume the supplier will disappear.

Before honoring or acknowledging an assignment, ask for:

1. The signed assignment.
2. The invoice or pay application being assigned.
3. The subcontract section allowing or limiting assignment.
4. Written direction from the subcontractor.
5. Confirmation that the assignment is partial or complete.
6. Any competing financing, factoring, tax levy, garnishment, or supplier notice.
7. A lien waiver or release matched to the payment.
8. A written credit against the subcontractor's account.
9. Confirmation that the payment will not impair lien, bond, retainage, defect, backcharge, or setoff rights.

Do not turn an assignment into a side deal by accident. A short written acknowledgment can say that any payment is being handled only as a credit against amounts otherwise due under the subcontract, subject to all contract defenses, offsets, lien and bond defenses, retainage, competing claims, and actual payment clearance.

Do not assume an assignment overrides licensing rules, bond rules, lien statutes, anti-assignment language, or competing financing claims. It is a document to verify, not a shortcut around the rest of the file.

If that sentence feels too legal for the truck, it belongs in the office file before money moves.

Third-party beneficiary language is where loose drafting bites

Third-party beneficiary law is state-specific, but the practical question is consistent: did the contract show an intent to give this outside party a direct enforcement right?

Virginia is a useful example because the statute is plain about the concept. Virginia Code Section 55.1-119 allows a person who is not a party to an instrument to sue when a covenant or promise is made for that person's benefit, subject to defenses the promisor could assert.

That does not mean every lower-tier subcontractor automatically wins. In Environmental Staffing Acquisition Corp. v. B & R Construction Management, a sub-subcontractor tried to sue the general contractor as a third-party beneficiary of the upper-tier contract. The Virginia Supreme Court treated the lower-tier party as only incidentally benefited by the contract, not an intended beneficiary of it.

The lesson for small contractors is not "Virginia says sub-subs cannot sue." The lesson is narrower and more useful: words matter. A contract that names a class of lower-tier parties as direct beneficiaries is different from a contract that simply requires the work to benefit the owner or project.

Watch these phrases:

If you intend to create a direct right, say it deliberately. If you do not, say that too.

Flow-down clauses should carry duties, not confusion

Flow-down language is supposed to align the chain. The owner requires the GC to meet schedule, insurance, safety, warranty, submittal, cleanup, and payment documentation obligations. The GC passes the relevant obligations to the first-tier sub. The first-tier sub passes relevant pieces to its sub-subcontractor or supplier.

That is sensible.

The problem is lazy flow-down language that says every upstream document, addendum, spec, general condition, insurance exhibit, change directive, and owner rule is incorporated into every lower-tier agreement whether it fits or not.

ConsensusDocs' flow-down guidance warns that broad incorporation can create conflicting terms and may fail to push the intended risk where the drafter thought it went. AIA's A401-2017 summary shows how one standard subcontract form passes defined contractor obligations to the subcontractor for the subcontracted work, and notes that A401 can be modified for a sub-subcontractor relationship.

For an owner-operator, the practical rule is simple: do not rely on "all prime contract terms flow down" as your entire subcontract.

Write the pieces that matter:

• exact scope;
• drawings and revisions that apply;
• excluded upstream terms;
• order of precedence if documents conflict;
• site rules and safety requirements;
• insurance and certificate requirements;
• pay application backup;
• lower-tier notice duties;
• lower-tier lien waiver duties;
• warranty pass-throughs;
• submittal and material approval rules;
• change-order procedure;
• no-direct-deal rule unless approved in writing.

Use the request for information when the upstream documents do not match the field. Use Change Orders: Get the Signature Before You Pick Up the Tool when the lower-tier scope is changing. Do not bury a scope change inside an email chain and expect a flow-down clause to clean it up later.

Bond and lien rights are separate from contract privity

Payment bonds and mechanics liens exist because construction payment chains are fragile.

On federal construction projects, the Miller Act at 40 U.S.C. Section 3133 allows covered persons who furnish labor or material and remain unpaid after 90 days to bring a civil action on the payment bond. A claimant with a direct contractual relationship with a subcontractor but no express or implied contract with the prime contractor must give the prime written notice within 90 days from last furnishing for the claim being made. The statute also sets a one-year outside period for filing the civil action.

Do not read that as unlimited lower-tier coverage. A supplier to a supplier, a party below the protected tiers, or a claimant outside the bond statute may have a different answer. Identify the claimant's tier before you treat the letter as either harmless or fatal.

That is not the same thing as a breach-of-subcontract claim against the prime. It is a bond claim. The difference matters, but the practical result is still a claim landing on the prime contractor's desk.

Federal construction contracts can add another layer. FAR 52.232-27 requires prompt-payment and interest clauses in subcontracts for property or services, including material suppliers, and requires lower-tier flow-down of those clauses. It also addresses notices from a second-tier subcontractor or supplier and the prime's ability to withhold from later first-tier payments when the prime may be ultimately liable. Check the current FAC version before using this on an active federal job.

Private lien law is state-specific, but the same pattern appears: lower-tier parties may have statutory rights even without a direct contract with the owner, GC, or prime contractor.

Florida is direct about it. Florida Statutes Section 713.06 covers liens of persons not in privity and expressly includes sub-subcontractors who comply with the statute. The notice-to-owner timing, required recipients, and final-payment rules matter.

Texas uses a derivative-claimant notice structure. Texas Property Code Section 53.056 requires a claimant other than an original contractor to send the statutory notice for the lien to be valid, with different timing for residential and nonresidential projects. If Texas is your state, pair this with Texas Mechanic's Lien Notices. If Florida is your state, pair it with Florida Construction Lien Notice to Owner.

The point is not to become a lien lawyer. The point is to stop confusing "not my subcontract" with "not my problem."

Joint checks and direct payments need a written lane

Joint checks can be useful. So can direct payments.

They are also where a GC accidentally creates a new argument.

Suppose the HVAC sub is behind with the equipment supplier. The supplier will not release the condenser package unless the GC issues a joint check. The GC wants the equipment on site because the job is already behind. Everyone is tired. Someone sends a text: "We will take care of you on the next draw."

That text can become evidence.

Before issuing a joint check or paying a lower-tier party directly, document:

• who requested the arrangement;
• whether the first-tier subcontractor authorizes it;
• whether the payment is a credit against the subcontract balance;
• whether the lower-tier party is releasing only the paid amount or a broader claim;
• whether retainage, backcharges, disputed scope, or stored materials are excluded;
• whether the check endorsement itself is treated as a release;
• whether future payments require separate approval;
• who remains responsible for warranty, completion, and defects.

A direct lower-tier payment should be tied to an invoice, pay application, delivery record, and conditional waiver. A joint check should not be a handshake workaround for a broken subcontract.

If the payment problem is already serious, read Stopping Work for Nonpayment before the crew response outruns the notice file. If the first-tier subcontract has conditional payment language, read Pay-When-Paid vs Pay-If-Paid before promising the lower-tier party anything.

Your first-tier subcontract should control lower-tier parties

The first-tier subcontract is where most of this risk should be managed.

A small GC or trade contractor should not need enterprise paperwork to do this. The subcontract should answer these questions:

This is where What to Cross Out in Big-Company Contract Templates matters in reverse. If you are sending the subcontract, do not add one-sided language you cannot administer. If you are signing someone else's subcontract, do not accept lower-tier risk without the control rights to manage it.

Pay applications should flush out unpaid lower tiers

The monthly application for payment should not just ask "How much work did you finish?"

It should ask:

1. Who performed the work in this billing period?
2. Which lower-tier parties supplied labor, materials, equipment, or special fabrication?
3. Which lower-tier invoices are included in this pay application?
4. Which lower-tier parties were paid from the last payment?
5. Which waivers are attached?
6. Are there any unpaid notices, disputed invoices, supplier holds, or threatened claims?
7. Are any payments assigned, factored, garnished, or subject to joint-check agreement?
8. Are any materials stored off site or paid by deposit?

Back up those answers with documents:

• conditional progress waivers;
• unconditional waivers only after payment clears;
• supplier invoices;
• delivery tickets;
• stored-material photos;
• daily report headcounts;
• certificate of insurance requests;
• submittal approvals;
• change-order logs;
• open notice log.

If a sub-sub later says it was invisible, the pay application file should show otherwise. The goal is not to paper them to death. The goal is to know whether the money you are releasing will actually close the lower-tier exposure it is supposed to close.

Be careful with warranty pass-throughs

Lower-tier parties can also reach the file through warranties.

AIA's A401 summary notes special warranties may need to be written in the owner's name or transferable to the owner. That makes sense for a roof membrane, HVAC compressor, coating system, window package, or other product-backed installation.

But warranty pass-throughs should be specific.

Do not write:

"All lower-tier warranties pass through to everyone."

Write the job reality:

• the installer remains responsible to its contracting party;
• manufacturer warranties pass through only to the extent the manufacturer allows;
• special warranties must name the correct beneficiary or be transferable;
• labor to remove and reinstall third-party products is covered only if stated;
• warranty claims must be documented with notice, photos, serial numbers, and maintenance records;
• the GC's warranty to the owner and the sub-sub's warranty to the first-tier sub are related but not identical unless the contract says so.

This pairs with Waiver of Subrogation and The Clause That Blocks Lost Profit Blowups. A warranty pass-through should fix defects and preserve product rights. It should not silently turn a $12,000 subcontract into insurance for every downstream business loss.

What to do when a sub-sub sends a claim

Do not ignore it. Do not admit it. Sort it.

Use this first-hour checklist:

1. Save the notice, envelope, email headers, delivery proof, and attachments.
2. Identify the claimant's tier and who hired them.
3. Identify the project, property, owner, prime contract, subcontract, bond, and job number.
4. Ask for the claimant's contract, invoices, delivery tickets, work dates, and amount.
5. Check whether you have paid the first-tier subcontractor for the claimed work.
6. Check whether the first-tier subcontractor listed the claimant on prior pay applications.
7. Check lien, bond, and prompt-payment notice deadlines.
8. Check existing waivers and releases.
9. Send the first-tier subcontractor a written demand for explanation, defense, and resolution.
10. Hold or reserve enough money, where the contract and law allow, to avoid paying the same work twice while you sort the claim.

The demand to the first-tier subcontractor should be short:

"We received a lower-tier claim from [claimant] for [amount] related to [scope]. Provide within three business days: your contract or purchase order with the claimant, all invoices, proof of payment, lien waivers, any dispute explanation, and your proposed resolution. Pending review, we reserve all rights to withhold amounts, require defense and indemnity, issue joint payment, or take other action allowed by the subcontract and applicable law."

Attach the claim. Log the date. Keep the response with the subcontract file.

If the amount is already past due, use a past-due notice or formal default letter for the first-tier sub, not a casual group text. If the issue is incomplete or defective work, document the defect before withholding. If the field facts are messy, send an RFI or write a daily report entry instead of trying to solve the entire dispute by phone.

The contract language worth having

For a small contractor, these are the clauses to review before the next subcontract goes out:

• No lower-tier subcontracting without written approval where licensing, insurance, safety, warranty, or site access matters.
• Lower-tier contracts must include applicable scope, safety, insurance, warranty, payment, waiver, dispute, and notice duties.
• No assignment of payment, claims, or subcontract rights without written consent, except where law prevents restriction.
• No third-party beneficiaries except those expressly named.
• Direct payment and joint checks are allowed only as a credit against amounts otherwise due, subject to all defenses and offsets, and do not create broader obligations unless signed separately.
• Subcontractor must provide lower-tier waivers, invoices, and proof of payment with each pay application.
• Subcontractor must defend, indemnify, and hold the contractor harmless from lower-tier payment claims to the extent caused by subcontractor nonpayment or breach.
• Contractor may withhold enough to cover lower-tier claims, disputed work, defective work, missing waivers, and unresolved notices, where the subcontract and applicable law allow it.
• Warranty pass-throughs must identify the beneficiary, duration, scope, transfer method, and labor responsibility.
• Notice addresses, delivery methods, and response deadlines must be written.

Do not overreach. A clause you cannot administer is not protection. It is future confusion.

The cleaner move is to pair the clause with the document workflow: approval before lower-tier hire, waiver with pay app, proof after payment, written notice when a claim appears, and a clear closeout file before final payment. If the whole agreement needs a wider review, use Every Trade Contract Needs These 12 Clauses before you isolate the lower-tier language. The affidavit of payment of debts and claims and consent of surety to final payment exist for bigger closeout files, but the same idea works on smaller jobs: final money should not move while lower-tier claims are hidden.

The owner-operator rule

"No privity" is a defense, not a filing system.

When a lower-tier party appears, do not start with the argument. Start with the documents.

Who hired them? What did they provide? Was the work in your scope? Was the first-tier sub paid for it? Did they send a lien or bond notice on time? Did anyone assign payment? Did you sign a joint-check agreement? Did your subcontract create a third-party beneficiary argument? Did your pay app include their invoice? Do you have a waiver? Is there enough money left to prevent double payment?

That is the difference between a claim you can contain and a claim that spreads through the job.

A sub-subcontractor does not become your subcontractor just because they send a letter. But if your paperwork is loose, your payments are undocumented, your flow-down language is sloppy, and your joint-check promises are casual, they may have enough hooks to make you spend real time and money proving otherwise.

Sources

• Office of the Law Revision Counsel, 40 U.S.C. Section 3133, Rights of persons furnishing labor or material, checked May 11, 2026
• Acquisition.gov, FAR 52.232-27, Prompt Payment for Construction Contracts, FAC 2026-01, checked May 11, 2026
• Florida Senate, Florida Statutes Section 713.06, Liens of persons not in privity; proper payments, checked May 11, 2026
• Texas Constitution and Statutes, Texas Property Code Chapter 53, including Section 53.056 derivative claimant notice, checked May 11, 2026
• Code of Virginia Section 55.1-119, When person not a party may take or sue under instrument, checked May 11, 2026
• Environmental Staffing Acquisition Corp. v. B & R Construction Management, Inc., Supreme Court of Virginia opinion reproduced by Justia
• AIA Contract Documents, Summary: A401-2017 Standard Form of Agreement Between Contractor and Subcontractor, updated October 29, 2025
• ConsensusDocs, Navigating the Flow-Down of Risk Through Multiple Contract Layers, Thomas J. Madigan, March 15, 2017
• ConsensusDocs, 750 Constructor and Subcontractor Agreement Long Form

This article is for general information and is not legal, tax, insurance, safety, or compliance advice. Verify contract, assignment, lien, bond, prompt-payment, trust-fund, waiver, warranty, licensing, and state-specific rules with your attorney, surety, insurance adviser, state contractor board, local authority having jurisdiction, or CPA before acting.