Start with the G703 lines — then prove the G702 roll-up
An incoming G702 application for payment is not ready for signature just because the cover sheet looks complete. The real audit starts on the G703 continuation sheet, where each schedule-of-values line shows the work completed this period, work completed to date, stored materials, retainage, and balance remaining. The GC needs to know that those rows describe the approved scope before the totals can be trusted.
Compare the submitted line number, description, and scheduled value against the current approved SOV. Then recalculate the row logic: previous completed work plus current work plus eligible stored materials should not exceed the line value, and the line balance should move in the right direction. Approved change orders should be visible as approved scope changes, not used as a quiet explanation for a mismatch.
Once the rows are clean, roll the G703 totals into the G702. The current-period amount, completed-to-date amount, retainage, prior payments, and current payment due should reconcile to the cent. A one-line discrepancy can hold the entire draw because the owner, lender, or architect is reviewing the G702 as the GC's certification of the package behind it.
Before the GC signs, confirm the packet answers each of these questions:
- Does every G703 line match the approved SOV number, name, and scheduled value?
- Do current-period, prior-period, stored-material, and balance columns make sense within each line?
- Do approved change orders appear in the scope and totals being billed?
- Do G703 totals reconcile to every corresponding G702 total to the cent?
- Does the requested payment agree with the prior payment history and retainage held?
Verify the billing window against the contract calendar
A correct dollar amount in the wrong period is still a bad application. Read the period-of-work dates on the G702 and supporting schedules, then compare them with the contract calendar, the GC's billing cutoff, and the owner or lender draw date. Those dates define whether the work belongs in the current funding request or the next one.
The audit should also compare the application's submission date with the cutoff. A subcontractor may have performed the work before month-end but submitted after the GC's cutoff, while another line may be dated inside the period but not supported by a progress report until the next cycle. Make the timing visible rather than silently moving lines between applications.
Work backward from the funding event. If the lender draw occurs on the tenth, the GC may need the signed application several business days earlier for review, waiver collection, and owner certification. A repeatable calendar lets the admin reviewer flag a late packet before the GC signs a document that will miss the draw.
1. Period of work
Confirm the dates match the contract billing cycle and the progress evidence.
2. GC cutoff
Check when the complete packet had to reach the GC for the current draw.
3. Review window
Leave time for corrections, waivers, payroll backup, and owner questions.
4. Draw date
Confirm the signed G702 can reach the owner or lender before funding.
Pair lien waivers with payment status
The waiver attached to an incoming application is part of the audit, not a box to check after the math. A conditional waiver commonly accompanies the current draw, while an unconditional waiver usually confirms that an earlier draw has actually been paid. The submitted form, stated payment period, amount, and payment evidence all need to tell the same story.
Review the payment register, ACH confirmation, joint-check record, or other approved evidence that the contract team uses to mark a draw paid. A signed unconditional waiver is not a substitute for checking the payment status. If the money has not cleared, hold the unconditional form and request the correct conditional form for the current application, subject to the contract and applicable requirements.
Conditional waiver
Match it to the current payment request and stated period. It should become effective only under the condition described on the form, commonly receipt of the related funds.
Unconditional waiver
Match it only to the earlier payment the records show has cleared. If payment is still pending, the waiver should not be treated as an unconditional release.
Conditional final waiver
Use the form required for the final request while the final funds are still in flight. Confirm closeout documents and the contract's final-waiver process before sending the signature packet.
Unconditional final waiver
Release only after the payment record supports it. Keep the final payment status, waiver date, and closeout log together so the GC has an auditable trail.
Use certified payroll as a second record
On projects with prevailing-wage or certified-payroll requirements, the payroll package gives the GC a second record of labor behind the application. It can help surface a wrong period, a classification mismatch, omitted fringe amounts, or a labor line that moved faster than the reported workforce.
The cross-check is not a demand that every payroll total equal a G703 line. Payroll records may cover several SOV lines, and a pay application may include materials, equipment, or stored items. Instead, compare the dates, labor-heavy scopes, classifications, hours, rates, fringe amounts, and approved change-order work. Note what is explainable and escalate what is not before certification.
- Period: payroll weeks overlap the period of work shown on the application.
- Scope: labor-heavy G703 lines and approved changes have a reasonable workforce record behind them.
- Classification: reported classifications, rates, hours, and fringe amounts are complete for the project requirements.
Recalculate retainage from the contract
Retainage is where a clean-looking pay application can quietly become expensive. Start with the governing contract language, approved change orders, and any written release or reduction. The rate, eligible base, milestone, and treatment of stored materials may differ by project, so the audit should never rely on a remembered default.
Recalculate current-period retainage and retainage held to date using the same basis the contract defines. Then compare the result with the G703 rows and the G702 summary. Approved retainage releases belong in the review trail, as do credits, change-order values, and any line that is excluded from the retainage base.
Eligible current-period value
× contract rateCurrent retainage
G703 line totalRetainage to date
G702 summaryLess approved releases
Remaining holdbackThe exact basis comes from the project documents. The reviewer's job is to make the basis visible and make the G703, G702, payment history, and remaining contract balance agree.
Give the GC a clean packet before signature
A strong admin-support review is a repeatable pre-signature workflow, not a second signature. The GC remains responsible for certifying the work and signing the G702; admin support makes the evidence easier to inspect by assembling the source documents, running the checks in the same order each cycle, and separating resolved items from exceptions that need the GC's decision.
Each cycle starts with the approved SOV, prior application, current G702/G703, contract calendar, waiver package, payroll support where required, payment history, and approved change-order log. The reviewer then records the checks, highlights any unresolved amount or date, and returns a signature packet that can be followed by the owner, lender, architect, or internal project team.
Source packet assembled
SOV + prior app + current appNumbers reconciled
G703 → G702 → payment historyDocuments paired
Waiver + payroll + backupExceptions listed
Owner decision before signatureGC signature packet
Ready for certificationJohnston Admin Management Services runs this kind of construction administration at $45/hour, billed to the exact minute through Clockify. The scope can be a single incoming application or a recurring monthly review, with the review trail and open questions visible before the GC signs. Send the contract, SOV, or current packet through the services page to start the conversation.
Frequently asked questions.
What should a GC audit first on an incoming G702 application?
Start with the G703 continuation sheet and the approved schedule of values. Confirm that each line uses the approved description and number, that current-period work plus prior work and stored materials does not exceed the line value, and that the G703 totals roll up to the corresponding G702 totals to the cent. Review approved change orders separately so an honest scope change is not mistaken for a math error.
How should the billing period dates be checked?
Compare the pay application period of work with the contract calendar, the GC billing cutoff, and the owner or lender draw date. The application should identify work performed in the correct period and arrive before the cutoff that controls the current draw. If the dates do not agree, hold the packet for clarification instead of signing a period that belongs in a different cycle.
Which lien waiver should accompany a current G702 application?
A conditional waiver generally pairs with the current payment request because it becomes effective when the stated funds are received. An unconditional waiver should correspond only to money that has actually cleared, commonly the prior draw, and the payment register or bank confirmation should support that status. The contract and applicable state requirements control the exact form, so the GC should never treat a signed waiver alone as proof that payment cleared.
Why should certified payroll be cross-checked against a pay application?
For projects with prevailing-wage or other certified-payroll requirements, payroll reports provide a second record of who worked, when they worked, and which classifications and fringe amounts were reported. Compare those periods and totals with labor-heavy G703 lines, approved change orders, and the payroll certification package. A mismatch should be documented and resolved before the application is certified, not buried in the next cycle.
How does a GC verify retainage rate and retainage-to-date math?
Read the subcontract, prime contract, change orders, and any approved retainage-release language first; do not assume a universal rate or milestone. Recalculate current retainage from the contract-defined eligible base, compare it with retainage held to date, subtract only approved releases, and confirm that the G703 and G702 use the same basis. The remaining contract balance should also reconcile after retainage and payments are applied.
What does admin support review before the GC signs?
Admin support can assemble the approved SOV and prior application, recalculate the line-item roll-up, verify dates and cutoff, pair the conditional or unconditional waiver with payment status, cross-check certified payroll, recalculate retainage, and list unresolved exceptions in a short review note. The GC still owns the certification and signature, but receives a packet where the math, dates, and supporting documents have already been checked in a repeatable order.
The pre-signature version.
- Tie every G703 line to the approved schedule of values before looking at the final G702 total.
- Check the period of work, contract calendar, GC cutoff, and lender draw date as one timeline.
- Pair conditional and unconditional lien waivers with the actual payment status, not the requested amount.
- Use certified payroll as a second record for labor-heavy work, classifications, periods, and fringe amounts.
- Recalculate contract-specific retainage for the current period and to date, including approved releases.
- Give the GC an exception list and a clean signature packet only after the review is complete.