← Knowledge base

Communication

Site communication: why WhatsApp is not enough

9 July 2026 · 6 min read

Photos scattered across phones, decisions buried in chat threads and a language barrier in the field. Here is how to take control of site communication.

Introduction

Site communication has moved to instant messengers, and in practice that usually means WhatsApp: a group for every site, with the foreman, the installers and often the subcontractors too. It is fast, familiar and free — and precisely for that reason it has quietly become many companies' most important information management system.

The problem is not the communication itself, but what happens to the information after the message is sent. In this article we go through the most common pitfalls of site communication — decisions buried in threads, photos scattered across phones and the language barrier — and what a working solution looks like.

A site message thread and weekly summary on a phone in the van

Where instant messengers fail

WhatsApp, Telegram and text messages were designed for free-form conversation, not for managing a project. In site use the limits appear quickly:

  1. Information drowns in the thread. An agreed change or additional work is under hundreds of messages within a couple of days. Search knows nothing about projects or tasks — only words.
  2. Groups multiply uncontrollably. The same thing is agreed in one group and overturned in another, and nobody knows which group is the "official" one.
  3. History leaves with people. When an employee changes companies or a phone breaks, the conversation history — and the agreements in it — can be lost for good.
  4. Work and free time mix. Work matters travel in the same app as family messages, and the company has no control over its own information.

Photos: the most valuable documentation scattered across phones

Site photos are a small company's most valuable documentation. They prove what was done, when, and what condition the site was in before work started. In an instant messenger, however, a photo is saved to the sender's and recipients' phone galleries with no link to the project.

When the photos are then needed — for a complaint, for invoicing additional work or for a warranty question — they are dug out of someone's personal gallery or found by scrolling months of message history. Often the decisive photo is on the phone of the very installer who no longer works for the company.

The language barrier is the site's silent risk

A significant share of the construction site workforce has a foreign background — estimates hover around one fifth. On Finnish sites you hear Estonian, Polish, Ukrainian and Russian daily, yet communication still runs almost exclusively in Finnish or English.

A misunderstood instruction is not just an efficiency problem but a safety risk: an unclear assignment or warning can lead to mistakes and dangerous situations. In practice many people confirm they understood even when part of the message was left to guesswork.

Try Fisas for free, 14 days, no payment details.

Start trial

What does working site communication require?

Working site communication does not mean yet another detached chat app, but connecting the communication to the project. The hallmarks of a good solution:

  • Project-specific discussions. Every site has its own thread, and the messages are stored under the project — not on anyone's personal phone.
  • Photos and files in the right place. A photo shared in the discussion is found in the project's files a year later too.
  • Mentions and push notifications. An @-mention reaches the right person without disturbing the whole group.
  • Message translation. A message can be translated into your own language at the press of a button — into Estonian, Polish or Ukrainian, for example — so the instruction is understood correctly for certain.
  • From message to task. An observation or instruction becomes a task with one click, with an owner and a status, instead of staying "read but forgotten".
  • Works in dead zones too. Messages go through even when the connection drops, and sync when the network returns.

Communication is also evidence

In a dispute, documentation decides. When the discussions, photos and agreed changes sit under the project with timestamps, "who said what and when" is not a question of memory. A history scattered across private messengers is weak in a dispute: messages disappear, get deleted and stay on former employees' phones.

Summary

WhatsApp is an excellent conversation app but a poor project tool. The biggest problems of site communication — drowning information, scattered photos and the language barrier — are not solved with new groups but by connecting communication to the project. When discussions, photos and tasks live in the same system under the project, the information stays with the company instead of in individual phone galleries.

Try Fisas for free

14 days, no payment details, no commitment.

Start free trial