A daily concrete pour log is the record of a pour as it happened: which concrete arrived, when, what was added to it on site, what the tests said, how it was placed, finished and cured, and what went wrong. It is the document everyone reaches for when a cylinder breaks low, a slab cracks or an invoice is disputed — and it can only be written on the day, because nobody remembers truck seven's slump a month later. This log keeps one row per truck, records the spec limits at the top so each reading can be judged against them, and lifts rejected loads, water beyond the allowance and out-of-range temperatures into a summary of findings. You can fill it in here and download a finished PDF without creating an account.
What a pour log is for
Three people read a pour log after the fact. The engineer, when a strength result comes back low and they need to know which loads went where and what happened to them. The project manager, when the supplier's invoice says 112 yards and the takeoff said 98. And whoever is defending a claim, when a slab has cracked or curled and the question is whether it was cured, protected and loaded the way the spec required.
Each of those questions is answered by something you can only see on the day: a ticket, a time, a thermometer reading, a hose going into a drum. So the log is written as the pour runs, not reconstructed from memory at the end of the shift.
One row per truck
Every load gets its own entry: the ticket number, the truck, when it was batched, when it arrived, when discharge started and finished, how much it carried, and where it went. Photograph the ticket — it carries the mix, the batch weights and the time, and it is the first thing anyone will ask for.
The two numbers that matter most are the batch time and the water. Most specifications set a limit on how long concrete can sit in the drum after batching, and a limit on how much water can be added on site without changing the mix. A load that is late, or that has had a hose in it beyond the allowance on the ticket, is a different concrete from the one that was approved. The log flags both, and asks who authorized any water that was added.
Speak while you walk, and the document writes itself: "truck six, ticket 40812, batched 9:14, arrived 9:52, ten yards, fifteen gallons added, slump four and a half" fills the row.
Tests, temperatures and the spec limits
Write the spec limits at the top of the log before the first truck — strength, slump or spread, air, concrete temperature, the time limit and the water allowance — so every reading can be judged against them on the spot instead of later. Record the concrete temperature on every load if you can; it costs ten seconds with a probe and it is the reading most often missing when a hot-weather or cold-weather pour goes wrong.
When a test is outside the limits, record what happened next: a retest that passed, a load rejected, or a load accepted after the engineer was told. Each of those is a different story, and the log should tell the right one.
Cylinders are evidence too
Strength specimens are only as good as their first two days. Note which load each set was taken from, how many specimens, what ages they will be broken at, and how they were stored on site — in a curing box at a controlled temperature, out of the sun and protected from frost and knocks. A low break from a cylinder that spent the night on a truck bed in freezing weather says more about the cylinder than the concrete.
Sampling frequency is set by the spec. A common US pattern is at least one set per day for each mix, plus another for every 150 cubic yards or so — but the project specification decides.
Curing and protection are part of the pour
The pour is not over when the finishers leave. How the surface was cured, how soon curing started, and how the concrete was protected from heat, wind, frost, rain and early loading all decide what strength and durability it ends up with. Record the method and the start time, and in hot or cold weather the measures taken and whether the concrete stayed inside its temperature limits for the protection period.
Common questions
What should a concrete pour log include?
The pour location and element, the mix and quantity ordered, weather and temperatures, every truck with its ticket number, batch and discharge times, volume, any water added, and test results, plus how the concrete was placed, consolidated, finished and cured, which specimens were taken, any delays or rejected loads, and the total placed against the total ordered.
Who fills in the daily pour log?
Usually the contractor's superintendent or concrete foreman, often alongside the testing technician's own field report. On projects with special inspection, the inspector keeps a record of their own; this log is the contractor's account of the whole pour, trucks and all.
How much water can be added to a concrete truck on site?
Only what the mix design and the ticket allow, usually stated as an amount that can be added without exceeding the approved water-cement ratio, and only with the authority the specification names. Water beyond that allowance weakens the concrete and should be refused or reported. This log flags it as a finding.
How long can concrete stay in the truck?
Many US specifications allow about 90 minutes, or a set number of drum revolutions, from batching to the end of discharge unless the engineer agrees otherwise. Hot weather shortens the practical limit. Check the project specification and record the batch time on every row.
What temperature should concrete be when placed?
The spec decides. As a general guide, many specifications set an upper limit around 90 to 95 °F for fresh concrete and a lower limit around 50 °F, adjusted for the size of the section and the weather. Write the project's limits at the top of the log and record the temperature of each load against them.
Is this log scored?
No. A pour log is a record, not a pass mark. Answers that are problems — a rejected load, water beyond the allowance, a test or temperature outside the spec, an unplanned cold joint, a form that moved — are listed in the report's summary of findings so they cannot be missed.