Why concrete pours need an especially good log
A concrete pour compresses a lot of risk into a few hours. The weather has to cooperate, the mix has to arrive on schedule, the placement and finishing have to keep pace with delivery, and the result has to cure correctly — and any of those can become a dispute. Was the slab poured below the temperature the spec allowed? Did the pump truck sit idle waiting on the next mixer, and whose fault was that? How many yards actually went in versus what was ordered and billed?
A daily log made on the day, with times and quantities, answers all of those before anyone has to argue about them. It is also your record for cure time — the reason work could not proceed the next day — which is one of the most common legitimate delay entries on a concrete job.
The example daily log (template)
Here is what a complete, defensible daily log for a footing-and-slab pour might look like. Every value here is an example for illustration only — fill in your own.
- Date / Project / Author: 2026-06-15 · "Example — Building A foundation" · Foreman, example template (not a real project).
- Weather: 62°F at start, rising to 78°F; clear, light wind ~5 mph; no precipitation. (Logged because mix temperature and curing depend on it, and weather is the #1 documented delay cause.)
- Crew on site: 6 total — 1 foreman, 3 finishers, 2 laborers. Pump operator (subcontracted) arrived separately. (Headcount drives labor cost and backs up the rest of the log.)
- Equipment on site: 1 concrete pump truck (rented), 1 power trowel, 2 vibrators, 1 skid steer. (Owned and rented machines present and in use — the basis for equipment cost and any idle-equipment claim.)
- Work completed: Placed and finished footings and slab-on-grade, grid lines A–D. Vapor barrier and rebar inspected and approved by inspector at 7:40 AM prior to pour.
- Quantities / production: 8 truckloads delivered; 78 cubic yards placed against 80 ordered (2 yards returned). Slab area ~3,100 sq ft. First truck 8:05 AM, last truck 11:20 AM.
- Delays / issues: ~35-minute gap between truck 4 and truck 5 (batch plant backlog) — pump and crew idle. Logged with times because idle-equipment and labor time may be recoverable.
- Notes / visitors / inspections: City inspector on site 7:40 AM (pre-pour rebar/vapor barrier — passed). Concrete supplier delivery tickets collected. Slab to cure; no foot traffic or follow-on trades until 2026-06-17.
- Photos: pre-pour rebar and vapor barrier; pump truck in position; placement in progress; finished slab; delivery tickets. (Dated images tie the written record to visible conditions.)
Why each field carries weight later
Read the example again as evidence rather than a status update. The weather line establishes that the pour was within spec. The crew and equipment lines support both job costing and any claim involving idle time. The quantities line — 78 placed against 80 ordered, with delivery times — is your reconciliation against the supplier's tickets and the owner's invoice. The 35-minute delay, logged with its cause and its times, is the difference between "we think we lost some time" and a documented, dated, attributable delay.
The cure note matters too: it is the contemporaneous reason the next day's follow-on work could not start, which preempts a "why weren't you working?" question before it is asked. None of this requires legalese — just specific, dated facts recorded while they were fresh.
In Vexor
In Vexor, this entire entry is one daily log inside the pour's job: the foreman captures weather, the crew on site, the equipment, the work completed, the yards placed, and the delay note, then attaches the pre-pour, in-progress, finished-slab, and delivery-ticket photos to the same record. It is timestamped automatically, so the 8:05 AM first truck and 11:20 AM last truck are anchored to real time, and the office and GC can see the pour the same day.
Adapting the template to your pours
The shape above works for most flatwork and foundation pours; tune the detail to the risk. On a hot- or cold-weather pour, expand the weather and mix-temperature notes and record any admixtures or protection used. On a structural or post-tension pour, add the cylinder/test sample count and the testing lab. On a pump-dependent pour, always log delivery and idle times — those gaps are where money is lost and where claims live.
The one rule that does not bend: make the entry on the day, on site, with quantities and times, and attach the photos to it. A pour log written from memory the next morning has lost exactly the property that made it worth writing.
Step by step
- 1
Record conditions before the pour starts
Log date, project, weather, and the pre-pour inspection result. Photograph rebar and vapor barrier before any concrete is placed.
- 2
Log crew and equipment on site
Capture headcount by role (yours and subs) and every machine present and in use — pump, trowels, vibrators.
- 3
Track quantities and times as trucks arrive
Note loads delivered, yards placed versus ordered, slab area, and first/last truck times against the delivery tickets.
- 4
Document any delay with its cause and times
If the pump or crew sits idle, record the gap, the times, and the cause (e.g., batch-plant backlog) the moment it happens.
- 5
Add cure note and attach photos, then save on site
Record the cure period that gates follow-on work, attach pre-pour/in-progress/finished/ticket photos, and save the timestamped entry before leaving.