How to manage site team commitments on WhatsApp

If you're a contractor, whether you build homes, commercial buildings, industrial plants or infrastructure, you probably manage much of the work on your sites from your phone. Supervisors, subcontractors and suppliers report in WhatsApp groups, and most decisions come back to you. Commitments slip, not because people are careless, but because a promise typed once in a busy group has no owner anyone checks, no date anyone tracks, and nobody closing the loop. This guide covers how to fix that by hand, and then where AI can take over the chasing.

Why commitments slip on WhatsApp-run sites

Whatever the project type, most contractors will recognise the pattern:

• Decisions run through one person. A supervisor asks, the owner or project manager answers, somewhere between a client meeting and a site visit. When that person is busy, the site waits.
• Updates are spread across groups. One for the site team, one per subcontractor or trade, one for materials, often one with the client. A single project can easily have several groups, each moving fast.
• Commitments look like chatter. "Tiles will reach Thursday." "Shuttering done by Saturday." Each one is typed once, scrolls away within the hour, and is only remembered when it's missed.
• Nobody closes the loop. Saturday comes and goes. Unless someone asks "was the shuttering done?", there's no record either way.

This isn't a small cost. In a 2018 survey of 600 US construction professionals, PlanGrid and FMI found that poor communication caused 26% of rework, and poor project information another 22% (Construction Dive). The numbers are from the US, but anyone who has chased a contractor through four WhatsApp groups knows the problem travels.

Set up your groups so every update has a home

• One group per subcontractor and per supplier, plus the core groups. For example: Tower B · Site team, Tower B · Shuttering (Ramesh), Tower B · Electrical (Sharma Electricals), Tower B · Cement (Gupta Traders), Tower B · Client. Keeping conversations with different subcontractors and suppliers separate reduces confusion: each one's commitments, photos and queries stay in one place, and nobody acts on a message meant for someone else. Keep the client in their own group too, so internal back-and-forth stays internal.
• Use the same naming pattern on every project. Project name first, purpose second. Anyone, including a new supervisor, knows where to post.
• Keep members to the people who act. You and whoever runs projects for you (a GM Projects or project manager) sit in every group. Everyone else joins only the groups where they have work to do. Make the two of you the admins.
• Use events for fixed dates. WhatsApp lets you create events in a group and track RSVPs (WhatsApp). Use them for a client walkthrough, a concrete pour or an inspection, so the date isn't just another message.

Make every commitment trackable

Construction already has a well-tested method for this. The Last Planner System, from the Lean Construction Institute, calls weekly planning "commitment planning". It asks that the work promised is only what the people doing it say they can and will do, and it tracks promises kept so the team can learn from the ones that slip (Lean Construction Institute). You don't need to adopt the full system to borrow its core ideas.

1. Give every commitment four parts: who, what, where and by when. "Shuttering soon" is not a commitment. This is:

Who:   Ramesh (shuttering subcontractor)
What:  First-floor slab shuttering
Where: Tower B, grid C–F
By:    Saturday, 5 pm

2. Let the person doing the work make the promise. A date you set without asking is a hope. A date the subcontractor gives, after checking material and labour, is a commitment they own.

3. Restate it in the group as one line. When a commitment comes up in a voice note or a long thread, the supervisor (or you) posts it back in the four-part format. That one line is what everyone checks against.

4. Close the loop on the due date. Done, or not done with a reason:

Tower B – first-floor shuttering: NOT DONE
Reason: plywood delivery came a day late. New date: Monday, 12 pm

5. Look at the reasons once a week. If the same reason keeps coming up (material arriving late, labour short, a drawing not issued), that's the problem to fix, not the subcontractor's memory. A simple weekly count of promised versus kept tells you which sites and subcontractors you can rely on.

A daily rhythm that doesn't depend on you asking

Accountability is much easier when updates arrive without being chased. A light routine is enough:

• Morning: each supervisor posts who is on site and the plan for the day. A voice note in Hindi or any other language is fine. What matters is that it's posted.
• Through the day: photos with a one-line caption saying where and what, such as "Tower B, first floor, slab shuttering about 70% done". A photo without a caption is hard to use a week later.
• Evening: a short end-of-day update in the same format every day.

Tower B – end of day, 24 Oct
Done:     ground-floor plastering, east wall
Blocked:  first-floor shuttering (plywood late)
Tomorrow: steel binding on the first-floor slab, needs 6 bar benders

The weekly client report

Whether your client is a homeowner, a developer, a PMC or a government department, they want to see progress regularly and clearly, without having to ask. A good weekly report answers four questions:

1. What got done this week? Progress by area or floor, with photos.
2. What's planned next week?
3. What do we need from you? Decisions and approvals with a date: a drawing revision by Wednesday, a material approval by Friday.
4. Is anything affecting the timeline? Said plainly, with what you're doing about it.

A simple structure that works:

Tower B – weekly progress report, week ending 25 Oct

Summary:            two or three lines on the week
Work completed:     one line per item, each with a captioned photo
Plan for next week: one line per planned item
Decisions needed:   item, options, decide by
Timeline:           on track / at risk, and why

The slow part is rarely the writing. It's scrolling back through several groups to find the right photos, working out what each one shows, and captioning it.

Doing all of this by hand

Everything above works without any software, and it's worth doing even if you never use a tool. Be honest about the cost, though: it depends on one person, usually you or whoever runs projects for you, reading every group, restating every commitment, chasing every due date and compiling every report. It holds up with one or two sites. It starts to break when you add a third project, travel for a week, or the person doing it leaves.

Where AI helps

This is the part Velora takes over. Your team keeps posting in the same WhatsApp groups. Nobody installs anything.

• Picks up commitments from messages and voice notes. Velora reads the groups, including voice notes and photos, in Hindi, Telugu, English and other languages, and lists commitments as action items with an owner and a deadline. Every item links back to the message it came from, and your team reviews them.
• Follows up in the group when something is overdue. Follow-ups go back into the WhatsApp group, and they're held outside your site's working hours, then sent when the shift starts.
• Shows you what's overdue across every project. The portfolio view lists actions overdue by more than three days, per project. Each morning, a single WhatsApp message ranks what needs attention across all your sites; reply to it to ask for detail or send a reminder.
• Drafts the weekly client report. Velora drafts the report from the week's site record: an executive summary, key accomplishments with their photos, and the plan for next period, in Word and PDF. You review it, remove a photo or change a line, and send it.

	By hand	With Velora
Spotting commitments	You read every group	Picked up from messages and voice notes, for your team to review
Chasing what's overdue	You remember, then message	Follow-ups posted in the group, within site working hours
Seeing every site at once	In your head, or an Excel sheet	Portfolio view and a morning WhatsApp summary
Weekly client report	Collect photos, caption them, write	A draft from the site record; you review and send

Frequently asked questions

How do I hold my site team accountable when we work on WhatsApp?

Make every commitment specific (who, what, where and by when), let the person doing the work give the date, restate it in the group as one line, and close the loop on the due date with done or not done and a reason. Reviewing the reasons each week shows you what to fix. Velora can pick up the commitments from your groups and follow up when they fall due.

How many WhatsApp groups should one construction site have?

Most contractors run a site team group, a separate group for each subcontractor and each supplier, and a separate client group. Keeping those conversations apart reduces confusion, since each party's commitments and photos stay in one place. Use the same naming pattern on every project, keep members to the people who act, and make the owner and whoever runs projects the admins.

What should a weekly progress report to the client include?

What got done this week with photos, what is planned next week, any decisions needed from the client with a date, and anything affecting the timeline, said plainly. A short summary at the top helps clients who only read the first few lines.

Can AI understand site voice notes in Hindi?

Velora reads voice notes as well as text and photos, in Hindi, Telugu, English and other languages, and turns them into structured updates and action items. Your team keeps sending voice notes the way they already do.

Does my site team need to install a new app?

No. Velora works from the WhatsApp groups your team already uses. They keep posting updates, photos and voice notes as before; follow-ups come back into the same groups.