A paper site diary gets lost or stays unclear. A digital version is always available and searchable.
A site diary is often treated as a routine filled in because that is the custom. Its value is only measured when a disagreement arises, and at that moment it either exists or it does not.
Disputes in construction contracts are almost always about the same thing: who said what and when, and what happened on site that day. Each party remembers it their own way, and both remember in good faith. The resolution does not come from who remembers better but from who has the entry.
This is why the most important property of a diary is not coverage but timing. An entry made the same day is a different thing from a description written six months later from memory.
Four situations where a diary has resolved a dispute or prevented one.
Schedule slippage. The contract runs late and the question is whose delay it was. If the diary says the slab pour waited nine days for the client's decision, the conversation is short. If it does not, the conversation is long.
Conditions. A cold spell, rain, a late delivery. These are grounds for a schedule change only if they were recorded when they happened. The weather can be proven afterwards, but not that it stopped this particular stage of work.
Client instructions. Verbal instructions given on site are the most common seed of dispute in construction. An entry saying the client asked on Monday to move a partition wall changes the later conversation completely.
Defects and their repair. When a complaint arrives during the warranty period, the diary says what was done, by whom and in what order. Without it you are demonstrating your diligence from memory.
A diary most often fails because someone tries to make it comprehensive. When an entry takes twenty minutes it does not get made on a busy day, and busy days are exactly the ones where the entry would be needed most.
A workable minimum is three things.
Who was there and what was done. Not a timesheet, but a sentence on which stage progressed.
What deviated. Waiting, a shortage, weather, an interruption, damage. This is the line that has value later.
What was agreed. Who asked for what and who promised what.
If only one of the three fits in the day, it is the second. A normal day needs no evidence. A day that deviated does.
A photograph is an entry that cannot be reinterpreted
A photograph solves the problem a written entry always has: the wording is the writer's interpretation of the situation. A photograph of the frame before boarding shows what was there, and a photograph of a defect before repair shows that the defect existed.
A photo works as evidence when it is known when and where it was taken. A phone's camera roll knows the time but not the place, and the photo disappears with the device. What to photograph and how is covered in the article on site documentation.
A paper diary is not bad because it is paper. It is bad for three practical reasons.
It is in one place. It is in the site hut, and when you need the entry you are at the office. Or the other way around.
It disappears. The site is dismantled, the huts move, the notebook is in somebody's van. When the question comes up years later, it is rarely found.
It cannot be searched. The question is never "what happened on 14 March" but "when did we talk about the partition wall". In a notebook that is found by leafing through, if at all.
A paper entry is also easy to make after the fact, which weakens its evidential value. An entry whose time of creation can be verified is stronger than one that could have been written at any point.
The most common arrangement is that the site manager keeps the diary. That is logical but fragile.
The site manager is not on site all day. They record what they saw or what was told to them. What was not told is left out, and deviations are exactly what does not get told, because they usually resolve themselves.
A better arrangement is that a worker can record an observation directly and supervision adds to it. Then the entry appears where the event was, without passing through memory.
This requires recording to be effortless for the worker. If it means walking to the site hut, it does not happen.
Extra work is the most common invoicing dispute in construction, and it is almost always settled by documentation.
The sequence is typically this. The client asks for a small change on site. It is done. The invoice goes out. The client says they ordered no such thing.
If the diary holds an entry of the request with a date and a name, the situation is clear. If it does not, the contractor either writes off the receivable or argues for it with a lower chance of winning.
For this reason the value of a diary entry is not administrative but financial, and it can be calculated. Take last year's extra work that had to be negotiated, and see how much of it had been recorded somewhere before the invoice.
A common question, and the answer is to write that.
An entry saying "frame work progressed as planned, no deviations" is worth more than an empty day. An empty day is ambiguous: it can mean everything was fine or that nobody recorded anything.
An unbroken diary is also evidence of what did not happen. If the other party claims the site stood still for two weeks, an unbroken series of entries refutes it. A broken series refutes nothing.
Site documents carry a long retention obligation, and the diary is the one most often needed afterwards.
The warranty period is typically two years, but liability for latent defects reaches considerably further. When a question arises ten years later about how a structure was built, the diary and the photographs are the only remaining information.
This is an argument for a digital diary that has nothing to do with ease of use. A notebook that is somewhere is not evidence. Material that can be found by searching is.
The entries are all the same length. A real site produces uneven days. Smooth material has been filled in for form's sake.
There are no deviations. Every site has waiting, shortages and changes. If they are not recorded, they are not recorded, which is not the same as them not having happened.
A month of entries was made on one day. If the timestamps show a month's entries appearing in one evening, they were written from memory.
There are two separate grounds for keeping a diary, and they are often confused with each other.
The contractual ground. In the general conditions for construction contracts the site diary is an established practice, and a contract usually provides for it explicitly. The diary is then a contractual obligation, and failing to keep it is a breach regardless of whether anything happens on site.
The evidential ground. This is the one that decides matters in practice. A diary is kept not because it is compulsory but because without it you cannot show what happened. This ground applies even where no obligation exists.
The difference shows in what gets written. A formal entry satisfies the contractual obligation. Only an entry that records a deviation and its time serves the evidential purpose.
In practice most diaries satisfy the first and fail the second. They have been filled in, and they are of no use when they are needed.
A contractor starts a renovation on the agreed day. According to the plans the partition walls are demolished in the first week. Demolition cannot begin, however, because the client was to clear the premises and has not.
The contractor calls, the client promises to sort it. The clearance is finished nine days later. Work proceeds, the contract runs about two weeks late, and overtime is worked at the end to catch up.
In the final settlement the client demands liquidated damages for the delay. The contractor argues the delay was caused by the client's clearance.
If the diary says, for every one of those days, that demolition cannot start because the premises are not cleared, the contractor has evidence of the cause of the delay. The diary alone is not enough, however. Under the Finnish general conditions for building contracts (YSE 1998), the starting point is that the contractor claims an extension of time from the client in writing as soon as the grounds are known, stating what the claim is based on. The diary shows what happened, and the written claim preserves the right to the extension. Without either, it is one party's word against the other's.
Nine short daily entries and one written extension claim to the client would have covered both the liquidated damages and the overtime in this case.
The reader of a diary is never its writer. It is the client's representative, the supervisor, a lawyer, an insurance handler, or someone from your own company who was not on site.
Three practical rules follow.
Write names, not roles. "The client asked" does not say who. Six months later the client's organisation has three people who all deny asking.
Write what happened, not what you thought of it. "The premises were not cleared" is an observation. "The client is completely indifferent" is an opinion, and it weakens the credibility of the whole entry.
Write so that the sentence stands without context. The reader does not know what happened the previous day.
A rule of thumb: write as if for someone who will read the entry two years from now and has never visited the site. That is exactly the situation in which entries are actually read.
Three forms of documentation with different strengths. Confusing them leads to relying on the wrong one.
A diary entry records the time and the event. It is strong on timing and weak on substance, because it is the writer's interpretation.
A photograph records the situation. It is strong on substance and weak without context: an image does not say why it was taken or what happened next.
A message to the client is the strongest, because it is two-way. It shows not only what you observed but that you told the other party. A lack of reply is evidence too.
The strongest combination is all three about the same event: an entry in the diary, a photograph attached, and a message to the client the same day. That sounds heavy, but it applies only to deviations, of which a site has a few a month.
An ordinary day needs an entry. An unusual day is worth all three, and unusual days are exactly the ones later argued about.
The practice dies the same way every time: three good weeks, then a busy one, and after that a gap nobody returns from.
Three things keep it alive.
Attach it to something that already happens. Ending the day, returning to the yard, locking the site. A new habit attaches to an old habit, not to an empty slot in the day.
Make an empty day as easy as a full one. If "no deviations" takes the same effort as describing a deviation, empty days go unrecorded and the series breaks.
Read the entries once a week. Not because they contain something, but because reading them keeps writing them meaningful. An entry nobody reads stops being written within about a month.
The problems above are practical ones: the notebook is in the wrong place, the time of an entry cannot be verified, the weather has to be proven afterwards, and recording gets skipped on a busy day. The FiSAS site diary is built around them:
- The diary travels on your phone. An entry can be made on site straight away, and the office sees it at the same moment. Every entry has a timestamp.
- Weather is saved automatically. Weather data is fetched for the entry based on the site's location, so conditions can be verified afterwards without a separate investigation.
- Dictation speeds up recording. Entries can be typed or dictated, and AI turns speech into text and suggests a title and a category. A three-line entry then takes less time than walking to the site hut.
- Categories and search. Site events, inspections and reviews, work phases and safety observations have their own categories, and entries filter by site and by customer.
- Photos in the same place. Photos are stored on the project and locations on the floor plan, so the entry and the photo are found together.
- PDF in one click. The diary is available as a report for the client, the supervisor, or a lawyer in a dispute.
Documentation and the site diary are included in every plan, including the single-user Maker plan.
A site diary is the cheapest insurance a construction company can buy. It costs a few minutes a day and it pays off precisely on the days when something goes wrong.
What decides its value is not coverage but three things: the entry appears the same day, it includes deviations rather than routine only, and it can be found years later without anyone remembering where the notebook ended up.
If your own practice feels uncertain, the test is simple: pick one contract from last year where there was a disagreement, and see whether an entry exists for that day. The answer tells you whether you have a practice or only a habit.
