Newsroom
ArchitectGeneral contractorSupplier
ArchitectGeneral contractorSupplier

BIM Engine for

  • Architect
  • General contractor
  • Supplier

Company

  • Media kit
  • Contact

Legal

  • Privacy
  • Terms
  • Security

Socials

Ask about BIM Engine:

Cause of extinction: legacy SaaS
Still saving v_final_FINAL(2) when the asteroid hit
Emailed the spec as a PDF. Nobody opened it for 66m years
← Newsroom

Reading a G702 and G703 the way an architect reads one

The AIA pay application is two pages that decide whether a contractor gets paid this month. Here is what each line does, and the three places a certifying architect actually looks.

Product
BIM Engine Team·July 8, 2026·4 min read

Two documents, one certification

AIA G702, the Application and Certificate for Payment, is the summary page. G703, the Continuation Sheet, is the line-by-line detail behind it. A contractor submits both, an architect certifies the pair, and the owner pays against the certificate.

That certification is a professional act, signed under an architect's license, stating that the work has progressed to the point indicated and that the quality conforms to the contract documents. It carries real exposure, which is why the review is slower than contractors expect and faster than it should be.

What the continuation sheet holds

G703 lists the schedule of values: every line item in the contract, each with a dollar value, and the sum of those values equals the contract sum. The columns then track that line across time.

Each row carries the scheduled value, the work completed in previous applications, the work completed in this period, the value of materials stored on site but not yet installed, the total completed and stored to date, that total as a percentage of the scheduled value, the balance remaining, and the retainage held.

The stored-materials column is where disagreements live. A contractor who has taken delivery of switchgear worth a quarter of the electrical scope wants to bill for it, and the owner reasonably wants proof the material exists, is insured, is stored properly, and cannot be moved to another job. Contracts handle this with bills of sale, insurance certificates, and site inspection, and the requirement is usually in the general conditions rather than in anything printed on the form.

What the summary page computes

G702 runs a short chain of arithmetic that anyone can check with a calculator and few owners ever do.

It starts from the original contract sum, adds the net change from executed change orders to reach the contract sum to date, and pulls the total completed and stored figure up from the continuation sheet. Retainage comes off that figure to give total earned less retainage. Subtract everything certified in previous applications and the remainder is the payment due this period.

The final line is the balance to finish, including retainage, and it is the line an owner's representative should read first, because it answers how much money is left against how much work is left.

1M10M100M1B10B$1 million$10 million$100 million$1 billion$10 billion
The chain from contract sum to payment due, one application at a timeBIM Engine

The three places an architect looks

Percentage complete against observed work comes first. A reviewer walks the site with the continuation sheet, and any line claiming 80 percent where the observed condition reads closer to half becomes a conversation before it becomes a certificate.

Front-loading comes second, and it is the oldest game on the form. A contractor assigns generous values to early line items such as mobilization, submittals and site preparation, and thin values to the finishes and closeout work at the end. Cash arrives early, and by the time the job is 90 percent complete the contractor has drawn 97 percent of the money, so the remaining work is being performed at a loss with no financial reason to finish it. A reviewer catches this at the schedule of values approval, before the first application, or does not catch it at all.

Stored materials come third, for the reasons above.

Where the process breaks down

The form itself works. What fails is the workflow wrapped around it, which in most offices runs like this. The contractor prepares the application in accounting software that exports a PDF. The architect receives that PDF by email, marks it up, and returns comments as a separate PDF. The contractor revises and resubmits. The owner's representative receives the certified copy, keys the numbers into a separate system for the lender's draw package, and the lender's inspector visits the site and produces a fourth document with its own percentages.

The same numbers are now typed four times by four organizations, and each transcription is an opportunity for a discrepancy that surfaces two months later during a draw reconciliation. No one in that chain is careless; the chain itself manufactures the errors.

The fix is unglamorous: one record for the schedule of values that all four parties read, where the contractor's claimed percentage, the architect's certified percentage, and the lender inspector's observed percentage sit on the same row as three separate fields rather than in three separate documents. Disagreement then becomes visible on the line where it happens, instead of arriving as a summary variance no one can trace.

Why this matters more than it looks

A pay application is the only regular moment when the architect, the contractor, the owner, and the lender all evaluate the same question at the same time. Getting a shared answer out of it costs a few days of clerical work per month per project, which across a portfolio is a full-time job that produces no building.

Reducing that cost does not require anyone to change how they read a G702. It requires the numbers to stop being retyped.