How to catch a front-loaded pay application: what the padding costs you

The short answer: front-loading is billing the early line items above their true value, so the cash arrives before the work does. The contract sum does not change and every total on the form still ties. You catch it in two places. Inside this month’s document: read each line’s percent complete against the job’s overall percent complete, because padded overhead lines run far ahead of the lines that build the job. Against last month: this application’s Column D, work completed from previous applications, must equal the prior application’s D + E for that item, and Line 7, less previous certificates, must equal the prior application’s Line 6. Not the prior Line 8, and not the cash you paid. What front-loading never breaks is the document’s own arithmetic: G = D + E + F on every row, the sum of Column G equal to Line 4, retainage on the right bases.

What front-loading is, and what it costs the receiver

A schedule of values splits the contract sum into line items. Front-loading pads the early ones: mobilization, general conditions, submittals, bonds, temporary facilities, anything billable before production starts. The contract sum does not move. Value moves, from the late lines to the early ones. The money is real and it sits inside the contract, which is why nothing on the form looks wrong.

Take the $400,000 mechanical subcontract used through the rest of this page. Six lines, priced two ways: the scheduled value the subcontractor submitted, and what the work behind each line is worth.

The three overhead lines carry $120,000 of scheduled value for $80,000 of work, so the three production lines carry $280,000 for $320,000 of work. Once the overhead lines have billed out you hold $280,000 of contract balance against $320,000 of work still to buy. Retainage covers part of that $40,000 gap and not all of it: 10 percent of the $120,000 billed on the overhead lines is $12,000 held. The exposure is largest in the middle of the job, when the padded lines are paid and the expensive lines are not built, and it becomes a real number the day the subcontractor walks off or goes under.

Some of this is ordinary cash flow. A subcontractor funds mobilization, bonds and submittals before a dollar of production is billable, and asks the schedule of values to reflect it. The difference between financing and front-loading is size and disclosure, and you can ask about both. Price it either way, because the exposure on your side is the same $40,000.

Application 1: the baseline

Six lines, 10 percent retainage on completed work and on stored material, on a ten month schedule. Application 1 covers month one. Every row is G = D + E + F, the percent column is G ÷ C, and the balance to finish is C − G.

Read line 4: 0 + 12,000 + 0 = 12,000 for Column G, 12,000 ÷ 120,000 = 10% complete, 120,000 − 12,000 = 108,000 to finish. Column C sums to the $400,000 contract. Column G sums to $96,000, and that is the figure that has to appear on the certificate as Line 4. In dollars the job is 96,000 ÷ 400,000 = 24% complete. The same arithmetic is walked column by column in the worked G703 schedule of values.

A note on the lettering. On AIA’s own G703 the percent complete column carries no letter: H is the balance to finish, C − G, and I is retainage, used where the contract lets it vary by line. Vendor forms printing a G702-style layout often do letter the percent column H and shift the rest along, which is where the widespread “H = G ÷ C” comes from. The tables here leave the last two columns unlettered for that reason. Read the letters off the form in front of you, and trust the description printed above each column over the letter beside it.

What the padding is worth by month two

Month two. The underground crew is producing, the equipment arrives and sits uninstalled, and the overhead lines keep billing.

By the end of month two the three overhead lines have billed 100,000 of their 120,000 of scheduled value, and the honest value of all three together is 80,000. The padding is already inside the money certified. The production lines show 42,000 of work in the ground and 25,000 of equipment standing on a pallet, and 213,000 of scheduled value is left on them to cover 320,000 of work. Two months into a ten month job, that gap is fixed.

The carry-forward checks pass on this application. Every line’s Column D equals last month’s D + E: 36,000, 30,000, 18,000, 12,000, and zero on the two lines that had not started. The Column D total of 96,000 equals last month’s D + E total, and Line 7 will read 86,400 against last month’s Line 6. Running that comparison cell by cell, and finding the item when one fails, is cause 5 of a G703 that does not match the G702.

Stored material does not carry into Column D. The $25,000 of equipment sits in Column F this period. When it is installed it moves out of F and into E, and Column D on that line still reads zero: D carries completed work forward, not stored value. Some forms roll previously stored material into D instead, so that line would read 25,000 with F back at zero. Both conventions tie the row totals. They do not tie Line 5: still-stored value sitting in D lands in the 5a base, and under a split rate of 10 percent on completed work and 5 percent on stored material that retains the 25,000 at 2,500 instead of 1,250, while every row still adds up. A sheet that switches between the two conventions line by line is double-counting somewhere.

Now the break. Suppose general conditions had arrived with Column D reading 34,000 rather than 30,000. Last month reported D + E = 0 + 30,000 on that line, so 4,000 of billing appeared with no period behind it. Follow it through: G on that line becomes 34,000 + 10,000 = 44,000 and the line reads 44,000 ÷ 60,000 = 73.3%, Column D sums to 100,000 rather than 96,000 and Column G to 171,000, so Line 4 becomes 171,000, retainage on completed work becomes 10% of (100,000 + 46,000) = 14,600, Line 5 becomes 17,100, Line 6 becomes 153,900, and against a Line 7 of 86,400 the check is 67,500 rather than 63,900. The application still ties everywhere. Every row is G = D + E + F, the column total equals Line 4, Line 8 equals Line 6 minus Line 7. Only last month’s sheet catches it, and the overstatement reaches the check net of retainage: 4,000 less the 400 retained, a 3,600 difference.

Both certificates, side by side

The G702 for both months, computed from the two continuation sheets above.

Line 5a is the rate on completed work, 10% of D + E = 96,000 + 46,000 = 142,000, so 14,200. Line 5b is the rate on stored material, 10% of 25,000, so 2,500. Line 7 on application 2 is 86,400, application 1’s Line 6, because Line 7 is the total of the certificates already issued and each certificate was a Line 6. The rest follows: 150,300 − 86,400 = 63,900 for Line 8, the check, and 400,000 − 150,300 = 249,700 for Line 9. The chain from Line 4 through both retainage bases is in how retainage is calculated.

Two things Line 7 is not. It is not the prior Line 8, which is already net of everything certified before it, so putting it in Line 7 subtracts the earlier periods twice. It is not the cash you paid either, which moves with backcharges, short payments and released retainage. A second application hides the first of those errors, because with Line 7 at zero the first application’s Line 6 and Line 8 are the same 86,400. It surfaces from application 3 onward, where Line 7 is 150,300 and the prior Line 8 of 63,900 would overstate the payment by exactly the 86,400 already certified.

The front-loading signal itself

Those two comparisons catch a schedule that moved after it was approved. Neither tells you the schedule was padded to begin with. That reading comes from one number per line: percent complete, against the job’s overall percent complete.

On application 1 the job is 24% complete in dollars. Mobilization is at 90%, submittals 90%, general conditions 50%, underground rough-in 10%, the last two lines at zero. Three lines holding $120,000 of the $400,000 contract, 30% of the money, produced $84,000 of the $96,000 billed. By application 2 the shape is fixed. The three overhead lines stand at 100,000 of 120,000, 83.3%. The three production lines have 42,000 of work in place against 280,000, so 15.0%, plus 25,000 of equipment stored but not installed. The job reads 41.8% complete counting stored material and 35.5% counting only work in place, and the overhead lines are at 83.3% on either reading.

Then compare each number against something outside the document. Mobilization at 90% in month one is normal, and the percentage is not the problem: the $40,000 behind it is. General conditions is a time-based cost, so at the end of month two of a ten month schedule it belongs near 20%, not 66.7%. Underground rough-in at 35% is a claim a site walk can price: count the footage in the ground. The lines a walk cannot price, mobilization, general conditions, submittals and bonds, are the lines front-loading uses.

None of this comes out of the document’s own identities, and a front-loaded application passes every one of them: each row’s G = D + E + F, Σ Column C = Line 3, Σ Column G = Line 4, retainage at the contract rate on both bases, Line 8 = Line 6 − Line 7. They prove the document agrees with itself and say nothing about whether line 1 was ever worth $40,000, which is the boundary what a G702 checker cannot check maps out. Those same five identities are what the free G702/G703 checker runs on figures you type.

The arithmetic proves less than it looks like it proves on the other side too. It shows that a carry-forward broke; it does not show intent. A Column D that jumps 4,000 can be a padded line, a prior application everyone agreed to revise, two items merged, or a number typed over a formula. The arithmetic gives you the size and the location; the subcontractor gives you the cause. That is a short conversation when you can name the item, the figure printed, and the figure the prior application requires. A named line is a correction request. A vague complaint is a bounced packet, which is where most rejected pay applications end up.

Scrutinize the first application, not the fifth

The first application from a new subcontractor is the cheapest one to read closely, because it sets the baseline every later application is measured against. From application 2 onward Column D and Line 7 are inherited: if the schedule of values was padded at the start, every carry-forward check afterwards passes with the padding still in it. The checks confirm the numbers moved correctly; they cannot re-open a value you already approved.

So ask for the schedule of values before the first application, not attached to it. Review it against the bid breakdown and your own estimate, and push on the overhead lines and on any line whose value you cannot picture as work. Many contracts cap mobilization or general conditions as a percentage of the contract sum; read yours first. After approval, scheduled values change only through a change order, and the argument narrows to percentages on dollars you already accepted.

Three questions are enough for most schedules. What does mobilization cover, and what does it cost. How does general conditions spread across the months, given that it is a time-based line and belongs on a flat curve rather than in the first two periods. Does any line carry money you cannot picture as work standing on site. Write the answers down next to the approved schedule: they are what every percent complete gets read against for the rest of the job. The carry-forward itself is check 6 in the pay application review checklist.

What PayAppCheck checks here

With the prior application on file, PayAppCheck runs both comparisons on an upload: Line 7 against the prior Line 6, and each line’s Column D against that line’s prior cumulative, wherever the line can be matched to its prior row with certainty. Matching goes by description rather than by item number, because item numbers drift between documents, and the scheduled value has to corroborate the match. It accepts either carry-forward convention and flags a line only when neither fits. Each row’s G, the column totals, both retainage bases and the certificate lines are recomputed at the same time. When a total is off and you need the cell, tracing a G703 that does not match the G702 is the companion to this page.

What it cannot do: it does not know your contract, it cannot price the work in place, and it cannot tell a padded scheduled value from an honest one. A line it cannot pin to a prior row is left unchecked rather than compared against the wrong one. It hands you the failing lines and the dollars attached. Whether $40,000 of mobilization is defensible is for you and the site walk.

Questions people ask

PayAppCheck is software, not a law or accounting firm. Not legal, accounting or tax advice. Verify lien, notarization, and retainage requirements against your contract, your state statute, and your accountant.