From Pay App to Follow-Up: A Subcontractor Workflow

A subcontractor project manager checks a payment timeline and job records beside an active construction site
Make payment follow-up part of the job rhythm, not a scramble at month end.

Quick answer

A dependable subcontractor payment workflow starts before billing day. Set up the schedule of values, notice dates, required backup, waiver rules, and retainage terms from the signed contract. Update quantities and changes during the job. Reconcile the pay application before sending it, save proof of delivery, and follow up against the contract’s actual dates.

Why do pay apps turn into a last-minute scramble?

Because billing is often treated as paperwork someone can finish after the field work is done. But the records live in different places. The foreman has quantities. The project manager has change emails. Accounting has invoices and payment history. The subcontract has notice rules and forms. If nobody joins those pieces until billing day, one missing detail can hold up the package.

Here is a workflow that keeps the file moving. Adjust it to the contract and project. The dates in the agreement control.

Step 1: Set up the payment calendar when the subcontract is signed

Read the subcontract and any incorporated documents. Put the payment application cutoff, submission method, required backup, review period, notice requirements, retainage terms, and dispute contact on one calendar. If the prime contract has flow-down language, identify the clauses that apply to your scope.

Build a schedule of values with enough detail to support progress. Each line should map to a measurable item, milestone, or agreed unit. Avoid a single broad line that is hard to substantiate. If the contract requires a specific billing form or portal, save the current version and access instructions in the job folder.

Make a payment tracker before work starts:

FieldRecord
Billing cycleCutoff date, submission deadline, and required channel
BackupQuantities, tickets, photos, payroll or supplier records required by contract
RetainageRate, cap if any, running total, and release condition
WaiverRequired form, through-date, amount, and payment condition
Follow-upReviewer, expected response date, and escalation path in the agreement

Step 2: Record installed work as it happens

Do not wait until the last afternoon of the month to rebuild quantities from memory. Ask the field lead to update completed quantities on a regular cadence. A short weekly review is often enough for a small job. For unit-price work, record the measured unit and location. For milestone work, note what was completed and who accepted it.

Use photos as supporting context, not as a substitute for measurement or an inspection required by the contract. Label them with date, area, drawing reference, and what the image shows. Keep delivery tickets, inspection records, and daily reports with the matching schedule-of-values line.

If stored materials are billable, confirm the contract conditions first. Keep invoices, delivery records, insurance or storage evidence if required, and an inventory that distinguishes site materials from off-site materials. Never assume a material can be billed simply because it has been ordered.

Step 3: Keep changes out of the “we’ll remember later” pile

Open a change log as soon as someone asks for extra, revised, or omitted work. Record who gave the direction, date and time, location, drawing or scope reference, notice sent, cost estimate, schedule impact, and approval status. Link the entry to the email, field directive, photo, and labor or material backup.

Check the contract’s change procedure before starting non-emergency work. It may require written authorization, notice within a set period, or daily records. If safety or property protection requires immediate action, follow the site’s emergency process and document the direction and work promptly. An AI tool can help summarize the file, but it cannot decide whether an instruction changed the contract.

Keep approved, submitted, disputed, and pending amounts separate. When you build the pay application, bill approved changes as the contract allows. Show a pending item transparently and follow the agreement for disputed work. Do not bury an unapproved extra in another line.

Step 4: Reconcile the pay application before it leaves your office

Compare current quantities with the schedule of values and prior applications. Check that the billed-to-date amount does not exceed the line value unless an approved change has updated it. Subtract previous billings, credits, and retainage using the project’s agreed method. Confirm the requested amount matches the attached backup.

Use a second review for arithmetic and completeness. A simple two-person check can catch an accidental duplicate, a stale retainage percentage, or an old change amount. If a required attachment is missing, find it before sending rather than hoping the reviewer will ask.

For covered federal fixed-price construction contracts, FAR 52.232-5 describes progress-payment substantiation that includes itemized amounts tied to contract work and amounts included for subcontractors. FAR 52.232-27 addresses prompt-payment terms and subcontract clauses for covered federal construction contracts. Those clauses are not universal rules for every private project. Confirm they are incorporated and apply to the work you are billing.

Step 5: Match the waiver to the payment status

Waivers deserve their own check. Confirm the correct project, amount, billing period, through-date, and whether the form is conditional or unconditional. Compare its language with the payment expected. Check any exclusions for pending changes or disputed amounts.

Requirements vary by state. California’s Contractors State License Board provides separate conditional and unconditional progress and final forms. Texas has its own statutory forms and conditions. Neither state’s form is a national default. Use the form required for the project’s jurisdiction and get qualified advice if a release is broad or unclear.

Keep the signed waiver with the payment application and the bank record showing when the payment arrived. If your agreement requires releases from lower-tier subcontractors or suppliers, track those separately. A prime’s receipt of your release does not prove every lower-tier account is settled.

Step 6: Save proof, then follow up with a useful question

Save the exact package you submitted and proof of delivery from the required portal or email. Record the date and recipient. If the reviewer identifies a gap, ask which line or requirement needs correction. Send the missing item with a short note that identifies the job, application number, and version. Keep both the original and corrected package.

Set the next follow-up using the agreement’s review and payment dates. If a payment is late or reduced, compare the reason with the contract, notices, and applicable law. Keep the discussion factual. “Can you confirm whether the missing item is the signed inspection report for line 04, and whether the rest of the application is accepted?” will get you further than “Where’s my money?”

A sample month-end sequence

  1. One week before cutoff: Confirm quantities, delivery tickets, inspections, and change status with the field lead.
  2. Three business days before cutoff: Update the schedule of values and calculate prior billings, current work, credits, and retainage.
  3. Two days before cutoff: Collect required backup and review every waiver for amount, period, and payment condition.
  4. One day before cutoff: Have a second person check math, completeness, and contract references.
  5. Submission day: Send through the required channel and save the timestamp, package, and confirmation.
  6. After review: Log questions, corrections, approvals, and payment dates. Update the next cycle’s opening balance.

Use AI for the comparison work, then verify it

AI can help compare a redacted pay application to a schedule of values, list missing attachments, or turn a change log into follow-up questions. Do not upload tax identifiers, bank details, signatures, confidential owner information, or records you are not allowed to share.

“Review these redacted files for this billing cycle: the subcontract requirements, schedule of values, prior application, current quantities, approved change log, and attachment list. Make a table with each billed line, source quantity, prior billed amount, current amount, retainage, and any mismatch or missing support. Quote the source file and page or row. Mark unclear items as questions. Do not interpret legal rights, decide payment entitlement, or invent deadlines.”

Open every cited source yourself. Scans can be misread, formulas can be wrong, and an email marked “looks good” may not be the approval your agreement requires.

Want reusable prompts for your payment file?

The Subcontractor Payment AI Prompt Book is built around getting paid, waivers, retainage, and unpaid change orders. It can help you prepare a clearer application checklist, organize the record behind an extra, and draft a calm follow-up. Use the prompts with your own signed documents, then confirm every amount, term, and date before you send anything. The book helps with drafting and organization. It cannot guarantee payment or replace legal advice.

For the rest of the series, see the guide to building a clearer payment file, payment gaps to catch, questions about retainage and waivers, and reusable pay application templates.

Common questions

How often should I update job quantities?

Choose a cadence that gives your team time to resolve gaps before the billing cutoff. Weekly works for many smaller jobs, while fast-moving or unit-price work may need more frequent records. Follow any contract-specific measurement or inspection process.

What should I do when a pay app is returned?

Save the returned version and ask which specific requirement is missing. Correct only the identified issue, note the revision, and resubmit through the required channel. Keep the new delivery confirmation with the original package.

Should I send a waiver with every payment application?

Follow the signed contract and the applicable jurisdiction’s requirements. Verify the requested form, amount, through-date, and payment condition. Do not assume another project’s waiver form is appropriate.

How can I track retainage without losing it?

Show it as a separate running balance by project and billing period. Record amounts withheld and released, plus the written trigger for release. Reconcile it with each pay application and closeout statement.

Does this workflow apply to federal jobs?

The records workflow can help organize any project, but federal payment clauses apply only when incorporated and applicable. Review the actual contract and agency requirements. The FAR clauses cited here are federal examples.

Can an AI tool calculate what the prime owes?

It can help check arithmetic when you provide accurate records and a clear formula. Verify the calculation yourself and confirm the contract’s payment terms. Do not treat an AI output as a legal determination of what is owed.

Sources and scope

Last reviewed: November 16, 2026. This workflow is general information, not legal or accounting advice. Contract terms and payment, retainage, and waiver rules vary by project and jurisdiction. Get qualified local help if a payment dispute or release may affect your rights.


Leave a Comment

Item added to cart.
0 items - $0.00