The invoicing paperwork subcontractors collect when GCs are slow to pay

It is the third week of the month and the GC's PM has not returned the invoice. The sub's crew got paid on the last draw, the materials were delivered six weeks ago, and the line item on the payment application says 'pending — see email'. There is no email. The sub texts the GC at 7:30 a.m., the GC replies 'we'll get to it Friday,' and Friday becomes the following Friday. By then the sub is funding week two of the next scope out of pocket and the only paperwork that would have moved the money — a keyed invoice, a conditional lien waiver, a payment-application line item ready to drop into the GC's billing packet — was never collected. The slow-pay crisis is not a crisis of cash. It is a crisis of paperwork the sub could have collected in the first week and didn't, because the GC said the verbal ask was fine.

Most invoicing paperwork on a small sub job lives in three places: a spreadsheet on the office laptop, a folder of email PDFs the GC's PM keeps meaning to clean up, and a text thread between the sub's foreman and the GC's super who doesn't process pay apps. The three documents that change the slow-pay dynamic are the ones the sub files in the binder before the draw goes out — not the ones the sub writes six weeks later when the money is already late.

Document 1 — The lien-waiver stack: conditional before the draw, unconditional before the next draw

A lien waiver is the document the sub signs that says 'I have been paid, and I waive my right to place a mechanics lien on this property.' On a small job it is the worst-collected document in the invoicing packet — most subs sign it after they have been paid, sometimes after they have been paid twice, sometimes never. The fix is a two-tier stack that rides with every draw: a conditional waiver that says 'I waive my lien rights if and when this draw clears,' signed concurrent with the draw request, and an unconditional waiver that says 'I have been paid, period,' signed concurrent with the next draw going out the door.

• Conditional waiver (draw request): signed and dated the same day the invoice / pay app goes to the GC — runs in front of the payment, not behind it.
• Unconditional waiver (next draw): signed and dated the day the prior draw actually cleared the sub's bank — closes the prior cycle before the next one opens.
• Sequential by draw number: waiver stack is numbered draw-by-draw, so the GC's PM sees one continuous paper trail from draw 1 to retainage, not five conditional waivers and three unconditional waivers in no order.
• Notarized on final draw: the last unconditional waiver — the one tied to retainage release — is notarized, dated, and filed with the county recorder's office if the contract calls for it. The working sub does not rely on the GC's counsel to remember.

Document 2 — The invoiced change order: keyed by CO number, dated the day the work closed

The second document the sub files in the binder is a change-order invoice — a separate line item, or a separately keyed entry on the service form, that references the CO number instead of riding as 'extra work' at the bottom of the base-contract bill. A CO invoice that calls out CO-001 by number ties the slow-pay dispute to the change-order authorization the GC already signed. It survives a billing audit. It gives the sub a paper trail at lien-waiver time — the conditional waiver covers CO-001 specifically, not a vague 'extra' line that the GC's counsel can contest six weeks later when the payment application is 'pending.'

For a handyman or solo sub working without a GC-supplied change-order log, a dated line item on a service form — scope, parts, labor, CO number, client initial — is enough documentation to collect on scope creep at a small-job scale. The service form is the change-order log: a per-visit page with sequential CO numbers, deposit columns, and client sign-off at the bottom. When the homeowner is six weeks late paying the balance, the sub hands the service-form page back over and points at the signature line. Slow-pay gets resolved at the kitchen table, not in a dispute.

• CO number reference: drops into the GC's billing audit as a line keyed to the original authorization — the GC's PM has to find a way to dispute the specific CO, not the whole pay app.
• Date tied to scope close: the invoice is dated the day the work closed on site, not the day the base-contract bill happened to be assembled — timestamps the authorization, not the billing cycle.
• Scope + parts + labor split: three lines that mirror the change-order authorization the GC signed, so the sub's invoice matches the GC's authorization line by line.
• Conditional waiver keyed to CO: the lien waiver that rides with the CO invoice names the CO number in its scope line — so the waiver covers the specific CO, not the entire pay app.

Document 3 — The payment-application trail: the four lines per draw the GC's PM actually reads

A payment-application packet is what the GC's PM processes every month — schedule of values, current draw amount, prior draw balance, retainage held, conditional waivers from every sub billing on the draw. The sub's invoicing paperwork that wins slow-pay arguments is not the long-form invoice that totals up at the bottom. It is the four lines per draw the GC's PM reads first: contract sum to date, work completed this period, materials stored on site, retainage held. A sub whose pay-app packet carries those four lines clearly is the sub whose 'pending' line item moves to 'paid' by Wednesday.

• Contract sum to date: a running total that matches the schedule of values page 2 of the contract — the GC's PM reads this number against the schedule of values, line by line.
• Work completed this period: a dollar amount that drops in cleanly next to the schedule-of-values line item — not a percentage that has to beconverted.
• Materials stored on site: a one-line itemization (what's on the pad, what it's worth, what the GC is paying for the storage) — the line item the GC's PM specifically asks for in the AIA-style pay app.
• Retainage held: a one-line figure that names the percentage AND the release trigger — the line that closes the slow-pay argument on retainage, because the contractual release date is on the same line.

A sub whose pay-app packet fails has already lost the slow-pay argument before the GC opens the email. The four lines per draw — contract sum to date, work this period, materials stored, retainage held — are the lines the GC's PM reads on a Monday morning with cold coffee. Anything that does not fit those four lines is at the bottom of the inbox when Friday's wire goes out.

— Gridpin founder · 20 years on a clipboard

The kit that holds the invoicing log

CC-01 (Construction Contract) carries the lien-waiver stack as a precondition of every draw — conditional waiver concurrent with the pay-app request, unconditional waiver concurrent with the next draw, notarized waiver on retainage release. HM-05 (Handyman Service Form) carries the per-visit CO log that becomes the invoice line a solo sub hands back at the kitchen table when the balance is late. For a superintendent running multiple subs on a larger project — framing, MEP, finish all billing the same GC at the same time — the Construction Superintendent Bundle carries the twenty-five working-super forms in one kit, including the pay-app four-line block, the CO log, and the per-visit lien-waiver stack a multi-prime super keeps moving across multiple billing cycles.