Construction Pay Applications: An Owner's Checklist Before Approving Payment

Before approving a contractor pay application, an owner should confirm that the amount requested matches the signed contract and approved change orders, that claimed progress reflects work actually in place on a verified date, that retainage and stored materials follow the contract, that prior payments are credited, and that the required waivers and approvals are in hand. Signing off on less than that shifts risk to the owner.

A pay application is a monthly claim, not a formality. Each one restates the contract value, the work completed and the money owed. Errors compound: an overbilled line this month becomes the baseline for next month, and a missing waiver becomes harder to collect once the money has moved. The review takes discipline, not heroics.

This checklist is general guidance. Your governing contract, lender requirements and applicable law define what is actually required on your project. Where those differ from anything below, they control. Get legal advice on lien, retainage and prompt-payment questions in your jurisdiction.

Application, certification and payment are three different steps

Owners often treat "approving the pay app" as one event. On many projects it is three.

• The payment application (or payment request) is the contractor's claim. It states what the contractor believes it has earned through the period.
• Certification, where the contract uses it, is a separate review. Under AIA-style agreements the architect reviews the application and certifies an amount, which may be less than the amount requested. Other contracts assign that review to the owner's representative, a construction manager or the owner directly.
• Payment release is the owner's act of paying, often subject to lender approval, retainage terms and receipt of supporting documents.

Knowing which step you are in matters. A certification does not necessarily mean every document the owner needs has been received, and a lender's draw approval may have its own conditions. Each party should sign off on what they actually reviewed.

What the standard forms summarize

Many US projects use AIA G702 (Application and Certificate for Payment) with the G703 continuation sheet. AIA's own instructions describe the G702 as summarizing the original contract sum, net change orders, the current contract sum, work completed and materials stored to date, retainage, previous certificates for payment and the current payment due, with the architect's certification where the contract provides for it. The G703 breaks that total down line by line against the schedule of values.

Read AIA's instructions for G702 and AIA's instructions for G703 for the authoritative description. Projects that use other formats still need the same underlying information.

The owner's pay application checklist

Work through these items every month, in order. Each depends on the one before it.

1. Confirm the contract sum. The original contract sum on the application should match the executed agreement exactly.
2. Reconcile approved changes. Net change orders should equal the sum of fully executed change orders through the period—no more, no less. Compare against your change order log.
3. Keep pending changes out. Proposed, priced or disputed changes do not belong in the current contract sum until they are executed. Track them separately as exposure.
4. Tie the schedule of values to the contract. Line items on the continuation sheet should total the current contract sum and match the approved schedule of values. Watch for lines that were quietly reallocated.
5. Verify percent complete against the field. Compare claimed progress with site observations, inspection records, schedule updates or photos, and record the date it was verified. Front-loaded general conditions and early-phase lines deserve extra attention.
6. Check stored materials. If materials stored on or off site are billed, request the documentation the contract requires—typically invoices, proof of storage and insurance, and sometimes proof of title or bills of sale.
7. Calculate retainage independently. Apply the contract's retainage rate and any reduction terms yourself, and confirm they are consistent with applicable law. Do not simply accept the figure on the form.
8. Credit previous payments. "Previous certificates" or "previous payments" should match what was actually certified and paid, not what was requested.
9. Look for double billing. The same work can appear twice—in a base-contract line and a change order, or in two periods after a schedule of values revision.
10. Collect waivers and releases. Confirm the conditional and unconditional lien waivers the contract requires, from the contractor and, where required, from subcontractors and suppliers. Waiver forms and their effect vary by state.
11. Confirm contract-required compliance documents. Insurance certificates, bond documents or certified payroll apply only where the contract or applicable rules require them. Where they do, check them before release.
12. Record who approved what, and when. Capture each reviewer's sign-off—owner's rep, architect, lender, owner—with the amount they approved and any exceptions noted.

Decision table: what to check, what to request, who resolves it

Who does what

The general contractor prepares the application, supports the claimed progress and collects subcontractor documentation. A good GC submits a pencil draft before the formal application so disagreements surface early.

The architect, under contracts that give it a certification role, reviews progress and certifies an amount. Certification reflects the architect's observations and the contract terms; it is not a guarantee of quality or of every supporting document.

The owner's representative often runs the review day to day: reconciling the schedule of values, checking change orders, walking the site and assembling the package for the owner and lender. If you are evaluating tooling for that role, see how cost management workflows connect budgets, commitments and changes.

The owner approves payment and carries the consequences. That includes the cash-flow decision and, on financed projects, coordinating with the lender's draw schedule.

The lender, on financed projects, may require its own draw package, inspection and title update before funding. Build its requirements into your monthly calendar instead of discovering them after certification.

Red flags worth stopping for

• Percent complete jumps on lines with no visible field activity.
• General conditions or mobilization billed far ahead of schedule progress.
• A revised schedule of values arrives with the application instead of before it.
• Change order totals on the application don't match your log.
• Stored materials billed without documentation, or the same materials billed twice.
• Retainage calculated on a different base than the contract specifies.
• Waivers missing, in the wrong form, or covering the wrong period or amount.
• Previous payments on the application differ from what you actually paid.
• Subcontractor waivers lag several months behind subcontractor billing.

None of these is proof of a problem. Each is a reason to ask a specific question before money moves.

A repeatable monthly routine

1. Before the pencil draft: Update the change order log and confirm which changes are executed.
2. Pencil draft review: Walk the site, compare claimed progress to observations and agree on adjustments with the GC.
3. Formal application: Reconcile the contract sum, schedule of values, retainage and previous payments line by line.
4. Supporting documents: Collect waivers, stored materials evidence and any contract-required compliance documents.
5. Certification and approvals: Route the package to the architect or owner's rep, then to the owner and lender, recording each sign-off.
6. Release and record: Release payment, file the certified application with its backup and update forecasts and draw reporting.

The routine is the control. Doing the same steps in the same order each month is what makes exceptions visible. Our construction project controls checklist covers the broader cost, schedule and reporting disciplines that sit around this process.

Keep pay applications connected to the project record

The hardest part of pay-application review is rarely the arithmetic. It is assembling the evidence: the current budget, executed and pending changes, commitments, prior payments and who approved what. When those live in separate spreadsheets and inboxes, each review starts from scratch.

Jet.Build keeps budgets, commitments, change orders, documents and approvals in one project record, so owners and owner's reps can review a draw against the same information the project team is using. See how financials and reporting support monthly cost review and portfolio visibility. Certification decisions, lien waiver requirements and payment release remain with the people and contracts responsible for them.