What running your sites on group chat actually costs
Group chats are fast, free and lossy. A practical look at which site information belongs in a chat, which belongs in a record, and how to move the second kind without a fight.
Every construction firm has the group. Photos, delays, a truck at the gate, a question about a level, someone forwarding a voice note at 11pm. It works, which is precisely why it becomes the system of record by accident.
The problem shows up later, in three specific places: payroll, client disputes, and the moment somebody leaves the company with the phone.
The test: coordination or evidence?
Ask one question about any message: will anyone need to find this again in six months?
| Message | Type | Belongs in |
|---|---|---|
| "Concrete truck delayed to 3pm" | Coordination | Chat. It expires today. |
| "18 masons on site today" | Evidence | Attendance record. It becomes payroll. |
| "Slab done, see photos" | Evidence | Progress against a BOQ line, with the photos attached. |
| "Client asked to move the doorway" | Evidence | A dated variation, before anyone builds it. |
| "Who has the keys?" | Coordination | Chat, obviously. |
The three failures you are paying for
1. Payroll built from scrollback
Attendance sent as a daily photo of a paper register cannot be totalled. Someone retypes it at month end, which means a transcription error is a payroll error, and a missing day is an argument with a worker you need on site tomorrow.
2. Progress claims you cannot substantiate
When a client queries a valuation, you need the date, the quantity and the photo for a specific line item. Scrolling a chat for a picture taken eleven weeks ago is not a process, and the delay itself signals uncertainty to the client.
3. Instructions with no author
Verbal and chat instructions are the single most common source of unpaid work. If a change is not dated, priced and acknowledged before it is built, you are funding it.
Chat history also walks out of the building. When a supervisor leaves, the project record leaves with them unless it lives somewhere the company owns.
Moving without a fight
Do not announce that the group is banned. It will not work, and it should not: coordination genuinely belongs there. Move one record type at a time, starting with the one that costs you money most reliably.
- 1
Week 1: attendance only
Supervisors mark attendance in the app instead of photographing the register. Nothing else changes. Payroll gets a total it can trust and the supervisor stops being asked to recount.
- 2
Week 2: progress with photos
The same daily log, but attached to the BOQ line it advances. This is the entry that later substantiates a valuation.
- 3
Week 3: materials received
Delivery logged against the project, with the docket photographed at the gate rather than found in a cab three weeks later.
- 4
Week 4: instructions and changes
Anything a client asks for goes in as a variation before work starts. This is the habit that pays for the whole exercise.
Give supervisors a phone app that works with bad signal and syncs later. If the tool needs a good connection to accept an entry, site staff will fall back to chat and you will have two half-records instead of one good one.
What you should expect to see
- Payroll prepared from a total, not a transcription, in a fraction of the time.
- Valuations backed by dated evidence, which shortens the query cycle rather than the argument.
- A project record that survives staff turnover, because it belongs to the company.
- A quieter group chat, still doing the job it is actually good at.
Questions this raises
Our site has no reliable internet. Does this still work?+
Yes, if the field app stores entries locally and syncs when a connection returns. Attendance and photo logs are small, so a sync catches up quickly once the phone is back in coverage.
Will supervisors actually use it?+
They will if it is faster than what they do now. Marking 18 workers present should take seconds and replace an existing task, never sit on top of it.