Pay Application (AIA G702/G703)

Definition — what it is

A pay application is the formal, periodic document by which a contractor requests payment for work completed and materials stored during a billing period, computed against the agreed schedule of values and certified for accuracy. On most commercial work it takes the form of the AIA G702 summary sheet, sworn and notarized by the contractor, supported by the G703 continuation sheet that carries the line-item detail. A pay application is not an invoice in the accounts-payable sense and it is not self-executing: it is a request that must be reviewed, certified by the architect against observed progress, and approved by the owner before payment is due. It is simultaneously a financial instrument, a legal certification, and, when paired with lien waivers, the mechanism that keeps title to the improvement clear of claims.

Also known as: Application for Payment, Payment Application, AIA G702, Progress Payment Application, Requisition

Why it matters — what it protects

The pay application is how a contractor converts installed work into collectible cash, and its timing dictates project liquidity. Because contracts specify a review-and-payment window measured from submission, a day late in submitting or a rejected application pushes payment out by an entire cycle, which on a large project can mean financing hundreds of thousands of dollars of work out of the contractor's own capital.

It is a sworn legal certification, not a casual bill. The contractor's signature attests that the work billed is actually in place, that prior payments have been applied to labor and material, and increasingly that lien waivers are exchanged. A knowingly inflated application can expose the signer to fraud and false-claims liability, particularly on public work.

It is the pivot point of the payment chain. The prime's application depends on subcontractor billings flowing up, and the owner's payment depends on the architect's certification flowing back; a break anywhere, such as a missing lien waiver or a disputed line, stalls the entire chain and every party downstream of it.

It is the primary evidentiary record of what was paid for what and when. In a payment dispute, a delay claim, or a surety investigation, the sequence of certified applications, the retainage held, and the exchanged lien waivers establish the financial history of the project more authoritatively than any narrative.

Lifecycle — how it moves

1. Cutoff and progress assessment

   At the billing-period cutoff, the team assesses percent-complete per SOV line against installed work. This is the step where accuracy is either disciplined against the field or fabricated to hit a cash target.

2. Subcontractor billing intake

   Subcontractors submit their own applications to the prime, which must be reviewed and rolled up into the prime's application. Late or disputed sub billings are the most common reason a prime application slips.

3. Drafting the G702/G703

   The continuation sheet is updated with work-this-period, stored materials, and retainage; the summary sheet computes total earned, less retainage, less prior payments, equals current amount due.

4. Lien waiver assembly

   Conditional waivers for the current request and unconditional waivers for prior payments are collected from the prime and subs. Missing waivers are a leading cause of a certified application still not being paid.

5. Certification and notarization

   The contractor signs and notarizes the sworn statement. The signature carries legal weight and is the point at which optimism about percent-complete becomes a personal representation.

6. Architect review and certification

   The architect compares the request to observed progress and either certifies the full amount, certifies a reduced amount, or withholds. Reductions here are where disputes begin.

7. Owner review and payment

   The owner, and on financed projects the lender's inspector, review the certified application and release payment within the contractual window, less any withholding. Delays here cascade to every subcontractor.

8. Disbursement and downstream payment

   The prime receives payment and is contractually and often statutorily obligated to pay subcontractors within a defined period. Failure triggers prompt-payment penalties and preliminary notices.

Anatomy — the data it carries

Application number and period

Sequential number and the from-to dates it covers. Gaps or overlaps in periods are an immediate red flag for reviewers.

Original contract sum

The base contract amount before any changes, the anchor the whole calculation builds from.

Net change by change orders

Cumulative approved additions and deductions. Must reconcile to the executed change orders and to the SOV total.

Contract sum to date

Original sum plus net changes, the current adjusted contract value the SOV must equal.

Total completed and stored to date

Cumulative earned value from the G703, the figure certification is built on and the one the architect verifies against the field.

Retainage

Amount withheld this period and cumulatively, computed per the contract rate and any variable or early-release provisions.

Total earned less retainage

Certified earned value net of retainage, the ceiling on what can be paid to date.

Less previous certificates for payment

Cumulative amount already paid, subtracted to isolate what is owed for this period alone.

Current payment due

The bottom-line amount requested this period. Every other figure exists to derive and defend this number.

Balance to finish including retainage

What remains payable on the contract, a quick check on whether billing is tracking or running ahead of the work.

Contractor certification and notarization

The sworn statement that the work is in place and prior funds properly applied. Carries fraud exposure if false.

Architect's certificate for payment

The design professional's certification of the amount, which may differ from the amount requested and is the trigger for owner payment.

Attached lien waivers

Conditional current-period and unconditional prior-period waivers from the prime and subs. Absence commonly holds payment even after certification.

Stored-materials documentation

Invoices, delivery proof, and off-site storage and insurance evidence supporting any stored-materials line.

Failure modes — how it breaks

Submitted after the cutoff and missing a whole cycle

The application misses the owner's submission deadline by a day and, because review-and-payment windows run in monthly cycles, payment slips a full period. The contractor finances another month of work it has already performed.

Percent-complete not supported by the field

Lines are billed ahead of installed work to improve cash. The architect's site visit contradicts the request, the application is certified down, and the resulting correction shows a line going backward next period, which erodes credibility.

Missing or defective lien waivers

The application is certified but a required subcontractor waiver is missing, the wrong statutory form is used, or the waiver amount does not match the payment. The owner withholds payment on an otherwise valid application.

Reconciliation failure with change orders

The contract-sum-to-date on the application does not match the executed change orders and the SOV total, usually because a change order was billed before it was formally executed. The arithmetic fails and the whole application is rejected.

Stored materials billed without security

Materials stored off-site are billed without proof of delivery, a bailment agreement, or insurance naming the owner. The owner pays for goods it has no protected interest in and refuses similar requests thereafter.

Prime paid but subs paid late

The prime collects the certified payment but does not pass funds to subcontractors within the contractual or statutory window. Preliminary notices, prompt-payment penalties, and eroded trust follow, and future waivers become harder to collect.

Retainage miscalculated or misreleased

Retainage is computed at the wrong rate, released early without authorization, or not reduced when the contract provided for stepped release. The error compounds across every subsequent application until it is caught.

Metrics — how it is measured

Days sales outstanding on applications

Average days from application submission to cash receipt. The core liquidity metric and the clearest measure of payment-chain health.

First-pass certification rate

Share of applications certified at the full requested amount without reduction. Low rates indicate billing that runs ahead of the field or recurring documentation gaps.

Application rejection and rework rate

Frequency of applications returned for arithmetic, reconciliation, or waiver defects. Measures billing-process discipline directly.

Lien waiver completeness

Percentage of applications submitted with all required current and prior waivers attached. A leading indicator of payment delays.

Retainage held versus contract

Cumulative retainage against the contract's schedule, checked for correct rate and timely stepped release.

Subcontractor payment cycle time

Days from prime receipt to subcontractor disbursement, measured against prompt-payment obligations. Protects the downstream chain.

The AI shift — what actually changes

Conversational

The application stops being a sheet you scan for errors. You ask whether every line's percent-complete is supported by the latest field progress, whether the contract-sum-to-date reconciles to executed change orders, which required lien waivers are still missing, and whether the retainage math matches the contract, each answered against the underlying records.

Generative

The draft application is assembled rather than typed. Given the locked SOV, the current field progress, executed change orders, and the retainage terms, a model produces the G703 with work-this-period populated and the G702 computed, plus a checklist of the exact waivers and stored-materials documents required for the request to be paid, leaving the person to verify and certify.

Orchestrated

The application is coordinated across the chain. Subcontractor billings are matched to their SOV lines and rolled up, the request is validated against the schedule so nothing is billed ahead of progress, change orders are reconciled to the total, and required lien waivers are tracked to each payment so certification and disbursement do not stall on a missing form.

Autonomous

Routine application preparation runs continuously inside guardrails: rolling up sub billings, reconciling to change orders, checking percentages against field progress, computing retainage, and assembling the waiver and stored-materials package for review before the cutoff. The sworn certification, any line that runs ahead of the field, and every disbursement decision stay with a person.

Prompts — put it to work

Tool-agnostic and copy-ready. Adapt the specifics — thresholds, contract windows, cost codes — to your own project before you run them.

Conversational — Sanity-checking a draft pay application before you sign and notarize it.

Review this draft pay application before I certify it. Confirm the contract-sum-to-date equals the original contract sum plus the net of all executed change orders, and flag any change order billed here that is not yet formally executed. For each SOV line billed this period, tell me whether the percent-complete is consistent with the latest field progress reports and photos, and flag any line billed ahead of installed work. Verify the retainage is calculated at the contract rate, list every lien waiver required for this request that is missing, and confirm any stored-materials line has delivery proof and insurance naming the owner. Give me a short go/no-go with the specific issues to fix.

What good output looks like: A concrete go/no-go list naming specific lines, missing waivers, and reconciliation gaps, not a generic checklist of what a pay application contains.

Follow-ups:

• Which issues will hold payment versus which will hold certification?
• Recompute the current payment due if we back out the two unsupported lines.
• Draft the note to the architect explaining the stored-materials request.

Generative — Building this period's application from the SOV and field progress.

Prepare a draft G702/G703 pay application for this billing period. Start from the locked schedule of values, populate work-completed-this-period per line from the current field progress assessment, and do not bill any line beyond its supported installed percentage. Include stored materials only for lines with delivery documentation, apply retainage at the contract rate, reconcile the contract-sum-to-date to the executed change orders, and compute total earned less retainage, less previous certificates, equals current payment due. Then produce the exact list of lien waivers, conditional and unconditional, from the prime and subs required for this request to be paid, and flag any documentation gap that would cause a reduction or hold.

What good output looks like: A populated continuation sheet and summary with correct arithmetic, retainage, and reconciliation, plus a specific waiver-and-documentation checklist and any flagged gaps.

Follow-ups:

• Regenerate assuming change order 7 executes before the cutoff.
• Produce the summary G702 figures as a clean one-page summary.
• List which subcontractor billings still need to arrive to complete the roll-up.

Orchestrated — Coordinating subcontractor billings and waivers into the prime application on a tight cutoff.

The pay-application cutoff is in three days. Roll up all subcontractor billings received into our prime application by matching each to its SOV line, and identify which subs have not yet submitted so I can chase them. For every prior payment, confirm we hold an unconditional lien waiver from the paying party, and for this period confirm each sub has provided a conditional waiver matching its billed amount. Validate that nothing is billed ahead of the schedule progress for its line, reconcile the total to executed change orders, and produce a single readiness summary listing exactly what is missing and who owns each gap. Flag anything you are unsure about rather than assuming it is fine.

What good output looks like: A readiness summary with each missing billing and waiver named and assigned to an owner, plus a reconciliation check and progress validation across the rolled-up application.

Follow-ups:

• Draft the chase notes to the three subs with outstanding billings and waivers.
• Which gaps will stop certification versus stop payment?
• Show the current payment due with and without the missing sub billings.

Autonomous — Standing policy for how pay-application preparation should run every cycle.

Run our pay-application preparation each cycle under these rules. Ahead of every cutoff, roll up received subcontractor billings against their SOV lines, reconcile the contract-sum-to-date to executed change orders, compute retainage at the contract rate, and assemble the required conditional and unconditional lien waivers and stored-materials documentation. Compare each line's billed percent-complete to the latest field progress and hold, without billing, any line that runs ahead of installed work, escalating it to me with the discrepancy. Prepare the draft application and readiness summary for my review. Never certify or notarize the application, never bill a change order that is not formally executed, never bill stored materials without delivery proof and owner-named insurance, and never release retainage. Route every ahead-of-field line and every missing waiver to me with your reasoning.

What good output looks like: A ready-to-review draft each cycle, a short exception queue of ahead-of-field lines and documentation gaps, and a hard boundary that certification, notarization, and retainage release always require a person.

Follow-ups:

• Show me this cycle's draft plus everything you held and escalated.
• Which subs have repeatedly submitted late or with defective waivers?

Get the full Construction AI Prompt Catalog — every prompt in the library in one document.

Maturity — locate yourself honestly

0. Level 0 — Manual and last-minute

   The application is rebuilt by hand each period, sub billings are chased at the deadline, and waivers and stored-materials proof are collected reactively, so slipped cutoffs and rejections are routine.

1. Level 1 — Templated and reconciled

   A standard G702/G703 is used, arithmetic and retainage are correct, and the total reconciles to change orders. Percent-complete is still office-estimated and waivers are tracked on a side list.

2. Level 2 — Linked to SOV, schedule, and subs

   Applications draw from the locked SOV, validate against schedule progress, roll up matched subcontractor billings, and tie required lien waivers to each payment so gaps surface before submission.

3. Level 3 — Assisted preparation and review

   Drafts are generated from progress and change orders, ahead-of-field lines and reconciliation gaps are flagged automatically, and the waiver-and-documentation package is assembled for human review.

4. Level 4 — Operated

   Roll-up, reconciliation, retainage, progress checks, and documentation assembly run unattended inside guardrails, while people own certification, notarization, ahead-of-field decisions, and every retainage release.

Common questions

How is a pay application different from an invoice?

An invoice is a demand for payment of a fixed amount for goods or services, typically due on its own terms once received. A pay application is a certified request for periodic payment against a schedule of values that must be reviewed and certified by the architect and approved by the owner before payment is due. The G702 is also a sworn legal statement, which an ordinary invoice is not.

Why is a pay application notarized?

The G702 includes a sworn certification that the work billed is actually in place and that prior payments were properly applied to labor and materials. Notarization formalizes that oath, and it matters because a knowingly false certification can create fraud exposure, especially on public projects governed by false-claims statutes. The signature turns an estimate of progress into a personal representation.

Why does a certified application sometimes still not get paid?

Certification by the architect establishes the amount earned, but payment can still be withheld for reasons outside that certification, most commonly a missing or defective lien waiver, an unresolved backcharge, disputed stored materials, or a lender-inspector hold on a financed project. Contractors who track waivers and documentation as rigorously as they track percent-complete get paid faster.

How does retainage interact with the pay application?

Retainage is a percentage, commonly 5 to 10 percent, withheld from each certified amount and accumulated until the contract allows its release, which protects the owner against incomplete or defective work. The application shows retainage withheld this period and cumulatively, and errors in the rate or in stepped or early release compound across every subsequent application until corrected.