Short answer: The schedule of values is the breakdown of the contract sum that the pay application bills against, and the cost-loaded schedule is the same contract sum spread across the activities in Primavera P6. Owner specifications require the two to agree: the activities must add up to the contract sum, the pay application entries must match the schedule, and the update must go in with the pay request. When the G703 percent and the schedule percent disagree, the reviewer asks for a reconciliation before certifying. The fix is to build both documents from one breakdown so one number serves both.
What the schedule of values is
Under the AIA general conditions, the contractor submits a schedule of values to the architect before the first application for payment. It "allocates the entire Contract Sum to various portions of the contractor's work," must be supported by data that substantiates its accuracy, and "is used as a basis for reviewing the Contractor's monthly payment applications" (AIA Contract Documents). The AIA publishes no schedule of values form; the breakdown lives on the G703 Continuation Sheet, which "breaks the contract sum into portions of the work in accordance with a schedule of values," attached to the G702, which shows "the status of the contract sum to date," retainage, previous payments and the amount requested.
The University of Houston's Section 01 29 00, Payment Procedures requires at least one line item per specification section, a total equal to the Contract Sum, multiple line items for any subcontract over 5 percent of the contract, closeout items totaling 5 percent, and a separate line wherever stored materials may be billed (1.3.B); Vanderbilt's Section 01 29 00 wants it 7 days before the first application, resubmitted with every application, each change order on its own line (1.03.A, 1.03.F).
How the owner ties payment to the schedule update
Houston says it directly: "Coordinate preparation of the schedule of values with preparation of Contractor's construction schedule," and on each application, "Entries shall match data on the schedule of values and Contractor's construction schedule" (1.3.A, 1.4.D.1). The San Jacinto River Authority 01 32 16 does not process progress payments unless an acceptable updated schedule accompanies the pay request (1.12.D.1). The Bakersfield City School District 01 32 13 requires the schedule to be cost loaded on the approved schedule of values, with an update accompanying each progress payment application. Iowa DOT SP-230037 sets the update's data date equal to the pay request date and loads cost by bid item, within plus or minus 1 percent of the contract sum (230037.04, 230037.06.B). On federal work, UFGS 01 32 01.00 10 requires that "the aggregate value of all activities coded to a contract CLIN must equal the value of the CLIN" and states that a contractor without an approved schedule "will be deemed not to have provided an estimate upon which a progress payment can be made" (3.2, 3.4).
The schedule is the owner's check on the pay application, not a second document glanced at.
How cost loading works in P6
Cost loading assigns a budgeted cost to each activity, through a resource or an expense, so the activities under a WBS node or activity code add up to a known value and the project total equals the contract sum on the G703.
Oracle's P6 documentation defines the choices. Each activity has a Percent Complete Type of Units, Duration or Physical. Duration percent complete is planned duration minus remaining duration, divided by planned duration. Physical percent complete is "either user-entered or calculated from activity steps." Performance percent complete "is used to calculate earned value" and follows the activity percent complete or a 0/100 or 50/50 rule set at the WBS. Earned cost on an activity is budgeted cost times performance percent complete; summed by schedule of values line, it is the G703 "completed to date" figure before stored materials and retainage.
The setting matters. An activity on Duration percent complete earns money because days passed, not because work was installed, which is why Iowa DOT requires Physical percent complete (230037.04). A schedule left on Duration pays itself on the calendar, and a reviewer who knows P6 will see it.
Where the two numbers come apart
Seven mismatches cause most reconciliation requests:
- Line items that do not map to activities. The schedule of values is organized by specification section or subcontract; the schedule by area and sequence. One line item spreads across many activities, one activity touches several line items, and neither document can be derived from the other, so the two percents come from different people making different judgments.
- Front-loading. Early activities carry more than their cost. UFGS prohibits it outright (3.2.1), and a reviewer reads the cost curve against the work in place.
- Stored materials. The G703 has a column for materials presently stored, and Houston requires a certificate of insurance, evidence of title, surety consent and paid invoices to bill it (1.4.E). A P6 activity has no such column. If material value sits on the installation activity, the pay application shows money the schedule does not, and the reverse once installed.
- Retainage. The G702 requests payment net of retainage. P6 earns gross. Comparing net to gross produces a difference that is not a problem but is often reported as one.
- Activities at 100 percent with nothing billed. Work finished after the pay application was cut, or activities statused complete by date while the installation was not accepted.
- Money billed on activities still in progress. The reverse, and the one that gets a pay application held. A line item well ahead of the activities under it reads as overbilling, whatever the cause.
- Change orders and general conditions. Vanderbilt gives each change order its own line (1.03.F) and Houston requires the schedule of values updated before the next application after any change to the Contract Sum (1.3.B.8). If the change order activities do not go into the schedule the same month, the totals diverge. Overhead and profit is a second trap: Bakersfield wants it as a separate activity, Houston wants each item to carry its proportionate share (1.3.B.7). The spec decides.
What the reviewer does when they disagree
The owner's reviewer, or the architect certifying under the AIA forms, compares the percent on each line item to the percent on the activities coded to it and asks for any difference beyond the causes above to be explained before certifying. Houston returns applications whose entries do not match the schedule of values and construction schedule without action (1.4.D). SJRA does not process payment until an acceptable update is in (1.12.D.1). Under UFGS the contracting officer may withhold 10 percent of each pay request while schedule revisions it directed are left out of the updates (3.2.3).
For a small or mid-size GC that means a pay application that sits a review cycle while the numbers are rebuilt by hand, and subcontractors who wait with it.
Build both from one breakdown
The fix is structural and belongs before the first pay application, not after the first rejection:
- Write the schedule of values and the activity list from the same outline. Follow the owner's rule for line items, then make every activity belong to exactly one line item. A P6 activity code with one value per line item is the simplest way.
- Load cost by line item, then check the sum. The activities under each code value must total that line item's scheduled value, and the project total must equal the contract sum (Houston 1.3.B.4; Iowa DOT within 1 percent). Run the check before the baseline goes out.
- Set Physical percent complete on cost-loaded activities. Status by work installed, not days elapsed, so earned cost means what the pay application says.
- Give stored materials their own place in both documents. A separate line item per the owner's rule, and a delivery activity in the schedule carrying the material value apart from the installation activity that carries labor.
- Put closeout at the owner's stated value. Houston sets closeout at 5 percent of the Contract Sum; the commissioning, O and M, record document and training activities carry that value, so the last pay application is not a surprise.
- Add change orders to both in the same month. New line item, new activities loaded to the change order value, before the next application.
- Set the data date to the pay period cutoff and run the earned value report by schedule of values code. The report columns become the G703 columns, the pay application is a printout of the update, and the monthly narrative explains any line where the two still differ for a reason the reviewer will accept, such as stored material or late-period completions.
Done this way, the reviewer opens the update and the pay application and sees one set of numbers. The update is accepted, the application is certified in the same cycle, and the subcontractors are paid on time, which is the gain described in monthly schedule updates that keep pay applications moving. The same breakdown makes a later time extension defensible, because the cost record and the time record were never two different stories.
Most small and mid-size general contractors already produce a schedule of values; the missing step is building the P6 activity list to it rather than beside it. That is a one-time setup at the baseline, then a monthly status run on the quantities the project manager already uses for the G703: the same report, produced once.
Send the scheduling specification and the drawings, and CPM Pros will send back a written quote with a firm price and delivery date, typically within 3 business days.