How to keep track of subcontractors without chasing them on WhatsApp
Subcontractor control is the set of mechanisms that let you know, without asking, what each trade built, with what resources and to what quality. When that mechanism does not exist, the site engineer ends up chasing information by phone, and the project finds out about problems only once they are visible.
On a mid-sized project, between 50 and 80 % of the work is executed by third parties. Which means most of your project is built by people who are not on your payroll, who answer to a different boss and who have different incentives. And yet control over them is usually the least designed process in the whole operation.
Why follow-up fails
It is not for lack of nagging. It is four design problems.
Nobody agreed what to report. The contract defines scope, price and duration, but rarely defines what information the subcontractor must hand over, in what format and how often. Without that clause, asking for a report is a favour, not an obligation.
The incentive runs the other way. A subcontractor who reports precisely reveals their own delays. One who reports vaguely protects themselves. If nothing depends on reporting well, vagueness is the rational strategy.
There is no common channel. Everyone sends it however they like: one on WhatsApp, another by email, another mentions it to the foreman in passing. The information exists but it is scattered, and consolidating it is manual work for the site engineer.
Follow-up is reactive. You ask once something already looks wrong. By then the information arrives late and biased, because the subcontractor already knows they are in trouble and will soften it.
The five minimum data points
Do not ask for long reports. Nobody fills them in properly. Ask for few data points and require them every day.
| Data point | Why it matters |
|---|---|
| Workers on site, by trade | The earliest predictor of delay. If headcount dropped, progress will drop within three days |
| Quantity built, in the contract unit | It is what you will pay for and what feeds your schedule |
| Work faces they worked on | Lets you verify and spot spreading |
| Constraints that stopped them | It is what you can actually fix, and what prevents later claims |
| Plan for the next two days | Lets you release faces and anticipate clashes |
The first is the most underrated. Attendance is a leading indicator; progress is a lagging one. When progress falls, the problem happened days ago. When the crew drops from twelve people to seven, the problem is happening today and you can still act.
How to structure it
Put it in the contract. A short clause setting out the obligation to report the five data points daily, the channel, the cut-off time, and making the payment process conditional on being up to date with reports. That last part is what makes it work: the incentive has to sit where the money is.
One channel for everyone. Do not negotiate the channel subcontractor by subcontractor. One channel, the same for all, and one they already use. WhatsApp works because nobody has to learn anything or install anything.
A fixed cut-off time. A report arriving at eleven at night is no use for deciding anything the next day. Set a time — the end of the working day — and treat it as part of the deliverable.
Verify by sampling, not exhaustively. You cannot verify everything they report and you do not need to. Check one random line item per subcontractor per week. It is the existence of the sampling that keeps report quality up, not its completeness.
Progressive sign-off on quantities. Get the quantities they report signed off weekly rather than at month end. It avoids the monthly negotiation over work that is no longer visible, which is where most disputes come from.
The warning signs
Three patterns that show up before the delay is obvious.
A sustained drop in headcount. Two or three days of reduction with no explanation usually means the subcontractor moved people to another project, almost always because it pays better or faster. It is the number one cause of trade delays and the attendance figure catches it.
Reports that turn vague. When someone who used to report specific quantities starts reporting “still progressing on the same face”, they are almost always covering something up.
Progress spread across many faces. A subcontractor who opens five faces and closes none is usually managing the perception of progress instead of producing it. Closing faces is what can be invoiced; opening them only looks good.
What to do when they fall behind
In order, documenting every step.
Check the cause is not yours. Face not released, client-supplied material that never arrived, technical information outstanding. If the cause is yours, demanding progress is not just useless — it weakens your position if there is a claim later.
Put it on the record formally. An entry in the site record, dated, describing the delay and the instruction given. Without this, any later action — retention, substitution, penalty — has nothing to stand on.
Ask for a written recovery plan. With concrete resources and dates. This is almost always the point where you find out whether the problem is capacity or priority.
Escalate only if the plan fails. Payment retention, reinforcement with another crew at their cost, or substitution, depending on what the contract allows. Each of these steps needs documentary support, and that support had to be built beforehand.
Frequently asked questions
- Can I require daily reports if the contract does not mention them?
- You can ask for them, but with no contractual basis you are relying on goodwill. If the contract is already signed, the practical route is to agree it in writing as a site procedure and tie it to the payment process through a signed minute.
- What do I do about a subcontractor who never reports?
- Record the failure in writing, every time. It is objective evidence that supports later decisions and it also tells you whether to hire them again. Plenty of contractors find out too late that their worst subcontractor is one they have been using for five years, because nobody kept the record.
- Should I track attendance of subcontracted labour?
- Yes, as a progress indicator. Be careful with the scope: in several countries recording and directing someone else's workers can carry employment implications around subordination. Check the legal framework where you operate and limit the record to what site control actually needs.
- How many subcontractors can one site engineer coordinate?
- It depends more on the information mechanism than on the number. With a structured daily report, eight or ten are manageable. Chasing information by phone, three already saturate.
- Is it better to have one large subcontractor or several small ones?
- One large one simplifies coordination and concentrates risk. Several small ones spread the risk and multiply the coordination. The call depends on how good your control mechanism is: if it is weak, concentrate; if it is solid, diversifying works out cheaper.
Chilean, designing for Latin America. Field research surfaces what actually matters to clients, and that becomes products non-technical people adopt on their own — legal, education, accounting — and that show up in productivity from week one.
See all their articles →
