Review Mixed Units and Precision in NDT Result Tables

Begin by naming what each result represents. A table can contain thickness, sound path, indication length, coating thickness and a location coordinate, all expressed as lengths but answering different questions. A shared unit does not make those values interchangeable. Confirm the quantity against the source record and the agreed deliverable. The report heading should identify enough meaning for the reader to understand the number without referring to an informal conversation. If the heading simply says result, determine whether the table needs a more specific label or a separate quantity column.

Keep the measurement basis connected to the row. A value may describe a local reading, an average, a nominal drawing dimension or a calculation supplied by another party. Do not present these as equivalent observations merely because they fit the same numeric format. Ask which distinctions matter to the customer’s decision and record them clearly. The unit review should expose ambiguous meaning before anyone attempts conversion. Otherwise, careful arithmetic can produce a convincingly formatted value that still represents the wrong quantity or the wrong physical location.

Check the source cells, headings, notes and instrument export labels for unit information. A workbook may show one unit in the main heading but include rows copied from another source. A report preparer should not assume that the first visible unit applies to the entire column. Identify the origin of each group of values and mark any unresolved unit explicitly. Compare the table with the supporting examination record when a unit appears only in a separate instrument setting or a supplier’s explanatory note.

Record the original value and its original unit before making changes. Keep the source file and relevant cell or result reference available. If the source has no unit, ask the author rather than inferring it from the magnitude. A small number could be a different quantity, a different unit or an incomplete entry. Guessing from what seems reasonable for the component is not a reliable documentary correction. Leave the affected entry pending until the responsible source can establish what the number means and how it should be represented.

Use the client’s actual reporting requirement to decide the presentation. Some recipients need the original acquisition units; others request a common unit for comparison or integration. Where both are useful, label them separately so the converted display cannot be mistaken for an independent measurement. Agree which representation governs if rounding makes the two displays appear slightly different. Do not insert an unrequested second value if it creates confusion, but do not discard the original basis when the project needs it to interpret the evidence.

A US assignment can still involve metric drawings, imported equipment or suppliers using another unit convention. Geography does not determine the correct unit for every technical record. Confirm the required convention at the project level and retain exceptions that have a documented reason. If separate tables use different units, make that difference conspicuous in their headings. A reader should not need to remember a note from several pages earlier to know what a value represents in the table currently being reviewed.

NIST provides conversion-factor and rounding guidance as part of its SI publication. Use an appropriate controlled reference for the quantity being converted and retain the conversion basis where it matters to review. A conversion factor is not an acceptance criterion and does not establish the suitability of the original measurement. Before applying it, confirm that the source and destination describe the same kind of quantity and that the original unit was identified correctly.

The free calculator directory can provide a convenient starting point for applicable calculations, but every tool has assumptions that need checking. Do not treat an available calculator as authority to convert an unfamiliar quantity. Record the original input, the chosen calculation reference and the accepted output. For repeated conversions, test representative entries before applying the preparation method to the whole set. Include values with different signs, decimal places and qualifying notes when those occur in the actual source, and retain any exception that needs a different treatment.

NIST’s conventions for expressing quantity values distinguish the numerical value from its unit and discuss clear table headings. Apply a consistent, intelligible presentation in the report. A unit can appear in a well-defined column heading when every applicable entry shares that unit, or beside the individual value when the table contains a justified mixture. Choose the arrangement that makes the meaning clear to the actual recipient rather than the arrangement that merely saves the most space.

Check that the unit remains understandable when a table continues across pages or is extracted for a separate work package. Avoid a heading that combines several possible units without identifying which applies to each row. Similarly, a footnote that says all values are metric may be too vague when the table includes several kinds of quantities. Give the reader enough information to distinguish millimeters from micrometers, degrees from temperature, and dimensionless administrative counts from physical measurements. Do not rely on column position alone to carry that meaning.

A spreadsheet can display additional decimal places without adding information to the measurement. Conversely, a shortened display can conceal differences present in the accepted source record. Determine the project’s agreed presentation rule and the basis for any rounding. Do not choose decimal places by copying the longest value in the table or by assuming that every instrument produces the same meaningful precision. The responsible technical process should establish how results are reported for the examination and any subsequent evaluation.

Preserve the original accepted value even when a converted display uses a different number of digits. Record the displayed result separately from the source used for later calculation or review. Repeatedly converting and rounding an already rounded display can introduce avoidable differences. If another party needs more detail than the report shows, provide the appropriate controlled source through the agreed handover route. Do not invent missing digits or imply a measurement uncertainty that was never established. A tidy decimal format is a presentation choice, not evidence of accuracy.

Some entries carry qualifiers such as estimated, approximate, below a stated reporting limit or not measurable under the recorded conditions. Those qualifiers affect the meaning of the number and must survive preparation. Do not strip symbols or explanatory words just to make the column numeric. Ask the technical reviewer how the entry should be presented and whether a separate status or qualifier column is needed. A value that originally described a bound should not become an exact-looking measurement after a copy-and-paste operation.

Treat a missing value, zero and an unavailable measurement as different states unless the governing record explicitly says otherwise. A unit conversion cannot resolve missing evidence. Where an entry is withheld pending clarification, retain the item identity and the reason so the report remains reconcilable with the requested scope. The inspection report buyer-review guide helps assess that larger scope question. The unit worksheet should make the representation issue visible without changing the underlying technical disposition.

Before comparing two campaigns, suppliers or instruments, confirm that the values describe comparable locations and quantities. Converting units alone does not make two different measurement positions equivalent. Check the source date, method, location reference and any stated limitation that could explain a difference. Preserve the distinction between an observed change and a change caused by representation. If the available records do not support a comparison, describe the missing relationship instead of producing a difference column that gives the impression of a valid trend.

When a comparison is supported, retain the original source values and show the common presentation used for the comparison. Record any rule applied to rounding or excluded entries. A later reviewer should be able to follow why one row was compared and another was left unresolved. Do not use a report-formatting task to calculate remaining life, establish a corrosion rate or choose an inspection interval without the required technical basis. Those are separate analytical decisions whose inputs and authority must be addressed through the appropriate process.

Consider a fictional workshop record containing a confirmed thickness value of 0.250 in. The customer requests a metric display in the report while retaining the original evidence. The responsible preparer uses the agreed conversion reference and records 6.35 mm as the converted value. The table labels the original and converted columns separately. This simple example illustrates representation only; it does not establish that the reading is suitable for a particular evaluation or that the item meets any acceptance requirement.

A second source row contains an unlabeled value, and a third includes a note that the result awaits technical review. The preparer does not apply the same conversion blindly to those rows. The unlabeled entry remains open until its unit is confirmed; the review qualifier stays with the third entry. Before issue, the reviewer checks the original record, conversion worksheet and exported PDF together. The resulting table is more useful because it distinguishes verified presentation changes from unresolved evidence instead of making every row look uniformly complete.

Calibration records may help identify the equipment, measurement range or stated uncertainty relevant to an examination, but a report author should not invent reporting rules from a certificate without the required technical interpretation. Confirm the equipment actually used and the applicable source evidence. If a unit discrepancy raises a question about the instrument setup or recorded reading, escalate that question rather than treating it as a display issue. The calibration certificate review guide provides a separate framework for checking the document itself.

The calibration reminder tool supports entered due dates and configured reminders. It does not validate units, assign measurement uncertainty or determine the acceptability of a result. Keep those tasks distinct when documenting the preparation process. A reminder can prompt a person to obtain evidence, while the evidence and responsible review determine what can be stated. This distinction is particularly useful when a report is assembled from multiple instruments whose records use different units or describe different kinds of calibration activity.

A location expressed in millimeters can use a different origin or positive direction from another location expressed in the same unit. Identify the datum and orientation before combining coordinate columns. Changing inches to millimeters does not resolve a reversed axis, an offset origin or a measurement taken from another edge. Preserve the source convention and ask the responsible technical person to establish any required relationship. A report preparer should not infer a geometric transformation merely because the resulting positions seem to fit the component.

Keep a coordinate-convention note close to the relevant table or referenced sketch. State which source defines the origin and direction, and distinguish physical coordinates from sound-path or instrument-display quantities where applicable. If the client requests a different convention, retain the original reference and the authorized mapping used to produce the new display. The review should establish both the numerical representation and the physical meaning. This prevents a correctly converted distance from being reported at the wrong location.

A supplier’s decimal comma or grouping separator can be misread when data is prepared under another regional convention. Confirm the intended numerical value in the source application before replacing punctuation. Do not run a global find-and-replace across a report that also contains identifiers, dates and descriptive text. Test the affected numeric fields and retain a record of the source convention. An apparently small punctuation change can alter a value substantially, while a careful field-specific transformation preserves meaning and leaves unrelated content intact.

Use the free reporting workspace to assemble the reviewed values, then inspect the downloaded PDF. Read a representative row from its identifier through quantity, value, unit and qualifier. Check the headings on every page where the table appears. Confirm that a long heading has not become so abbreviated that it changes meaning. Technical symbols and unit prefixes should be legible, and the exported number should match the accepted display value in the worksheet.

Compare the conclusion with the units used in the body of the report. A narrative can retain an old unit label even after a table has been revised. Check captions, notes and any separately supplied summary for the same inconsistency. If a previously issued document contains a unit error, assess its consequences through the applicable amendment process rather than silently replacing a file. A unit-label correction can affect interpretation even when no numeric characters change, so the responsible reviewer should determine the significance.

Close the worksheet by identifying which changes were purely presentational, which used a checked conversion and which remain unresolved. Keep the source reference and the agreed output convention with the relevant report identity. The next preparer should not have to infer why one table contains original units and another contains a converted display. A concise explanation can prevent repeated reformatting that gradually disconnects the report from the examination evidence.

Apply the same review when a client changes a template or when a new supplier contributes data. An established layout is not proof that the new data uses the same quantity definitions or units. Check the affected columns and representative exceptions again. The intended result is a report whose values remain interpretable and traceable through a change of presentation, with original evidence preserved and technical decisions left with the responsible process. That is more useful than forcing every number into a common appearance without knowing what it describes.