Liquid nitrogen concrete cooling, lower 48 delivery
724-809-3385  ·  info@hydrotechtesting.com

Specifications

Concrete Temperature Monitoring and the Cooling Record

Projects that care about temperature usually need more than one kind of reading. The cooling record shows what happened to the fresh concrete. In-place monitoring shows what happened in the pour afterward. They should not be asked to impersonate each other.

Two records, two jobs

The cooling record is the set of readings taken on the fresh concrete as part of the injection work, or at the measurement point the specification names for placement temperature. It should identify the load or the time, the target, and the temperature that was achieved, in a form the project can file. That is the record we ordinarily produce.

In-place monitoring is the set of sensors, often thermocouples, cast into a mass placement to track peak temperature and differential over hours and days. It is how a thermal control plan knows whether those limits were met. It is usually the contractor’s or the testing laboratory’s instruments and data, not a by-product of a lance.

A project that keeps only one of these records, when the specification asked for both, has a gap. A project that treats a drum reading as a peak temperature has a confusion. Write down which number came from where.

A rebar cage being set for a foundation east of Queens Boulevard
Photo: MTA Capital Construction Mega Projects. CC BY 2.0, via Wikimedia Commons.

Who owns which reading

Unless a job is written otherwise, we own the fresh-concrete temperatures associated with the cooling scope. The laboratory or the contractor owns the in-place array. The engineer owns the interpretation against the limits. If a meeting tries to move one of those duties without changing the contracts, say so in the meeting, not after a limit is missed.

The form of the cooling record should be agreed before the pour if a submittal or a plan requires a particular format. Some projects want a simple log. Some want the readings attached to ticket numbers or load IDs. Ask early. See TCP documentation.

What a record cannot do

A complete cooling log cannot prove a peak or a differential. A complete sensor file cannot prove that a given truck was inside a placement cap if no one measured the fresh concrete. Neither record can repair a load that was out of specification and placed anyway. The point of writing this down is not decoration. It is so the project can see what was actually done.

What to send

Send the limits, the required measurements, and who the plan currently assigns them to. If you want us to match a particular log format, attach an example. If in-place monitoring is still unassigned, that is a plan problem to solve with the engineer, not a sentence we will quietly absorb.

Do you leave sensors in the pour?

Not as a standard part of the cooling scope. In-place monitoring is typically a separate arrangement.

What goes in the cooling record?

The fresh-concrete readings, the target, and enough identification of load or time for the project file. The exact format should follow what the plan or the specification asked for.

Can one report cover both placement and peak temperatures?

They can be filed together. They should still be labeled as different measurements from different instruments.

Get a Quote

Send Us the Spec and the Pour Date

Tell us the maximum placement temperature, the volume, the location, and when you are pouring.