Document Unreliable UT Thickness Readings and Follow-Up

A thickness exception records a measurement question that has not yet been resolved through the applicable examination process. It may concern an unstable displayed value, an uncertain echo assignment, inconsistent repeat readings or another documented limitation. Identify the actual observation rather than labelling every unusual number unreliable. A low reading can be real and significant; a stable-looking number can still be unsupported. The responsible examiner and technical process determine what evidence is sufficient to retain a result.

Keep the questionable value distinguishable from the reportable result. If the source record contains a displayed number, preserve it in the appropriate supporting record with its state and context. Do not place it in a final minimum-thickness column without the required review. This guide addresses the reporting exception and follow-up trail, not the operating procedure for acquiring thickness measurements. The piping thickness survey guide provides broader planning context for the original examination scope.

Record the component and location using the survey’s established convention. A repeat measurement cannot answer the original question if it is taken at an unidentified nearby point. Include the relevant grid, clock position, axial reference or drawing relationship where the source supports it. Avoid inventing precise coordinates from a vague field note. If the location is uncertain, make that a separate exception because it affects both interpretation of the original reading and the usefulness of any follow-up.

Keep the measurement point distinct from the wider examination area. One retained reading does not necessarily characterize every nearby surface, and a questionable point does not automatically invalidate the entire survey. The responsible process establishes the significance and affected scope. The exception log should help that assessment by preserving the point, surrounding context and source event. It should not replace the original location with a more convenient one simply because the first point is difficult to find or access again.

Write what the examiner recorded: a changing displayed value, loss of a usable response, disagreement between repeated observations or another specific condition. Do not diagnose severe corrosion, coating interference or equipment failure solely from the existence of a questionable reading. Those may be possibilities for the responsible technical assessment, but the report should distinguish an observation from an explanation. A useful exception gives the reviewer enough context to investigate without presenting an unverified cause as an established finding.

Keep the original signal or supporting data reference where the equipment and project process provide one. A screenshot can help explain the observation but may not contain the full information needed for review. Identify the source and any selected view rather than treating the picture as the entire acquisition record. The free reporting tool does not interpret ultrasonic waveforms or import native instrument datasets. It can record the evidence references and the eventual supported outcome supplied by the responsible examination process.

Identify the actual equipment and relevant measurement mode used for the event. Similar-looking gauges or probes can have different capabilities and setup requirements. Evident’s thickness-gauge transducer selection tutorial discusses material, thickness range, geometry and temperature as selection considerations. For the exception record, preserve the actual configuration and conditions that the technical reviewer needs. Do not turn the manufacturer’s general guidance into a universal probe choice or an automatic explanation for every unusual result.

Reference the applicable setup and verification records without claiming that a current equipment certificate resolves every measurement question. Instrument evidence and event-specific measurement setup address different aspects of the work. If the record cannot establish which probe or mode was used, document that gap. Avoid filling the field from a standard kit list when the actual event may have used another configuration. Accurate configuration context can prevent an unnecessary repeat visit or an unsupported conclusion based on assumptions about the equipment.

Record the surface and coating conditions relevant to the measurement as observed and required by the project. Evident’s application note on measuring through paint explains that coatings can affect conventional thickness measurements and that through-coating approaches have their own limitations. The reporting lesson is to preserve the actual measurement mode and surface context. Do not subtract an assumed coating thickness from a questionable value or claim that every coated reading is automatically corrected by the instrument.

If surface preparation or a different authorized approach is proposed, record the decision and subsequent event separately. The reporting worksheet does not authorize coating removal or prescribe preparation on operating equipment. The site and technical processes determine what is permitted and suitable. A later reading after preparation may address the original question, but the report should retain enough history to explain why the earlier observation was uncertain and what changed before the retained result was obtained.

When the examination cannot establish a usable thickness value, do not enter zero as a placeholder. Zero is a numerical value with a very different meaning from an unresolved measurement. Use the project’s explicit state label and preserve the location and reason. A dash or empty cell can also be ambiguous unless its meaning is defined. The exception table should make clear whether no examination occurred, an attempt produced no usable result or a value exists but remains under review.

Keep those states out of automated minimum, average or corrosion calculations until the responsible process determines how they are to be handled. A placeholder can become a false extreme or disappear from a calculation without explanation. The reporting app does not decide which readings are technically valid or evaluate the resulting trend. The preparer must preserve the supported state and use reviewed data through the appropriate calculation and engineering process when a downstream assessment is required.

A repeat reading can help investigate an exception, but it should not automatically replace the first observation. Record the same-location evidence, relevant setup changes and the actual reason for the repeat. If the measurement was taken at another point, identify that difference. The responsible reviewer determines whether the repeat resolves the original question or represents a separate observation. Do not average inconsistent values merely to produce a stable-looking number unless the applicable measurement process specifically supports that treatment.

A later higher value is not automatically more credible, and a later lower value is not automatically the correct minimum. Evaluate the evidence rather than selecting the result that fits an expected trend. Keep the original and repeat event references available in the exception log. If a value is excluded from the final result set, record the responsible basis for exclusion. This preserves the distinction between rejecting unsupported data and removing an inconvenient but potentially valid observation.

In a fictional twelve-point survey, eleven locations have retained results under the project’s examination process. At point T-09, the examiner records inconsistent observations and cannot support a final thickness value from the available evidence. The report keeps T-09 in the location list with an explicit review state. It does not copy the value from T-08, substitute the nominal wall thickness or treat the missing result as zero. The exception record identifies the equipment context, source evidence and responsible next decision.

A later authorized follow-up returns to the identified T-09 location and produces evidence that the responsible reviewer evaluates. The log records whether that event resolves the question and which value, if any, is retained. This hypothetical example sets no acceptable variation, minimum wall or required repeat technique. It shows how one unresolved point can remain visible without being disguised as a measurement or being used to make an unsupported conclusion about the other eleven points or the whole component.

A historical comparison needs compatible locations, quantities and measurement context. A questionable current value should not be used to calculate a precise corrosion rate simply because an earlier reading exists. Establish whether the points and methods are meaningfully comparable through the responsible process. If the current state remains unresolved, preserve that limitation in the trend record. A numerical difference between two cells is not automatically evidence of a physical change at the same location.

Keep engineering decisions about minimum required thickness, remaining life and operation separate from the exception log. Those decisions require their actual inputs and authority. The log supplies traceable measurement states and evidence references; it does not determine fitness for service. If the project requires prompt escalation of a potentially consequential observation, follow that process without waiting for a completed trend calculation or a polished report. Record the notification relationship accurately without implying that notification itself resolved the technical question.

Identify what evidence or decision is missing. The next action might be review of an existing record, clarification of a location or an authorized further examination plan. Do not default to another site visit when the relevant data already exists, and do not ask for a formatting change when the underlying measurement is unsupported. Record the responsible role and actual agreed timing where available. The action should be specific enough that another coordinator can tell whether it has been completed.

Separate technical assessment from operational arrangements. The person arranging access may not decide the measurement technique, while the technical reviewer may not control site permissions. Keep those responsibilities clear. The worksheet is a planning and reporting aid, not a live dispatch system. It does not send automatic instructions to an examiner or authorize a change in equipment use. Use the organization’s actual communication process and record the decision references needed to connect the resulting work with the original exception.

The equipment tracker can organize instrument and probe identity along with supporting record references. The calibration reminder tool can help manage entered due dates and configured reminders. Neither determines whether a specific thickness reading is reliable. Use those records to retrieve relevant evidence while preserving the actual examination configuration. A green administrative status is not a substitute for reviewing the signal, setup and conditions that produced the questioned observation.

If the investigation reveals a separate equipment-evidence issue, record its scope explicitly. Do not assume that every measurement made with the equipment is affected in the same way. The responsible technical process determines the relevant period, configuration and report impact. Preserve the original exception as a location-specific measurement question while connecting it to any wider review. This prevents an equipment record problem and a local surface or signal problem from being merged into one vague explanation that cannot be investigated effectively.

Use the free digital reporting workspace to enter retained values, units and the explicit states for unresolved locations. Add an exception table with source and action references where useful. The tool can import supported DOCX or XLSX grids, but it does not determine which values should be retained or parse native gauge data. Review the import preview against the source and preserve warnings about unsupported structures. Do not describe a successful table import as technical validation of the measurement.

Keep the main table readable while making the exception easy to find. A short exception ID beside T-09 can point to the detailed record without crowding the result column. Ensure the legend explains the state and that the conclusion preserves the unresolved boundary. The report buyer-review guide supplies broader package checks. For thickness exceptions, the crucial check is whether the recipient can distinguish a supported measurement from an attempted but unresolved observation at the same location.

Open the actual exported PDF and inspect every exception row alongside the summary. Confirm that units, location references and review states remain readable after wrapping and page breaks. A table can lose meaning when a state column is detached from the value it qualifies. Check that an unresolved point has not disappeared through a filter or been excluded from a stated count without explanation. A report can summarize retained readings while still accounting explicitly for the requested points that lack final values.

Read any minimum or range statement against the underlying set. It should identify the scope of the retained data and preserve relevant unresolved locations. Do not imply that the reported minimum establishes the minimum thickness everywhere on the component when the actual examination scope does not support that claim. The responsible technical evaluation determines what the measurements mean. The report preparer’s job is to communicate the supported set, its location context and its limitations accurately.

A completed follow-up action does not automatically mean the measurement question is resolved. Record the responsible evaluation and the resulting retained value, limitation or further action. If a distributed report changes, follow the actual amendment and communication process. Preserve the original observation and the relationship to the later event in the supporting record. Do not overwrite history in a way that makes the original report appear to have contained evidence acquired only afterward.

Use the worksheet below to organize the point identity, observed behavior, measurement context and resolution reference. Replace the fictional entries with actual project evidence. A useful UT thickness exception log protects both unusual valid readings and genuinely unsupported values from careless handling. It allows the technical process to decide what can be retained while giving the recipient an honest account of what was measured, what remains uncertain and what action connects the two states.