Concrete maturity method and temperature monitoring field guide

The maturity method, and why the slab tells you its own strength

The concrete maturity method estimates the in-place compressive strength of concrete in real time from the concrete's own temperature history. A small sensor cast into the fresh pour logs temperature over time, runs that record through a maturity function, and reads the result against a calibration curve for that exact mix. The output is a strength number in psi for the concrete sitting in the slab right now, not a cylinder in a lab across town.

That distinction is the whole point. Strength testing with cylinders tells you what a separately cured specimen did. The maturity sensor tells you what the concrete in the structure is doing, at the spot you care about, without waiting on a 7-day or 28-day break to come back. When the sensor says the deck has reached stripping strength, you strip. When it says the slab is ready to post-tension or open to traffic, you move.

Maturity does not replace curing and it does not replace acceptance cylinders. It rides alongside both. The concrete still has to be cured to gain the strength the curve promises, and the project still proves f'c with standard-cured cylinders. What maturity adds is a real-time, in-place strength number that lets the schedule move on data instead of on a fixed calendar guess.

Why use maturity instead of waiting on cylinder breaks?

Speed, and a strength number that actually matches the structure. Field-cured cylinders meant to track the slab are cured next to the work in a box, and they rarely see the same temperature the slab sees. A small cylinder loses and gains heat faster than a thick element, so the cylinder and the slab drift apart. The cylinder can read low when the mass of the slab is actually warmer and stronger, which costs you days you did not need to wait. It can read high on a thin section that ran colder than the box.

Maturity closes that gap. The sensor measures the concrete in place, so the strength estimate reflects the real temperature history of the real element. On a fast-track job that turns into schedule. You strip forms, stress tendons, saw the joints, and open the deck the moment the in-place strength is there, often well ahead of the calendar date a fixed waiting period would have set.

The other gains are fewer field-cure cylinders to make and break, a continuous temperature record instead of a couple of snapshots, and a defensible data trail behind every early strip or early opening. The catch is that all of it rides on one thing being right. The calibration.

How does temperature turn into strength?

Concrete gains strength because cement reacts with water, a process called hydration, and that reaction runs faster when the concrete is warm and slower when it is cold. Strength is the product of how long the concrete has been reacting and how warm it was the whole time. Hold a mix warm and it reaches a given strength in less time. Let it run cold and the same strength takes longer.

The maturity index is the single number that folds those two variables, time and temperature, into one. Two slabs of the same mix that reach the same maturity index have gained about the same strength, even if one got there in two warm days and the other took five cold ones. That equivalence is what lets a temperature log stand in for a strength test.

There is a floor. Below a certain temperature, hydration effectively stops and the concrete gains no maturity no matter how long it sits. That is why a pour that freezes early can show calendar age with almost no strength behind it. The maturity function carries that floor in its math, which is the next piece to get right.

Nurse-Saul or Arrhenius: which maturity function?

ASTM C1074 gives two maturity functions, and the calibration has to declare which one it uses. The Nurse-Saul function is the common one in the United States. It treats the rate of strength gain as a straight-line function of temperature and reports the maturity index as a time-temperature factor, the TTF, in units of degree-Celsius-hours. It needs one parameter, the datum temperature, the temperature below which the mix is assumed to stop gaining maturity. ASTM C1074 includes a procedure to measure the datum temperature, and notes a common assumed value near 0 degrees C for Type I cement without admixtures.

The Arrhenius function is the other option. It treats the rate as an exponential function of temperature, which is closer to the real chemistry, and reports the maturity index as an equivalent age at a reference temperature, usually in hours. It needs the activation energy instead of a datum temperature. ASTM C1074 gives a procedure to determine it, or a commonly cited assumed range of 40,000 to 45,000 J per mol for a Type I cement.

For most field work the Nurse-Saul TTF is accurate enough and simpler, which is why the trade leans on it. Arrhenius equivalent age is the better choice when temperatures swing wide or the mix carries heavy admixtures. Whichever the calibration uses, the sensor and the curve have to use the same one. Confirm the function and its assumed constants against ASTM C1074 and the mix, because a datum temperature or activation energy that does not fit the mix pushes the strength estimate off.

How do you calibrate the maturity method?

The calibration is the strength-maturity relationship for one specific mix, and it is the foundation the whole method stands on. Without it, a maturity number is just a temperature log. ASTM C1074 lays out the procedure, and it is not optional.

The work happens in the lab before or alongside the first pour. You batch the actual mix design and cast a set of cylinders, commonly on the order of 17, with temperature sensors embedded in two of them so the maturity is logged as they cure. The cylinders cure together in a controlled moist condition. You then break sets of them at a spread of ages, commonly 1, 3, 7, 14, and 28 days, three cylinders per age, recording both the compressive strength and the maturity index at each break. Plot strength against maturity and you get the calibration curve. From then on, any maturity value off a field sensor reads across to a strength on that curve.

The break ages are chosen to bracket the strengths the schedule cares about, the stripping and stressing and opening numbers, not just the 28-day f'c. Two practical rules ride on top of the procedure. Cure and handle the calibration cylinders right, because a sloppy calibration poisons every field reading that follows. And confirm the exact procedure, the function, and the constants against ASTM C1074 for the edition in play. The curve is the asset. Build it carefully or do not trust the method.

The calibration belongs to one mix

A maturity calibration is valid for the exact mix it was built from, and nothing else. Change the cement source, the supplementary cementitious materials, the water-cement ratio, the admixtures, or the aggregate, and the strength-maturity relationship moves. The old curve now reads the wrong strength off the right temperature, and it reads it confidently, which is the dangerous part.

This is where the method gets people. The crew runs a calibration in the spring, the plant swaps a fly ash source or bumps an admixture over the summer, and the field keeps reading the spring curve. The temperature log is honest. The strength number is wrong, because the concrete in the slab is not the concrete the curve was made from. A mix change is a new calibration, full stop.

Treat the curve like it is stamped to a mix number. When the mix design changes on paper, the maturity calibration changes with it before that concrete is trusted for a strength call. If you cannot say which calibration goes with the concrete in the slab, you do not have a maturity reading you can defend.

The sensors and data loggers

The hardware is a temperature sensor and a logger embedded in the fresh concrete. The older arrangement is a wired probe or thermocouple cast into the pour with the lead run out to a handheld reader or a datalogger box. The newer arrangement is a self-contained logger with the battery and memory in one unit, dropped in and tied off, read later by cable or wirelessly.

What matters is that the sensor sits in the concrete and records temperature on an interval tight enough to catch the curve, commonly every 15 to 30 minutes through the early gain. The logger either computes the maturity index itself or hands the raw temperature record to software that does. Either way the chain is the same: temperature in place, maturity from the function, strength from the calibration.

Sensors are mostly one-pour consumables. The probe stays in the concrete, and on the wired types the reusable part is the reader, not the lead. Budget the sensor as a cost per monitored location per pour, and place each one where the reading will actually drive a decision.

Where does the maturity sensor go?

At the location that controls the decision, which is usually the coldest, slowest-gaining spot in the element. That is the critical location, because it reaches strength last. If the sensor sits in the warm, fast part of the pour, it reads strength the slow corner has not made yet, and you strip or stress against concrete that is not ready.

On a slab or deck, that often means an edge, a corner, an exposed face, or the section over the coldest part of the formwork, not the warm middle of a thick mass. In cold weather it is the spot most exposed to the ambient or the least protected by blankets. Pick it by asking where this element will be weakest when you want to make the call.

Set the depth where it represents the element, commonly near the level that governs the structural decision rather than right at a hot or cold surface, and protect the sensor and its lead from the vibrator, the screed, and foot traffic. On a critical pour, put sensors at more than one location so you read the real spread, not a single hopeful point. The reading is only as good as the spot you chose.

The field workflow, start to finish

The method runs in a fixed order, and skipping a step breaks the chain.

First, calibrate the mix in the lab and load that strength-maturity curve into the reader or software. Second, embed the sensor at the critical location as the concrete is placed, and confirm it is logging. Third, let the sensor record temperature through the cure while the concrete gains strength. Fourth, read the maturity index off the sensor and convert it to in-place strength against the calibration curve for that mix. Fifth, make the call: strip forms, release shoring, stress tendons, saw the joints, or open to load when the in-place strength meets the required number. Sixth, keep the record.

The order is not negotiable because each step feeds the next. No calibration, and the maturity index means nothing. Wrong location, and the strength is for the wrong concrete. No record, and you cannot defend the early strip when someone asks. Run it in sequence every pour and the method is fast and clean. Jump a step and it quietly lies to you.

What maturity decides: stripping, stressing, sawing, and opening

Maturity earns its keep on every schedule call that waits on strength. Each one moves to where the strength actually is, against a number the engineer or the specification set, instead of to a fixed calendar date.

The pattern is the same across all of them. The decision used to wait on the calendar, or on a cylinder break that lagged the work by days. Maturity lets it wait on the concrete instead, which is the thing the decision was always really about.

Form stripping, shoring, and post-tensioning on strength

Form and shore removal is the most common maturity payoff, and it is pure schedule. Instead of holding forms a fixed number of days, you strip or reshore when the in-place strength meets the required stripping strength the engineer set. On a multi-floor job that frees forms to fly to the next level sooner, and the deck cycle tightens by a day or two each floor, which compounds up the building.

Post-tensioning has its own strength gate. PT tendons are stressed once the concrete reaches the stressing strength the engineer specified, which is often a value well below the 28-day f'c. Stress too early and you crush the concrete at the anchorages or crack the slab. Maturity reads that stressing strength in place, so the stress happens on the first day the concrete can take it rather than on a conservative calendar guess. That early stress can be the difference that keeps the deck cycle on track.

The discipline in both is the same. The required strength comes from the structural engineer or the specification, not from habit or from the last job. Maturity tells you when that number is reached at the critical location. It does not set the number, and it does not give you license to strip or stress against a strength nobody specified. For holding the moisture and temperature that let the concrete reach those strengths in the first place, the curing and protection guide carries the cure side.

Does the maturity method work in cold weather?

Yes, and cold weather is where it pays off most, because that is where strength gain is slowest and least predictable. The maturity function already accounts for the slow gain. Cold concrete logs less maturity per hour, so the curve simply takes longer to reach the strength you need, and the sensor shows it.

That said the concrete still has to be kept above the floor where hydration stops. A pour that freezes early gains almost no maturity, and no curve recovers strength the concrete never made. Cold-weather work pairs maturity with heated enclosures, blankets, and heat, and the sensor then tells you two useful things: whether the protection is keeping the concrete warm enough to gain, and when the in-place strength is high enough that the protection can come off without exposing weak concrete to a freeze.

Put the sensor at the coldest, least-protected spot for this, not the warm interior near a heater. That is the concrete that governs when it is safe to pull the protection. For the cold-weather protection framework itself, the heated enclosure, the temperature limits, and the protection period, the curing and protection guide carries it. Maturity is the strength read that tells you when that protection has done its job.

Validation with field cylinders and cores

Maturity is an estimate built on a calibration, so good practice checks it against the real concrete now and then. ASTM C1074 expects the strength-maturity relationship to be verified, not taken on faith forever.

The check is straightforward. Cast a few field cylinders or pull a small core near the sensor, break them, and compare the measured strength to what the maturity curve predicted at the same maturity. If they agree within reason, the calibration is holding and the field readings stand. If the break comes in well under the prediction, something has drifted, the mix, the placement, the consolidation, or the cure, and the maturity number is no longer trustworthy until you find out why.

This is the spot-check that keeps the method honest. It does not have to be every pour, but it belongs on the critical ones and on the first pours of a new calibration. For how to make and break those cylinders and how to read a core result, the cylinder strength testing guide carries the detail. Validation is what separates a maturity program you can defend from a sensor nobody ever proved against the concrete.

Does maturity replace cylinder breaks for acceptance?

No. Maturity and acceptance cylinders do two different jobs, and confusing them is the fastest way to get the method thrown out.

Maturity estimates in-place strength for schedule and construction calls: when to strip, stress, saw, and open. Standard-cured cylinders, broken per the test method and judged against the ACI 318 acceptance rule, prove the concrete met its specified strength, f'c, for acceptance of the work. The standard-cured cylinder is cured under controlled conditions precisely so it measures the potential of the concrete as delivered, independent of how the slab in the field was protected. That is the number the structural engineer accepts the concrete on.

Maturity cannot do that job, because it reads the in-place concrete, which depends on field curing and placement, and because it rides on a calibration that assumes the mix did not change. So the two run together. Maturity moves the schedule. Standard-cured cylinders own acceptance. Keep both, label each for what it is, and never let an early maturity strip strength stand in for the f'c the project still has to prove. For the acceptance side, the cylinder making, the break, and the ACI 318 rule, the cylinder strength testing guide carries it.

Accuracy and what maturity cannot see

Maturity is accurate when its one assumption holds: the concrete in the slab matches the concrete the calibration was built from. When that is true, the in-place strength estimate is good enough to make real money decisions on. When it is not, the number is still confident and now wrong.

The big blind spot is a bad batch. Maturity reads temperature, not what is in the truck. A load with too much water, the wrong admixture dose, low cement, or a batching error will still log a normal-looking temperature curve and report a normal-looking strength, while the actual concrete is weaker than the curve says. The sensor cannot see it. Poor consolidation, honeycombing, and a cold joint are the same story, real strength problems that leave no fingerprint on the temperature log.

This is exactly why validation cylinders or cores and standard-cured acceptance cylinders stay in the program. They catch the things maturity is blind to. Treat maturity as a fast, in-place strength estimate that assumes good concrete and a valid calibration, not as a quality test that proves the concrete is sound. It tells you when good concrete is strong enough. It does not tell you the concrete is good.

Wireless and smart sensors

The current generation of maturity sensors is wireless. A logger cast into the pour holds the temperature record and the calibration, and a phone or tablet reads it over Bluetooth on the deck, or a gateway pushes the data to the cloud so the strength shows on a dashboard without anyone climbing the structure.

The practical wins are real. You read strength without uncovering the pour or running leads to a box. Several locations report at once. The software computes the maturity index and the in-place strength against the loaded calibration on the spot, so the strip or stress call does not wait on hand math. Many systems will alert when a location crosses a target strength or when temperature runs outside a set band, which on a cold-weather pour means you hear about a cooling slab before it is a problem.

The cautions are the same as the wired method, plus a couple. Bluetooth range through thick concrete and rebar is shorter than the box claims, so plan the read points. Watch battery and logging interval on long monitoring jobs. And none of the convenience changes the rule: the curve loaded in the app still has to be the calibration for the mix in that slab.

Cost and the schedule payback

The sensor is the small number. The schedule is the big one. A maturity sensor is a modest per-location, per-pour cost, plus the up-front cost of running the calibration once per mix. Against that sits what early strength information is worth on a job where the calendar is money.

The payback shows up wherever waiting on a fixed period or a lab break was holding the work. Flying forms to the next floor a day or two sooner on every cycle compounds over a high-rise. Stressing tendons or opening a pavement on the first day the strength is there, instead of a conservative date, pulls the whole schedule in. Fewer field-cure cylinders to make, store, and break is a smaller saving on top.

The honest version is that maturity pays on fast-track and repetitive work, and pays less on a small, slow job where nobody was waiting on strength anyway. Size the program to the schedule risk. On a deck cycle, a PT job, a pavement, or a data center pour where days have a dollar figure, the sensor cost disappears against one avoided day of delay.

Mass concrete, fast-track slabs, and data centers

The same embedded sensor that reads maturity also reads raw temperature, which makes it double duty on two kinds of pour.

On mass concrete, the big mats, transfer beams, and thick foundations, the controlling risk is not early strength but heat. The core gets hot as the cement hydrates, and if the inside-to-surface temperature difference runs too high the element can crack from the thermal gradient. The same loggers track peak core temperature and the differential to the surface, so the crew can manage cooling and insulation against the limits the spec or ACI guidance sets. The maturity and the thermal-control reads come off one sensor program on these pours.

On fast-track slabs and data center pours, the driver is schedule. These jobs live or die on turning floors quickly, and maturity is how you strip, shore, and open on strength rather than on a padded calendar. The slab tells you when it is ready, the forms move, and the next level starts. The two uses often ride on the same sensor: it watches the heat on the way up and reports the strength that releases the schedule.

What to document

When you strip forms or stress strands on a maturity number instead of a broken cylinder, the sensor data behind that number is what backs the call. The record is what answers the engineer or the inspector when they ask how you knew the concrete was ready.

Capture the mix and its calibration identity, the maturity function and constants used, the sensor type and where it sat, the temperature record, the maturity index and the in-place strength at the moment of the decision, the required strength and where it came from, the validation result if you ran one, and who made the call. Tie it to the pour. When the decision and its data live together, the early strip defends itself, and a field tool that logs the pour, the sensor location, and the strength at the call keeps that record where the next person can find it.

Common mistakes

• Reading maturity off a mix that was never calibrated, so the index points to no real strength.
• Using an old calibration after the mix design, cement source, admixture, or water-cement ratio changed.
• Placing the sensor in the warm interior instead of the coldest, slowest-gaining critical location.
• Treating a maturity strip strength as the f'c acceptance the standard-cured cylinders still have to prove.
• Running no validation cylinders or cores, so the curve is never checked against the real concrete.
• Trusting a normal-looking maturity number on a load that was actually a bad batch the sensor cannot see.
• Mixing the Nurse-Saul and Arrhenius functions or their constants between the calibration and the field reader.

Field checklist

Standards and references

ASTM C1074 is the standard practice for estimating concrete strength by the maturity method. It defines the two maturity functions, Nurse-Saul and Arrhenius, the procedure to develop the strength-maturity calibration, and the procedures to determine the datum temperature or the activation energy when you do not assume them. It is the document to cite and to follow for the method itself.

The strength side ties back to the rest of the program. The specified strength, f'c, and the acceptance of the concrete run under ACI 318 and the project specification, proven with standard-cured cylinders, not with maturity. ACI also gives guidance on in-place strength evaluation and on form removal and reshoring strengths, and the structural engineer or the specification sets the required strengths for stripping, stressing, sawing, and opening. The maturity method tells you when those numbers are reached. It does not set them.

Two more points belong in any citation. The sensor manufacturer's instructions govern the hardware, the logging, and the software. And the exact procedures, assumed constants, and section references shift between editions, so confirm them against the ASTM C1074 edition and the project documents in force before relying on them. Above all, the calibration has to be mix-specific. That requirement is the method, and no standard reference replaces it.

Units, terms, and conversions

The maturity method carries its own vocabulary, and the same idea reads differently across the calibration report, the sensor software, and the spec.

Maturity index is the umbrella term for the single time-and-temperature number. Under Nurse-Saul it is the time-temperature factor, the TTF, in degree-Celsius-hours, sometimes written degree-C-hr. Under Arrhenius it is equivalent age at a reference temperature, usually in hours. Temperature is logged in Celsius in most maturity work and in Fahrenheit on some US jobs, so check which the calibration used. In-place strength is reported in psi in the US and in megapascals (MPa) in metric documents, where roughly 1 MPa is about 145 psi.

Maturity index

The single number combining time and temperature, either TTF or equivalent age

TTF (time-temperature factor)

The Nurse-Saul maturity index, in degree-Celsius-hours

Equivalent age

The Arrhenius maturity index, time at a reference temperature, in hours

Datum temperature

The temperature below which Nurse-Saul assumes no maturity gain, often near 0 C

Activation energy

The Arrhenius parameter for temperature sensitivity, often 40,000 to 45,000 J/mol

Strength-maturity calibration

The mix-specific curve of strength against maturity, built per ASTM C1074

f'c

Specified compressive strength, accepted with standard-cured cylinders, not maturity

Related tools

Calculators and readiness checks for this work

Compare your options

FAQ

People also ask

• How is concrete strength tested?
• How long do you cure concrete?
• What is a concrete admixture?
• What is the difference between a mechanical and an adhesive anchor?
• What is the difference between integral color and stain?