Master Valuation Schedule: A Practical Construction Guide

A master valuation schedule construction teams can actually use must connect the accepted scope and price to work that can be checked, measured and valued again each month. For UK subcontractors, that means turning a won job into a controlled schedule before the first Application for Payment. This guide follows that handover from opportunity to approved schedule and first application.

The aim is not to impose one universal format. Contract wording, client requirements and trade practice vary. The aim is to create a controlled breakdown that reconciles to the agreed contract value and makes cumulative progress understandable to both parties.

What is a master valuation schedule?

For this guide, a master valuation schedule means the agreed breakdown of a construction contract into priced, measurable work items. We use it to record the phases, descriptions, quantities, units, rates and values against which cumulative progress is assessed. Each Application for Payment then reuses that structure instead of recreating the contract breakdown every month.

This article uses the term for a practical commercial control: a priced structure that connects agreed scope to repeatable valuations. It does not suggest that every contract, employer or project uses the same label or document format.

UK Parliament (1996), in Part II of the Housing Grants, Construction and Regeneration Act 1996, sets payment provisions for qualifying construction contracts, including stage payments, payment dates, notices and payment of the notified sum. Part II does not prescribe a standard master valuation schedule. Your contract still controls the required submission format, valuation rules and dates, so check it before preparing an application.

From Project Pipeline to a live contract

A pipeline opportunity is an estimate of possible work; a live project is a contract that needs operational and commercial control. Marking an opportunity as won should therefore start a deliberate review, not automatically treat its forecast value as the final contract sum or as revenue earned.

In BuildQS, a won pipeline entry can be converted into a live project. The conversion carries the opportunity name, estimated value and dates into project setup, where the user reviews the contract value and adds the client and contract details. That saves retyping while preserving the distinction between an estimate and an agreed contract.

Before conversion, compare the latest order, accepted quotation, tender clarifications and negotiated adjustments. Confirm whether the value includes VAT, discounts, provisional sums, design allowances or other items that affect the schedule. Record the final agreed basis rather than copying an outdated tender total.

For the full pipeline workflow, read BuildQS Project Pipeline for construction forecasting. That guide covers opportunity stages, probability weighting and timing without confusing them with certified work or cash due.

What should a master valuation schedule contain?

A useful schedule contains enough information for another person to identify each item, verify its price and assess progress. It should reconcile from individual line values through phase subtotals to the contract total, with later changes identified separately from the original scope.

Include these core fields:

• Phase or work section: a logical group such as preliminaries, containment or pipework.
• Line description: a clear statement of the location, system or deliverable being valued.
• Unit and quantity: for example metres, number, item or lot, using a basis that can be evidenced.
• Rate: the agreed price per unit where the work is quantity based.
• Line value: the quantity multiplied by the rate, or an agreed lump sum where appropriate.
• Phase subtotal and contract total: visible checks that the breakdown reconciles to the signed value.
• Variation identity: a separate label for instructed changes so original scope is not silently rewritten.

The Royal Institution of Chartered Surveyors (RICS, accessed 2026) presents its New Rules of Measurement as measurement guidance. This example does not claim NRM compliance merely because it uses quantities and rates. Apply the measurement rules named in your contract or tender documents, and keep descriptions, units and measurement bases consistent within the schedule.

Worked example: a £186,500 mechanical package

Consider a mechanical subcontract agreed at £186,500. The following compact breakdown shows the contract structure before any progress is entered:

• Preliminaries: 1 item × £18,500 = £18,500.
• Containment: 1,200 m × £32.50 = £39,000.
• Pipework: 1,500 m × £48 = £72,000.
• Plant installation: 5 items × £9,000 = £45,000.
• Testing and commissioning: 1 item × £12,000 = £12,000.
• Contract total: £18,500 + £39,000 + £72,000 + £45,000 + £12,000 = £186,500.

The basic line calculation is Quantity × rate = line value. If the schedule contains more detailed lines within each phase, add those lines to obtain the phase subtotal, then add every phase subtotal to verify the £186,500 contract total.

Now assume the first valuation records preliminaries at 60%, containment at 40%, pipework at 25%, plant installation at 0%, and testing and commissioning at 0%. The cumulative value is:

• Preliminaries: £18,500 × 60% = £11,100.
• Containment: £39,000 × 40% = £15,600.
• Pipework: £72,000 × 25% = £18,000.
• Plant installation: £45,000 × 0% = £0.
• Testing and commissioning: £12,000 × 0% = £0.
• Cumulative gross value: £11,100 + £15,600 + £18,000 = £44,700.

For the first application, the previous cumulative value is £0, so the current-application value is £44,700 - £0 = £44,700. If the next valuation reaches a cumulative gross value of £73,250 and the previous cumulative value remains £44,700, the movement is £73,250 - £44,700 = £28,550 for the current application. Retention, agreed deductions and VAT are then treated in line with the contract. This keeps contract pricing separate from progress and prevents cumulative work from being claimed twice.

How detailed should the schedule be?

The right level of detail lets progress be evidenced and assessed without turning the schedule into hundreds of trivial lines. A single line for an entire mechanical package is usually hard to measure, while a separate line for every small fitting can make monthly updates unmanageable.

Use four practical tests. Can site records or drawings support the stated progress? Can the client or quantity surveyor understand what the line covers? Can an instructed change be separated from original scope? Will the cumulative percentage still make sense after several applications?

Break work where cost, location, sequence or evidence changes materially. For example, separate pipework by system or area if those sections progress independently. Keep genuinely inseparable lump-sum deliverables together. Use the same units and descriptions as the accepted pricing documents unless both parties agree a clearer breakdown.

Review and approve the schedule before the first AFP

Approval establishes the controlled baseline for the first Application for Payment, shortened to AFP in this guide. It confirms that the structure is ready for progress entry; it does not replace contractual acceptance by the payer or decide the value of later work.

Before approval, check that descriptions match the agreed scope, quantities and rates match the pricing record, line values calculate correctly, phase subtotals add up, and the total reconciles to £186,500 in this example. Confirm the treatment of discounts, provisional items and exclusions. Ask the relevant client contact or quantity surveyor to resolve disputed breakdowns before a monthly deadline puts pressure on the review.

BuildQS reflects this control point precisely: approval locks Add Phase and Add Task until approval is revoked. Add Variation remains available so post-contract changes can be recorded without rewriting original scope. Revoke approval only when a genuine baseline correction is needed, then document why it changed and obtain the appropriate agreement again.

Create the first Application for Payment

The first Application for Payment uses the approved schedule as its valuation grid. Enter progress against each line, support the assessment with project records, and let the application show the difference between value to date and the previous cumulative position.

Start with the valuation date required by the contract. Review each line against evidence such as measured quantities, delivery records, progress photographs or signed records where relevant. In BuildQS, percentage mode enters cumulative completion. Pound mode enters this application's movement, and BuildQS converts it into the cumulative position by adding the equivalent percentage to the previous completion. This distinction lets a user choose the input that matches the assessment without confusing monthly movement with cumulative progress.

At summary level, the application should make the path from gross cumulative value to the current amount clear. Previous cumulative value is deducted to identify this application's movement. Retention, releases, agreed deductions and other contract adjustments then contribute to the net amount due. The payment terms and notices remain contract specific. UK Parliament (1996), in sections 109 to 111 of the Construction Act 1996, addresses stage payments, payment dates, notices and the notified sum for contracts within scope, but the schedule itself does not determine whether an application complies.

Use the construction payment application checklist for submission content, and compare percentage and amount entry for the two valuation methods. The payment applications feature shows how BuildQS carries the schedule into repeat applications.

Common master valuation schedule mistakes

Most schedule problems begin before the first valuation. Catching them at setup is quicker than explaining inconsistent totals after several cumulative applications.

• Not reconciling to the contract sum: even a small gap leaves the application basis open to challenge.
• Using vague descriptions: lines such as "mechanical works" do not explain what has progressed.
• Mixing original work and changes: keep variations visible rather than increasing base lines without an audit trail.
• Changing units or rates: inconsistent measurement makes comparisons and evidence harder to follow.
• Applying before agreement: unresolved schedule structure can turn every progress entry into a second argument.
• Maintaining parallel files: two spreadsheet versions create uncertainty about the current baseline.
• Treating a pipeline estimate as final: review the won value against the order and accepted pricing documents.
• Entering monthly movement as cumulative progress: this overstates work when the next application adds another cumulative figure.

When scope changes, follow the contract's instruction and valuation process. The guide to variations in UK construction contracts explains why changed work should remain visible and evidenced.

How BuildQS connects the workflow

BuildQS keeps the commercial sequence in one connected workflow: convert a won opportunity, review the project details, structure phases and priced tasks, approve the Master Valuation Schedule, then create the first draft application against those same lines.

That sequence reduces duplicate setup and makes each transition explicit. Pipeline values remain planning information until reviewed. Schedule values become the contract baseline. Completion entries become cumulative valuation data. Variations remain distinct, and later applications retain the previous position needed to calculate current movement.

Software does not decide whether a description, measurement or application complies with a particular contract. The commercial team still reviews scope, evidence, dates and notices. Its value is in preserving one controlled structure so the team can see what was agreed, what has progressed and what changed.

Prefer to walk through your workflow live first? Book a Demo

Frequently asked questions

Is a Master Valuation Schedule the same as a schedule of works?

Not automatically. In this guide, a schedule of works describes project activities or scope, while the Master Valuation Schedule is the priced breakdown used to assess progress. A project may use one accepted document for both purposes when it contains the scope, quantities, rates and values needed for valuation.

Does the schedule have to match the contract sum?

Yes, the original schedule should reconcile to the agreed contract sum on the basis stated in the contract, including the agreed treatment of discounts or allowances. Later variations should be shown separately rather than disguising a mismatch in the original breakdown. Investigate any difference before the first application.

Can the schedule change after the first payment application?

It can be corrected or restructured where the contract and relevant parties permit, but changes need control because previous cumulative valuations relied on the earlier baseline. Record the reason, preserve the audit trail, reconcile prior applications and obtain the required agreement. Do not overwrite history merely to make a current valuation easier.

How are variations added after the schedule is approved?

Record each instructed change as a separate variation with its own description, value and supporting record. In BuildQS, Add Variation remains available while the approved schedule prevents new ordinary phases and tasks. This preserves the original contract baseline while allowing changed scope to flow into later applications under the contract's valuation process.

Sources

• UK Parliament (1996, revised version accessed 20 July 2026). Housing Grants, Construction and Regeneration Act 1996, Part II construction contracts and payment provisions.
• Royal Institution of Chartered Surveyors (RICS, accessed 20 July 2026). New Rules of Measurement.

This article provides practical workflow information, not legal or contractual advice. Check the signed contract and obtain professional advice for project-specific interpretation.