Comparison
RainDelayLog vs Procore
Procore is built to run the whole commercial project from contracts to closeout, while RainDelayLog is built to make one weather day hold up in front of a reviewer who was never on the site.
Comparison
RainDelayLog vs Raken: daily reporting against delay proof
Raken is built so a foreman can finish a complete daily report from the field without dreading it, while RainDelayLog is built so one of those days survives an owner's challenge a year later.
The short answer
These two overlap more than people expect and compete less than people expect. Raken solves the field reporting problem: getting real daily reports, time entries and photos out of crews who would rather be working. RainDelayLog solves the claim problem: turning the specific days you lost to weather into a record with a station reading, lost hours, affected activities and a notice date. If your daily reports are already landing every night and your weather days still get denied, the gap is not reporting discipline. It is the shape of the weather record.
RainDelayLog and Raken side by side
| What you are deciding | RainDelayLog | Raken |
|---|---|---|
| Center of gravity | The qualifying weather day and the claim that follows it. | Field reporting rhythm across every working day, built around the crews filling it out. |
| Who it is designed for | The general contractor superintendent and the project engineer defending schedule. | Field leaders on general contractor and subcontractor crews producing daily reports. |
| Weather handling | Named station capture stamped to the entry, with the qualifying threshold from the contract applied. | Weather appears within the daily report workflow as part of the day's field record. |
| Lost time | Crew hours and equipment hours recorded against the specific activities that stopped. | Time and production tracking oriented to the working day and payroll rhythm. |
| Notice and contract terms | Notice window, baseline day table and named station stored per contract on each job. | Contract mechanics such as notice deadlines are handled outside the reporting workflow. |
| Output when challenged | A packet ordered for a reviewer: narrative, weather evidence, hours, schedule impact, notice trail. | Daily reports and photo records exported from the field reporting system. |
| Days it cares about | The thirty or so days a year that cost you calendar time. | Every day the crew is on site. |
The right hand column places Raken by scope and by the sort of operator it serves, with no attempt at a priced feature list. Products change, so check the current details with them before you decide. RainDelayLog is published by MLJ, SASU and this page is written by Jimenez Julien.
Choose RainDelayLog when
- When your daily reports are already good and the weather days still come back denied, the record shape is the problem.
- When the contract names a station and a monthly day allowance, you need those terms living inside the daily entry.
- When a job has moved into dispute and a consultant is about to read fourteen months of logs, the packet order matters.
- When dry out days are the real cost on an earthwork package, you need the hours after the rain stopped captured too.
Choose Raken when
- If the real problem is that daily reports do not get filled out at all, fix the reporting habit first.
- If subcontractor crews need to submit their own field reports and time in a shared rhythm, that is what a field app is for.
- If you need production tracking and time entry across every working day, a weather focused tool is the wrong center.
Good daily reports still lose weather days
We see complete, disciplined daily report sets that still fail. The entry says heavy rain, crew released at 10 am. That sentence tells a reviewer nothing they can verify. It does not name a measurement, it does not say which scheduled activities were affected, it does not separate the crew that went home from the crew that stayed on interior work, and it does not connect to a notice.
The fix is not more writing. It is different fields. When the same superintendent is asked for tenths of an inch at the named station, the released crew count and hours, and the two activity codes that could not proceed, the entry takes the same two minutes and carries ten times the weight.
The dry out day is where field apps and claims diverge
Rain stops at midnight and the site still cannot take a scraper at seven. On a field reporting app that morning looks like a normal working day with reduced production, because that is honest reporting. On a delay record it needs to be a documented dry out day with subgrade conditions, standing water photos, the moisture call and the hours the earthwork crew stood by.
Both descriptions are true. Only one of them survives a challenge. RainDelayLog prompts for the dry out day the morning after every qualifying rain event, because that is the day contractors most often forget to record and most often lose.
Using them together on a self perform job
On self perform concrete and earthwork jobs, running both is reasonable. Crews keep producing daily field reports the way they already do, and the superintendent adds the weather day entry only on the days that qualify. That is roughly two dozen entries a year, not two hundred.
The dividing line to hold is simple. Anything about production and payroll stays in the field reporting system. Anything you might have to prove to an owner about lost calendar time lives in the weather day record, with the photos attached to it rather than scattered across a phone gallery.
Questions people ask before they choose
Is this a replacement for our daily field reports?
No. RainDelayLog covers the weather days and the dry out days that follow them, not every working day on the job. Most customers keep their normal daily report process running and add the weather entry only when the day qualifies.
Our foremen already resist one app. Why add another?
Because the weather day entry is not a foreman task in most of our accounts. The superintendent or project engineer owns it, and it fires maybe twenty five to forty times a year. The crews never see it.
What if we only self perform sitework?
Then dry out days are probably your biggest uncaptured cost. Saturated subgrade keeps a scraper off the pad long after the rain gauge goes quiet. Recording those standby hours the same morning is the single highest value habit for an earthwork operation.
Other comparisons on raindelaylog.com
Comparison
RainDelayLog vs Autodesk Construction Cloud
Autodesk Construction Cloud connects design, models and field execution across a project, while RainDelayLog stays on one narrow contractual problem that starts the morning it rains.
Put the two side by side on a wet job
A criteria table only takes the decision so far. Send us a job that is already losing calendar time and we will enter one qualifying morning the way a reviewer reads it, from the station reading through the released crew hours to the notice date. If what you run today already produces that packet, we will say so and you can get back to the schedule.