Slow-Pay Packet for Small GCs: What to Include

The project manager says the check is “in accounting.”

Accounting says the invoice is missing backup. The owner says the architect has not approved it. The architect says the general contractor never submitted the revised schedule of values. A subcontractor asks whether the GC has been paid. The supplier wants a date, payroll is approaching, and another week of work is already on the schedule.

A small general contractor often does one of two things. The office keeps resending the same invoice with “Just following up” in the email body, or the owner sends an angry message threatening a lien, lawsuit, and shutdown all at once.

Neither is a slow-pay system.

A useful slow-pay packet is an organized job file. It shows what was contracted, performed, and billed; when a complete payment request was delivered; what the payer disputed; what remains undisputed; which notices the contract or law may require; which deadlines are running separately; and what decision comes next.

The packet should let a project manager, bookkeeper, company owner, customer, lender, surety, mediator, lawyer, or court understand the account without reconstructing it from a crowded inbox.

It should also prevent a costly mistake in construction collections: treating the invoice due date, statutory prompt-payment clock, contractual suspension right, mechanic's lien deadline, bond-claim deadline, and lawsuit deadline as if they were the same date.

They are not.

Use Documentorium to organize the business records in this sequence. Have qualified, state-specific counsel or another appropriate professional prepare or review statutory notices and legal filings before a right or deadline is at risk.

Start with the application for payment or invoice. Reconcile approved changes, retainage, credits, receipts, prior billings, disputed lines, and the undisputed balance in the customer statement of account. If an ordinary reminder is appropriate, issue the past-due notice from that reconciled balance.

The statement-of-account guide shows the supporting sequence. The nonpayment notice guide explains why a reminder, contract default notice, suspension decision, lien step, and lawsuit are not interchangeable.

A slow-pay packet is a sequence, not one letter

Organize the packet in stages:

Each stage should be a preserved snapshot. Do not overwrite the original invoice, authorization, notice, or statement after it is sent. Issue a numbered correction or revision and retain both versions.

If payment is already late, do not wait to rebuild every earlier stage before protecting a deadline. Preserve the original submission, confirm whether it was complete, reconcile the account, separate disputed from undisputed amounts, and refer any lien, bond, or filing deadline for qualified review immediately. Then fill the earlier gaps without rewriting the original record.

A reminder is not a default notice. A default notice is not a statutory stop-work notice. A notice of intent to lien is not a recorded lien. A recorded lien is not a foreclosure action. A payment-bond notice is not a lawsuit on the bond. Winning a small-claims judgment does not put money in the bank.

The packet should make those differences visible.

Track three calendars from day one

Use three separate calendars from the beginning of the job.

The contract and prompt-payment clock

This calendar tracks:

• billing-cycle close;
• work or milestone completion;
• proper-invoice submission;
• architect, owner, lender, or GC review;
• approval or written rejection period;
• payment due date;
• retainage release;
• interest or statutory remedy trigger;
• cure notice; and
• any lawful suspension notice and waiting period.

The lien, stop-payment, and bond-preservation clock

This calendar tracks events such as:

• first furnishing;
• preliminary notice;
• each month in which work, equipment, or material was furnished;
• last furnishing;
• substantial completion, completion, termination, abandonment, or cessation;
• recording or serving a completion notice;
• notice to owner, contractor, lender, or surety;
• claim of lien or public-improvement lien;
• payment-bond claim;
• foreclosure or bond action; and
• any deadline-shortening notice.

The triggering terms are legal terms, not casual project labels. “Last furnishing” may not include returning later to correct a punch item. “Completion” may not mean the date the office issued its final invoice. Get jurisdiction-specific advice before assigning those dates.

The dispute and filing calendar

This calendar tracks:

• contractual negotiation or meeting requirements;
• mediation;
• arbitration demand;
• small-claims or civil filing deadline;
• statutory limitation or repose period;
• service of process;
• lien or bond action deadline;
• judgment enforcement; and
• bankruptcy or insolvency events.

Do not pause the lien or bond calendar because the customer promises to pay under the contract calendar. Do not assume a small-claims filing preserves a lien. Do not wait for a lien deadline to decide whether the contract requires arbitration.

Map the payment route before the first invoice

The first page of the packet should be a payment map.

Record:

• project name, address, legal property description where needed, and internal job ID;
• public, private commercial, owner-occupied residential, tenant improvement, federal, state, local, or other project type;
• contracting entity's exact legal name and assumed name;
• customer entity and signer authority;
• property owner, construction lender, tenant, developer, prime contractor, payment administrator, architect, owner's representative, and surety as applicable;
• contract and purchase-order identifiers;
• original contract sum, approved changes, current contract sum, amount billed, amount paid, retainage, and balance;
• billing cycle and payment trigger;
• invoice and notice addresses, portals, recipients, and required delivery methods;
• required schedules, sworn statements, certified payroll, insurance evidence, lien waivers, releases, photos, tickets, inspection records, or other backup;
• dispute, default, suspension, termination, mediation, arbitration, venue, attorney-fee, and governing-law clauses;
• preliminary-notice, lien, bond, stop-payment, and action deadlines identified by qualified state-specific review;
• license and home-improvement-contract requirements where relevant; and
• the responsible employee and backup for each deadline.

Do not infer the property owner from the person giving field instructions. Do not infer the legal customer name from a logo. Do not assume the billing contact is an authorized notice recipient.

For an entity, confirm the exact name through the current official business registry. For real-property rights, use the county or other authoritative land record and the legal rules governing owners, lenders, and required notice recipients. For public jobs, obtain the agency contract and bond information early.

The map prevents a complete invoice from being delivered to the wrong company and a legally significant notice from being sent only to a project manager who lacks authority to receive it.

Make the first payment request complete and provable

Sometimes the payer is late. Other times, the invoice never satisfied the contract in the first place.

Use an application for payment or invoice that includes the information the contract and applicable law require. Depending on the job, that may include:

• contractor legal name, address, taxpayer or vendor identifier through the secure approved channel, and remittance instructions;
• customer, project, contract, purchase order, work authorization, and billing period;
• invoice number and issue date;
• schedule-of-values line, quantity, unit, rate, stored material, prior billing, current work, retainage, and balance;
• approved change-order references;
• dates and locations of performance;
• delivery tickets, equipment logs, daily reports, photos, inspection evidence, or completion acceptance;
• conditional waivers or releases in the exact lawful form and amount;
• lower-tier affidavits or payroll evidence only when authorized, required, and handled securely;
• taxes, credits, offsets, and prior payments;
• payment due date derived from the contract and law;
• the address or system for disputes; and
• an authorized certification that is accurate for the actual payment request.

Never certify that lower tiers have been paid when they have not. Never sign an unconditional release merely because a check is expected. Never include a false amount to create negotiating room.

For federal construction contracts containing FAR 52.232-27, the clause specifies detailed invoice content, points to separate progress-payment substantiation and certification requirements, and sets subcontract payment-clause requirements. The controlling contract and current Federal Acquisition Regulation should be reviewed rather than reduced to a generic commercial invoice checklist.

Preserve the transmittal, not just the attachment

The due-date analysis may turn on when a proper invoice reached a designated office or when required work was accepted.

For every payment request, retain:

• the exact submitted file and a stable version identifier;
• portal submission number, upload result, or acceptance screen;
• email sender, recipients, subject, sent timestamp, and delivery result;
• certified-mail, registered-mail, overnight, personal-service, or other proof where used;
• required attachments and their filenames;
• the contract provision or payer instruction governing delivery;
• a receipt acknowledgment;
• any rejection, deficiency, or resubmission notice; and
• the date the payer treated the package as complete.

An email in the estimator's sent folder does not prove an invoice reached the contractually designated payment office. A portal screenshot showing “uploaded” may not show that all attachments passed validation. A postal tracking page does not prove what was inside the envelope.

Use a transmittal index:

If something is rejected, issue Rev 2 with a short change log. Do not replace Rev 1 in the job folder.

Ask early whether the submission is complete

The first follow-up should not ask only, “When will we be paid?”

Ask:

1. Was the payment request received by the designated office?
2. Is it complete under the contract?
3. Has it been approved, partially approved, or rejected?
4. What exact line, amount, and reason is disputed?
5. What undisputed amount will be processed?
6. What approval and payment dates are currently recorded?

A useful message is:

Please confirm receipt and completeness of Payment Application PAY-004, submitted through the contract portal under confirmation ID ____. If any item is incomplete or disputed, please identify the document or schedule-of-values line, amount, contractual basis, and correction requested in writing. Please also confirm the undisputed amount and its scheduled payment date.

This forces a useful distinction in the record. The payer either confirms the request, identifies a correctable defect, or states a dispute.

Do not let “under review” remain the only status for weeks.

Separate administrative holds from substantive disputes

Use a discrepancy log with one row per issue:

Useful issue categories include:

• missing or incorrect administrative document;
• disputed work quantity or percent complete;
• defective or incomplete work allegation;
• unapproved change;
• backcharge or setoff;
• retainage;
• insurance, payroll, waiver, affidavit, or compliance hold;
• upstream funding or owner-payment claim;
• payee, tax, or banking verification;
• duplicate invoice or credit;
• undisputed amount awaiting payment; and
• unknown reason.

Do not accept a broad “work incomplete” response when only one line is contested. Ask the payer to identify the location, condition, contract requirement, evidence, correction requested, and amount withheld.

At the same time, do not label a genuine performance dispute an “administrative delay” simply to trigger a remedy. Preserve the other side's words and respond with evidence.

Reconcile the account before every formal notice

Use a customer statement of account as the packet's financial spine.

It should show:

• each invoice or pay application;
• original amount;
• approved amount;
• disputed amount;
• undisputed amount;
• retainage withheld;
• payments received and application date;
• credits, corrections, and approved backcharges;
• contractual or lawful interest shown separately;
• current balance;
• aging by due date; and
• the source document behind every line.

Reconcile the statement to the general ledger and bank receipts before sending it. A payment may have reached the wrong project, been applied to the oldest invoice contrary to remittance instructions, or arrived by joint check and remain unresolved.

Do not silently roll a disputed change order into the undisputed contract balance. Do not demand release of retainage before its trigger. Do not add late charges that the contract or law does not authorize.

Use a separate internal calculation sheet for contractual or statutory interest and penalties. The customer-facing notice should state the authority and calculation clearly if those amounts are claimed.

Keep the first reminder administrative

An ordinary slow payment can be corrected without a legal threat.

The first reminder should identify:

• payment request and project;
• complete-submission evidence;
• due date;
• current undisputed balance;
• stated disputes, if any;
• the requested payment date or missing decision;
• who can resolve an error; and
• attachments.

Example:

PAY-004 for Project J-118 shows an undisputed unpaid balance of $18,650. Our record reflects complete submission under portal confirmation ____ and a contractual due date of ____. Dispute log D-02 remains open for $4,200 and is not included in the undisputed amount requested here. Please confirm the payment release date or identify any additional written basis for withholding the $18,650 by ____.

That message is more useful than “third request” in red type. It also creates the factual foundation for a later notice if the account is not resolved.

Send a formal notice only when the facts support it

A formal past-due notice should be drafted from the contract and jurisdiction, not from emotion.

Include, as applicable:

• sender and recipient legal names;
• project and contract identifiers;
• the notice provision being used;
• payment request, submission, completeness, approval, and due-date facts;
• original, paid, disputed, retainage, and undisputed amounts;
• prior communications;
• the specific breach or failure asserted;
• exact cure required;
• cure deadline and how it was calculated;
• permitted payment instructions;
• a contact for a documented dispute;
• the next step actually under consideration;
• a reservation of rights that does not invent rights; and
• attachments and delivery method.

Use “may” when the next step still requires review. Do not say “we'll file a lien tomorrow” if the claimant, project, amount, preliminary notice, deadline, recording office, or legal description has not been verified.

Do not threaten criminal prosecution, license complaints, adverse publicity, immigration consequences, or personal contact with employees or family to force payment. Do not copy unrelated customers or lower tiers as a pressure tactic. Escalation should become more precise, not more dramatic.

Prompt-payment rules depend on the project and state

There is no nationwide “net 30” construction-payment law for every private job.

Current examples show why the packet needs a jurisdiction field:

California private work

California Civil Code section 8800 generally requires an owner to pay a direct contractor an undisputed progress payment within 30 days after the contractor gives a payment demand pursuant to the contract and the applicable statutory notice rules, unless the owner and direct contractor agreed otherwise in writing. The statute allows withholding of no more than 150 percent of an amount subject to a good-faith dispute and provides a statutory consequence for wrongful withholding. Other provisions separately address subcontractor payments, retention, claims, and stop-work notices.

That does not mean every invoice from every tier is automatically due in 30 days. Identify the claimant's tier, written agreement, notice compliance, dispute, and the particular article that applies.

Contracts entered into on or after January 1, 2026, may also fall under California Civil Code section 8850. This temporary statute, scheduled to remain in effect only until January 1, 2030, excludes non-mixed-use residential projects of four stories or fewer. It creates a response, conference, mediation, payment, and conditioned-suspension process for a defined construction claim—not for every routine invoice. Do not assume that an ordinary invoice or a section 8800 payment demand also satisfies section 8850.

New York private construction contracts

New York General Business Law article 35-E addresses billing cycles, invoice review, written disapproval, payment, interest, retainage, and remedies for covered construction contracts. Section 756-a generally requires an owner to approve or disapprove a properly supported contractor invoice within the statutory review period and to identify rejected items in writing. Section 756-b provides carefully conditioned suspension rights, including written notice and an opportunity to cure.

Section 756 generally limits the article to construction projects of at least $150,000 and excludes specified public and residential work. Read the current definitions, contract, and project type before relying on these provisions.

Texas private construction

Texas Property Code chapter 28 governs prompt payment on covered private construction projects and distinguishes owner-to-contractor and downstream payment. It also contains good-faith-dispute and suspension provisions and excludes listed project types. Texas Property Code chapter 53 separately governs lien and notice rights.

A chapter 28 payment notice should not be used as a substitute for the monthly notices or other steps chapter 53 may require.

Florida private construction

Florida Statutes section 715.12 applies to specified written contracts to improve real property for which a construction lien is authorized. It ties prompt-payment treatment to the contractual right to payment, written payment requests, and other conditions. Florida's chapter 713 lien process is a separate system with its own notices, forms, service methods, recording, and enforcement rules.

Federal construction

Federal construction payments can involve the Prompt Payment Act, the current Federal Acquisition Regulation, the prime contract, subcontract clauses, and the Miller Act. FAR 52.232-27 contains construction-specific invoice, payment, interest, retainage, and subcontractor-payment provisions. The Miller Act provides a payment-bond remedy for qualifying unpaid labor or material on covered federal work rather than a lien against federal property.

Do not paste a private-state lien threat into a federal project notice.

Use these examples to identify which rules need checking. They are not a multi-state form.

Treat suspension as a management decision, not a collection threat

Stopping work can limit further exposure. It can also create claims for abandonment, delay, damage, default, replacement cost, or lost schedule if the contractor lacks the right or follows the wrong procedure.

Before any suspension, verify:

• the contract permits it or applicable law supplies the right;
• the invoice is due and the relevant amount is undisputed where required;
• required approvals or conditions were satisfied;
• the correct parties will receive notice;
• content, method, and waiting period are correct;
• no statutory or contractual exception applies;
• the notice preserves rather than waives remedies;
• safety, weather protection, security, permit, inspection, insurance, and property-protection duties can be met;
• stored materials, rented equipment, keys, access credentials, and temporary utilities are addressed;
• schedule, demobilization, storage, and remobilization consequences are documented; and
• management or counsel has approved the step at the company's threshold.

New York General Business Law section 756-b illustrates the point: in covered circumstances it requires specified written notice at least ten calendar days before the intended suspension and an opportunity to cure. A subcontractor's recipient list differs from a contractor's. The provision also addresses site property, time extensions, and remobilization.

That is why “We stop tomorrow unless paid” is not a safe national template.

If suspension is authorized, create a field record before the crew leaves:

• work complete, incomplete, and disputed;
• jobsite condition and photos;
• installed and stored materials;
• open systems and temporary protection;
• hazards and access controls;
• equipment and tools removed or remaining;
• keys and credentials;
• inspections, permits, and notices pending;
• work needed to keep the site from damage; and
• the conditions and approval needed for restart.

Use the daily report to record the as-left condition. A payment dispute does not authorize leaving a dangerous or unprotected site.

Keep lien and bond preservation out of the reminder sequence

Mechanic's-lien and bond rules are formal claim systems. They are not escalating versions of a collection email.

Four examples show how early the separate calendar can start:

• California Civil Code section 8204 generally requires claimants subject to the rule to give preliminary notice no later than 20 days after first furnishing. If served later, the notice generally preserves only work furnished during the preceding 20 days and work furnished afterward. Recipient and tier rules matter.
• Texas chapter 53 uses tier-, project-, and month-dependent notices and deadlines. A GC's monthly billing routine does not replace the claimant's chapter 53 calendar.
• Florida chapter 713 uses notice-to-owner, claim-of-lien, service, and enforcement requirements tied to statutory events. The current statute also permits some deadline-shortening procedures, making passive assumptions especially risky.
• The federal Miller Act allows qualifying claimants on covered federal construction to pursue a payment bond, with a special written-notice rule for a person contracting with a subcontractor rather than the bonded prime.

For each project, create a deadline sheet reviewed by a qualified person:

Do not rely on a generic lien-deadline website, invoice software countdown, or the payer's statement that “you still have time.” Check the current statute, local recording practice, contract, and facts, and involve construction counsel or a reputable notice professional early enough to act.

Control waivers, releases, affidavits, and joint checks

Payment packets often stall around lien waivers or lower-tier documentation.

Track every lien waiver in a release register that shows:

• claimant legal name and tier;
• project and through-date;
• progress or final status;
• conditional or unconditional status;
• amount requested, amount actually received, and payment instrument;
• disputed claims, retainage, change orders, or extras expressly preserved where lawful;
• statutory form or contract form used;
• signer and authority;
• sent and effective dates; and
• matched bank clearance or other condition.

Some states prescribe waiver language or restrict advance waiver. Do not edit required language casually. Do not sign an unconditional waiver before the payment it covers has actually been received and, where relevant, cleared. Do not reuse a waiver with the wrong through-date or amount.

For joint checks, document:

• parties named on the instrument;
• amount and invoices it covers;
• endorsement and deposit authority;
• releases exchanged;
• allocation among projects or lower tiers;
• any remaining dispute; and
• whether the arrangement changes, or expressly does not change, contractual duties.

A joint check can move money. It does not automatically resolve every lien, trust-fund, assignment, priority, or contract issue.

Offer a controlled payment plan when it improves recovery

A payment plan may be better than immediate litigation if the customer acknowledges the balance, can make credible payments, and the plan does not sacrifice more valuable rights unintentionally.

The written plan should identify:

• principal balance the customer acknowledges and any disputed amount;
• credits and prior payments;
• installment amounts and dates;
• payment method and application order;
• lawful interest or fees;
• whether work remains suspended or will resume;
• remobilization and schedule terms;
• what happens on a missed installment;
• whether any concession is conditioned on full timely payment;
• whether lien, bond, guaranty, security, or other rights are preserved, extended, released, or affected;
• who has settlement authority; and
• how full payment will be acknowledged.

Do not agree to wait past a lien, bond, or action deadline because the customer signed a payment schedule unless qualified counsel confirms the effect and the necessary preservation step is completed.

Issue a receipt for each payment and update the statement of account without erasing the balance the customer originally acknowledged.

Set escalation triggers before the account gets worse

Define internal triggers in advance:

The goal is not to send every late invoice to a lawyer. It is to send the right ones early, with a usable file, before a deadline or admission narrows the options.

Small claims is an option, not a threat

Small claims can fit a clean, modest, collectible money claim. The rules are local.

Current official examples differ materially:

• California Courts says an individual can generally file a small-claims case for up to $12,500, while a corporation or other business entity is generally limited to $6,250.
• The Texas State Law Library explains that justice-court claims may reach $20,000, excluding statutory interest and court costs but including attorney fees.
• New York distinguishes ordinary small claims from commercial claims by claimant type and court. New York City Civil Court currently permits qualifying commercial claims up to $10,000, while other city, district, town, or village courts can have different limits and procedures.

Before threatening a small-claims filing in a demand notice, verify:

• the exact legal plaintiff and defendant;
• claimant-type eligibility;
• local monetary limit;
• venue and service;
• whether the claim seeks money only;
• contract mediation, arbitration, or forum language;
• counterclaim and defect risk;
• filing and representation rules;
• lien, bond, and limitation deadlines;
• evidence and witness availability; and
• whether a judgment is realistically collectible.

Do not split a claim improperly to fit a limit. Do not promise that filing produces immediate payment. A court judgment can require separate collection work.

Build the handoff index before the account becomes a case

Keep every approved change order, issued waiver or release, completion record, delivery event, and receipt behind the matching account line. For jobs billed by visible phases, the milestone billing guide helps make the first payment request easier to approve and the later account easier to reconstruct.

The final packet should have a one-page cover memo:

1. project and parties;
2. one-paragraph contract and scope summary;
3. contract sum, approved changes, billed, paid, retainage, disputed, and undisputed balance;
4. current work and site status;
5. chronological payment and dispute timeline;
6. current contractual notices and cure dates;
7. lien, bond, and action deadlines with source and reviewer;
8. known defenses, offsets, counterclaims, or insurance issues;
9. settlement discussions and authority limits; and
10. decision requested.

Index the evidence:

• contract, scope, and payment terms;
• bid, estimate, and schedule of values;
• approved and disputed changes;
• daily reports, photos, tickets, inspections, and sign-offs;
• invoices and pay applications with transmittals;
• account statements and bank reconciliation;
• dispute log and payer responses;
• reminders, notices, and proof of delivery;
• preliminary notices, waivers, bond, lien, and recorder evidence;
• site-protection or suspension record;
• payment plans, releases, and receipts; and
• communications in chronological order.

Do not bury the strongest evidence in a 900-page email export. Give every document a stable ID and cite those IDs from the timeline.

Example: one disputed line on a $24,500 pay application

Assume a small GC has a $96,000 commercial tenant-improvement contract. PAY-003 requests $24,500 for framing, rough electrical coordination, and approved Change Order 2. The contract requires submission through a portal with daily reports, inspection evidence, and a conditional waiver.

At submission

The GC uploads PAY-003 and all required backup. The portal gives confirmation PX-4418. The packet index shows every attachment and version.

Completeness check

Two business days later, the office asks the payment administrator to confirm receipt and completeness. The administrator says the inspection card is unreadable. The GC uploads a legible copy as PAY-003 Rev 1A and preserves both submissions.

Dispute split

The owner approves $20,300 and disputes $4,200 of Change Order 2, saying the signed change covered material but not added labor. The GC creates D-02, attaches the signed change language and daily reports, and carries $20,300 as undisputed rather than demanding $24,500 as one undifferentiated number.

Slow-pay reminder

The undisputed amount reaches its calculated due date without payment. The GC sends the statement, portal proof, approval, and a concise payment-status request. The separate deadline sheet shows that any required preliminary or periodic notices were already handled; their calendar does not wait for the reminder.

Formal review

When payment still does not arrive, management reviews the contract notice clause, applicable prompt-payment law, cure path, suspension exposure, bond or lien preservation, and forum clause. The formal notice demands the $20,300 undisputed balance, preserves D-02, uses the required recipient and delivery method, and states only remedies actually under review.

Resolution

The owner pays $20,300. The GC issues a receipt, updates the statement, matches any conditional release to actual payment, and continues the documented process for D-02. The packet proves that partial payment did not erase the disputed change.

The GC did not need a dramatic letter. It needed a controlled record that made the undisputed obligation difficult to obscure.

Final quality check

• [ ] Project, owner, customer, contracting tier, lender, surety, and notice parties are verified.
• [ ] Contract payment, notice, dispute, suspension, termination, and forum clauses are indexed.
• [ ] The payment request satisfies contract and project-type requirements.
• [ ] Submission content, recipient, time, and delivery proof are preserved.
• [ ] Completeness, approval, rejection, and dispute decisions are requested in writing.
• [ ] Administrative defects and substantive disputes are separated.
• [ ] Statement of account reconciles invoices, payments, credits, retainage, disputed amount, and undisputed balance.
• [ ] Prompt-payment calculations use the correct project and claimant rules.
• [ ] Lien, stop-payment, and bond deadlines run on a separate reviewed calendar.
• [ ] Conditional and unconditional waivers are matched to actual payment and correct through-dates.
• [ ] Formal notices comply with required content, recipients, delivery method, and cure period.
• [ ] No suspension occurs without contract, statutory, site-protection, schedule, and management review.
• [ ] Any payment plan preserves or changes rights only as deliberately documented.
• [ ] Court or arbitration language is used only after forum, amount, deadline, and collectability review.
• [ ] The final handoff is indexed, chronological, and readable without inbox reconstruction.

Sources

Sources were checked on August 19, 2026, against the official legislative, court, FAR, and U.S. Code pages then available. The FAR page displayed FAC 2026-01, effective March 13, 2026, and the Texas State Law Library page was last updated November 25, 2025. Always confirm the governing contract, statute, court rule, official form, and local procedure for the actual project and claimant before acting.

• California Civil Code § 8800 — Private-Work Progress Payments
• California Civil Code §§ 8850–8851 — Private-Work Claims and Disputes
• California Civil Code §§ 8200–8216 — Preliminary Notices
• California Civil Code — Private Works of Improvement, Liens, Stop Payment Notices, Bonds, and Prompt Payment
• New York General Business Law § 756-a — Construction Contract Obligations
• New York General Business Law § 756-b — Construction Contract Remedies
• New York General Business Law § 756 — Definitions and Coverage
• New York General Business Law Article 35-E — Construction Contracts
• Texas Property Code Chapter 28 — Prompt Payment to Contractors and Subcontractors
• Texas Property Code Chapter 53 — Mechanic's, Contractor's, or Materialman's Lien
• Florida Statutes § 715.12 — Construction Contract Prompt Payment Law
• Florida Statutes Chapter 713 — Liens
• Federal Acquisition Regulation 52.232-27 — Prompt Payment for Construction Contracts
• 31 U.S.C. § 3903 — Prompt Payment Regulations
• 40 U.S.C. § 3133 — Miller Act Payment-Bond Claim Rights
• California Courts — Small Claims or Limited Civil
• Texas State Law Library — Justice Court Claim Limit
• New York City Civil Court — Small Claims and Commercial Claims

This article is a document-workflow framework, not legal, accounting, tax, insurance, licensing, lien, bond, or collection advice. Prompt-payment rules, lien and bond remedies, notice recipients, forms, service methods, deadlines, suspension rights, waivers, public-project procedures, small-claims limits, arbitration duties, and record-retention requirements vary by jurisdiction, project, contract, claimant tier, and current law. Verify every material step with current primary sources and qualified local counsel before a deadline or remedy is at risk.