Monthly pay applications, drafted and checked before the GC sees them.

Each month your PM marks percent complete against the schedule of values, someone adds stored materials and executed change orders, and billing builds the pay app the GC wants: an AIA G702 and G703, the subcontractor versions G702S and G703S, or the GC's own format. It often goes back and forth as a pencil draft until the GC agrees the numbers.

In the proof of concept, AI takes the inputs your team had for past pay apps and drafts each pay app, every line's math checked. Nothing is submitted. Your reviewer compares the drafts with what your team sent and what the GC approved.

The continuation sheet carries the math. On the G703, column C is each line's scheduled value, D is work completed on earlier applications, E is work completed this period and F is materials presently stored. G is D plus E plus F, G divided by C is percent complete, and H is the balance to finish. AIA's instructions reserve column I for retainage where the contract allows a different rate line by line. When stored material is installed, its value moves from F into E; a draft that leaves it in both bills it twice.

The summary sheet has to tie out. The G702 runs from the original contract sum and net change by change orders to the contract sum to date, then total completed and stored to date, retainage on completed work and on stored material, total earned less retainage, less previous certificates for payment, current payment due and balance to finish including retainage. The previous-certificates line must agree with what was certified on earlier applications, which is not always what was billed. Executed change orders are usually listed separately, on their own sheet or at the end of the schedule, not folded into the original lines.

The subcontractor version changes the paperwork. On AIA's G702S, the contractor and subcontractor version, the sub signs, has it notarized and sends it with the G703S; AIA publishes no standard schedule of values for it. Many GCs skip AIA forms and have subs bill in a portal such as Oracle Textura, GCPay or Procore; in Procore, the GC invites you to bill against your schedule of values each billing period. A line billed past its scheduled value is the kind of thing that sends a pay app back.

Stored materials and closeout bring their own documents. Billing stored material usually needs the supplier invoices and delivery records behind it, and some contracts want insurance or a bill of sale for material stored off site. The final pay app pulls in closeout papers: on AIA-based contracts, often the G706 affidavit of payment of debts and claims, the G706A affidavit of release of liens and, when you are bonded, the G707 consent of surety to final payment, plus final waivers.

Where your reviewer will look first: column math that ties to the summary, previous certificates that match what the GC certified, retainage at the contract's rate, stored materials moved into work completed once installed, and change orders billed only once executed.

If your reviewer says yes, the job runs live for about 30 days, roughly one billing cycle on each open job.

Each drafted pay app waits for a person to approve it before it goes to a GC or a portal. Percent complete still comes from your PM; the draft never estimates progress.

It gets a fixed price before you sign. What follows is priced on its own, with monthly support once it runs.