Charts • Reviewed 2026-08-09

Fresh Concrete Observation & Response Chart

Connect common field observations with questions to investigate before changing the mixture.

Scope: This page explains recognized concrete practice for planning and field understanding. It does not reproduce copyrighted standards or replace the adopted code, structural design, project specification, testing agency, or product instructions.

Key takeaways

  • Fresh-concrete behavior should be investigated systematically before adding water or rejecting material.
  • Observations are not diagnoses. Formal acceptance follows project specifications and applicable test methods.
  • Treat these tables as field-reference and planning aids. Project drawings, specifications, current standards, manufacturer data, and local requirements govern when they differ.
ObservationPossible contributorsFirst checks
Slump lower than expectedTemperature, elapsed time, mixture variability, measurementTicket, time, temperature, approved adjustment procedure
Slump higher than expectedWater, admixture dosage, sampling/test variationTicket, field additions, test procedure
Rapid slump lossHot concrete, long haul, cement/admixture interactionTemperature, timing, producer guidance
Excessive bleedingMixture proportions, water, aggregate grading, placementDo not finish bleed water into surface
Sticky/harsh mixPaste/aggregate balance, admixtures, gradationPlacement method and producer discussion
SegregationHigh slump, poor handling, drop height, mixturePlacement/consolidation practices

How to read this table

Fresh-concrete behavior should be investigated systematically before adding water or rejecting material.

Where it is useful

Use the table as a pre-pour troubleshooting prompt and to guide communication with the producer and testing agency.

Limitations

Observations are not diagnoses. Formal acceptance follows project specifications and applicable test methods.

How to apply this reference

Use visible symptoms as prompts for investigation, not as automatic permission to change the mixture.

Segregation, delayed set, crusting, excessive bleed or unexpected air/slump can each have multiple causes.

For fresh concrete observation & response chart, write down the project-specific value that controls and use the table only to interpret or convert information. This keeps a quick-reference chart from quietly becoming a substitute specification.

Field documentation tip

When a value from this table influences an order, inspection or repair decision, record the source input and the project document or manufacturer information that authorized the decision. That makes the field record auditable if conditions or requirements change. On the Fresh Concrete Observation & Response Chart page, apply this point specifically to the conditions and records described above.

Example field use

A good way to use fresh concrete observation & response chart is to start with a known project condition and use the table to translate or organize it—not to select an unknown requirement. For example, the first rows of this reference include Slump lower than expected / Temperature, elapsed time, mixture variability, measurement; Slump higher than expected / Water, admixture dosage, sampling/test variation; Rapid slump loss / Hot concrete, long haul, cement/admixture interaction. Those entries are useful only after you know which row applies to the concrete, reinforcement, test, product or geometry you actually have.

When a table contains a typical range, planning factor or example value, write that label into your notes. If the project documents later provide a different value, replace the planning value rather than averaging the two. This is especially important for strength, air, cover, jointing, weather, testing and repair decisions where a quick field reference can look more authoritative than it really is. On the Fresh Concrete Observation & Response Chart page, apply this point specifically to the conditions and records described above.

What to verify before acting on the table

Before using fresh concrete observation & response chart to support a material order or field decision, verify the units, edition/source where relevant, exposure or service condition, and whether the value is mandatory or illustrative. If the table points to an ASTM test, use the current procedure and trained testing personnel. If it touches structural design or reinforcement, use the approved drawings and governing code. If it concerns a proprietary repair, coating or curing product, the manufacturer's current technical data governs application details.

Keep the reference useful by pairing it with a field observation. A measured dimension, actual batch ticket, photograph, test report or marked-up pour plan gives the table context and makes later troubleshooting far more reliable. On the Fresh Concrete Observation & Response Chart page, apply this point specifically to the conditions and records described above.

Field checklist

  • Confirm the table applies to the material or operation being reviewed.
  • Verify units before using a value.
  • Check the project documents for a controlling requirement.
  • Use the current edition of any cited standard for formal work.

Common mistakes to avoid

  • Copying a planning value into a specification without engineering or code review.
  • Using a table without checking units or exposure conditions.
  • Assuming a typical value is a universal minimum or maximum.

When project-specific review is needed

Use a qualified engineer, local code official, testing professional, concrete producer, or product manufacturer when the decision affects structural capacity, public safety, regulated work, unusual soil or environmental exposure, post-tensioning, heavy equipment, significant distress, or a requirement shown on the project documents. Rules of thumb are useful for planning only when they are clearly identified as such.

References & further reading

These links identify the primary organizations and documents used to frame this article. Project documents and the full current standard control where applicable.