Slow-Pay Packet for Small GCs: What to Include Before You Escalate
Build a slow-pay packet with complete billing records, delivery proof, a reconciled balance, disputed lines, and separate notice, lien, bond, and filing calendars.

For example, a GC resends a pay application three times. Accounting says backup is missing; the project manager says one change is disputed. Nobody has separated the amount awaiting paperwork from the amount already approved but unpaid.
A slow-pay packet should show the agreed payment trigger, complete submission, approved and disputed amounts, missing backup, and response requested. Start with Documentorium's application for payment template, then reconcile it with a statement of account. Keep contractual notices, lien or bond deadlines, and collection decisions on their own tracks.
Map the parties and payment route
Record the exact contracting entities, project, claimant tier, owner, payment administrator, designated billing office, notice recipients, and any lender or surety. Classify the project as private, public, or federal; do not select a remedy from the job's nickname.
Index the contract's billing requirements, payment trigger, review process, retainage, notice methods, cure, suspension, dispute forum, and fees. Keep approved change orders connected to their billing lines.
There is no universal construction “net 30” rule. For example, FAR 52.232-27 defines proper-invoice and payment requirements for contracts containing that federal construction clause. Its framework is not a private-job default.
Preserve a complete submission
Retain the exact invoice or pay application, required backup, version, recipient, submission time, portal confirmation, and delivery evidence. A tracking record alone does not identify the documents delivered.
Ask the payer to confirm receipt and completeness, then identify every rejected line and missing item. If corrected, issue a new version with a short change note and preserve the original. Do not silently alter a sent invoice or signed certification.
For milestone jobs, the billing-schedule guide helps connect each payment request to its agreed trigger and evidence.
Reconcile before demanding payment
Use a statement of account that shows original billings, approved changes, payments, credits, disputed amounts, retainage, and the current balance. Match receipts to the correct invoice and remittance instructions. The account-reconciliation guide explains that sequence.
Keep one row per unresolved issue:
| Issue | Evidence needed | Treatment |
|---|---|---|
| Missing inspection card | Contract requirement and legible record | Correct administrative submission |
| Disputed change labor | Signed scope, authorization, daily support | Preserve and investigate the disputed amount |
| Claimed cleanup backcharge | Notice, basis, work and cost evidence | Record as a disputed offset until resolved |
| Approved unpaid balance | Approval, due-date basis, payments | Request a specific release date |
Do not concede a disputed change by excluding it from an undisputed-payment request. Label it separately. Claim interest or fees only with a valid basis and transparent calculation.
An illustrative reminder might say: “PAY-04 has an approved unpaid balance of $8,000. The separate $1,200 change remains disputed in issue D-02. Please confirm release of the $8,000 or identify the specific withholding basis.” These are example figures, not a legal demand form.
Run independent calendars
Track three groups of dates:
- Billing, approval, payment, contractual notice, and cure.
- Preliminary notices, lien or bond preservation, and any enforcement or deadline-shortening notice.
- Negotiation, mediation or arbitration, lawsuit, service, and other filing deadlines.
For each deadline, retain its governing source, triggering event, supporting evidence, calculated date, reviewer, and responsible person. Do not assume a final invoice establishes “last furnishing,” or that a payment promise pauses a statutory clock.
The Miller Act, 40 USC 3133, illustrates a separate payment-bond remedy on covered federal work, including tier-dependent notice and action conditions. An ordinary reminder does not satisfy those requirements.
Escalate with the right document
A past-due notice can state the verified balance, due-date basis, prior delivery, dispute status, requested cure, and appropriate next step. It does not automatically serve as a default notice, suspension notice, lien, or bond claim.
New York GBS 756 limits its construction prompt-payment framework by project value and exclusions. Within covered circumstances, section 756-b conditions suspension on specified notice and cure steps. Other projects require different analysis.
Before stopping, follow the nonpayment-suspension guide and document safe site protection, unfinished work, materials, access, and restart conditions. Do not threaten a remedy that has not been verified.
Control releases too. CSLB's waiver guidance distinguishes California's conditional and unconditional forms. Match the applicable form, amount, period, and actual payment; do not certify unpaid lower tiers as paid.
If bankruptcy appears, obtain advice before further collection activity. The US Courts' bankruptcy overview explains the automatic stay and its limits.
Make the handoff readable
Provide management or counsel a one-page chronology, reconciled amounts, open disputes, current work status, deadline sheet, and decision requested. Index the contract, billing submissions, evidence, notices, responses, releases, and receipts. A payment plan also needs review before it carries the account past a preservation date.
Common questions
Does a reminder preserve lien rights?
Not by itself. Lien and bond rights have separate eligibility, notice, service, filing, and enforcement requirements. Maintain an independent reviewed calendar.
Should the full invoice be called undisputed?
Only when that description is accurate. Show approved, disputed, retained, credited, and paid amounts separately without abandoning a legitimate disputed claim.
Can a GC stop immediately when payment is late?
Do not assume so. Verify entitlement, project coverage, notice and cure requirements, and site-protection duties before suspension.