This article builds on What is a UPV test and focuses on the steps "after the results are in": when the report shows values lower than expected, how to read them, how to rule out causes and what to check next, so you can make a real decision without jumping to the conclusion that the structure is damaged.
What UPV Velocity Counts as Low?
A low pulse velocity is one that is significantly lower than other points in the same structural member, not merely lower than a textbook figure, because each concrete mix gives a different baseline velocity. The table below therefore focuses on "what to do next" rather than assigning quality labels.
| Pulse velocity (km/s) | What to do next |
|---|---|
| Above 4.5 | Record as the structure's reference value for comparing other points; no further checks needed |
| 3.5 – 4.5 | Normal; investigate further only if values are unusually scattered within the same member |
| 3.0 – 3.5 | Re-measure and add points around the area; if still low, verify with another method |
| 2.0 – 3.0 | Always verify, e.g. with Impact Echo or by drilling cores (Core Test) |
| Below 2.0 | Suspect a serious internal defect; have an engineer assess before continuing to use that area |
If a column reads 4.2 km/s at every point except one that reads 3.4 km/s, the difference of about 0.8 km/s means more than the figure 3.4 itself, because it indicates that the concrete at that location differs from the rest of the same member.
Is the Value Low Because the Concrete Is Poor, or Because of the Measurement?
Low values can come from the concrete itself or from the way it was measured. Several site factors can push readings off in either direction. This table helps you tell whether a reading has likely been pushed up or pulled down.
| Factor | Direction of error | How to handle it |
|---|---|---|
| Insufficient couplant or rough surface | Falsely low | Grind the surface smooth, reapply gel, press the transducers firmly, then re-measure |
| Plaster or paint over the surface | Falsely low | Chip off the plaster only at the test point to reach the concrete |
| Transducer spacing measured incorrectly | Either high or low | Measure the actual distance with a tape measure and record every point; do not use drawing dimensions |
| Pulse path parallel to reinforcement | Falsely high | Scan for bars with GPR, then avoid them or apply a correction |
| Saturated concrete or recent rain | Falsely high | Record the moisture condition in the report and compare with points in the same condition |
| Young concrete that has not yet gained full strength | Lower than final value | Wait until the age specified by the engineer before concluding |
| Indirect transducer arrangement | Lower than direct | Do not directly compare values from different arrangements |
| Different mix or aggregate type | Not comparable | Compare only within the same concrete batch |
Following ASTM C597 and DPT 1504-51 (Standard for Non-Destructive Inspection of Reinforced Concrete Structures: Ultrasonic Pulse Testing of Concrete, issued by the Department of Public Works and Town & Country Planning), reported values must come with the path length, transducer arrangement and surface condition; otherwise the velocity figure alone cannot be interpreted.
What Should You Check Before Concluding the Concrete Has a Problem?
When you find a low value, go through these 5 steps in order before deciding on further testing.
- Calibrate the instrument with a reference bar — both before and after each set of measurements. If the reading on the reference bar is off, the problem lies with the instrument, not the structure.
- Re-measure 2–3 times with fresh gel — if the value jumps up after reapplying gel, the cause is the contact, not the concrete.
- Move the test point away from the reinforcement — shift the transducers sideways 5–10 cm and re-measure to see whether the value changes significantly.
- Check that the path length and arrangement are fully recorded — a 10% error in distance immediately gives a 10% error in velocity.
- Expand to a grid around the low point — measure all around to see whether the low value is a single point or covers a wide area, which directly guides the next testing method.
UPV Results Are Genuinely Low — What Should You Test Next?
Once measurement causes have been ruled out and the value is still low, the next step depends on the "distribution pattern of the low values", not on the number itself, as shown in the diagram below. Combining several non-destructive methods to confirm results before concluding is a practice described in the guidance document ACI PRC-228.2 (Report on Nondestructive Test Methods for Evaluation of Concrete in Structures).
Low at isolated points usually indicates a local defect, such as a void from incomplete placement or insufficient vibration. Use Impact Echo (per ASTM C1383) or GPR to locate the defect and its depth first, then drill to confirm only where necessary, to minimize the number of holes in the structure.
Low across the whole member points to the quality of that concrete batch as a whole. In this case, take Rebound Hammer readings as well, then drill cores for compressive strength testing per ASTM C42, because estimating strength from pulse velocity alone is not sufficient for structural decisions.
Low only around a crack is normal behavior for a wave that has to detour around the crack. It can be used to estimate crack depth, but must be paired with monitoring whether the crack is widening before concluding that repair is needed.
Concrete exposed to high heat gives clearly lower velocities in proportion to the depth of damage. Comparing fire-exposed and unexposed areas helps assess the extent of damage, but the residual compressive strength must always be confirmed with cores.
What Must a UPV Report Contain to Support Decisions?
A report with only a table of velocity figures often cannot support the next decision. A usable report should contain at least these 7 items.
- A test point layout with numbers, clearly locatable on the structural drawings
- The actual transducer spacing at each point and the arrangement (direct / semi-direct / indirect)
- The raw pulse transit time (µs), not just the calculated velocity
- Reference bar calibration results before and after measurement
- Surface and moisture condition during testing, including the reinforcement locations avoided
- Comparisons within the same member, not only against a standard table
- Conclusions and recommendations certified by a civil engineer licensed by the Council of Engineers Thailand (COE), with signature and registration number
SPN reports include all of the above and can be used for submissions to the relevant authorities. See all services under Non-destructive structural evaluation (NDE)
5 Common Mistakes When Interpreting UPV Results
- Comparing values with a quality table straight away without looking at what other points in the same member read, so concrete whose mix naturally gives lower velocities gets judged as defective.
- Converting velocity to compressive strength with an off-the-shelf formula that has not been calibrated for that concrete batch. The resulting figure can be so far off that it is useless for decisions.
- Not recording the transducer arrangement and then comparing values from an indirect arrangement with a direct one, which naturally gives lower values.
- Assuming high values are always good, even though the pulse path may run parallel to reinforcement or the concrete may be saturated, masking internal defects.
- Concluding without verification when values are very low. UPV can tell you that something is abnormal, but not what it is; it must be confirmed with another NDT method or a Core Test.
If the test results suggest that concrete strength may be below the requirement, the decision steps that follow are covered in Concrete compressive strength fails: what to do. Testing fees depend on the number of points and site conditions; contact us for a free quote within 24 hrs. Prices exclude travel and equipment mobilization, which are charged extra according to the distance to the site.