Concrete slump and water-added records before the truck leaves

Direct answer

A concrete slump and water-added record should prove which truck was tested, which mix was delivered, when the sample was taken, what the fresh-concrete test results were, whether water or admixture was added, who authorized the adjustment, how the load was mixed after adjustment, what the retest showed, and whether the load was placed, held, or rejected.

The record has to be built before the truck leaves because the evidence is still present: the driver, ticket, batch time, water meter or held-back water note, sample location, test equipment, field conditions, and people who made the decision. Once the load is in the slab and the ticket is gone, the argument becomes much harder to reconstruct.

Use this as documentation guidance only. Current project specifications, the ready-mix ticket, testing agency procedures, ASTM and ACI requirements adopted by the project, supplier instructions, owner requirements, and the responsible engineer or authority control the actual acceptance decision.

A slump number is not the whole record

A number by itself does not explain whether the sample was representative, whether the test was preliminary or for acceptance, whether the truck was still within the allowed range, or whether anyone changed the load after that number was taken. A note that says 3 inch slump, added water, placed is too thin for a serious record.

The field packet should tell the sequence. It should show the truck arrived, the ticket was reviewed, the correct mix was verified, the sample was taken under the required procedure, the fresh tests were recorded, and any adjustment was handled under the project rules before the load was accepted.

That sequence matters because slump is often used as a quick field signal, but it is not the only acceptance concern. Air, temperature, density, unit weight, cylinders, ambient conditions, time, and placement location can all matter depending on the specification and the concrete use.

Start with the ticket and sample

The ticket is the anchor for the record. Capture the supplier, truck number, ticket number, mix ID, batch time, load size, target slump or slump-flow information when shown, water held back when shown, admixtures, placement location, and any project-required delivery notes.

Then connect the ticket to the sample. The packet should say who sampled, where the sample came from, whether it was a preliminary consistency check or the acceptance sample, when the sample was taken, and which tests were run from it.

Keep the preliminary check separate from the acceptance record. A quick check near the start of discharge can help the crew decide whether an adjustment is needed, but it should not be mislabeled as the acceptance test when the project requires sampling under a specific standard or agency procedure.

Water-added notes need custody

A water-added note is a custody record. It should not say only water added. It should say how much water was added, where the quantity came from, who requested it, who authorized it, whether the ticket allowed it, when it was added, how the drum was mixed afterward, and what the retest showed.

If the project allows jobsite adjustment, the record should still show that the adjustment stayed inside the allowed slump, water-cementitious ratio, ticket, and specification limits. If the project prohibits water addition, the record should show that the issue was escalated instead of quietly changed in the field.

When the record is strong, later reviewers can tell whether the load was brought into range or whether a limit was crossed. That protects the project team, supplier, testing agency, and owner from having to guess from a single handwritten word on a ticket.

Minimum acceptance packet

Use the project form first. Add a short packet only where it supports the required report and ticket. The goal is not a second paperwork system. The goal is a record that makes the required form understandable when someone reviews it later.

At minimum, the field packet should cover the items below.

Before the truck leaves checklist

The best time to fix a weak record is while the truck is still in front of the crew. Before the driver leaves, the foreman, inspector, or project representative should be able to answer the questions below from the ticket and packet.

If the answer is not clear, stop and complete the record before the load becomes a memory problem.

• Confirm the ticket, mix ID, truck number, placement location, and batch time are readable.
• Mark whether the sample was preliminary or the acceptance sample.
• Record the slump and any other required fresh-concrete values with time and tester.
• Record the exact amount of water or admixture added, or write none if no adjustment was made.
• Record who requested and authorized any adjustment.
• Confirm the required mixing step after adjustment was completed under the project procedure.
• Retest and record the final value before release when adjustment affects acceptance.
• Write the final disposition: placed, held, rejected, or escalated.
• Attach photos only where they clarify the ticket, meter, sample setup, or disputed condition.

Weak and strong truck notes

Weak note: slump low, water added, ok.

That note does not show the mix, ticket, sample type, original value, quantity of water, authorization, mixing after adjustment, retest value, or final decision.

Stronger note: truck 42, ticket 11873, mix 4000-A, east slab pour. Preliminary check showed low consistency before significant discharge. Inspector and superintendent reviewed ticket water note and project limit. Added 8 gallons shown on ticket, mixed under supplier/project procedure, retested acceptance sample. Final slump and temperature recorded on field report. Load accepted for east slab placement by site representative.

The stronger note is useful because it answers the later questions. It shows what was checked, what changed, who knew, and what record supports the decision.

Common mistakes

The first mistake is writing a slump value without sample context. A reviewer needs to know whether the value came from a preliminary check, acceptance sample, or informal observation.

The second mistake is recording water added without the amount. A later dispute usually turns on quantity, authorization, and whether project limits were still respected.

The third mistake is forgetting the retest. If the load was adjusted because the first result was out of range or questionable, the record should show the final value that supported the decision.

The fourth mistake is letting the ticket and field report disagree. If the ticket says water was added and the field report says no adjustment, the packet creates its own dispute.

Specification and safety limits

This field note is not an ASTM procedure, ACI certification guide, mix-design instruction, engineering approval, or authority to accept or reject concrete. Qualified personnel, the adopted standards, the testing agency, the project specifications, the ready-mix supplier, the owner, and the responsible engineer control the work.

Do not use this checklist to bypass required sampling, testing, cylinder handling, personal protective equipment, site traffic controls, washout rules, environmental controls, or project approval steps. The record helps preserve the decision. It does not replace the decision authority.

Sources checked

• American Concrete Institute, Concrete Field Testing Technician Grade IUsed to frame fresh-concrete field testing as a defined knowledge area covering sampling, temperature, slump, density, air content, and field specimens.
• NRMCA, CIP 26 - Jobsite Addition of WaterUsed for water-added documentation, ticket signoff, adjustment limits, and retest themes.
• NRMCA, CIP 31 - Ordering Ready Mixed ConcreteUsed for slump/slump-flow tolerance and mix-design limit boundaries.
• FHWA, HMEC Module G Testing Fresh Concrete Laboratory ManualUsed for sampling, timing, calibration, and fresh-concrete testing workflow context.

Related guides