Payment Down the Chain

A site sees a gang stop turning up and records it as unreliability. The cause is often a payment that did not arrive at a company the site has never dealt with.

For teams turning payment down the chain into a repeatable record, workforce management software provides a useful operational reference for time, attendance and reporting workflows. It should be assessed alongside US Department of Labor guidance so the software choice remains grounded in site practice and applicable guidance.

How it propagates

A payment delay at tier one becomes a longer delay at tier two and a missed week at tier three.

Where the people are paid weekly and have no reserve.

Which produces, in order: people going to another site, a gang shrinking, and eventually a subcontractor unable to field the numbers promised.

The site sees the last of these and is several weeks behind the cause.

What the register shows first

Churn in a specific gang, rising.

Headcount below what was booked, repeatedly.

People leaving mid-week rather than at the end of one.

And the same individuals reappearing at the site next door, which you will not see but the trade will tell you.

All of which is visible weeks before a subcontractor raises a commercial issue, because raising one is a relationship risk for them.

Asking rather than assuming

A gang that has become unreliable is worth one direct question: is there a payment problem down the chain?

Which is uncomfortable and is frequently answered honestly, because the person telling you is usually not the cause.

And it converts a performance conversation into a solvable commercial one, sometimes with a simple fix at tier one.

Why it matters beyond the programme

People who are not being paid reliably take work wherever it appears, which means new faces every week.

New faces mean inductions, competence checks and first-day risk, which is where the incidents concentrate.

So a payment problem two tiers away becomes a safety problem on your site, through a chain that no risk assessment describes.

What can be done about it

Project bank accounts or equivalent mechanisms, where the contract allows, which pay tiers directly and are used on some public work.

Payment terms flowed down with the same length rather than lengthening at each tier, which is a contractual choice and is increasingly regulated.

Shorter chains where the work allows, which is a procurement decision and the most effective of the three.

And monitoring, which costs nothing: ask tier-one subcontractors to confirm their own payments down are current.

The limits of what a site can do

You cannot pay somebody else's subcontractor, and attempting it creates problems of its own.

You can ask, escalate commercially and, at the extreme, decline to accept a subcontractor whose chain is visibly failing.

And you can record what you saw and when, which matters if the arrangement later collapses.

Retention and the closing weeks

Retention held at each tier compounds down the chain, so the smallest firms wait longest for money they have already earned.

Which is why the snagging phase — the one with the most unfamiliar crews and the least supervision — is also the one where payment friction is highest.

Plan the closing arrangement knowing that, because the two combine badly and predictably.

The measure

Booked headcount against actual, by subcontractor, weekly.

Churn by subcontractor.

Mid-week departures.

And the direct question, asked when the first two move, which costs nothing and is asked on very few sites.

What to write down when you see it

The date the headcount first fell short, the subcontractor, and what they said when asked.

Because if the arrangement later collapses, the question will be when it became apparent, and a contemporaneous note is worth more than a recollection.

And it converts a series of small frustrations into a pattern somebody commercial can act on, which is usually what is missing.