Schedule of values and front loading explained

Published . Updated .

Every monthly pay application on a lump sum job rests on one document: the schedule of values. It splits the contract price into lines, and each month the contractor claims a percent of each line. If the lines are wrong, every pay application built on them is wrong too, even when the arithmetic is perfect. This guide explains what the schedule is, how it gets distorted and how to test it.

For the monthly check of claims against the site, see how to check a pay app against field reports. For the arithmetic tests, see the pay app error checklist.

What a schedule of values is

A schedule of values breaks the contract sum into parts that match the work: site work, foundations, structure, mechanical, electrical, finishes, general conditions and so on. Each part has a scheduled value in dollars, and the parts add up to the contract sum.

On the payment forms published by the American Institute of Architects (AIA), the schedule of values is laid out on G703, the Continuation Sheet, which supports the summary on G702, the Application and Certificate for Payment. GroundClaim is not affiliated with the AIA. Each row of the continuation sheet carries:

Contractors who do not use AIA forms keep the same structure in a spreadsheet. The columns have other names, and the logic is the same.

Why the schedule matters more than it looks

The schedule is the unit of measure for progress. When a superintendent says the HVAC is 80 percent done, the percent only means something if the HVAC line holds the right share of the price. A line that is too large in the early months turns a small amount of work into a large payment.

What front loading is

Front loading means assigning more value to early work than it costs, and less to later work. The total contract sum is unchanged. The timing of the cash is not: the contractor is paid earlier, and the party paying carries the risk if the contractor leaves, fails or disputes the later work.

A simple illustration with invented numbers. A $1,000,000 job has an excavation line fairly worth $50,000. The schedule shows $120,000. After excavation is finished and billed at 100 percent, the contractor has been paid $70,000 more than the work is worth. The contract sum is still $1,000,000, so the remaining lines together are worth $70,000 more than the schedule gives them. The arithmetic on every month's pay application can still be perfect.

Legitimate reasons for large early lines

A big first line is not proof of a problem. Valid reasons include:

The test is whether the value matches costs actually incurred or work actually done, with some documentation behind it.

Signs of a front-loaded schedule

Look at the schedule before the first payment, and again whenever lines change.

  1. Early lines bigger than the work suggests. Compare sitework, mobilization and general requirements with your own estimate or last job's numbers.
  2. A thin final stretch. Closeout, commissioning, punch list and startup lines that are tiny compared with their real effort leave little value behind to motivate finishing.
  3. Round or lump-sum lines. A broad line such as "Mechanical, lump sum" cannot be measured. Ask for it to be split.
  4. Lines that reach 100 percent early. Several lines at full billing in the first months, on a job that has barely started, is a pattern to explain.
  5. Changes with no change order. Scheduled values should move only through documented changes.

How to test the schedule

  1. Compare each line with a bid breakdown, your estimate or the subcontract amounts.
  2. Ask for backup on any line that looks high: the subcontract, a purchase order, a quote.
  3. Add up the lines you expect to finish in the first months and compare their share of the contract sum with their share of your own estimate. If the schedule puts 30 percent of the price on work your estimate puts at 20 percent, ask why.
  4. Ask for the final lines to hold enough value to finish the job. Many contracts keep a share through retainage, and the rate is set in the contract, so check yours.
  5. Record your findings at the start. Raising a concern before the first payment is easier than challenging the schedule after months of billing against it.

Front loading versus over-claiming

The two are related but different:

ProblemWhere it livesHow you find it
Front loaded scheduleIn the scheduled values themselvesCompare lines with costs and estimates
Over-claimed progressIn the percent complete claimed this monthCompare claims with field reports
Arithmetic errorIn the sumsRecalculate

A job can have all three at once. A clean schedule does not protect you from an inflated percent, and a correct percent applied to an inflated line still overpays.

What to do if you suspect front loading

Raise it early and in writing, and ask for a revised schedule or backup. Rewriting the schedule is a contract matter, and the process depends on what you signed, so check your contract and speak to your counsel or accountant if the amounts are material. Do not wait for the last pay applications to discover that little value remains.

How GroundClaim does this step

GroundClaim reads the schedule of values from the pay application you upload (a spreadsheet, a Word or PDF table, or a scan or photo, up to 400 lines) and treats each scheduled value as given. It does not judge a schedule against a bid or an estimate, and it does not tell you what a line should be worth. What it does check each month is the claimed percent on each line against your field notes, plus the arithmetic: the schedule of values total against the contract sum, tie-out of the lines to the summary, retainage, and lines past 100 percent.

That means it helps with the second and third rows of the table above, and it can show you lines claimed far ahead of what the notes support. The first row, whether the scheduled values are fair, stays with you. The output is an exceptions memo ranked by dollar exposure and a reconciliation of every line, clean ones included. A second, stronger AI model reviews every result, fixes what it can, and lists what is left for you to decide. Results are model output checked by code and by a second model; they are not verified by a person.

A pay application costs 25 credits. Create an account to test one.

Questions

Is front loading always a problem?
No. Real up-front costs such as mobilization, bonds, submittals and long-lead equipment can justify larger early lines. The issue is value that has no cost or work behind it at that point in the job.
Who sets the schedule of values?
On common contract forms, the contractor prepares it and submits it before the first pay application, and the architect, the owner or the contractor above can object to it. Check your contract for how it is submitted and changed.

Check this month's pay app before you sign.

Create an account, upload the pay app and field notes, download the exceptions memo.