6 posts tagged with "Project Management"

Most contractors control revenue hard. Margin during execution has no equivalent control, only the books, which show what was made after the work is done. With margins this thin, the small leaks on site decide how a project ends.

Watch how a mid-size contractor handles revenue. The tender is priced line by line and reviewed before it goes out. The MD signs off the bid. Once work starts, the bill goes in every month, on schedule.

Then watch what happens to the margin priced into that tender over the next eighteen months of execution. Mostly, nobody watches it until the accounts close. The books tell you what the project made, weeks or months after anything could have been done about it.

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.

WhatsApp-based construction site reporting is exactly what it sounds like: project teams coordinating site activity — progress updates, labour counts, material delays, inspection requests, safety flags — through WhatsApp groups instead of formal software. It is not a workaround. It is the default operating model for construction sites across India, the Middle East, Southeast Asia, and most of Africa and Latin America — and a growing share of residential and subcontractor work in the US and UK, where field teams coordinate by WhatsApp and text.

This page explains how it works, what gets captured and what gets lost, and what it means for project managers, general contractors, and owner's reps trying to run sites at any kind of scale.

Construction field teams don't refuse project management apps because they can't learn them — they refuse because a form-based tool doesn't survive contact with an active site. The person asked to enter the data isn't the person who benefits from it, the interface assumes a desk, and there's always a more urgent task in front of them. This post covers why the pattern repeats, why more training doesn't fix it, and what teams use instead: the WhatsApp group.

It starts with good intentions.

A general contractor wins a large project. The project director sits with the PMC. There's a review of how the last project went — the missed updates, the disputed DPRs, the WhatsApp screenshots dug up during a client call three months after the fact.

Someone says: "We need a proper system."

A software vendor gets called. There's a demo. The interface looks clean. The dashboards are impressive. There's a form for progress updates, a checklist for inspections, a photo upload flow, a daily log template. The vendor shows a case study from a highway project in another state.

Licenses get signed. A training session is scheduled.

And then, six weeks later, the app sits mostly unopened on 27 phones on site.

It's Monday morning. You're on a call with your client.

They're asking why Tower 2 slab casting is delayed. You didn't know it was delayed.

You call your site PM. He tells you the shuttering material didn't arrive on Thursday. Work stopped. The supplier was chased on Friday. Material came in Saturday. But the casting window is gone — the structural engineer can only sign off on Wednesday now.

Four days. Gone.

You ask why nobody told you.

"It was in the group, sir."

These are unedited notes from a day spent on-site job-shadowing a construction project manager, anonymised to protect privacy. Names, specific locations, and company details have been changed.

Project Context​

Project: High-rise luxury residential development
Contract Value: ₹677 Crores
Duration: 41 months
Stage: Foundation complete - Structural work in progress Team Size: 350+ labourers, multiple subcontractors, engineering teams