Your WhatsApp groups are project records. Treat them like it.
If a delay event went to adjudication tomorrow, the strongest evidence you hold is probably sitting on a site manager's personal phone, and you have no way to get at it. Adjudication is fast by design: the right to refer a dispute at any time, and the twenty-eight day timetable, come from the Housing Grants, Construction and Regeneration Act 1996, which does not leave room to go hunting through phones. The fix is not to ban WhatsApp. It is to capture what the team already writes and give it the same discipline as the rest of the project record.
Ask any site manager where the real story of the project lives and they will not point at the CDE. They will point at their phone. The weather that stopped the pour. The photo of the blocked access. The voice note about the late delivery. The message confirming the architect was happy with the detail. It is timestamped, honest, and written in the heat of the moment, which is exactly what makes it valuable.
And in most businesses, none of it survives.
Why does construction control some records and not others?
Because the controlled records have a process attached and the uncontrolled ones have a habit attached. Nobody decided that messages do not matter. The process simply never followed the conversation onto the phone.
A drawing revision goes through a controlled process with a transmittal and an audit trail. A message that changes the sequence of works gets typed into a group chat and scrolls away within a day. The double standard is invisible right up until the moment it costs money.
| Record | Where it lives | Survives the author leaving | Dated and attributable | Retrievable months later |
|---|---|---|---|---|
| Drawing revision | CDE | Yes | Yes | Yes |
| Formal instruction | Email or CDE | Usually | Yes | Usually |
| Written site diary | Site file | Sometimes | Yes, if written on the day | If it was kept up |
| WhatsApp message | Personal phone | No | Yes, but only to the phone's owner | Rarely |
| Voice note | Personal phone | No | Not unless transcribed | Almost never |
| Site photo | Personal camera roll | No | Metadata only, no context | Almost never |
Read the bottom three rows together. The records with the highest evidential value carry the weakest chain of custody, and they are weak for the same reason every time: they live on a device the business does not control.
What actually happens when you need those messages?
Someone is asked to scroll back through eight months of chat, on a phone that may no longer exist, belonging to someone who may no longer work for you.
That is not a records strategy. It is a gamble on three things at once: that the handset survived, that the employee is still contactable and willing, and that nothing was deleted in a clear-out. Adjudicators and courts increasingly see message evidence, and the party that can produce a clean, dated, attributable record of what was said on the day holds the stronger position. The party that cannot is not neutral, it is worse off, because the arguments that end up costing real money almost never start big.
What does good capture actually look like?
Capturing what the team already produces, without asking them to change how they work. Four things have to happen, and the order matters.
- Capture automatically. Messages, photos and voice notes from project groups are logged as they happen, against the right project and date. Nobody files anything.
- Transcribe and structure. Voice notes become searchable text. Photos are tagged and filed. Content is sorted into the categories that decide arguments: weather, labour, plant, deliveries, progress, delays, instructions, safety.
- Produce the diary. The day's traffic becomes a structured daily record, generated in the evening and reviewed by a named person. This is the step that turns a chat log into a document that carries evidential weight.
- Keep it queryable. Months later you can ask when the access issue started, what was said about the parapet detail, or how many days weather stopped work in February, and get an answer with the source attached.
Miss the third step and you have an archive rather than a record. Miss the fourth and you have a record nobody can use under time pressure, which in practice is the same as not having one.
What does this change commercially?
It changes who pays to assemble the evidence, and when.
Contemporaneous records win arguments. Reconstructed ones invite them. The businesses we work with rarely lose because the facts were against them. They struggle because the facts were scattered across personal devices and inboxes, and rebuilding them cost more than the argument was worth. That cost is real, and it is paid at the worst possible time, under deadline, by your most expensive people.
Captured properly, the evidence assembles itself as a by-product of how the team already communicates. Nobody fills in a form. Nobody writes up the diary at seven in the evening. The record is simply there, structured and dated, when it is needed. The same capture also feeds the golden thread obligations under the Building Safety Act, which is the other place a scattered record turns into a problem.
This is exactly what we built Construction Metric to do, and it exists because of a pattern that kept repeating on live projects: the best evidence in the business, sitting in the one place the business could not reach.
Your site team already writes the diary. They just do it in WhatsApp. The only question is whether the business keeps it.