You can't build it all yourself, and the subcontractors you rely on are the ones most likely to sink your programme. Here's how to run packages so they deliver.
On most jobs, you're not really a builder. You're a manager of other builders. The main contractor who self-delivers everything is rare — the reality is that 80% or more of the value on a typical project is built by subcontractors, and your job is to get all of them to the right place, at the right time, doing the right thing, without standing over each one.
That's the tension. The subcontractors you depend on to deliver are also the single biggest source of programme risk on your job. A good package manager makes it look effortless. A bad one spends every day firefighting — chasing labour that didn't turn up, resolving clashes that should never have happened, and paying twice for work that was done wrong the first time.
The difference isn't luck, and it isn't about micromanaging. It's about setting each package up so it can't easily go wrong, then managing by exception. Here's how.
Most subcontractor problems are baked in before the first operative arrives. If you get the front end right, the management gets easy. Get it wrong and no amount of chasing on site will save you.
Buy the right firm, not the cheapest number. This is where it begins. The lowest quote that's missing half the scope isn't cheap — it's the most expensive thing on the job once the extras start. Compare like for like, understand what each price includes and excludes, and weight capability and reliability alongside price. Our guide on subcontractor bid comparison covers this properly.
Define the scope so there's no grey area. The biggest cause of subcontractor disputes is scope ambiguity — the bit of work that each party assumed the other was pricing. Nail down exactly what's in the package, what isn't, what attendances you're providing, and where the interfaces with other trades sit. Every gap you leave is a variation, a delay, or an argument waiting to happen.
Hold a proper pre-start meeting. Before they mobilise, get them in and walk through the programme, the scope, the interfaces, the information they need and when, the site rules, and how you'll manage payment and variations. An hour here saves days later. It also sets the tone: this is a managed job, not a free-for-all.
A subcontractor working to their own idea of the sequence is a subcontractor about to clash with the trade in front of and behind them. The programme is how you prevent that, but only if it's actually used as a management tool rather than a document that sits in a drawer.
That means each package knows its start, its duration, its dependencies, and — critically — what has to be finished before they can begin. The M&E first fix can't start until the partitions are up. The decorator can't start until the M&E second fix is done and tested. When one package slips, you need to see immediately which packages downstream are affected, so you can act rather than discover the pile-up a fortnight later.
The best package managers are always looking two or three weeks ahead, not at today. Today looks after itself. It's the interface three weeks out — the drawing that isn't approved, the material with a six-week lead time nobody ordered, the trade that's going to arrive to find its predecessor hasn't finished — that sinks programmes.
Subcontractors can't build what they can't see, and a huge amount of delay is nothing to do with labour or productivity — it's information starvation. The drawing that's still in revision, the RFI that's sat unanswered for a fortnight, the submittal stuck in the architect's inbox — each one stops a subcontractor from working, and each one is your responsibility to unblock.
Managing information flow is half of managing subcontractors. Know what each package needs, when they need it, and chase it before it becomes critical — not after they've downed tools and put you on notice for a delay claim. The subcontractor who's been kept supplied with information has no excuse for slipping. The one who's been left waiting has a legitimate one, and they'll use it.
Once they're working, the goal is to manage by exception — to know quickly when a package is drifting, and to intervene early, without hovering over every operative.
Here's something the hard-nosed approach misses: paying subcontractors fairly and on time is one of the most powerful management levers you have. The good subcontractors — the ones you want back — have a choice of who they work for, and they remember who paid them straight and who messed them about. A reputation as a fair, prompt payer gets you the best gangs, priority when they're busy, and goodwill when you need a favour on programme.
That doesn't mean paying for work not done or waving through inflated applications. It means assessing applications properly, certifying what's genuinely earned, issuing your notices on time, and paying when you said you would. Squeeze subcontractors on payment and you'll win the odd battle and lose the war — the good ones stop pricing your work, and you're left with the firms nobody else wants.
At Construction AI, a subcontractor package lives in one place — scope, programme, drawings, RFIs, submittals, variations, applications and snags all tied to that subcontractor, on a platform they can be invited into to submit their own applications and receive their instructions. You see the whole package at a glance: where they are against programme, what information they're waiting on, what's agreed commercially, and what's outstanding. Managing by exception is only possible when you can see the exceptions — and that's the point.
You can't build it all yourself, and you can't stand over every trade. But you can set each package up so it's hard to go wrong, keep it fed with information, watch the interfaces ahead of you, and pay the good firms straight so they keep coming back. Do that and you're managing a job — not babysitting one.
How do you manage subcontractors effectively on a construction project?
Set each package up well before mobilisation (right firm, clear scope, proper pre-start meeting), integrate them into the programme with defined dependencies, keep information flowing (drawings, RFIs, submittals), manage progress and quality by exception, and pay fairly and on time.
What's the biggest cause of subcontractor disputes?
Scope ambiguity — the area of work each party assumed the other was pricing. Defining exactly what's in and out of each package, including attendances and interfaces, prevents most disputes before they start.
How far ahead should a package manager be looking?
Two to three weeks. Today's work looks after itself; the risks are in the upcoming interfaces — unapproved drawings, long-lead materials not yet ordered, and trades about to arrive before their predecessor has finished.
Why does paying subcontractors on time matter for management?
Good subcontractors choose who they work for. A reputation as a fair, prompt payer secures the best gangs, priority when they're busy, and goodwill on programme. Squeezing payment loses the firms you most want to keep.
How do you stop snagging piling up at the end of a job?
Deal with quality as it happens — inspect and reject defective work while the gang is still on site, rather than letting hundreds of items accumulate for close-out when the labour has moved on.
Stephen Mckenna MCIOB
30+ years in UK commercial construction, from site management to director level. Now building the project management tools he wished he'd had.
Tier-one contractor processes shouldn't only be available to tier-one contractors. Drawing registers, document control, RFIs, programmes, financial tracking — built for how you actually run projects, priced so any construction business can access them. Try everything free for 30 days.
By subscribing, you agree to our Privacy Policy.
Practical completion isn't the finish line — the O&M manual and handover pack are. Get them wrong and your retention sits there while the client waits on paperwork.
The wrong drawing revision cost a six-figure rework bill. Here's how to set up construction document management — from naming conventions to digital control.
A submittal stuck in an architect's inbox for three weeks is a programme delay. Here's how to manage submittals so approvals don't hold up your project.
Tier-one processes, priced for any size business. Try everything free for 30 days — no charge until your trial ends.