// Commercial concrete contractors · Pour and cylinder records
Pour and cylinder records, assembled by placement for the project manager who submits them.
A placement leaves paper behind at the plant, on the deck, at the lab and in the field office. Before a record set goes out, someone has to pull the tickets, the pre-pour sign-offs, the cylinder breaks and any flatness report, then see what's still missing. In a free AI proof of concept, AI assembles copies of 20 to 30 pours your team already closed out. Your reviewer, the project manager who knows those files best, checks each set against what your team actually submitted.
- Closed pours
- 20 to 30
- Results judged
- None
- Records submitted
- None
// The one job
From scattered field paper to one record set per pour
The paper for a single elevated deck can sit in four places at once: delivery tickets with the superintendent, pre-pour sign-offs in a shared folder, break reports in somebody's inbox and a flatness report attached to a thread with the general contractor. Your project manager sorts all of it by placement, works out what that job's specification asked for, and chases whatever isn't there.
In the test, AI reads copies of those records and assembles them by pour: the delivery tickets for that placement, the pre-pour sign-offs, each cylinder break report, the floor flatness report where the specification calls for one, and a list of the records missing. It judges no result and submits nothing. Your reviewer compares each set with the one your team actually sent.
placement
// What makes it hard
Why a pour's file is harder than it looks
A ticket has to reach a place in the building. Old Dominion University's standards and New York's state master specification both ask for a batch ticket showing project name and number, date, mix type, mix time, quantity and water added, then say to record the approximate location of final deposit in the structure. The City of Madison's section for the Warner Park community center wants each test report to carry truck and batch ticket numbers and the location in the work the samples represent, and each ticket to state mix identification, admixtures, design strength, aggregate size, design air and slump, and the water that may be added at the site. Ticket to location and ticket to cylinder set are the two links that let a file hold together by placement.
What counts as missing depends on that project's sampling rule. Wisconsin's state master specification, dated April 14, 2025, samples each class of concrete at least once a day, once per 150 cubic yards, or once per 5,000 square feet of slab or wall. Massillon City Schools' Westside PK-3 section samples each day's pour of each mixture over 5 cubic yards and under 25, plus one set for each additional 50 yards. The University of Maryland takes two 6-by-12 or three 4-by-8 laboratory-cured cylinders at 28 days for acceptance, and Massillon also calls for three-cylinder lab-cured and field-cured sets at seven days and two-cylinder sets at 28. The draft counts what that project's own documents say should exist, then lists what it can't find.
Two kinds of cylinder answer two different questions. Maryland's standard says field-cured cylinders are not for strength acceptance and can instead support early form removal, if the structural engineer approves, or an early end to moisture curing. Powhatan County, Virginia's statement of special inspections lists field-cured tests before stressing or stripping on a separate line from laboratory-cured strength tests, and it requires a final report of special inspections before final building inspection approval. New York City's Bulletin 2009-026 caps initial curing at 48 hours, and cylinders staying on site longer go into final curing there. The set keeps those reports apart, so nobody reads a stripping break as an acceptance break.
Sign-offs and forms change with the owner and the city. Massillon wants formwork, reinforcement, embedded items and vapor retarder confirmed and inspections done before placing, with 24 hours' notice to the architect and testing agencies. Old Dominion uses an inspection request form at least 24 hours ahead. A September 2010 specification in the City of Portland, Maine's permit files calls for 48 hours' notice to the special inspector and approval or waiver before placement. New York City's bulletin stops concrete work if the laboratory on site doesn't match the TR2 filing, and the TR2's test report section runs cylinder ID, slump, air, temperature, unit weight, placement location, total yards and break strength, with original lab reports attached before sign-off. California's Division of the State Architect lists a concrete placement record in its project inspector job file review, and its inspection card manual says test reports have no required format.
Flatness reports arrive on their own clock. Massillon wants floor flatness and levelness measured under ASTM E1155 within 72 hours of finishing, while Wisconsin leaves a blank for 24, 48 or 72 hours and each project fills it in. Wisconsin also limits levelness tolerances to non-sloping slabs on ground and slabs still shored at testing, and defines local test areas by joints on grade and by column and wall lines on elevated slabs. The set shows the report, its date and the areas it covers. What your reviewer will check is whether each set has the right tickets, breaks and sign-offs for that pour and names the real gaps. Whether any result passes stays with the testing agency, the special inspector and the engineer of record, and nothing here is legal or engineering advice.
// What you send
Pours your project managers already closed out
20 to 30 closed pours
A mix of footings, slabs on grade, elevated decks and, if you place them, tilt-up panels, each with the record set your team actually submitted.
The field paper behind them
Delivery tickets, pre-pour sign-offs, cylinder break reports, floor flatness reports and any placement logs your superintendents keep, as scans or exports.
What each job required
The Division 03 sections, the statement of special inspections or its local equivalent, and any city or owner forms those pours had to fit.
Signed NDA, then copies
The NDA is signed before any record moves. We never sign in to your project management system, your document system or a lab's portal. Records that can't leave your office become look-alikes, built with your reviewer.
// Before it starts
Settled before a record is copied
The owner writes these down first, because a missing record has to mean the same thing to everyone.
- Your reviewer
- Named by the owner, usually a senior project manager
- Success criteria
- In writing, by pour and record type
- Sample
- Your reviewer's pick, with slabs, decks and at least one flatness specification
- Missing means
- Measured against each job's own documents
- Who submits
- A project manager submits every record
- Price
- A range for the live job, quoted first
- NDA
- Signed before any record moves
// How it's judged
Each record set beside the one your team sent
| On the same 20 to 30 pours | What your team submitted | The AI draft |
|---|---|---|
| Delivery tickets tied to the right placement | Filled in from your pours | Filled in from your pours |
| Pre-pour sign-offs present and dated | Filled in from your pours | Filled in from your pours |
| Cylinder break reports tied to their pour | Filled in from your pours | Filled in from your pours |
| Lab-cured and field-cured sets kept apart | Filled in from your pours | Filled in from your pours |
| Flatness reports where the specification calls for them | Filled in from your pours | Filled in from your pours |
| Records missing, named specifically | Filled in from your pours | Filled in from your pours |
// After a yes
About 30 days on live placements
Once your reviewer says yes, the same job runs on new pours for about 30 days.
A project manager submits every record after reading the set, and the lab and the inspector keep reporting as they do today.
The live job's price is fixed before you sign, and the next job is its own decision, priced on its own, with monthly support after that.
// What could come next
Where pour records could lead
- 01Next
Structural note takeoffs
Bid sets read element by element into a draft takeoff sheet for your estimator.
- 02Then
Closeout record binders
Approved submittals and field records pulled into the turnover package a general contractor asks for.
- 03After that
Cold and hot weather placement logs
Temperature readings and protection notes listed by placement beside what the specification asked for.
// One hard limit
It never judges a break and never submits a record.
The test works on copies of closed pours. It never opens your estimating system, a live bid or your project management system, never prices a bid, and never decides whether a cylinder, a slab or a flatness number passes. A project manager submits every record, and questions about a result belong to the testing agency, the special inspector and the engineer of record. Nothing on this page is legal or engineering advice.
Priced per job. You get a range before the proof of concept and a fixed price before you sign.
The range comes on the call, from how many pours you close out in a month and how many owners or cities ask for their own forms.
// Questions
Questions about pour records
Will the AI tell us whether a cylinder break passed?
Our delivery tickets are handwritten and some are photos. Can it read them?
What if the lab sends its reports straight to the general contractor?
Does it connect to our project management system?
Who decides what counts as missing?

Rob Eason, founder
// Book a proof of concept call
Start with pours you've already closed out.
Half an hour with Rob about your company, your role and how your project managers build a record set today. Tickets, lab reports and sign-offs stay with you until the NDA is signed.
- Co-owned a 60-employee financial services firm and sold his share to his partner.
- Ran GOSO Technologies, a Boston solar company rated 5/5 across 24 Google reviews.
- 5/5 across 83 reviews in HighLevel's Certified Admin Directory.
- 4.3/5 from 6 Google reviews of Massmarket AI.
- Every directory and Google review, critical ones included, is shown word for word at massmarket.ai/reviews.
- Takes every proof-of-concept call himself.
