G703 Continuation Sheet Template: Every Column Explained
The G703-style continuation sheet is where pay applications are won or lost. It breaks your contract into line items and tracks, period by period, what's been billed, what's stored, and what remains. GC reviewers check it line by line — and one bad cell rejects the whole package.
Skip the spreadsheet — build a live continuation sheet
PayAppFlow computes Columns D, G, %, and H automatically and carries previous applications forward each period. Free to start.
Open the Free Pay App BuilderColumns A through H
| Column | Name | How it's computed |
|---|---|---|
| A | Item number | Your numbering — keep it stable across periods |
| B | Description of work | Matches your schedule of values |
| C | Scheduled value | From the SOV; total must equal contract sum to date |
| D | Work completed — previous applications | Sum of all prior periods for that line |
| E | Work completed — this period | What you're billing now |
| F | Materials presently stored | Delivered but not installed; not in D or E |
| G | Total completed & stored | D + E + F |
| % | Percent complete | G ÷ C |
| H | Balance to finish | C − G |
The Column D trap
Column D is "work completed from previous application (D + E)" — meaning last month's D plus last month's E. Do that by hand across 30 line items and 8 billing periods and the odds of drift are close to certain. When D doesn't reconcile with what you previously billed, the reviewer bounces the application, and you wait another payment cycle. This is the specific problem PayAppFlow eliminates: every application is stored, and D is always the exact sum of prior periods.
Stored materials (Column F) done right
Materials on site but not installed bill under Column F — and usually carry a different retainage rate. When they're installed, they move into Column E of that period. Keep backup (invoices, bills of sale, insurance) because GCs frequently request it for stored material amounts.
Change orders on the continuation sheet
Approved change orders should appear as their own line items so the C column total ties to the contract sum to date on the G702 application. Deductive change orders enter as negative scheduled values. PayAppFlow flags CO lines and rolls them into the change order summary automatically. Also see the schedule of values guide.
Build it in PayAppFlow instead — free
Enter your schedule of values once and PayAppFlow computes every column, carries previous applications forward, and prints a G702/G703-style package ready to submit.
Open the Free Pay App Builder