The 28-day compressive strength test is the commercial concrete sub’s irreversible-phase risk window.
Rough-in inspections fail and get corrected. A low concrete break can’t be corrected — the concrete is already in the structure, it’s already cured, and 28 days of construction activity has happened around it. At that point the PM either has a pour record that explains what happened or he doesn’t. The record doesn’t get built after the break comes back low. It gets built the day of the pour, before the finishing crew starts, while the trucks are still on site.
Most commercial concrete subs have a version of pour documentation. Batch tickets in a folder. A note in the daily report. The foreman’s memory of how many cylinders got cast. That version isn’t the problem until a break comes back at 3,400 psi against a 4,000 psi spec and the structural engineer asks for the pour record — and the “record” is a daily report that says “poured Floor 3 East, 8 trucks” and a folder of batch tickets that may or may not all be there.
What a commercial concrete sub actually needs is a pour tracking system built for the field: what gets logged before the first truck arrives, what gets captured truck by truck during placement, and how the 28-day break result closes out the record. This is what that looks like.
How to Document Concrete Pour Progress
Concrete pour documentation runs in three stages. The table below is the field reference — what gets captured at each stage, and why it matters when the 28-day break comes back.
| Stage | What to Capture | Why It Matters |
|---|---|---|
| Pre-pour | Structural inspection clearance (inspector name, time, any deficiencies) | Phase gate — pour doesn’t start without it; first document the engineer asks for |
| Pre-pour | Reinforcing photos by zone, before forms close | Only record of what’s below the surface once concrete is placed |
| Pre-pour | Weather conditions (air temp, concrete temp on first truck, wind, RH) | Defensible context if break result is low |
| During | Batch ticket log (ticket #, batch time, arrival time, discharge time) per truck | Out-of-spec trucks traceable by ticket; rejected truck disposition documented |
| During | Cylinder sample record (cast time, truck ticket #, number of sets, who cast, slump, lab) | Chain of custody for the 28-day break — without it, a low result has no context |
| During | Pour start time, end time, pump location start/end if multiple pumps | Reconstructs placement sequence if a localized strength question arises later |
| After | 28-day break result logged against pour date, zone, and cylinder set | Closes the pour record; if it fails, the pre-pour and during record is already built |
| After | Curing method and duration (type, start date, end date) | Required for strip authorization; explains break timing if result comes in early |
Each row is a field entry, not a memory. The foreman who logs these during the pour has a record. The foreman who reconstructs them on Friday has a document that will fail under scrutiny.
Before the Pour: Three Things That Must Be on Record
Structural Inspection Clearance
On a commercial building, every structural concrete pour requires a pre-pour inspection — the structural engineer of record or their special inspector verifies that the reinforcing, formwork, and embedded items match the drawings before concrete is placed.
That inspection clearance is a phase gate. The pour doesn’t start until it’s cleared. The record of the clearance — inspector name, inspection time, any deficiencies noted and how they were corrected — goes into the pour log before the first truck arrives. Not after. If a dispute arises about the structural integrity of the slab, the inspection clearance record is the first document the structural engineer and the building department will ask for. If it was captured at the time of inspection, it’s a dated record. If it’s reconstructed, it’s a guess.
Reinforcing Photos
Before the forms are closed and the concrete covers the rebar, photograph the reinforcing in place. Zone by zone, floor by floor, before any concrete. The photo that shows the bar size, spacing, and cover — taken before the pour — is the evidence that the slab was built as designed. The photo taken after the pour can’t show anything.
This is especially important at locations where the drawings show congested reinforcing, unusual bar placement, or post-installed anchors. These are the areas the structural engineer will scrutinize first if a strength question arises. The photo taken at the point of placement establishes what was there.
Pre-Pour Conditions Log
Weather conditions at pour time affect both the placement and the cure. High ambient temperature increases the rate of hydration and can cause plastic shrinkage cracking. Low temperature slows strength gain. Wind accelerates evaporation. These aren’t just note-worthy — they’re defensible variables if the break comes back low.
Record before the first truck: ambient temperature, concrete temperature on first truck, wind speed and direction if notable, cloud cover and sun exposure. Takes 90 seconds. Establishes the environmental context for the entire pour.
During the Pour: What Gets Logged Truck by Truck
Batch Ticket Documentation
Every ready-mix truck arrives with a batch ticket from the plant. That ticket shows the mix design (design strength, cement type, water-cement ratio, admixtures), the batch volume, the plant it came from, and the batch time. The batch time matters: concrete placed more than 90 minutes after batching, or that has had more than 300 revolutions of the drum, is out of spec under ASTM C94.
For each truck: ticket number, plant name, batch time, arrival time on site, discharge start time. If a truck is rejected — over-age, low slump, wrong mix design — document the rejection: ticket number, reason, disposition. The rejected truck that went back to the plant is fine. The rejected truck where the driver added water and the super let it go anyway is a future problem.
Cylinder Sample Records
Compressive strength cylinders are the concrete sub’s most important field documentation. Every set of cylinders is the physical record of the concrete placed during a specific period of that pour. The chain of custody starts at the pour — who cast the cylinders, from which truck, at what time, how many sets, and which lab they were delivered to.
For each set of cylinders: cast time, truck ticket number cylinders were sampled from, number of cylinders in the set (typically four — two for 7-day breaks, two for 28-day breaks), who cast them, field slump and air content at time of sampling, and lab name and delivery confirmation.
The 28-day break result is tied to this sample record. If the break comes back low and the chain of custody is complete — the sample was cast from a specific truck, at a specific time, by a specific person, and delivered to the lab — the structural engineer can determine whether the low result is a sampling issue, a curing issue, or a mix design issue. Without the chain of custody, the low result is just a number with no context.
Pour Progress Times
Start time of pour, end time of pour, start time of finishing crew. These three timestamps reconstruct the pour sequence if questions arise later about when specific areas of the slab were placed. On a large elevated deck pour with multiple pump locations, the start and end times by pump location establish which part of the deck was placed when — relevant if there’s a localized strength question.
After the Pour: Connecting the Record to the Break
The 28-Day Test Follow-Through
The pour log doesn’t end when the finishing crew wraps. It ends when the 28-day break results are received, logged, and filed against the pour record.
When the lab reports the break: record the result against the pour date, the cylinder sample set, and the floor zone. If the result passes, close out the pour record. If it fails, the pour log is already built — the batch tickets, the inspection clearance, the cylinder chain of custody — and the structural engineer has a complete record to evaluate.
A pour that passes its 28-day break with a complete pour record is fully documented and defensible. A pour that fails its 28-day break without a pour record is a structural dispute with no paper trail on the sub’s side.
The Daily Report Connection
The pour log and the daily report are not the same document. The daily report is the communication document that goes to the GC — crew count, work areas, any issues. The pour log is the technical record of what was placed, under what conditions, with what documentation.
Both should generate from the same source data. When the foreman logs the batch tickets, cylinder casts, and pour start and end times in the field during the pour — that data populates both the pour log and the daily report. The pour conditions are captured once, at the point of work, and they flow into both records automatically.
The foreman who reconstructs the pour log from memory at 5 PM is building an argument. The foreman who logs it during the pour is building a record.
What Makes a Pour Record Hold Up Under Dispute
When a 28-day break comes back low, the structural engineer’s first questions are: Was the pre-pour inspection completed and documented? Is there a cylinder chain of custody? Were the batch tickets logged by truck? What were the weather conditions at placement?
If the answer to all four is a dated field record — inspector’s name and clearance time, cylinder cast record tied to a specific truck ticket, batch ticket log with arrival and discharge times, pre-pour weather log — the engineer has something to evaluate. He can determine whether the low break is a mix design issue (plant problem), a sampling issue (cylinders not cured properly), a placement issue (water added on site), or an environmental issue (pour in 95-degree heat without hot weather measures).
If the answer is a daily report that says “poured Floor 3, 8 trucks, passed inspection” and a partial stack of batch tickets, the structural engineer has no context. At that point the investigation is adversarial: the building department gets involved, the GC starts looking for who pays for coring, and the sub is defending a pour that happened six weeks ago with whatever he can reconstruct.
The difference between those two outcomes isn’t the result — both started with a low 28-day break. The difference is whether the pour record was built at the point of work.
Three specific details that pour records typically lack and engineers ask for first:
Cylinder curing condition. Were the cylinders stored in the field (temperature-matched cure per ASTM C31) or transported to the lab the same day? If field-cured overnight in a job trailer that hit 45°F, the 28-day break will be suppressed. That’s not a mix problem — it’s a curing protocol problem. Without the curing condition in the record, the low break looks like a mix problem.
Slump at sampling vs. slump at delivery. The batch ticket shows the plant slump. The cylinder sample record should show the slump at the time of sampling. If those numbers diverge significantly — especially if field-added water is suspected — the discrepancy is the evidence. Without slump at sampling, the comparison can’t be made.
Rejected truck disposition. If a truck was rejected, where did it go? Back to the plant is fine. Poured in a non-structural area is documented. If the foreman can’t say — and there’s no rejection record — the investigation starts wondering whether the low break is from a batch that shouldn’t have been placed.
These are the details that batch ticket folders don’t capture. They’re captured in the pour log, by the foreman, at the point of work.
What to Start Capturing on the Next Pour
If the current pour documentation is “batch tickets in a folder and notes in the daily report,” the improvement is sequential:
- Pre-pour: photograph the reinforcing before the forms close, log the pre-pour weather conditions, record the inspection clearance
- During: log each truck’s ticket number and arrival time, record the cylinder sets as they’re cast
- After: receive and file the 28-day break against the pour record
None of these steps adds significant time. The foreman who logs truck arrivals on his phone as they happen, photographs the rebar before the pour, and records cylinder sets at casting builds a complete pour record in the normal course of the pour. The foreman who tries to reconstruct it afterward builds a document that will fail under scrutiny.
For how pour-phase cost codes connect the pour record to the PM’s labor tracking, see concrete contractor time tracking. For what the commercial concrete software stack needs to support this documentation workflow, see concrete contractor software. For how the ready-mix dispatch tools that return for “concrete pour tracking software” compare to what a specialty concrete sub actually needs to capture in the field, see concrete pour tracking software.
See how LogLoon’s field reporting works for commercial concrete subs, or check the pricing — it’s on the website.