Use origin labels carefully rather than creating a false hierarchy
A report can combine an instrument reading, a derived summary, a drawing value and a planning assumption. The reader needs to know where each entry came from and what it can support. Labels such as measured, calculated and estimated can help describe that origin, but they are not mutually exclusive scientific categories. A measurement process can involve computation and estimation. Do not use the labels to suggest that one number is automatically certain while another has no value. State the actual process and the evidence behind the entry.
NIST’s measurement uncertainty introduction describes measurement as a process that produces a value associated with a defined property. For this reporting workflow, begin by identifying that property and the source process. Then explain whether the report entry reproduces a recorded result, derives a new presentation from it or supplies a separate planning assumption. The worksheet is a practical provenance aid. It does not establish a new metrological taxonomy, validate a measurement model or replace the organization’s technical reporting requirements.
Identify the quantity and the event represented
Write down what the number describes before assigning an origin label. Thickness at a particular point differs from nominal wall thickness, and a count of examination events differs from a count of unique components. Include the relevant location, time or event reference when it changes the meaning. A value without that context can be misused even when its unit is correct. The report should let the recipient distinguish the property of interest from a convenient label inherited from a spreadsheet.
Confirm whether the value belongs to the examined item or to a reference used during the work. A reference-block dimension, drawing dimension and local measurement may all be lengths but serve different roles. Keep those roles separate in the result table or notes. Do not place a reference value in a result column simply because the local result is missing. If the source does not establish which event or item the number belongs to, retain that uncertainty as an open identification question before using the value in a conclusion.
Describe a recorded reading with its relevant context
When reproducing a recorded reading, retain the source result identity, unit and context required by the project. Identify the examination method and the instrument or record reference where applicable. Do not imply that copying the number into a new report constitutes another measurement. The preparer’s task is faithful representation of the accepted source, including qualifications or limitations supplied with it. If a value was marked for review in the field record, that marker should not disappear during report preparation.
An instrument display is not the complete description of how a result was obtained. The governing procedure, setup, location and review may be necessary to interpret it. The report does not need to reproduce every supporting document, but it should provide usable references and preserve the stated boundaries. Ask the responsible technical person which context is required for the recipient’s intended use. A label reading measured is not enough by itself to establish the validity, traceability or applicability of the result.
Make derived outputs distinguishable from their inputs
A derived output may summarize several recorded values, convert a presentation or apply a calculation selected by the responsible process. Identify the inputs and the calculation reference used for that output. Do not present an average, difference or other summary as though it were a separate reading taken at a specific location. The recipient should be able to tell whether the number came directly from an examination record or from subsequent processing of that record.
Keep the original inputs available through the agreed evidence route. A useful summary can make a report easier to read, but it should not conceal a relevant outlying value or an excluded entry without explanation. State the inclusion rule and the scope of the summary. If the calculation requires technical assumptions, identify their source and review. The free calculator directory does not remove that responsibility; a tool output still needs an appropriate quantity definition, input set and applicability check.
Keep nominal and specified values in reference fields
A nominal drawing value or a specified limit is not evidence of the actual condition at an examined location. Label it as a reference and identify the document or instruction from which it came. Do not use a nominal value to fill a missing measurement unless the governing process explicitly supports a different stated purpose. The report should make clear when a number describes intended design, an evaluation requirement or a recorded observation.
Check the revision of the reference and its applicability to the component under review. A drawing value from a similar item may not apply to the actual configuration examined. If the project uses a reference value in a calculation, preserve that role and the responsible review rather than letting it appear as another measurement. The comparison may be useful, but its meaning depends on the relationship between the reference and the observed item, not on the fact that both values can occupy adjacent spreadsheet cells.
Identify planning assumptions without disguising them as findings
A planning estimate can help schedule access, prepare a quotation or organize a future examination. It should remain identifiable as an assumption for that purpose. Record who supplied it, what information it was based on and which decision it is intended to support. Do not transfer it into the final result table without a supported explanation. A quantity estimated before mobilization does not become a measured examination outcome because the project later produced a report.
If the report needs to discuss an estimate, distinguish it from the findings and describe its limitation. Avoid giving a provisional assumption the same visual treatment as a reviewed technical result when that would mislead the recipient. Where the estimate affects a consequential decision, the appropriate responsible process should determine what evidence is required. The reporting workspace does not authorize estimation, assess its uncertainty or decide whether it is adequate for engineering acceptance.
Preserve uncertainty information that the source actually provides
When the source includes measurement uncertainty or another defined qualification, preserve its meaning and reference. Do not replace it with a generic percentage or assume that the last displayed digit establishes uncertainty. NIST’s guidance on reporting uncertainty emphasizes explaining how a reported uncertainty was obtained in its measurement context. Use the applicable project and technical requirements to decide what belongs in the report, and ask the responsible person when that information is missing.
Do not combine different kinds of uncertainty statements casually. A calibration certificate’s information may not describe the complete uncertainty of a field result, and a planning range may not be a measurement-uncertainty interval. Keep the source terminology and scope clear. This guide does not calculate uncertainty or prescribe a coverage factor. Its practical purpose is to stop a report preparation step from deleting a meaningful qualification or inventing one that the source evidence never established.
Keep units and presentation changes traceable
Changing the display unit does not create a new observation. Retain the original value and identify the converted presentation where the deliverable requires it. Similarly, rounding a derived result should follow an agreed rule rather than the report author’s preference for visual consistency. A recipient should be able to distinguish the accepted numerical result from the way it is displayed. Record the conversion or presentation reference when it is necessary to understand the value.
Check that the origin label remains appropriate after the transformation. A column labelled instrument reading should not quietly contain a converted or aggregated value without explaining the relationship. Where a concise heading cannot carry the full meaning, use a qualifier or reference column. The report is easier to review when its terms describe what actually happened to the data. Do not force all entries into one numeric format at the cost of losing source units, qualifying words or the distinction between an observed and supplied reference value.
Worked example: three numbers with different roles
In a fictional piping record, a technician’s accepted source contains a local thickness reading for one identified point. The customer drawing supplies a nominal wall value, and a planning worksheet contains an estimated length of accessible pipe. All three numbers are useful in their own context, but they describe different quantities or roles. The report preparer separates them into a recorded-result table, a drawing-reference field and a planning note. None is substituted for another merely because the original spreadsheet placed them on the same row.
A reviewer then asks for a summary of the completed measurement locations. The preparer obtains the supported summary and its inclusion rule rather than presenting the planning length as completed coverage. The report identifies the source of the summary and retains the individual result references. This hypothetical example does not provide a wall-thickness acceptance rule or a corrosion assessment. It shows how a clear description of origin prevents a design reference or planning assumption from being mistaken for examination evidence.
| Entry | Origin | Appropriate role | Unsupported substitution |
|---|---|---|---|
| Local thickness result | Accepted examination record | Result for the identified location and event | Condition of every nearby location |
| Nominal wall value | Applicable customer drawing | Design reference with document identity | Missing local measurement |
| Accessible length estimate | Planning worksheet | Planning assumption with stated basis | Verified completed coverage |
| Completed-location summary | Reviewed result set | Summary with a defined inclusion rule | Independent new measurement |
Review comparisons for differences in origin
Before calculating a difference or describing a trend, check whether the compared entries represent the same quantity and a supported physical relationship. A local reading and a nominal drawing value can be compared for a defined purpose, but the report must explain that purpose rather than imply two repeated measurements. A historical estimate and a later measurement need an equally clear distinction. The origin worksheet should expose those differences before a reader interprets the numbers as a time series.
Retain entries that cannot be compared with a clear reason, or omit them from the comparison while preserving their source record as required. Do not silently remove inconvenient values to produce a smoother trend. If a technical assessment is requested, provide the information to the responsible process and identify any missing relationship. A report preparation guide cannot establish that different methods, locations or measurement conditions produce interchangeable results. The conclusion should stay within what the actual comparison evidence supports.
Assign responsibility for each reported origin statement
Identify who can confirm the source and meaning of the value. The examiner may establish the recorded observation, another person may own the calculation, and the customer may control the drawing reference. The report compiler can organize those inputs without claiming to have performed every underlying action. Keep authorship and review roles accurate. An origin label should help the reader find the responsible evidence, not create an appearance of independent verification that never occurred.
Use the procedure draft workspace to organize proposed reporting responsibilities if needed, then obtain the appropriate technical review outside the tool. Generated wording does not establish competence or approval. The report buyer-review guide helps a recipient ask whether the package answers the requested scope. The origin worksheet supports that review by making it easier to see which values are reproduced, derived, referenced or still dependent on an assumption.
Enter the provenance in a form the recipient can use
In the free digital reporting workspace, use a clear result label and a source or qualifier column where the distinction matters. Do not overload a short cell with an entire calculation history. Reference the controlled evidence and retain the essential explanation in the report. The editor does not automatically classify the origin of entered values or verify a source dataset. Users must supply the descriptions that accurately represent their own records.
Review the PDF after export. Read the value, unit, origin statement and surrounding conclusion together. Check that a concise heading has not removed the distinction established in the worksheet. If the report uses a symbol or abbreviation for value origin, define it where the recipient can find it. A separately delivered table should remain intelligible without an undocumented verbal explanation. Keep the representation consistent across the detailed results and any executive or closeout summary.
Do not turn provenance labels into an unsupported quality score
A color or ranking system that marks every recorded reading as reliable and every estimate as unreliable can create another misunderstanding. The adequacy of a value depends on its intended use, the process that produced it and the supporting evidence. A carefully reviewed derived result may answer a question that an isolated instrument display cannot. Conversely, a number copied directly from a device may be unsuitable for the proposed conclusion. Use the origin description to direct the review, not to replace it with an automatic confidence grade.
If the project uses a separate quality or review state, define it independently and identify who assigned it. Keep the evidence for that state retrievable. The report can then show both how an entry originated and whether the relevant review has been completed. Avoid symbols whose meaning changes between tables, and ensure the explanation remains readable in a monochrome copy. The recipient should not have to infer technical adequacy from a color that was chosen only to make the document easier to scan.
Reassess the origin when the source changes
A revised source may change more than the numeric output. An estimate can be replaced by an actual observation, a calculation can use a different input set, or a drawing reference can be superseded. Record that change in role as well as the changed value. Do not leave an old origin label attached to a new kind of evidence. Where an issued report is affected, follow the applicable controlled amendment process and preserve the relationship to the earlier record.
Close the worksheet when every included value has a defined quantity, identifiable source, supported reporting role and relevant limitation. Keep unresolved entries visible for the responsible decision maker. The result is a report whose numbers can be interpreted in context, without pretending that every entry is a direct observation or that every calculation is an independent finding. That clarity helps the recipient ask the right follow-up question and reduces the risk of using a planning assumption as if it were examination evidence.
Reported-value origin map
Download this editable CSV for the task described above. Replace illustrative prompts with your own supported facts. The worksheet is a planning aid; it does not establish inspection acceptance or approval.
Download the free workflow worksheetQuestions about this workflow
Are measured and estimated mutually exclusive scientific categories?
No. Measurement can involve computation and estimation. Use practical origin descriptions to explain the actual process rather than treating the labels as a rigid taxonomy.
Can a nominal drawing value fill a missing measurement?
Do not represent it as an observed result. Keep it as an identified reference and obtain the responsible decision for any intended use.
Does the reporting tool classify or validate value origins?
No. Users enter the source description and technical content. The tool formats the record and does not independently validate a measurement or calculation.
What should accompany a calculated summary?
Identify the input set, inclusion rule, calculation reference, accepted output and relevant review, while preserving access to the supporting records.
Sources and editorial scope
Primary references support the specific context cited in the guide. Worked examples and suggested workflows are NDT Connect editorial guidance. Confirm the documents and authority applicable to the actual assignment.
More guides: report data integrity
- Review Mixed Units and Precision in NDT Result Tables
A number needs an identified quantity and unit before it can be compared. Preserve the original evidence and make any approved change of representation explicit.
- Prepare a Redacted NDT Report Copy Without Losing Context
Prepare a limited distribution copy only for a defined purpose and authorized audience. Preserve the master record and check that removing information does not misrepresent the examination.
- Build an NDT Report Field Dictionary for a Client
A column heading is only a shorthand. A practical field dictionary explains what belongs in the column, where it comes from and how the recipient should interpret it.
- Separate NDT Screenshots from Source Measurement Records
A screenshot records a selected view. Explain what it shows, which source produced it and which decisions require access to evidence beyond the image.
