Keep Multiple Acceptance Bases Clear in One NDT Report

For every reported acceptance or rejection statement, identify the actual criterion used and the component or examination scope to which it applies. A header listing several codes does not establish that relationship. The reader needs to know whether the documents apply to different items, impose concurrent requirements or represent alternatives awaiting clarification. Do not choose the relationship by assumption. Obtain the applicable instruction from the responsible project process and preserve it in the report’s basis mapping.

Keep the examination evidence separate from the decision made using it. A measured value, indication description or coverage statement may be reusable information, but a disposition belongs to its stated evaluation basis. Changing that basis can require a new review and may reveal that the original evidence is insufficient for the new question. The report should not make an acceptable label appear independent of the document, edition, scope and assumptions under which the responsible evaluation was performed.

Identify which document describes how the examination is performed and which supplies the relevant evaluation or acceptance requirements. Their relationship depends on the actual governing documents. ASME publishes BPVC Section V for nondestructive examination, but a public catalog title alone does not establish the complete acceptance basis for a particular item. Consult the controlled documents that apply to the project rather than deriving a pass or fail rule from a familiar standard name.

Record the applicable procedure reference separately where the project requires it. A procedure can incorporate or reference criteria, but the report should still make the controlling relationship understandable. Do not assume that an internal procedure title resolves every customer-specific requirement. If the instructions conflict or leave the acceptance basis undefined, raise the question before presenting a final disposition. The scope intake guide helps identify such requirements at the request stage; this matrix preserves them through the final report.

Record the document identifier, applicable edition or revision and the relevant project reference with enough precision to retrieve the intended requirement. Similar titles can describe different documents or revisions. A report that says latest edition may become ambiguous after publication changes. Use the edition actually required and applied, based on the project’s instructions. Do not automatically substitute the newest publication into an earlier examination record or assume that a current website listing determines the contractual basis.

Where a customer specification supplements another document, preserve both references and the actual relationship. A client addendum may address only a particular feature or reporting requirement. Do not describe it as replacing the entire governing document unless the authorized instruction establishes that effect. Keep the evidence of applicability available in the supporting package. The report preparer’s role is to record the real basis accurately, while the responsible technical and contractual processes resolve which requirements apply and how conflicts are handled.

Choose a table structure that makes each item’s basis visible. A component family, joint category, manufacturing stage or examination zone may determine which criterion applies. Use the actual project classification and avoid inventing categories to simplify the table. If several rows share one basis, a clearly defined group reference can keep the report concise. The group must be unambiguous, especially when the table continues across pages or when a subset is copied into another document.

Check whether one physical component contains areas governed by different requirements. A single component-level acceptance label may be too broad when the evaluated zones differ. Preserve the zone-to-basis relationship and the scope of the conclusion. Do not combine separate evaluations into a global acceptable statement unless the responsible process supports that conclusion. A good mapping lets the reader identify the basis of a particular result without searching through a long narrative or assuming that the first code in the header applies everywhere.

If two requirements apply to the same item, establish how they are to be used through the actual governing process. Do not default to whichever criterion appears stricter. Requirements may address different features, methods, reporting conditions or decision rules, so a simple numerical comparison may not resolve the relationship. Record the authorized interpretation and reference it in the basis matrix. Where the relationship remains unresolved, keep the disposition open rather than choosing the rule most likely to produce a convenient outcome.

Keep commercial preference separate from technical applicability. A buyer may request a different criterion, but the request still needs the appropriate assessment and authorization. A supplier’s standard practice does not automatically override the customer’s governing requirement. The quote comparison tool can organize actual scope assumptions and exclusions during procurement, but it does not decide which acceptance document has priority. Preserve the final agreed technical basis instead of allowing an unresolved bid assumption to become an implicit reporting rule.

A different acceptance basis may require information that the original examination did not record or was not designed to establish. The responsible reviewer must assess whether the data, coverage and procedure are adequate for the intended evaluation. Do not assume that a saved result can be reclassified under any new criterion simply because the underlying file still exists. Identify the missing information or technical question and retain the original evaluation context while the new request is considered.

Where the evidence supports only part of the new evaluation, describe that boundary accurately. A report can present the available measured information without making an unsupported final disposition. The matrix should distinguish the supplied criterion, the evidence reviewed and the resulting state. If additional work is authorized, record it as a new event with its own scope. Do not retrospectively describe the original examination as having followed requirements that were introduced only after acquisition or that the original setup did not address.

Confirm that the quantities being compared mean the same thing. A threshold expressed for one feature definition cannot automatically be compared with a measurement of another. Units, reference dimensions, classification and the applicable evaluation procedure may all matter. Use the actual technical requirements and reviewed source values. Do not invent a conversion, rounding rule or measurement uncertainty allowance because a spreadsheet needs a single pass or fail result. The responsible process must establish the appropriate comparison.

Record any derived or converted value separately from the original where necessary to understand the evaluation. Preserve the calculation reference and the actual precision used. A rounded display can hide a distinction that matters to the decision, while excessive digits can imply unsupported precision. This guide supplies no acceptance thresholds. Its purpose is to make the relationship between evidence and criterion visible so the authorized evaluator and recipient can understand how the stated disposition was reached.

In a fictional order, components A1 and A2 are assigned to customer specification CS-A at a defined revision. Component B1 is assigned to CS-B. The examination provider receives an additional note suggesting that CS-B may also apply to A2, but the relationship is not yet confirmed. The report matrix records the established assignments and the open question. It does not silently evaluate every item under both documents or choose whichever produces the more favorable result.

The responsible project authority clarifies the A2 requirement and the technical reviewer checks whether the available evidence supports the required evaluation. The report then records the actual basis and outcome, or the remaining limitation if further evidence is needed. This scenario is hypothetical; CS-A and CS-B are fictional labels with no implied thresholds. It illustrates how a small applicability question can affect a disposition even when the acquired data itself has not changed, and why the report should preserve the decision reference.

A report disposition under a specified examination criterion does not automatically answer every question about service suitability, remaining life or operational release. Those may involve different inputs and responsible processes. State the scope of the actual evaluation and avoid expanding it through broad phrases such as safe for all service. If another engineering assessment uses the examination evidence, identify that separate record rather than claiming the NDT report itself performed the assessment.

The same boundary applies when the customer asks for information only. Record what was requested and what the provider actually evaluated. An information-only measurement table should not inherit an acceptance label from a template if no applicable criterion was supplied or applied. Conversely, do not remove a required disposition merely by calling the report informational. Resolve the actual reporting obligation through the responsible process and make the resulting scope clear to the recipient.

For a wide result table, a short basis key can reduce repetition. Define each key in a nearby reference table with the exact document identity, applicable revision and relevant scope. Ensure the key is unique within the report and remains understandable across page breaks. Avoid codes such as A and B when those letters are already used for component zones or indication categories unless the labels are clearly distinguished. A compact presentation is useful only if it preserves the relationship the reader needs.

JPL’s QC14b NDI/NDT certificate clause separately identifies acceptance requirements and the NDI/NDT specification in that procurement context. This is a useful example of why the report should not collapse every reference into one generic standards field. It is not a universal template mandate. Use the actual customer requirements and make the examination instruction, evaluation basis and result relationship clear through a structure that fits the assignment.

If the customer changes the acceptance basis after an examination, record the request and its authorized applicability. Determine whether it concerns future work, a new evaluation of existing evidence or correction of an earlier misunderstanding. Those cases require different report histories. Do not simply replace the document revision in the header while leaving the old disposition untouched. The responsible technical review must establish whether the result remains supported and whether any additional information or work is needed.

Preserve the original basis in the historical record. A later evaluation can reference the same acquisition event while reaching a conclusion under a different stated requirement, but the relationship must be transparent. Do not imply that the original examiner used the later criterion at the time of acquisition. If an issued report needs amendment, follow the applicable document process and identify the affected versions. The report amendment guide provides planning questions for that controlled replacement relationship.

The free digital reporting workspace lets you enter project references, custom fields, tables and notes. When several bases apply, use an explicit table or scoped notes to preserve their relationships. Do not force a long mixed list into a single field and expect the application to decide which criterion governs each row. The tool does not interpret paid standards, evaluate indications or calculate technical acceptance from the references you enter.

If one combined report becomes difficult to read, consider separate clearly linked reports or tables under the project’s document process. Keep the shared acquisition references and distinct evaluation bases visible. The procedure draft tool can help organize proposed reporting responsibilities for review, but it does not approve a criterion selection. Choose the presentation that makes the actual decisions easiest to understand rather than the one that produces the fewest pages or the shortest standards list.

Read the conclusion against the basis matrix and the detailed rows. A statement that all items meet requirements is too broad if some items were evaluated under different scopes or remain unresolved. State the supported group and basis explicitly. Check that a summary count of accepted items does not combine records whose dispositions mean different things without explanation. The reader should not have to infer which requirements were satisfied from a colored status cell or a single total.

Inspect the exported PDF for readable references and correct table associations. Long identifiers and revision labels must remain distinguishable after wrapping. If a basis key is defined on another page, make its location easy to find. The report buyer-review guide offers wider delivery checks. This particular review asks whether a recipient can connect any reported disposition to the actual criterion and scope without relying on the preparer’s memory.

Keep the authorized clarification or instruction that established the basis relationship, using the project’s actual record process. The report may only need a concise reference, but the supporting decision should remain retrievable. Avoid copying proprietary standard text or a large customer specification into a worksheet when a precise controlled reference is sufficient. The free planning matrix is not a substitute for access to the governing documents by the people who must perform and review the evaluation.

Use the worksheet below to identify each item, examination reference, acceptance basis and unresolved applicability question. Replace the fictional labels with actual project information. The completed matrix should protect a simple but essential distinction: the examination produces evidence within a scope, and the responsible evaluation applies an identified requirement to that evidence. Keeping both parts visible prevents a valid result from being reused as an unsupported universal approval when a report crosses projects, specifications or later decision contexts.