Weather & Delays

Recording the day's weather and every delay on the daily log, and where they show up in the reports you send the client.

Weather and delays are recorded once, on the daily log. When you compile a client report, PleoStack totals them over the report's period: a Weather section with temperatures, rainfall and the days weather stopped work, and a Delays & Issues section with the hours lost and what caused them.

Quick Summary
  1. Daily Log → New Log — the Weather section fills itself on today's log; check it, or type the day's figures
  2. In Delays, click Add for each hold-up: cause, hours lost, responsible party, description, and Recurring if it keeps coming back
  3. Submit the log, and get it approved if the project requires approval — drafts and logs awaiting approval don't count in client reports
  4. In a client report, the Weather section totals the period and counts the days with a weather delay
  5. The Delays & Issues section totals the hours lost and ranks the causes and the longest delays
  6. Mark as Final, then Preview → Share to send it

Before You Begin

Prerequisites

  • Open a project first. Daily logs and client reports belong to a project.
  • A client report counts approved daily logs only, or submitted ones on a project that does not require approval.
  • Weather delays are counted from the Delays section. Heavy rain in the Weather section alone does not count as a delay day.

Step by Step

1

Record the weather

Open Daily Log and click New Log, or open today's draft. On today's log the Weather section fills itself from the site's current conditions; Fetch Weather fetches them again. For another date, or to correct what came in, type the figures yourself:

  • High Temp and Low Temp, with the Unit (°C or °F)
  • Conditions — for example Cloudy, Rain or Heavy Rain
  • Humidity (%), Precipitation (mm), Wind Speed and Wind Unit
The Weather section: temperatures, conditions, rainfall and wind for the day
2

Record each delay

In the Delays section ("Schedule delays and their causes") click Add for each hold-up and fill in:

  • Cause — Weather, Material, Labor, Equipment, Design, Permit, Client, Subcontractor or Other
  • Hours — the time lost
  • Responsible party — who caused it, if anyone
  • Description — what stopped and what it affected
  • Recurring — tick it when the same hold-up keeps coming back, such as a pump that fails again or an RFI still unanswered

A red badge next to the heading adds up the hours on the day. Pick Weather as the cause whenever the weather stopped work, because the client report counts weather delay days from this field.

One row per delay: the cause, the hours lost, who was responsible and what happened
3

Submit and approve the log

Save Draft, then Submit, and have someone else approve it from the Daily Reports tab. A log with a delay can be submitted even if nothing else is filled in, as long as the delay has a description and hours. In the register, the Delay column shows each day's hours lost.

The register: the Delay column is the hours lost that day
4

Read the Weather section of a client report

Create a client report for the period (Reports → Client Reports → New Report). Its Weather section opens with five figures:

FigureWhat it counts
Working DaysThe counted daily logs in the period
Weather DelaysDays with at least one delay whose cause is Weather
Avg High / Avg LowThe average of the daily temperatures
PrecipitationRainfall added up over the period, in mm

Below them, a line counts the clear or normal days and the Notable Weather list shows every day with rain or other bad conditions. At Standard detail a Temperature Trend and a Conditions Breakdown follow. Detailed adds Weather Impact and the full Daily Weather Log, one line per day.

The top of the Weather section: period figures, then every day with notable weather
5

Read the Delays & Issues section

The Delays & Issues section totals every delay in the period:

FigureWhat it counts
Total HoursThe hours lost across every delay
Delay EntriesThe number of delays recorded
RecurringDelays ticked Recurring on the daily log
Cause CategoriesHow many different causes appear

A callout names the top cause and its hours, a donut splits the hours by cause, and Top Delays lists the longest ones with their cause, date and responsible party: five at Standard, ten at Detailed. Standard also shows a Cumulative Trend of hours lost. Detailed adds a Cause Breakdown table and an All Entries list of every delay in the period, oldest first.

The Delays & Issues section: hours lost, the top cause and the longest delays
6

Send it to the client

Mark as Final, open Preview and click Share to create a link that expires, with an optional password. The Export tab in the same dialog prints the report or saves it as a PDF. Sharing a Report covers every option.

Good to Know

  • Section titles are yours to change. You can rename Delays & Issues to "Delays and disruption", for example. The figures stay the same.
  • There is no separate delay export. To see delays over any dates, create a Custom Range client report for them.
  • Tick Recurring on a delay that keeps coming back. The client report's Recurring figure counts those, so the client can tell a one-off from a pattern.

Questions

It rained all day but Weather Delays still shows 0. Why?

Weather Delays counts days with a delay whose cause is Weather in the Delays section. Heavy rain in the Weather section alone isn't a delay. Add a delay with cause Weather and the hours lost.

Why does a delay I recorded not appear in the report?

Only approved daily logs count (or submitted ones, if the project doesn't require approval). Check the log's status. Also check the detail level: Top Delays lists only the longest five or ten; All Entries, at Detailed, lists every one.