Commercial construction, weather days, written proof
RainDelayLog stamps each lost hour with the reading from the reporting station that governs your contract, then keeps it in a packet the owner's rep can check line by line. Your superintendent files from the truck in about ninety seconds, and the time extension file assembles itself while the site dries out.
Nobody argues that it poured on the fourteenth. The fight starts three months later, when the owner's scheduler asks which activities were on the critical path that morning, who was standing down, and where the number in your notice came from.
Most commercial contracts give you 7 to 21 days to put written notice of a weather delay in front of the owner. A super running two towers forgets a Tuesday in March, and that day is gone even though the gauge agrees with him.
$2,500 per day in liquidated damages"Rain, no work" is what most daily logs carry, and it does not survive a claim review. Without crew counts, idle equipment hours and the activity IDs that got hit, the reviewer has nothing to approve.
19 of 24 days rejected on one reviewThe owner says a wet April is normal in that county, so those days were already inside your schedule. You need the ten year normals and the actual totals side by side, on the day you file, not from memory in a deposition.
11 days written off in a single meetingWhen the claim is finally assembled, a project engineer spends days pulling texts, camera stills and a legal pad into one story. The hours are real, the record is thin, and the schedule analyst still has gaps to explain.
11 hours a month of engineer timeThe whole method fits in the ten minutes your superintendent already spends on the daily report. Nothing in it asks the field to become a scheduler.
Drop the pin on the site, and RainDelayLog picks the nearest National Weather Service ASOS or AWOS station along with the county rainfall normals for the last ten years. If your contract names a specific station or an on site gauge, that source governs instead.
Setup: about 20 minutes per jobThe super answers what stopped, which crews stood down, which equipment sat idle and which scheduled activities took the hit. Photos carry a timestamp and coordinates, and the whole entry closes in a minute and a half on a phone in a wet glove.
Field time: 90 seconds a dayYour rules decide what counts: precipitation over 0.10 inches, sustained wind above 25 mph for crane picks, a 7 a.m. reading under 32 degrees for masonry, or a dry out day after saturated subgrade. Each rule cites the contract clause it came from, so the classification is never a matter of opinion.
Rules run per activity, not per jobOne button produces a PDF with hourly station data, the normals comparison, signed daily logs, geotagged photos and the affected activity IDs pulled from Primavera P6 or Microsoft Project. A CSV of the same record goes to your scheduler for the time impact analysis.
Median build time: 9 minutes
Every part of this product exists because a delay claim got trimmed for a reason that could have been prevented on the morning it happened.
Each job is tied to the reporting station your contract recognizes, and the hourly record is pulled and archived every night whether anyone logs in or not. When a claim is reviewed two years later, the raw observations are still sitting under the day.
The rain stops at midnight and the subgrade is still soup at 6 a.m., which is the day owners contest hardest. Carryover rules record the saturation condition, the equipment that could not move and the trade that had to stand down.
Concrete, steel erection, roofing and earthwork do not stop at the same number, so they do not share a rule. You set the trigger for each activity type once, and the log classifies the day the moment the reading crosses it.
Every month shows actual precipitation against the ten year average for that county, printed on the same sheet as your logged days. The conversation about what counts as an abnormal month gets settled with a chart instead of a raised voice.
Photos land with coordinates, a timestamp and the entry they belong to, and nobody can quietly change them afterward. Crew headcount, idle equipment hours and the foreman signature ride along in the same record.
The contract notice period is stored per job, so the countdown for each weather day is visible to the whole project team. When you send, the packet, the recipients and the delivery time are recorded as part of the file.
Figures below come from 2025 customer reporting across 1,180 active job sites. They are averages, not the best case we could find.
A 14 month patient tower in central Florida logged every qualifying day from notice to proceed. The owner approved 31 of the 34 days submitted, because each one arrived with station data attached rather than a memo written after the fact.
Across 2,140 weather days filed last year, 94 percent were accepted without a second submission. The packet answers the reviewer's usual three questions before the reviewer asks them.
What used to be two days of digging through camera archives and text threads is now an export. The median packet covering a full month of weather days is built in 9 minutes.
Project engineers stop reconstructing history and start reviewing it. Customers report an average of 11 hours a month per job returned to submittals, RFIs and the work that moves the schedule forward.
Three customers agreed to put their names on the record. All three run commercial work where a lost calendar day carries a price.
"We got hit with 26 days of rain over a summer on a distribution center and the owner pushed back on nearly all of it. I pulled the packets, sent them Friday, and had 24 days approved by the following Wednesday. Before this we were arguing from my truck notes."
"My scheduler used to ask for the weather backup and I would wince. Now the activity IDs are already in the export, so the time impact analysis takes an afternoon instead of a week. The normals chart ended a fight with an owner's rep in about four minutes."
"Ninety seconds on a phone with wet gloves, that is the whole ask. My guys do it because it is shorter than the text message they used to send me. The notice countdown on the dashboard is what keeps me from losing a day to my own memory."
Every person on the project can log a day at no extra cost, because a record with gaps in it is not worth defending. You pay for the jobs you are running this month.
Every plan is billed monthly in US dollars and can be cancelled at any time from the account screen, with no term commitment and no exit fee. Cancel mid month and the jobs stay readable through the end of the paid period, and your exports remain downloadable. Prices are per company, not per user, and a job that closes out stops counting against your active total on the day you archive it.
If your question is not here, ask it in the form below and you will get a written answer from a person who has read your contract language.
Pricing is per active job site per month, and every person on that project can log a day at no extra charge. Single Site runs $59, Multi Site covers up to ten active jobs at $149, and Enterprise Site removes the cap at $349. Station data, county normals, unlimited exports and seven year retention are included in all three, so a heavy rain month never creates a surprise line on the invoice. A job stops counting toward your active total on the day you archive it.
One afternoon is the honest answer for a first job. You drop the pin, confirm the station our system picked, upload the delay and notice clauses from your contract, and set thresholds for the activity types on that project. Most teams log their first weather day the same week, and the second job takes about twenty minutes because your rule set is already written. Multi Site and Enterprise Site customers get a two hour session with their supers before the first log goes in.
You own every log, photo and packet you create, and we hold it as your processor and nothing more. Records live on US infrastructure, are encrypted in transit and at rest, and are versioned so an edit never quietly overwrites the original entry. You can export the full archive of a job at any time in PDF and CSV without asking us first. If you leave, we hand back the archive and delete our copy on written request.
No, and it should not. RainDelayLog pushes the finished weather entry into your Procore or Autodesk Construction Cloud daily log so the field is not typing the same thing twice. Activity IDs map to Primavera P6 or Microsoft Project, which means your scheduler receives the affected activities already tagged for the time impact analysis. Enterprise Site adds an API and scheduled exports if your risk team wants the record in a warehouse.
You cancel from the account screen and the plan ends at the close of the paid month, with no term commitment and no exit fee. The jobs stay readable through that period, and every packet you built stays downloadable while it is open. Teams that come back for a new project reopen the same account and keep their old rule sets. Nothing is deleted the day you stop paying, because a claim can surface long after a job closes.
A note is not evidence. A reviewer wants the governing station reading for that date, the threshold your contract set, the activities that were on the critical path, and proof the notice went out inside the window. A daily report line that reads rain, no work answers none of that, which is why so many days get trimmed at review. This log keeps the same field habit and produces the four things the reviewer is going to ask for.
The Weather Day
The Weather Day is written for superintendents, project engineers and schedulers on US commercial job sites. It covers how a claim package is assembled, what the notice clause actually asks of you, and what a wet week costs when the record is thin.
practical guide
A weather delay claim is read by someone who was never on the site. Here is the order the sections go in, what each one has to prove, and the exhibits that stop a reviewer from asking again.
regulation and compliance
Three standard contract families set the clock on a weather day, and each counts the days differently. Here is what A201, ConsensusDocs 200 and the federal default clause require in writing.
comparison
An owner's reviewer will accept one source and argue with another. Airport ASOS readings, an on site tipping bucket gauge and NOAA archived records compared on accuracy, distance and defensibility.
Send the dates of a stretch that cost you time, and we will rebuild it in the product on a shared screen using the station that governs that job. Most calls run 25 minutes, and you leave with the packet whether you buy or not.