A groundworks gang arrives on a Monday with four operatives. Two hold cards that expired in July. Nobody caught it, because the induction pack went to a foreman who left the business in June and his mailbox closed the week after. The pour goes ahead anyway. The concrete is already on the road.
Subcontractor management software is the system a main contractor uses to hold its supply chain in one place: who is approved to work, what each firm has been engaged to do, what they are owed, and whether their paperwork is still valid on the day somebody stands on the site. Most products in the category handle the first three competently. The fourth is where they come apart, and they come apart at the same joint every time. That joint is the handover between the office that appointed the subcontractor and the site that has to work alongside them.
What does subcontractor management software cover?
Five functions, bundled differently by every vendor. Prequalification decides who is allowed to bid and work at all. Engagement turns an approved firm into a specific order with a scope, a rate and a slot in the programme. Compliance tracks insurance, accreditations, competence records and method statements against their expiry dates. Commercial handles applications, valuations, notices and retention. Performance, in theory, records how each firm behaved once they were on site.
Buy anything in this space and you will get some mix of those. The trap is assuming that a strong compliance module means the compliance problem is dealt with. It tracks whether a document exists and when it runs out. It has no idea whether the document describes the work happening this week.
| Function | What it holds | Where it usually lives instead |
|---|---|---|
| Prequalification | Approved supplier list, accreditations, financial checks | A spreadsheet owned by one person in procurement |
| Engagement | Orders, scopes, rates, programme dates | Email threads, plus the accounts package |
| Compliance | Insurance, competence records, RAMS, training matrices | A shared drive folder per project, and paper in the cabin |
| Commercial | Applications, valuations, payment and pay less notices, retention | The quantity surveyor’s own spreadsheet |
| Performance | Defects, delays and safety observations attributed to a firm | Nowhere |
The last row is the one worth staring at. Ask a contractor which of its subcontractors cost it the most money last year and you will get a confident answer within about four seconds. Ask for the evidence and the room goes quiet. Everybody knows. Nobody can show it, because delay attribution lives in the site diary, defect cost lives in the final account, and neither is joined to the supplier record that procurement uses when it renews the framework.
Why the handover is the weak joint
Take the scaffold contractor. Their method statement was written for a four-week erection programme, approved by the office, filed, and marked compliant. Then the steel deliveries slipped nine days and the sequence changed. The scaffold is now going up in a different order, around a live loading bay, on a slab that has not been backfilled. The RAMS on file describes something that is no longer happening. Every dashboard in the business still shows green, because the document has not expired and nobody re-issued it.
Nobody has been sloppy here. The failure is designed in. The software models a subcontractor as a record with attachments. Site experiences a subcontractor as a set of people, doing a particular sequence, under conditions that change weekly. A record with attachments cannot tell you when those two have drifted apart.
The commercial side drifts the same way. An application lands on the 28th. Valuation is due on the 5th. The quantity surveyor spends that week on a different job, the pay less notice window closes, and a sum nobody agreed becomes a sum nobody can dispute. Software will remind you the date is coming. It cannot make the valuation happen.
What should you look for if you are buying?
Start with the question of where the truth lives. If the site team cannot see and change the same record the office sees, what you have bought is a reporting layer. Two copies of a supplier record will diverge, every time, on every job.
Then ask what happens when a document is superseded rather than expired. A system that only understands expiry dates will let a stale method statement sit there for months looking healthy. You want re-approval triggered by a change in scope or sequence, not just by the calendar.
Ask whether the tool can attribute anything. If a delay or a defect cannot be tied back to the firm that caused it, and carried forward into the next prequalification round, the performance data is decorative.
Finally, look at what it demands from the subcontractor. A four-operative bricklaying firm will not maintain a portal. If your compliance depends on them logging in, your compliance depends on something that will not happen. The systems that hold up are the ones where the main contractor’s own team can update a record from a phone on site in under a minute, and where a chase goes out by whatever channel the subbie already reads.
Where does AI change this?
Not in the dashboard. The useful work is further down, in the reading and cross-checking that nobody has time for.
A subcontract order, a method statement and the current programme can be read together and compared. When the sequence in the RAMS no longer matches the sequence in the programme, that is a machine-detectable mismatch, and it is exactly the mismatch that the scaffold example turns on. The same applies to insurance limits against contract requirements, and to a bespoke amended subcontract against your standard position. These are all document comparison problems, and document comparison is the thing language models are reliably good at.
What they are not good at is judgement about a supplier relationship. Whether to keep working with a firm that is slow but safe, on a job where safety is the binding constraint, is a decision with a business behind it. Treat the output as a flag for a human to look at, and the flags earn their place. Treat it as an approval and you have automated the thing that used to be somebody’s job to think about.
Common questions
Is subcontractor management software different from construction project management software?
Yes, though the categories overlap and several vendors sell both under one name. Project management software organises the work. Subcontractor management organises the firms doing it. Most contractors end up with both, which is fine as long as the supplier record exists once. See our note on construction project management software for where the boundary usually sits.
Do we need it if we only use three or four regular subcontractors?
Probably not as a purchase. At that size your exposure is concentration. What you need is a current record of insurance and competence for those firms, and a way to notice when a scope changes. A well-kept shared sheet does that. Buy software when the number of live orders exceeds what one person can hold in their head, which for most contractors happens somewhere around twenty.
Who owns subcontractor compliance under CDM 2015?
The principal contractor carries the duty to ensure subcontractors are competent and properly briefed, and to co-ordinate their work safely. The duty does not transfer to a software vendor. Our guides to the CDM Regulations 2015 and the principal contractor role set out what that involves.
How does this work for demolition packages?
Demolition sits awkwardly in most supply chain tools, because the compliance set is heavier than the rest of the trade: asbestos licences, notifications, permits, and a method statement that changes as the structure comes down. If demolition is a large share of your subcontract spend, check that the tool can hold trade-specific document sets rather than one generic checklist. We work on this directly with demolition contractors.
What about payment notices?
Software helps with the dates and nothing else. Missing a pay less notice is a diary failure with a contractual price attached, so any tool you buy should push the deadline at a named person rather than displaying it on a screen that person does not open. The related margin leak is covered in our piece on variation orders.
The part worth fixing first
Before choosing a product, walk one live subcontract package from award to the cabin and write down every place the information stops. Most contractors find three or four. Two of them will be a person forwarding an email. Fix those and a good deal of the case for new software evaporates, which is a useful thing to discover before you sign a three-year term.
If you want a second pair of eyes on where your supply chain data breaks down, book a discovery call.