Allocation Sheets That Don't Link to the Programme

What you need to know

The allocation sheet talks in trades. The programme talks in activities. Nobody translates between them, so the data floats in isolation.
Without the link, the CVR rests on the QS's estimate of the resource split, and the cost to complete inherits that guess.
A CE quotation that can't isolate cost to the affected activity gets rejected or reduced.
Disallowed Cost defence becomes argumentative rather than structural.
Fix it at source: an activity reference field, pre-populated from the two-week look-ahead, selected by the supervisor, reconciled monthly.

You've got 90 days of allocation sheets. Names, hours, trades. Every box is filled in. Every sheet was submitted on time. Your site team has been diligent. Your compliance rate is 100%.

To connect resource entries with the wider daily record, see the construction site diary guide.

And none of it links to a single programme activity.

Three months of data that won't feed your CVR, can't substantiate a CE quotation, can't justify Defined Cost under Clause 52.4, and never connects to the one document that ties your entire commercial position together: the Accepted Programme.

Your allocation sheets are complete. They're also commercially disconnected from everything that matters.

The disconnect nobody notices

The allocation sheet records resources against trades or work packages. Earthworks. Drainage. Piling. The programme records activities against time: earthworks cut Zone C, chainage 450 to 520, weeks 12 to 18, activity EW/014.

The two documents use different languages, different structures, and different reference systems.

The allocation sheet talks in trades. The programme talks in activities. Nobody translates between them.

The consequence: your allocation data floats in isolation. It tells you who was on site doing roughly what. It doesn't tell you which programme activity they were supporting, whether that activity is on track, or what the cost per programme activity is.

You have attendance data dressed up as commercial intelligence. And the gap between the two is where your CVR accuracy, your CE substantiation, and your Disallowed Cost defence all break down.

Why the link matters

CVR accuracy

Your Cost Value Reconciliation compares actual cost against tendered value for each activity. If your allocation data doesn't link to programme activities, the QS estimates the split.

I think about 60% of the earthworks resource was on Zone C this month.

That estimate feeds the CVR. The CVR feeds the cost to complete the forecast. The forecast feeds the commercial director's report. The entire chain rests on a guess because the allocation sheet didn't link to the programme.

When the commercial director asks whether you're making money on earthworks Zone C, the honest answer is that you don't know. Nobody gives that answer. They give the estimate. And the estimate is often wrong.

CE substantiation

A compensation event affects a specific programme activity. The CE quotation needs to show the resources deployed against that activity, the cost impact, and the time impact on that activity's duration and float.

If your allocation data just says earthworks, 8 operatives, 10 hours, you can't isolate the cost of the specific activity affected by the CE. You're asking the PM to accept a global allocation rather than a precise, activity-specific cost.

The PM's response is predictable: show me which of these earthworks costs relate to the activity affected by the compensation event. If the allocation data doesn't link to programme activities, you can't. The quotation is rejected or reduced. The revision cycle begins. This is one of the most common reasons a CE quotation fails PM scrutiny.

Programme justification

Under NEC4, the Accepted Programme needs to be realistic and based on actual progress. When the PM reviews a programme update for acceptance under Clause 31, they're looking for evidence that planned durations and resource assumptions are grounded in reality.

Without the link: the programme is aspiration, not evidence. Duration assumptions can't be verified against actual productivity. The PM has grounds to withhold acceptance.

With the link: every programme activity has corresponding allocation data showing actual resources deployed. Duration assumptions are validated by actual output rates. Acceptance becomes straightforward.

Disallowed Cost defence

Clause 11.2(26) disallows costs for resources not used to Provide the Works. Earthworks, 8 operatives could be any earthworks activity: ones already complete, ones not yet started, ones not in the Scope.

If the allocation data links to programme activity EW/014, the cost is pinned to a specific, verifiable piece of work within the Scope. The PM can check: is EW/014 in the programme? Is it within the Scope? Did it progress this week? If yes to all three, the cost is defensible.

If the allocation data just says earthworks, the defence becomes argumentative rather than structural. And argumentative defences take longer, cost more, and succeed less often. More on what gets struck out here.

Why it doesn't happen

Three reasons, all fixable.

The allocation sheet template doesn't have an activity reference field. It has columns for name, trade, and hours. Nobody added the activity reference because nobody asked for it.

The supervisor doesn't have the programme. They know what they're building. They don't know the activity reference for what they're building. The programme lives in Primavera on the planner's laptop. Neither that document nor the WBS codes ever reach the Portakabin where the allocation sheet gets filled in.

Nobody asked for it. The commercial team hasn't specified that allocation data should reference the programme because they've always done the translation manually. The QS receives earthworks, 8 operatives, 10 hours and mentally allocates it to EW/014 based on what they think was happening that day. The manual translation is so embedded in the process that nobody has questioned whether it should be automated at source.

How to fix it

Add an activity reference field to the allocation sheet. Whether digital or paper, the allocation sheet needs a column that links each entry to a specific programme activity. Not a trade. Not a work package. A programme activity with a reference number.

Pre-populate the activity list from the look-ahead programme. The supervisor shouldn't need to memorise WBS codes. The activities from the two-week look-ahead should be available as a selection list: earthworks cut Zone C, EW/014. Drainage run 7 Zone A, DR/007. Piling Zone B, PL/003.

The supervisor selects the activity their gang is working on. The link is created at source, not reconstructed by the QS three weeks later.

Run a monthly reconciliation. For every programme activity, check whether there is corresponding allocation data. A programme activity with no allocation data means either the work isn't happening or the records aren't being captured. Allocation data with no programme activity means either a scope change or a wrong selection. Either way, you need to know before it compounds.

Make it the planner's problem too. The planner creates the programme. The supervisor fills in the allocation sheet. If those two people never talk, the link never forms. Require the planner to provide a simplified activity list to site teams every two weeks, aligned with the look-ahead. The translation happens once, at source, rather than repeatedly and retrospectively by the QS.

The compound effect of disconnected data

One day of unlinked allocation data is a minor inconvenience. The QS can usually work out where the resources were deployed from context.

One week creates uncertainty. The QS is estimating rather than reporting.

One month means the CVR is fiction. The cost to complete the forecast is guesswork.

Three months means CE quotations are being built on estimated resource splits, the programme update can't be validated, and Disallowed Cost exposure is increasing on every activity where costs can't be linked to the Scope.

Six months means the data gap is permanent. Nobody can retrospectively allocate resources to programme activities with any accuracy after six months. The information that existed in the supervisor's head on that day is gone. The commercial position for the entire period rests on the QS's estimates and the PM's willingness to accept them.

Your allocation sheets might be 100% complete. Every box is filled in. Every sheet was submitted on time. But if none of them links to a programme activity, they're attendance records, not commercial evidence.

The link between allocation data and the programme is the connection that makes everything else work: your CVR becomes evidence-based, your CE quotations reference specific activities, your programme updates are grounded in actual deployment, and your Disallowed Cost defence is structural rather than argumentative.

The fix is an activity reference field, pre-populated from the look-ahead, selected by the supervisor, and reconciled monthly by the QS.

Pick any programme activity on your project. Can you pull up the allocation data that shows which resources were deployed against it last week? If you can't, your allocation sheets aren't linked to your programme. And everything downstream is based on estimation, not evidence.