The short answer
Instant messaging is excellent for alerting and coordinating in the moment, and poor as an archive of what happened on the project. A site log is the opposite: slower to fill in, but structured, ordered by date and designed to be consulted months later.
You do not have to pick one. The sensible approach is for the chat to remain where the project talks, and for what matters to be recorded in the site log.
What each one does well
| Criterion | Instant messaging | Digital site log |
|---|---|---|
| Immediacy | Very high: it reaches the right person instantly | Depends on someone filling it in; it can alert, but that is not its job |
| Structure | Free-form: each message says whatever the writer decides | Defined fields: date, weather, personnel, activities, incidents |
| Finding something later | You have to remember words and dates among thousands of messages | You filter by date, type of entry and person responsible |
| Who said what | The phone number appears, not necessarily the person or their role | Each entry carries its author and role |
| Changes and deletions | Messages can be deleted or edited | An edited entry leaves a trace of the change |
| Backup and export | Depends on the phone and on each person's backups | A single record of the project, exportable |
| Derived reports | You have to copy the relevant parts by hand | Reports are assembled from what is already recorded |
Worked example: finding a fact three months later
A project with 3 chat groups (site, warehouse, supervision), 25 messages a day each and 90 days adds up to 6,750 messages. The figures are invented, but the multiplication shows the order of magnitude.
If you need to know what was agreed about a change in specification, in the chat the information is one among 6,750 loose messages, mixed in with photos, greetings and alerts. In a site log the same project has 90 daily entries, one per date, each with its own section for incidents.
How to use both without duplicating work
- Define what must be recorded no matter what: progress, personnel, weather, orders, incidents, visits, material deliveries.
- Use the chat to coordinate and the site log to record, at the end of the day, what happened.
- If there is an important instruction in the chat, move it to the site log with its date and author.
- Once a week, check that the site log has complete days.
- Do not use the chat as the only backup of the project's photos and documents.
Limits of this comparison
It compares categories, not products, and it does not claim that a site log by itself guarantees an outcome in a claim. Many contracts set how the site log must be kept; check yours. If nobody fills in the site log on time, it stops being useful: the tool does not replace the habit.
Frequently asked questions
Can I keep using the project chat?
Yes, and you should. Just avoid making it the only place where the important things are kept.
What should a site log contain at a minimum?
Date, who writes and in what role, weather, personnel present, the day's activities and incidents. If your contract asks for more, that prevails.
Does a digital site log replace the physical book?
It depends on what your contract or your supervision says. Confirm it before you stop keeping the physical one.
Sources
- This comparison is based on professional practice criteria, not on studies or external data. The example is arithmetic with invented figures.