Construction Control

Construction Control — Articles

How to Create a Schedule of Values That Stays in Agreement With Your Change Orders

Most schedules of values are built once, at the start of the job, in a hurry. The contract amount gets broken into lines, the lines get values, and the sheet is done. Then the job starts changing. Change orders get priced, submitted, and approved in a separate log, in separate emails — and the schedule of values, the document every pay application is built from, never gets updated to match.

Two or three billings later, the schedule of values and the change-order record describe two different contracts. An approved change order has no line to bill against. Another is billed at the estimate it started with instead of the value it was approved at. Neither error is visible inside the schedule of values itself, because the schedule never gets compared to the log it drifted away from.

The fix is not a fancier template. It is building the schedule of values so that change orders have a defined place in it from day one — and tying it out against the change-order log every month, before the pay application goes out.

1. Start from the contract breakdown, not a blank grid

Build the lines from the contract's own scope breakdown — the way the work was estimated and bought out. Each line should be a chunk of work whose completion can be judged on its own: a system, a phase, a floor, a definable portion of the scope. Two failure modes sit at opposite ends. A line that covers an entire trade package is too coarse — progress on it is a guess, and a reviewer cannot tell what the billed percentage is based on. A line for every fitting and fitting type is too fine to maintain, and the sheet collapses under its own detail by the second billing.

The first test of the finished breakdown is arithmetic: the scheduled values of the base-contract lines must add up to exactly the contract sum. Not approximately — exactly. If the template starts a dollar off from the contract it represents, every application built on it inherits the difference.

2. Freeze the line structure, then never quietly edit it

Once billing starts, line numbers, descriptions, and scheduled values on the base contract stay fixed. The previous-applications figures on this month's schedule have to agree, line by line, with what was certified last month. Insert a line in the middle, renumber, or quietly adjust a scheduled value, and that tie breaks: previous plus this period no longer reconstructs the completed-to-date figure the reviewer certified last time, and the discrepancy surfaces as a question about your numbers generally — not just the edited line.

New scope does enter the schedule — jobs change — but it enters in one way only: as new lines, added at the end, through the change-order process described next. Existing lines are not the place to absorb new work.

3. Every approved change order gets its own line — at its approved value

Pending change-order requests do not belong on the schedule of values yet. They live in the change-order log, with their T&M ticket backup accumulating behind them, until they are approved. The moment one is approved, it becomes a schedule-of-values line of its own, at exactly the approved value.

This single habit prevents the two most expensive schedule-of-values errors, because both are born in the gap between the log and the sheet:

  • The approved change order that never got a line. The work is approved, documented, and performed — and never billed, because the pay application is built from the schedule of values and the change order is not on it.
  • The line billed at the wrong value. The change order was added to the schedule when it was still an estimate, and nobody replaced the estimate with the approved figure when approval came through.

SYNTHETIC EXAMPLE: Say the base contract is $184,000. COR-007 is approved at $6,400, but the schedule still carries it at its $5,900 estimate — every billing against that line is $500 short of the approved value. COR-009 is approved at $3,150 and never added as a line at all — that work cannot be billed until someone notices. Neither error requires bad intent; both are what happens when the log and the schedule are maintained as separate documents. (All figures in this example are invented for illustration.)

4. Use the columns the continuation sheet actually needs

A working schedule-of-values template carries, per line: line number, description of work, scheduled value, work completed from previous applications, work completed this period, materials and equipment suitably stored, total completed and stored to date, percent complete, balance to finish, and retainage. That is the structure of the AIA G703 continuation sheet the schedule feeds — the G702 summary form reports what the continuation sheet details — so a template built on the same columns moves into the application without re-keying.

Keep the arithmetic boring and visible. Completed to date is previous certified work plus this period's work. Stored materials are tracked in their own column; they are not completed work and should not inflate the percent complete. Percent complete is completed-to-date divided by the scheduled value — including, for change-order lines, the approved value from section 3, not the estimate it replaced.

5. Tie the schedule out before every billing

Creating the template is a one-time job. Keeping it true is a monthly one, and it is a short pass with four checks:

  1. Log to schedule: every change order marked approved in the log appears on the schedule of values, as its own line, at its approved value.
  2. Schedule to log: every change-order line on the schedule traces back to an approved change order. A line billed for a change order that is still pending is its own problem — and an honest warning here: this one is a discipline check, not a formula check. No exception check in our workbook flags a change order that was billed before approval; you catch it by making this comparison yourself.
  3. Previous period: the previous-applications column agrees line by line with last month's certified application — not just in total.
  4. Totals: the schedule's columns are re-added and agreed to the continuation sheet and summary they feed.

When the log and the schedule disagree anyway, why a pay application doesn't match its change orders breaks the divergence into the three places it sits — a pending COR against its tickets, an approved COR missing from the application, and a billed amount that differs from the approved amount.

Where the workbook fits — and where it doesn't

The tie-out above is one leg of a three-way reconciliation: T&M tickets prove the extra work, change-order requests carry it through approval, and the schedule of values is where it gets billed. Construction Control is an Excel workbook for use alongside your AIA G702/G703 that reconciles those three records against each other and flags seven exceptions by name: Duplicate ticket, Missing fields, Unlinked ticket, COR without backup, Pending COR vs ticket mismatch, Approved COR missing from pay app, and Approved COR vs billed value. The two schedule-of-values failures in section 3 are the last two checks on that list — the workbook compares the approved change-order record to the pay-app schedule of values directly, which is the comparison a static template never makes on its own. You can watch the workbook work in the demo — the same seven checks firing on synthetic example data.

The boundaries, plainly: the "Prior completed $" column (column D) on the workbook's Pay App SOV sheet is typed in by hand — it is not pulled from last month's application automatically. The workbook does not check your G702/G703 totals; re-adding those is still your step 4. It does not check retainage. And as noted above, it does not flag a change order billed before it was approved.

Three resources, in the order you'd use them. The Pay App Pre-Submission Checklist is a free one-page PDF (also on the Construction Control site) that turns the pre-submission pass — including the tie-out in section 5 — into a printable checklist. The free T&M Ticket Log Template covers the other end of the chain: the ticket records that stand behind your change orders. And the full reconciliation is the Construction Control Subcontractor Pay App Bridge, a one-time $39 purchase.

A schedule of values is not a form you fill in once. It is the contract as billed, kept current. Build it so change orders enter it in exactly one way, and check it against the log every month — that is most of what keeps it true.

Before your next application