Decisions Lost in WhatsApp: Why Your Site Has No Memory

Anatomy of a lost decision

Tuesday, 11:40. The site manager posts a photo of the bathroom-2 door frame to the group: “raise it 3 cm or leave it?” At 12:05 the architect replies with a 40-second voice message: raise it — but only in the north-facade bathrooms, because of the service skirting. At 12:06, the site moves on. The decision got executed.

Five weeks later, at handover, the client asks why the north-facade frames don’t match the drawing. And the ritual begins: hunt for the voice message, fail to find it, argue about who said what, reconstruct from memory. The decision existed — everyone half-remembers it — but it was never recorded. And a decision that isn’t recorded, for all practical purposes, doesn’t exist.

That’s the quiet disease of construction site communication: it’s not that information is missing. It’s that the site has no memory.

The official record keeps the “what”; chat swallows the “why”

Every project has an official record: drawings, minutes, certificates, the amended design. That record preserves the what — what finally got built. But the why — the technical query, the client instruction, the change requested at the workface — travels through WhatsApp, phone calls and emails titled “RE: RE: RE: bathroom”. The industry has been circling this problem at platform level for years — buildingSMART’s work on common data environments keeps landing on the same underlying point: without traceability, the approval flow falls apart (see, for context, buildingSMART’s CDE discussions). The boots-on-site version is simpler: paper keeps the result, chat loses the reason.

Why chat is not a record

This isn’t a WhatsApp defect; it’s WhatsApp’s nature. A record has four properties a chat structurally can’t offer:

• Search that works. “The thing about the frame” is somewhere in 3,000 messages, between memes and concrete-pour updates. The gallery sorts by time; your question is about a place and a topic.
• Anchoring to the place. The decision was about that frame in that bathroom. In chat it’s floating text — nothing ties it to the point on the drawing it refers to.
• An owner and a status. A message has no assignee and can’t be “closed”. Was it approved? By whom? Was it executed? The chat doesn’t know.
• Handover. When the foreman changes company, his phone leaves with him — and half the project’s decision archive leaves inside it.

What “project memory” means for a small team

For a large developer, the institutional answer is a CDE — a common data environment with approval workflows and governance (we wrote an honest guide: what a CDE is and why you may not need one yet). For a two-person technical practice or a fit-out contractor, that’s not the first-order need.

Project memory, small-team edition, is three properties:

1. Every decision lives where it happened — on the plan, the photo or the model, not in a thread.
2. Every decision carries context — who made it, when, with what evidence, what was replied.
3. Every decision has a status — proposed, approved, done — without maintaining a separate list.

None of that requires an enterprise platform. It requires capturing the decision at the moment and place where it’s born.

The fix isn’t a heavyweight platform — it’s capture at the source

Here’s the practical turn: you don’t solve this by “migrating the company” to a new system, but by changing the gesture. Instead of describing the frame in words in a chat, you open the plan on your phone, tap the point, and drop a pin: the photo of the frame, the architect’s voice note — auto-transcribed into searchable text — and the reply thread attached to that exact spot. You @mention the responsible person, it’s assigned, and the decision sits on the Kanban board until it’s marked done.

Five weeks later, the client’s question takes twenty seconds: open the plan, tap bathroom 2, and there it is — who decided, when, why, with the original audio and its transcript. Nothing gets reconstructed, because nothing was lost.

That’s how a small site gains what the industry chases with big platforms — traceability — starting from the end that actually bleeds: the moment of capture. How the same habit kills the nightly report rebuild is the subject of stop rebuilding site reports from WhatsApp, and the whole field routine fits in a 10-minute site visit checklist.

”And the WhatsApp group?” — it stays

No site is going to abandon chat, nor should it: for conversation it’s unbeatable. What moves house is something else: the decisions, issues and instructions — everything someone will need to find, prove or hand over a month from now. Conversation in the chat; record on the plan. The boundary is easy to remember: if failing to find it tomorrow could cost money, don’t leave it in the chat.

This also happens to be your first digital step

There’s a less obvious payoff. The industry is pushing toward open standards, IFC models reaching field teams, and common data environments. A team that already captures its decisions with location, context and status has done half of the cultural change those platforms demand — which, every industry analysis agrees, is the real barrier. Starting with your site’s memory isn’t the alternative to going digital; it’s the first step that doesn’t hurt.

FAQ

Why doesn’t WhatsApp work as a record of site decisions? Because chat sorts by time while a record is queried by place and topic: no anchoring to the drawing, no owner, no status, no export. The information technically exists; functionally, three weeks later, it’s gone.

What does it mean for a site to “have memory”? That any relevant decision can be found months later with its context: where it was, who made it, when, on what evidence, and how it ended. If that depends on people’s recollection, the site doesn’t have memory — it has witnesses.

Do I need a CDE to get this? Not as a first step. A CDE brings the document governance that big contracts demand; losing decisions is fixed earlier, by capturing them on the plan in the moment. When a contract does require a CDE, that habit will already work in your favour — more in what is a common data environment.

What PinMy is NOT

PinMy is the field-capture layer: pins with voice, photo, video and text on PDF plans, site photos and 3D IFC models, with assignment and Kanban status. It is not a CDE and doesn’t replace one, it doesn’t run document approval workflows, it claims no standards compliance, and our web PDF report is useful today but still maturing. It does one thing: your site’s decisions are born recorded, with a place and a context.

The twenty-second test

Think of your project’s last important decision. Could you show it — who, when, where, why — in twenty seconds? If the answer is “I’d have to search the group”, your site doesn’t have memory: it has luck. And send this to the colleague who is scrolling for a five-week-old voice message right now.

• Start free: pinmy.co
• Book a 15-minute walkthrough: tidycal.com/pinmy