Rebuilt from memory weeks later
When the weather delay is discussed at the end of the month, the details are reconstructed. Nobody remembers whether the crew was sent home at nine or at noon, and the only evidence is a line that says rain.
Daily log
Weather delay documentation in construction: the daily log entry
Weather that stops work has to be written down the day it happens, with its effect on the work, so that the schedule conversation later rests on records and not on memory. This page shows what to put in the daily report in Fidrel and what stays outside it: Fidrel keeps the record, it does not argue the claim.
30 days free · No long-term contract.
Why weather delays are hard to prove later
A line that says rain
An entry that names the weather but not what it stopped says nothing about the delay. Which work could not proceed, which crews stood down and for how long are the facts a later conversation needs.
Records that can be edited without a trace
A log that can be tidied up afterwards is worth less to everyone, including the superintendent who wrote it honestly. The value of the entry is that it was made on the day and stayed as it was.
What a useful weather entry says
Write the time the weather began to interfere with the work, the time work resumed, the work that could not proceed, the crews affected and how many people were sent home. Name the source of the weather observation. Put the amount, such as rainfall or wind, in the text if you measured it. Keep opinions out: the entry states what happened on site, and the argument about entitlement comes later, from the contract. The Weather field is text and People on site is a number, so the entry carries both the narrative and the head count.
Site & daily log
A record that stays what it was
A daily report cannot be deleted, and every change is logged field by field with the name of the person and the time. Reports are listed day by day, most recent first, and can be found again by searching the title or filtering by author, location, company, date and status. If somebody asks a month later what was written on the day and by whom, the history answers.
Recording a weather delay in Fidrel
Step 1
Open the day’s report
In the site area choose New log entry and fill in the title, time and location. Start the report while the weather is still what it is, from the phone browser if you are on the slab.
Step 2
Write the weather
Enter what the weather was and when it began and ended in the Weather field, and say where the observation came from, such as your own gauge or a weather service, in the same text.
Step 3
Write the effect
Use Delays / disruptions for which work stopped, which crews stood down and from what time to what time. Update Work in progress, People on site and Equipment / resources to match what actually happened.
Step 4
Add photos
Take photo opens the phone’s camera, and files of up to 25 MB can be attached, so standing water, a wet slab or a closed lift can be shown with the entry.
Step 5
Decide what the schedule shows
If your contract counts the day as lost, add it under Non-working dates with Add date, which moves later dates. Compare with the saved baseline to see the variance in days on the end date.
Connecting the record to the schedule
The schedule shows the variance in days between the end date and a saved baseline, and a progress line that reads ahead of plan, on track or behind plan. The working calendar holds the dates that do not count as working days; adding a date there moves every later date, so decide first what your contract treats as a lost day. When a change order follows, its Schedule impact (days) is a number you enter.
What the daily log does not do
Fidrel does not pull official weather data, and the weather is text typed in by the person writing the report. Fidrel does not calculate a normal-weather threshold, run a time impact analysis or draft a delay notice. Follow your contract’s notice terms: Fidrel does not know them, and a daily report is not a notice. A daily report cannot be linked to a schedule activity, so you connect the two in your own words.
Related solutions
One project. One subscription. The entire platform included.
Your trial applies to your first own project and starts when that project is created. No card required. Afterwards, choose card or invoice to continue.
- 30 days free
- Unlimited participants
- No minimum term
Insights
View all
Project coordination just got simpler
The project system of the future connects people, documents and decisions. Discover the thinking behind Fidrel.
Read more
Your drawing, on site. Open DWG on your phone.
On site, answers need to be close at hand. Fidrel displays DWG drawings in your mobile browser, within the project’s document structure.
Read more
A clearer schedule. From the first activity to the final milestone.
When everyone can see the next step, moving the project forward becomes easier. Fidrel brings activities, dates and reported progress together in a shared Gantt view.
Read more
No. The Weather field is text typed in by the person writing the report. Name the source of the observation in the same text if it matters.
A daily report can be changed, but it can never be deleted, and every change is logged field by field with a name and a time, so the original entry can always be seen.
Yes. Open the daily log in the phone’s browser, write the report and take the photos on the spot with Take photo. There is no app to install.
No. Fidrel does not calculate a normal-weather threshold or run a time impact analysis, and it does not know your contract. It keeps the record and the schedule.
A lost day is a date you add to the working calendar yourself, with Add date under Non-working dates. Later activities move, so check what your contract counts first.
No. A daily report is a record, not a notice. Follow the notice terms in your contract and send the notice the way the contract says.