The construction pay application: how it works and what goes in it

By Adam Chandler, founder of Pangea · August 28, 2026

A pay application — a "pay app" — is the formal, documented request a contractor submits to be paid for a billing period, almost always a month. It is not an invoice. It is a package built on the contract's schedule of values that states the percent complete for every line item, adds approved change orders and materials stored, subtracts retainage and everything already paid, and arrives with backup such as lien waivers and certified payroll. On most US commercial projects it takes the form of AIA documents G702 and G703, and the architect certifies it before the owner pays.

An invoice asserts an amount. A pay application proves one, against a document everybody agreed to before the job started. Which is also why pay apps get rejected for reasons that have nothing to do with whether the work got built.

What is a pay application in construction?

It is a periodic progress billing tied to a contract. The contract sum is broken into a schedule of values — a line-by-line allocation of the total price across the parts of the work — and each month you report how far along each of those lines is. The dollars follow from the percentages.

Everyone in the chain submits one. The general contractor bills the owner; subcontractors bill the general contractor on a cutoff a week or two earlier so their numbers can be rolled up. The logic is identical at every tier: last month's cumulative number, plus this month's progress, minus retainage, minus what has already been paid.

There is no such thing as a standalone pay app. If you overstated a line at 60 percent in June, July's application inherits the problem, and so does the argument you eventually have about it.

How is a pay application different from an invoice?

Both ask for money. Almost nothing else is the same.

How do the AIA G702 and G703 forms work?

G702, "Application and Certificate for Payment," is the one-page summary. G703 is the continuation sheet behind it. The contractor applies on the G702; the architect certifies on the same sheet, which is why one document carries both words in its title.

The G702 carries the running arithmetic of the contract: original contract sum, net change by change orders, contract sum to date, total completed and stored to date, retainage, total earned less retainage, less previous certificates for payment, and the current payment due. It is signed by the contractor, frequently notarized, then certified by the architect for the amount they determine is actually due.

The G703 is where the argument actually happens: one row per schedule of values line item, with columns for scheduled value, work completed in previous periods, work completed this period, materials presently stored, total completed and stored, percent complete, and balance to finish. Those column totals feed the G702. If the two do not tie, the package comes back.

You do not have to use AIA forms — plenty of owners and agencies have their own — but the columns are close to universal because the underlying logic is. AIA describes the G702/G703 pair as the standard for monthly payment releases under its A101 owner-contractor agreement.

What goes in a pay application package?

The forms are the cover sheet. The package is what makes it payable. A typical monthly submission includes:

• The signed G702 (or the owner's equivalent), notarized if the contract requires it.
• The G703 continuation sheet, with every SOV line item updated and the totals tying to the G702.
• Lien waivers: a conditional waiver from the applicant for this period's amount, unconditional waivers covering the prior period once it has cleared, and lower-tier waivers from subcontractors and suppliers. Missing lower-tier waivers are the most common flaw in an otherwise clean package.
• Change order documentation — executed change orders for anything billed as extra work, and the reference for anything authorized by directive but not yet converted.
• Stored materials backup: supplier invoices, delivery tickets, photographs, proof of insurance, and written owner approval if the material sits off site.
• Certified payroll on prevailing-wage and public work, for the periods covered.
• Progress documentation — photos, updated schedule, daily reports — where the contract requires it or a percent complete is going to be questioned.

One note on billing extra work: AIA A201-2017 section 9.3.1.1 allows an application to include payment for changes authorized by a construction change directive or an interim determination of the architect, even where those have not yet been folded into an executed change order — so directive work does not have to be financed by the contractor while the paperwork catches up. That only helps if the directive itself is documented.

How does the pay application process work, month to month?

The cycle is more or less the same everywhere, and it is longer than people expect the first time they run it.

1. Establish the schedule of values. Under A201-2017 section 9.2 the SOV is prepared in the form and with the substantiating data the architect requires, and unless objected to, it becomes the basis for reviewing every subsequent application. Get this right once and you save yourself twelve arguments.
2. Subs bill up. Subcontractor cutoffs land a week or two earlier so their numbers can be verified and rolled into the GC's SOV lines.
3. Walk the work and set percentages. Somebody has to decide whether the masonry line is at 40 percent or 55. On many projects this is settled with the owner's rep or architect at a pencil-copy review before anything is formally submitted.
4. Submit the application. Section 9.3.1 requires the itemized application at least ten days before the date established for the progress payment, supported by the data substantiating the right to payment — requisitions, releases and waivers of lien from subcontractors and suppliers — and reflecting retainage where the contract provides for it.
5. The architect certifies. Section 9.4.1 gives them seven days after receipt to certify the full amount, certify a smaller amount and explain the difference in writing, or withhold certification entirely with the reason stated.
6. The owner pays. Section 9.6.1 says the owner pays "in the manner and within the time provided in the Contract Documents" — the payment window is a contract term, not an AIA default, so know yours by number.
7. Money flows down. Section 9.6.2 requires the contractor to pay each subcontractor no later than seven days after receiving payment from the owner, reflecting the percentages actually retained.

The practical implication: a pay app that gets kicked back is not delayed by the days it takes to fix. It is delayed by a full billing cycle, because the correction usually lands after the certification window has closed and the next cutoff is a month out.

How is retainage handled?

Retainage is the percentage of each payment the owner holds back as security that the work gets finished and corrected. It shows on the G702 as a deduction from total completed and stored, often split into two lines — retainage on completed work and on stored materials — because contracts do not always treat those the same way. The percentage comes from your contract; public work in many states is capped by statute, and many contracts reduce retainage at substantial completion.

Three things cause most disputes: applying it to stored materials when the contract excludes them, failing to reduce it at the agreed milestone, and a GC withholding a higher percentage from subcontractors than the owner withholds from them.

Why do pay applications get rejected?

Rarely because the work was not done. Almost always because the package cannot be certified as submitted: arithmetic that does not tie, a missing or wrong-form lien waiver, billing that runs ahead of what a site walk supports, extra work performed on a verbal "go ahead" with no executed change order to bill against, retainage on the wrong base, stored materials with no backup, or missing certified payroll.

Every one of those is preventable at the desk. Run this before the package leaves your office — it is deliberately boring, and that is the point.

• Application number follows the last one in sequence, and the period dates match the contract's cycle.
• Every G703 line matches the accepted SOV — no lines added, renamed, or re-valued without an approved change.
• Previous-period columns equal last month's certified amounts, not last month's requested amounts.
• G703 column totals tie to every corresponding G702 line.
• Every change order billed is executed, with directive work identified as such.
• Percent complete for each line was walked or verified, not extrapolated from the schedule.
• Retainage matches the contract percentage, applies to the correct base, and reflects any agreed reduction.
• The waiver package is complete: conditional at this period's exact amount, unconditional for the prior period, lower-tier waivers on the correct state form.
• Signatures and notarization are complete, and it goes out by the contractual deadline to the named recipients.

The billing is arithmetic. The backup is memory.

The hard part of a pay application is not the form. It is reconstructing what was agreed. Was the added storm structure a change order or was it absorbed? Did the owner's rep approve off-site storage for the switchgear, and when? Did the architect agree in the OAC meeting that the curtain wall line could be billed at 45 percent? Those decisions get made in meetings and then have to be produced, a month later, by whoever is assembling the package — often not the person who was in the room.

The cost of that gap is well documented. FMI and PlanGrid's Construction Disconnected study put the cost of bad data and poor communication in US construction at roughly $177 billion a year in labor, with the average person spending about five and a half hours a week just looking for project information. A rejected pay app is that statistic with a due date attached.

Pangea is an AI notetaker built for project-based firms rather than for meetings in the abstract. It records the conversation — including in-person ones, with a phone on the table and no bot joining anything — writes minutes in your firm's format, and files every meeting, decision, and document to the correct project automatically. When billing week arrives and someone asks what the owner actually approved on the switchgear, you ask the project instead of the person, and get an answer with its source cited. It will not fill out your G703. It makes sure the commitments behind the numbers are still retrievable when the architect asks you to justify one.

It is worth a look if your monthly billing currently depends on somebody's recollection. There is a 14-day free trial with no credit card, and it is aimed at the coordinator role — the person expected to keep the minutes, the logs, and the PM software all telling the same story.

This article explains common practice and standard-form contract provisions. It is not legal advice — your contract and your state's statutes control.