Why Your Sub-Contractors Won't Update Your Project System (and What to Do Instead)
On most building and infrastructure projects, the main contractor sub-contracts a large share of the work: civil packages, MEP, finishing, labour supply. The main contractor stays answerable to the client for all of it. Under FIDIC's Red Book, for example, the contractor remains responsible for its sub-contractors' acts and defaults (Fenwick Elliott). But sub-contractors won't keep your DPR, tracker or project system up to date. So your site engineers do it, collecting updates over WhatsApp and calls all day and retyping them at night. More training or a stricter sub-contract clause won't fix this. Capturing updates from the channel sub-contractors already use will.
You're running four sites. The monthly review with the client is on Monday, and they want progress against the schedule, manpower deployed, and what's holding things up.
Your planning team opens the tracker, and half of it hasn't moved since Thursday. That's not because nothing happened. The shuttering sub-contractor finished the second-floor slab on Friday; you know because their supervisor sent a photo to the site WhatsApp group. Nobody entered it.
You Answer for Work You Don't Directly Control
Here's the structural problem.
On a typical project, the people doing the work mostly aren't on your payroll. They arrive through sub-contractors, and often through a further layer of labour contractors beneath them:
- India. Construction employs about 12% of India's workforce (PLFS 2023-24, via the Ministry of Labour & Employment). On large sites, crews usually arrive through chains of sub-contractors and labour contractors, a pattern documented in NIAS's 2025 study of contracting chains in Indian construction.
- UK. 37% of the construction workforce is self-employed (ONS data, via BCIS, Q2 2026). Many trades are engaged as sub-contractors and paid under the Construction Industry Scheme (CIS).
- Middle East. Main contractors routinely bring in specialist sub-contractors for MEP, façade and fit-out, and draw site labour from manpower supply companies.
The contract doesn't care how the work was sourced. Indian EPC contracts spell this out. One power-sector EPC contract's General Conditions say the employer's approval of a sub-contractor "shall not relieve the Contractor from any of its obligations." The same conditions require weekly progress reviews covering "manpower, tools and plants deployed by the contractor vis-a-vis agreed schedule," along with delays and hindrances.
So you're accountable for a weekly picture of work that's mostly reported by people who don't work for you.
Why a Sub-Contractor Won't Live in Your System
Put yourself in the sub-contractor's supervisor's shoes.
He's running crews on three of your sites and two of another contractor's. Each main contractor wants progress in a different format: one wants an Excel sheet by 6pm, another wants the portal updated, a third wants a signed daily report. That's five places to remember at the end of a day that ended when the light went.
None of those reports are for him. The value flows upward, to you, your client and the project management consultant. The effort flows downward, onto him.
So he does what works: he sends a photo and a line to the site group. "2nd floor slab casting done, deshuttering Monday." Thirty seconds, no login, from site.
That's not a discipline problem. It's a rational response to being asked to do data entry for someone else's reporting, five times over.
So Your Site Engineer Becomes the System
Because the sub-contractors won't enter the data, someone has to. Usually that's your site engineer or planning engineer.
Their day is a running stream of messages, calls and walk-around observations: photos from the shuttering crew, an MEP supervisor saying his team can't start until the front is handed over, a consultant confirming an inspection slot, the client asking why the finishing crew was short-staffed.
They can't record all of it as it happens, so they batch it. In the evening they reconstruct the day from their phone, scrolling the groups, remembering calls and typing it into the DPR or the tracker. On a bad day, with two fronts held up and one crew missing, the report slips, and tomorrow it's two days behind.
The tracker you review on Monday is only as current as the last catch-up. And the details that matter most later are the ones most likely to stay buried in the chat: the date a front wasn't handed over, or the drawing that hadn't arrived.
The Workarounds That Don't Fix It
Every main contractor tries some version of these:
Put it in the work order. "Sub-contractor shall submit daily progress in the prescribed format." It's in the document. In practice, nobody holds a sub-contractor's bill over a missing status line, and they know it.
Hire more planning or MIS staff. The report gets done, but the cost has just moved. Now you're paying someone to retype what's already in the site engineer's phone. It's still translated by hand, still a day late, and still filtered through one person's reading of the chat.
"Just send photos in the group." Now the day's record lives in a WhatsApp group with hundreds of messages. It's more accurate than the report, because it's the raw signal. But it isn't searchable or structured, and the client never sees it. When a dispute comes up months later about when a front was released, someone is scrolling.
An Excel sheet for open items. Commitments and snags end up in a separate tracker because the project system is too heavy for a quick "who owes me what." Now open items live in a third place that nobody reconciles against the schedule or the chat.
None of these close the gap. They all still need a person to move information from where the sub-contractors put it to where you need it.
What Actually Works: Read the Channel They Already Use
Sub-contractors already report. On most sites they do it in a WhatsApp group per project or per package, with short messages, photos and voice notes, because it costs them nothing. The data isn't missing. It's unstructured and stuck in your engineers' phones.
So capture it there.
Velora connects to the WhatsApp groups your sites already run on. It reads every message, photo and voice note, in English, Hindi, Arabic and other languages. It pulls out what each sub-contractor did, what's blocked, what they committed to and by when, along with manpower, deliveries and inspections, and structures it all by site, work front and sub-contractor. When something's missing, such as a crew that went quiet or a commitment with no follow-up, it asks that person directly in the same group and logs the answer. Hindrance and delay events are flagged for your team to review, with the original message attached.
For the sub-contractors, nothing changes. No app, no login, no new group. They message your site team exactly as they do now.
For you, the daily progress report drafts itself from what was actually said on every site. Slipped commitments show up on a dashboard instead of in an evening scroll. When the client asks, you have the answer and the timestamped message behind it.
Your site engineer stops being the integration layer and goes back to running the site.
What This Doesn't Replace
Velora doesn't replace your ERP, your Primavera or MS Project schedule, or a platform like Procore. It doesn't do scheduling, estimating, procurement or document control, and it isn't trying to.
It's the field-signal layer: the daily, on-the-ground record of progress, blockers, commitments, manpower and deliveries, captured from the channel sub-contractors actually use. Your system of record no longer depends on whatever your site engineer had time to type in last night.
For a side-by-side breakdown, see Velora vs Procore.
Frequently asked questions
- Why won't sub-contractors update the main contractor's project system?
- Because they don't work for the main contractor. A sub-contractor's supervisor is often running crews for several main contractors at once, each asking for progress in a different format, and the report benefits the main contractor and the client, not them. So they report the fastest way possible instead: a WhatsApp message or photo to the site team.
- Is the main contractor responsible for sub-contractors' progress and defaults?
- Generally, yes. Under FIDIC's Red Book, the contractor remains responsible to the employer for its sub-contractors' acts and defaults, and Indian EPC conditions of contract commonly state that approving a sub-contractor does not relieve the contractor of its obligations. The main contractor is accountable for progress, manpower and delays on work it sub-contracted.
- How do I get daily progress from sub-contractors without chasing every one of them?
- Capture updates from the channel they already use. Velora connects to the WhatsApp groups your sites run on and extracts what each sub-contractor did, what is blocked, what they committed to, and manpower on site, structured by site, work front and sub-contractor. The daily progress report drafts itself instead of a site engineer reconstructing it each evening.
- Does putting a reporting requirement in the sub-contract or work order work?
- Rarely on its own. The clause is common, but main contractors seldom hold a sub-contractor's bill over a missing status update, and sub-contractors know it. Reliable reporting comes from removing the data-entry step, not from adding another obligation.
- Does Velora replace Procore, an ERP or our scheduling software?
- No. Velora does not do scheduling, estimating, procurement or document control. It is the field-signal layer: the daily record of progress, blockers, commitments, manpower and deliveries, captured from the WhatsApp groups your sub-contractors already use, alongside the systems you already run.
See What Your Groups Already Contain
Your sub-contractors are already telling you what happened on every site. It's in your site engineers' phones.
- 👉 Explore Velora: see how updates, commitments and blockers are extracted and structured by AI, for your team to review.
- 👉 Try the free DPR Generator: one project, runs on your Windows machine, data stays local, free forever.