Concrete Maturity Low-Temperature Curing Strength Case Study

Concrete strength gain depends on time and temperature. A slab that would be ready for stripping in warm curing conditions may remain too weak after cold nights, even if standard-cured cylinders look acceptable. The maturity method helps connect measured in-place temperature history to estimated in-place strength, but it must be calibrated and validated for the specific mix.

This case study follows a suspended reinforced concrete slab placed during cold weather. The construction team wants to strip formwork and move shoring to maintain schedule. Field temperature sensors show that the slab cured colder than the standard cylinders. The engineering task is to decide whether stripping is acceptable, whether heating or reshoring is required, and what evidence is needed for release.

The central question is:

Does the in-place slab have enough early-age strength for the proposed construction-stage load path?

Release Boundary and Temporary Load Path

The release boundary is not only the concrete mix. It includes the slab bay, support system, formwork, shores, reshoring sequence, construction loads, curing protection, sensor locations, temperature gradients, cylinder results, maturity calibration and engineer acceptance. The decision is a temporary works decision made before the structure has reached its permanent design state.

The review should identify:

• which bay is proposed for stripping;
• which shores remain and which are moved;
• what construction live load, material storage and equipment load will be present;
• whether adjacent bays are transferring load into the reviewed bay;
• where sensors are embedded relative to edges, corners and thickened zones;
• whether the coldest concrete is represented by the sensor record;
• who has authority to release the bay and under what written conditions.

A maturity number without this boundary is incomplete. A slab can have enough average in-place strength for one stripping sequence and not enough for another sequence with different reshoring, stacked materials or local load transfer.

Failure Modes

The failure modes are not limited to immediate collapse. Early stripping can produce excessive deflection, cracking, bond damage, crushed bearing zones, support settlement, load redistribution into immature adjacent bays or hidden serviceability damage that appears later. Low-temperature curing can also leave cold corners or surface zones behind the average maturity estimate.

The release question is therefore conservative: is the weakest relevant concrete region strong enough for the actual temporary load path with uncertainty included?

Case Context

The slab is part of a multi-storey concrete frame. The permanent design is not the immediate problem. The immediate risk is temporary: removing forms and applying construction loads before the concrete has enough strength and stiffness.

The simplified release basis is:

Item	Value or criterion
minimum strength for stripping and reshoring move	20\ \text{MPa}
datum temperature for maturity calculation	T_0=-10^\circ\text{C}
approved maturity calibration target	20\ \text{MPa} at M=1500^\circ\text{C}\cdot\text{h}
planned stripping time	60\ \text{h} after placement
minimum curing protection requirement	no freezing and documented thermal history
construction-stage review	no material release without engineer acceptance

The numbers are educational examples. Real projects must follow the governing concrete specification, structural design, code rules, cold-weather concreting procedure, curing plan, sensor calibration, laboratory calibration curve, and engineer-of-record requirements.

Evidence Register

The engineer should separate evidence that confirms concrete quality from evidence that confirms in-place release readiness.

Evidence	What it proves	What it does not prove
standard-cured cylinders	batch potential under controlled curing	in-place cold slab strength
field-cured cylinders	local curing exposure near cylinders	exact strength at cold slab zones
embedded sensors	temperature history at sensor points	strength where no sensor exists
maturity calibration	mix-specific time-temperature-strength relationship	validity outside calibration range
field inspection	visible defects and curing protection condition	hidden internal maturity or strength
reshoring plan	temporary load path intent	concrete capacity unless paired with strength evidence

The release package should include all of these where required by the project specification. No single evidence item should be treated as universal proof.

Step 1: Understand the Cylinder Mismatch

The standard-cured cylinders were stored near:

For the first 48\ \text{h}, their approximate maturity is:

That is close to the 1500^\circ\text{C}\cdot\text{h} calibration target for 20\ \text{MPa}.

The field slab was colder. The embedded sensors recorded:

Interval	Average slab temperature	Duration
first night and day	7^\circ\text{C}	24\ \text{h}
second day	5^\circ\text{C}	24\ \text{h}
third morning	3^\circ\text{C}	12\ \text{h}

Engineering Comment

Standard cylinders are useful quality evidence, but they may not represent in-place strength when the member temperature history differs. The maturity calculation is a way to quantify that difference instead of arguing from schedule pressure.

Cylinder Role

The standard cylinder result can support acceptance of the delivered mix and laboratory strength potential. It should not override colder in-place temperature evidence. If field-cured cylinders are available, they can provide an additional check, but they still may not match the coldest slab region unless their storage and thermal exposure are controlled.

The key comparison is not “cylinders passed” versus “sensors failed.” The key comparison is whether each evidence source represents the decision being made. For stripping and reshoring, in-place strength at the critical concrete region is the controlling question.

Step 2: Calculate In-Place Maturity at Planned Stripping

Using the Nurse-Saul temperature-time factor:

First interval:

Second interval:

Third interval:

Total field maturity at 60\ \text{h}:

This is far below the release maturity:

Engineering Comment

The planned stripping time is not supported by the measured slab history. The issue is not whether concrete was placed correctly; it is whether the actual curing temperature created enough hydration progress for the construction-stage decision.

Cold-Spot Screen

Average slab maturity can overstate the coldest location. Edges, corners, thin zones, areas near openings, exposed soffits and zones where blankets were displaced can cure colder than the sensor average. If the release depends on a small margin, the engineer should check whether the sensor was placed at the controlling cold spot or whether an additional allowance is needed.

The cold-spot screen should ask:

• was the sensor near the most exposed location?
• were blankets and heaters continuous over the bay?
• were there thermal bridges through forms, supports or embedded steel?
• did any part of the slab approach freezing?
• were sensor readings continuous and time-stamped?

If the answer is uncertain, the maturity estimate should be guarded or supplemented by accepted in-place confirmation.

Step 3: Estimate Strength from the Calibration Curve

For this case, the approved mix calibration is approximated over the relevant range by:

where f_c is in MPa and M is in ^\circ\text{C}\cdot\text{h}.

At planned stripping:

The estimated in-place strength is:

Engineering Comment

This is a hold point. Stripping at this maturity would rely on hope, not evidence. The correct action is to maintain support, improve curing, and re-evaluate from measured temperature history or additional accepted tests.

Calibration Boundary

The maturity curve is valid only for the approved mix, materials, admixtures, water-cement ratio, curing range and test method used to establish it. A change in cement source, accelerator dosage, supplementary cementitious material, water addition, curing range or sensor method can invalidate the curve.

The release record should state the calibration identifier and confirm that the placed concrete matches it. If the mix changed during the pour, the maturity release should be limited to areas tied to the matching calibration.

Step 4: Add Curing Heat and Recalculate

The team adds insulated blankets and temporary heat. The next 24\ \text{h} has average slab temperature:

Additional maturity:

Updated maturity:

Estimated strength:

This just exceeds the threshold:

Engineering Comment

The result supports a conditional release, not an automatic one. The margin is small, so the engineer should check sensor validity, calibration scatter, cold corners, construction loading, reshoring sequence, and whether any concrete approached freezing.

Heating Control

Temporary heat can improve maturity, but it can also create gradients. Uneven heat can warm sensor locations while leaving edges or soffits colder. Excessive local heating can dry surfaces or create thermal stress. The heating record should document heater placement, blanket condition, enclosure continuity, fuel or exhaust controls where relevant and the actual sensor response.

The site should not assume that adding heat for 24 hours automatically makes the slab ready. The added maturity helps only if the heat reached the critical concrete and the protection system remained in place.

Step 5: Include Measurement and Model Uncertainty

The review assigns a conservative uncertainty allowance:

Source	Strength-equivalent allowance
maturity calibration scatter	1.2\ \text{MPa}
temperature sensor placement and accuracy	0.7\ \text{MPa}
member temperature gradient	0.8\ \text{MPa}

Combined standard allowance:

Guarded strength estimate:

This is below the 20\ \text{MPa} release threshold.

Engineering Comment

The average maturity result barely passes, but the uncertainty-adjusted result does not. A schedule-driven release would be weak. The better decision is to continue curing until the maturity margin is large enough or to obtain accepted in-place confirmation.

Guard-Band Logic

The guard band converts a marginal estimate into a conservative release decision. If the unguarded strength is only slightly above the threshold, the uncertainty in calibration, sensor position and member gradient can decide the outcome. This is the correct use of engineering judgment: the release is based on evidence margin, not on rounding a computed value upward.

The project should state whether the guard band is mandatory by specification or adopted by the engineer for risk control. Either way, the same rule should be applied consistently across bays.

Step 6: Final Release After Additional Curing

The slab receives another 12\ \text{h} of protected curing at:

Additional maturity:

Final maturity:

Estimated strength:

Guarded strength:

Now:

The release is technically defensible if the temporary load path and reshoring plan are also accepted.

Release Gate

The final release gate has three parts:

1. guarded maturity strength exceeds the threshold;
2. the reviewed temporary load path is acceptable;
3. field inspection does not reveal defects that invalidate the strength assumption.

If any part fails, the decision remains hold, even if the other two pass. For example, maturity may pass but reshoring may be incomplete; cylinders may pass but sensors may not; sensors may pass but the site may request unreviewed material storage.

Release Decision

The approved decision is conditional stripping with reshoring controls:

1. keep primary shores in place until guarded maturity strength exceeds the threshold;
2. strip only the approved bay sequence;
3. prohibit material storage beyond the reviewed construction load;
4. maintain reshoring until the next strength hold point;
5. document sensor locations, temperature records, cylinder results, and maturity calculation;
6. inspect for cold joints, surface damage, honeycombing, and early cracking;
7. require engineer review if curing protection is removed, the weather worsens, or construction loading changes.

Revalidation Triggers

The release should be revalidated if:

• site loading changes from the reviewed plan;
• shores or reshores are moved out of sequence;
• curing protection is removed before the next hold point;
• sensors stop recording or show a cold excursion;
• freezing is suspected at any slab location;
• field inspection finds cracking, honeycombing, cold joints or damaged bearing zones;
• later bays are colder or use a different concrete batch or mix adjustment.

These triggers keep the release tied to the conditions that justified it. A maturity approval is not a blanket permission for all future construction changes.

Validation Matrix

Evidence	Purpose	Result
standard cylinders	confirm batch quality under controlled curing	useful but not sufficient
embedded temperature sensors	represent in-place thermal history	required for maturity release
maturity calculation	estimate in-place strength from calibrated mix curve	initial hold, later pass
uncertainty allowance	prevent release on a marginal estimate	changed decision at 1548^\circ\text{C}\cdot\text{h}
reshoring plan	preserve load path during temporary stage	required before stripping
field inspection	check defects not captured by maturity	required before release

Engineering Lessons

This case shows why early-age concrete decisions are construction engineering decisions, not only material-test decisions. Standard cylinders can overstate in-place strength when the member cures colder than the lab samples. A maturity method can improve the decision, but only when the calibration, sensors, temperature history, and uncertainty are controlled.

Good cold-weather concrete release connects:

1. actual in-place temperature history;
2. mix-specific maturity calibration;
3. construction-stage strength threshold;
4. uncertainty and temperature gradients;
5. temporary works and reshoring sequence;
6. field inspection and documentation;
7. revalidation triggers when weather or loading changes.

The final question is not whether the concrete will eventually reach design strength. It is whether the concrete is strong enough today for the temporary load path the site wants to use.