One phone, four work-fronts: how a site engineer stopped drowning in WhatsApp groups

Meet Karthik. He's a site engineer on a residential project in Hosur — two towers, a clubhouse and a boundary wall going up at the same time, four work-fronts he walks between all day in a helmet with a phone in his hand. He is good at the actual engineering. What was quietly breaking him was everything around it: being the human bridge between the site, the office and a dozen chat groups that never agreed with each other.

This is an illustrative story — a composite of the site engineers we hear from most — about the week his phone stopped being a switchboard and started being a system of record.

A day spent being the message router

Here is how Karthik's day used to go, and if you've worked a site you'll wince. The drawings were in one WhatsApp group — the latest revision buried somewhere above a hundred “ok sir” messages and a forwarded reel. Material requests went to a second group, where he'd type “need 40 bags cement tower B tomorrow” and hope the store saw it before he lost signal near the lift core. The daily progress photos went to a third group, the client-facing one to a fourth, and the safety updates to a fifth that the safety officer had muted. When the architect had a query about a beam, it came as a voice note he had to replay four times standing under a slab.

None of it was joined up. A material request he sent on Monday and a bag count the store issued on Wednesday lived in different groups with no thread between them. When the PM asked “did the steel for the clubhouse footing come or not?” the honest answer was “let me scroll and find out.” Karthik wasn't running four work-fronts. He was running twelve chat windows that happened to be about four work-fronts.

“The engineering was never the hard part,” he says in this telling. “The hard part was that every fact about my own site lived in someone else's phone.”

One system of record, in his pocket

His firm moved the project onto Rebaar, and the change for Karthik wasn't a new app to learn so much as a place for things to land. Everything he used to route by hand now had one home, tied to the project and the work-front it belonged to:

• Drawings and documents — the current revision in one place, not the seventh forward of final_FINAL_v3.pdf. He opens the beam detail on his phone under the slab instead of replaying a voice note.
• Material indents — he raises a request against the work-front (“clubhouse footing: 1.2 t of 12mm TMT”), it goes for approval, and when the store issues it, the same record shows issued-versus-requested. No re-typing into a chat, no wondering whether it was seen.
• Daily logs — the day's progress, headcount and a couple of geo-tagged photos, filed once from the site and visible to the office the same evening. The photo carries a date and a location, so it's a record, not a rumour.
• RFIs — the beam query to the architect becomes a tracked question with a number, a status and an answer attached to the drawing, instead of a voice note that dies in a group.

The point wasn't that any one of these was fancy. It was that they were the samerecord the PM, the store and the accountant were looking at. When Karthik marked the footing steel as received, nobody had to ask him again.

Built for a site with two bars of signal

The objection every site engineer raises is fair: “my site has no network past the second basement.” A tool that needs four bars to log a pour is a tool you stop using by Thursday. The things Karthik does most — logging progress, raising an indent, snapping a photo — are quick, forgiving actions he can fire off in the gaps where the signal comes back, not a desktop form that punishes him for being on a real site. The record catches up; he doesn't have to babysit it.

What actually changed for him

Karthik didn't get fewer responsibilities. He got fewer places to look. The four work-fronts were still four work-fronts, but the question “what's the status?” had one answer instead of five, and it wasn't his memory. He stopped being the single point of failure between the site and the office — which, not coincidentally, is what makes a site engineer promotable instead of merely indispensable.

If your site still runs on a fistful of WhatsApp groups and a diary, that's the norm, not a failing — but it caps how many fronts one good engineer can actually hold. Here's the construction ERP overview and the full feature tour, if you want to see where the groups go.