NEC4 interim payment assessment: how to build an amount due the PM can't cut

Application submitted on the assessment date. Certificate comes back nine days later, £180,000 short, with a single line against the labour claim: "not substantiated." No breakdown of which shift, which gang, which day. Just a number that is smaller than the one you sent.

This is not a dispute yet. It is the interim assessment doing what clause 50 says it does: the Project Manager assesses what the records support, not what the application asks for. Get the assessment right every month and there is nothing left to dispute. This post covers how the amount due is actually built under NEC4, why applications get cut before they reach the PM's desk, and the records that make the number stick the first time.

How the amount due is assessed under clause 50

At each assessment date, the PM assesses the amount due: the Price for Work Done to Date, plus other amounts payable to the Contractor, less amounts payable by or retained from the Contractor. Clause 50.2 gives the Contractor the right to submit an application for payment before the assessment date, and on a UK contract with secondary Option Y(UK)2, that application carries real weight. But the assessment itself is still the PM's act, and the PM only has what is in front of them.

Two things decide what "in front of them" actually contains.

The definition of Price for Work Done to Date changes by main option. On Options A and B it tracks completed activities or measured quantities against the Activity Schedule or Bill of Quantities. On Options C, D and E it tracks Defined Cost, meaning every pound claimed needs a chain back to a timesheet, a plant ticket, a subcontractor certificate or a materials invoice. A percentage-complete estimate does not survive a Defined Cost assessment. It invites the PM to substitute their own estimate for yours, and their estimate is the one that gets certified.

The second is timing. Clause 50 runs on a fixed rhythm, an assessment date each month (or whatever interval the contract states), and clause 51 requires the PM to certify within one week of that date. There is no extra week to go and find the missing timesheet. Whatever substantiation exists on assessment day is what gets assessed. Everything else becomes next month's argument, if it becomes an argument at all.

For the full clause 50 to 51 mechanics, assessment date rules and the NEC4 payment guide covers the timeline in detail. Where that guide stops is where most of the money actually gets lost: not in the clause, in the evidence behind it.

Why applications get cut

Three patterns account for most of the gap between what gets applied for and what gets certified.

The application states a total, not a build-up. "Labour: £340,000" is an assertion. "Labour: £340,000, per attached timesheets by cost code and week" is a build-up the PM can check against something. A PM who cannot verify a line item has one safe option: reduce it to what they can see.

The records exist but were never linked to the application. Diary entries, delivery tickets and plant sheets sit in a folder somewhere, unattached to the specific line they are meant to support. The QS knows the evidence is there. The PM reviewing the application does not, because nothing on the application points to it.

The evidence is compiled after the fact. A supervisor asked in week three to reconstruct what a gang did in week one produces a best guess, not a record. The PM can tell the difference, and so can an adjudicator eight months later if it gets that far.

None of these three are disputes about entitlement. They are gaps between what happened and what could be shown to have happened at the moment it mattered.

What a defensible application actually needs

Strip the procedure back and a clause 50 application that survives assessment needs three things, every cycle.

A stated sum with a stated basis, not a total. Each line traceable to a cost code, an activity, or a compensation event reference, so the PM's review is a checking exercise rather than an interrogation.

Contemporaneous substantiation, meaning records made on the day the work happened, not reconstructed for the application. On Options C to F that is the Defined Cost trail: timesheets, plant hire days, subcontractor payments, delivery notes. On Options A and B it is dated evidence of the activity or quantity actually completed.

A consistent link between record and claim. The timesheet needs to say which activity, which cost code, which day. A diary entry that just says "concrete gang on site" supports nothing specific. One that says "concrete gang, pour to pier 4, 08:00 to 17:30, activity 2.14" supports a line item directly.

This is the layer the QS AI Agent is built for. Gather reads every site diary entry as it lands, ties it to the programme activity and the cost code behind it, and keeps the Defined Cost trail assembled in real time rather than reconstructed at month end under deadline. When the application goes in, the substantiation is already sitting behind every line, not scattered across a supervisor's notebook and four inboxes. If you want to see what a Defined Cost application pack looks like when it is built from live site records, book a 15-minute demo.

Common mistakes that cost real money

• Submitting a total per cost head with backup "available on request" instead of attached, which forces the PM to assess on what they can verify rather than what was spent.
• Letting the diary and the application drift apart, so the two records describe the same week differently and neither one is fully trusted.
• Treating month-end as the moment to build the evidence pack, rather than the moment to submit one that already exists.
• Accepting an under-certification quietly for two or three cycles, so the gap compounds and the trail that would explain it has gone cold.
• Assuming a strong verbal account of the month's progress will carry the same weight as a dated record. It will not, to a PM or to an adjudicator.

A worked example

A £30m water infrastructure package under NEC4 Option C, monthly assessment dates, Defined Cost running close to £1.4m a month. In month seven, the application goes in at £1.52m. The certificate comes back at £1.34m, £180,000 light, with the PM's note reading "labour substantiation insufficient for weeks 2 and 3."

Run it the usual way. The commercial team spends most of the following week chasing agency timesheets, cross-checking them against a foreman's paper diary, and trying to work out which shifts covered which activity. By the time a response goes back, the next assessment date has already passed. The gap rolls into month eight's application, now tangled with a second month of live substantiation, and the PM is now assessing two disputed months at once instead of one.

Run it record-referenced instead. Every shift for weeks 2 and 3 was logged in the site diary the same day, tied to the activity code and the labour on site. Within two days of the certificate, the QS sends a line-by-line response: each queried labour hour matched to a dated diary entry and the corresponding timesheet. The PM corrects £165,000 of the £180,000 at the next assessment. The remaining £15,000 turns out to be a genuine measurement difference on a shared activity, resolved in a ten-minute call. One assessment cycle of disputed cash instead of two, and the PM's confidence in the next application goes up rather than down.

Same contract, same PM, same £180,000 gap. The only variable was whether the record existed on the day or had to be built afterwards.

Frequently asked questions

How is the amount due assessed under NEC4 clause 50?

The Project Manager assesses the amount due at each assessment date as the Price for Work Done to Date, plus other amounts payable to the Contractor, less amounts payable by or retained from the Contractor. On Options A and B, Price for Work Done to Date follows completed activities or quantities. On Options C to F it follows Defined Cost, which must be substantiated by records such as timesheets, plant hire days and subcontractor payments.

Why do NEC4 payment applications get reduced at assessment?

Applications usually get cut because the sum claimed cannot be verified against the records available to the Project Manager on the assessment date. Common causes are stating a total without a build-up, holding substantiation separately from the application rather than attaching it, and reconstructing evidence after the work rather than recording it at the time.

What records does a Defined Cost application need?

Defined Cost applications under Options C to F need a clear chain from claimed cost to evidence: timesheets linked to cost codes and activities, plant hire records matched to days claimed, subcontractor payments assessed against the work certified, and materials evidence tied to delivery. Each element should reference the specific activity or compensation event it supports.

What is the difference between an interim payment assessment and a payment dispute?

An interim payment assessment is the routine clause 50 process the Project Manager carries out every assessment date. It becomes a payment dispute only when the certified amount is challenged and unresolved, typically escalating through the Y(UK)2 notice regime and, if needed, adjudication. Strong contemporaneous records resolve most assessment gaps before they reach that stage. See our guide to NEC4 payment disputes for what happens when an assessment gap does escalate.

The bottom line

Clause 50 rewards whoever can show their working. The PM is not looking for the biggest number. They are looking for the number they can verify inside a week, and they will certify exactly that much. The application that survives assessment is the one built on records made the day the work happened, tied to the activity and the cost code, ready before the assessment date rather than assembled after the query.

Get that right and there is no dispute to have. The amount due simply matches the amount claimed, month after month.

Want a Defined Cost trail that is already built when the assessment date arrives? Gather links every site diary entry to your programme and cost codes as the work happens. Book a 15-minute demo.

Source: Gather Insights, the AI-powered site diary and commercial record management platform for UK construction.

---