Describe TOFD Coverage Limitations in a Report

A TOFD report should explain the examined region and the limitations that affect its interpretation. A statement that a weld was scanned does not establish that every required location or depth was assessed with the necessary capability. Separate the physical length acquired from the technical region supported by the examination. Record the applicable reviewed basis for each conclusion. This gives the recipient a useful description of the work without implying that a continuous-looking display resolves every coverage question.

This worksheet concerns reporting an actual reviewed examination, not selecting probe spacing or approving a technique. The responsible technical process supplies the configuration, demonstrated capability and disposition of limitations. Do not replace that process with a standard-looking phrase copied from an earlier report. Where the evidence is incomplete, describe the remaining question and the associated action. A well-defined limitation is more useful than a reassuring general statement that cannot be connected to the examination record.

The primary research paper Towards an Alternative to Time of Flight Diffraction discusses limitations associated with the lateral-wave and backwall responses. Its experimental conditions are not a universal specification for another examination. Preserve the actual technical assessment for the component and setup being reported. Do not copy a published example depth into the report as if it were measured or demonstrated for the current job. The important reporting distinction is which region is affected and what supports that statement.

Use separate entries where the near-surface and far-surface questions differ. A single dead-zone note can hide different evidence, locations or follow-up requirements. Identify the relevant surface from the actual scanning arrangement rather than assuming that near surface always means outside diameter or that far surface always means inside diameter. Components can be scanned from different accessible surfaces. State the viewing or scanning reference explicitly so the recipient can relate the limitation to the physical component.

Record the applicable setup reference, probe arrangement and acquisition event. If configuration changed along the examination, identify the affected segment boundaries. A limitation assessed for one arrangement should not silently be assigned to another. Keep the supporting setup or demonstration record available through the agreed technical file. The report can use a concise reference instead of reproducing every setting, provided the relationship is clear and the referenced record can actually be retrieved by the intended recipient.

The manufacturer-hosted STIX scanner manual distinguishes probe-centre spacing and encoder-related positioning in its mechanical setup documentation. For reporting, preserve the actual configuration and position reference rather than relying on the scanner name alone. This source does not establish that a particular setup meets the project requirements. Equipment identification, acquisition configuration and a supported technical coverage conclusion are different pieces of the record and should remain distinguishable.

A limitation near one surface and a missed portion along the weld are different problems. Give each its own location description. A near-surface limitation may apply throughout a defined acquired segment, while an interruption may leave a specific length without usable acquisition. Combining them into one general percentage can make the result impossible to interpret. Preserve both dimensions of the question: where along the component the issue applies and what region or evidence within that extent remains limited.

Use the project datum, direction and segment identifiers consistently. Where the actual boundary is uncertain, keep that uncertainty visible rather than forcing the entry into a precise range. The worksheet does not calculate coverage percentages or determine an acceptable amount of missing examination. It provides a place to record the assessment supplied by the responsible reviewer. That distinction helps prevent an administrative summary from becoming an unsupported engineering claim about what the method could or could not detect.

A reported boundary may come from a reviewed demonstration, the approved technique basis, examination data or another documented assessment. State which evidence applies. Do not describe a planning assumption as an observed result or a generic manufacturer illustration as a project-specific demonstration. If the report uses a value supplied by another party, retain its source and review status. The recipient should be able to tell whether the boundary was established for this configuration or remains a question awaiting technical resolution.

Preserve the relationship between the evidence and the examination conditions it represents. A supporting record for a different geometry, material condition or setup may require review before it can support the current claim. The report preparer should not decide equivalence simply because both records mention TOFD. Ask for the actual decision and document its reference. When the available evidence does not establish the connection, an explicit pending entry is preferable to presenting the unsupported boundary as a settled fact.

Where another examination addresses a TOFD limitation, identify its method, event and reviewed scope. Do not write that a supplementary test covered the dead zones without a supporting relationship to the affected physical regions. The additional record may answer only part of the question or may use a different datum. Preserve the correlation supplied by the responsible technical process. A method name alone does not prove that its execution addressed the particular limitation described in the TOFD report.

Keep the supplementary result and the overall coverage decision separate where necessary. A completed surface examination does not automatically resolve a depth-related limitation beyond its supported scope. Equally, an additional ultrasonic record needs its own configuration and location relationship. This guide does not prescribe a mandatory companion method or claim interchangeability between techniques. It helps the report show which evidence addresses which question and which questions remain open after the actual combined review.

A change in a lateral-wave or backwall response is an observation requiring the appropriate analysis. Do not turn the report preparer’s description of that change into a diagnosis of a particular discontinuity. Preserve the responsible interpretation and any stated limitations. Where an observation triggered further review, identify the review record and its outcome. An unexplained signal feature should not disappear merely because the result table has room only for accepted or rejected entries.

Selected images can help explain the issue, but their display context matters. Reference the source data, selected view and relevant location. A cropped picture may remove the information needed to understand the physical relationship. Keep examination images and native data in the agreed external package and reference them accurately. The reporting workspace does not analyze native TOFD files or attach examination images through its logo controls, so a narrative reference must not imply that those materials are embedded in the generated PDF.

In a fictional examination, segment A has a reviewed near-surface limitation, and a supplementary record is supplied to address that defined region. Segment B also contains an acquisition interruption around a fixture. The draft conclusion says that supplementary examination completed all missing coverage. The reviewer separates the two entries because the supplementary record relates to the surface-region question in A, while the interruption in B has no documented follow-up. The report cannot combine those different relationships into one completed status.

The revised record links A to the actual supplementary examination and the responsible coverage decision. It keeps B open with its location and next required review action. No generic depth, scan length or acceptance threshold is assigned in this example. The scenario is hypothetical and illustrates evidence organization only. Its useful outcome is a report in which the recipient can distinguish a resolved limitation from a separate unresolved acquisition gap without having to infer either from the presence of another method name.

A later analysis can change the interpretation or presentation of existing data. It does not automatically add physical acquisition. Record whether the follow-up involved reanalysis, a new examination or a review of separate supporting evidence. This prevents a revised report from implying that the original field event included work performed later. Use the actual event dates and relationships supplied by the source records, particularly when the component condition or access arrangement changed between activities.

If a previously reported limitation is withdrawn or narrowed, preserve the basis for that change. Do not simply delete the original entry and leave no explanation for recipients who saw the earlier report. The project’s amendment process determines how the correction is issued. The reporting worksheet helps identify what changed, which evidence supports it and which conclusion is affected. It does not decide whether reanalysis alone is sufficient for a particular technical or contractual requirement.

Read the summary statement alongside the limitation register. A broad no-reportable-indications conclusion can be misleading if a required region remains outside the supported examination. Use the wording provided through the responsible technical review and preserve the scope qualification where it belongs. Do not hide a material limitation in a distant note while leaving the first page to suggest complete assessment. The practical goal is that a reader understands the examined scope before relying on the reported result.

Avoid treating reporting status as technical acceptance. Draft and Issued identify a user-declared document state in the workspace; they do not certify coverage or approve the component. Keep the actual decision reference and responsible role separate from the PDF label. If the report is an interim communication, state the outstanding examination or review boundary plainly. The report should not acquire a stronger technical meaning merely because it has a number, revision and polished layout.

Use columns for the component or segment, physical reference, limitation type, evidence basis, related examination and disposition reference. Long technical explanations can sit in numbered notes tied to the relevant row. Avoid a table so wide that important qualifications become difficult to read. The recipient needs to compare the boundaries and evidence relationships, not decipher a dense transcription of every instrument setting. Keep the actual values and units intact when transferring reviewed information from the source record.

The free reporting workspace can hold this table and the explanatory narrative. Review supported DOCX or XLSX imports before applying them, including empty cells and source identifiers. The equipment tracker can organize supporting instrument records, but it does not determine examination capability. The procedure workspace produces a draft for responsible review and cannot approve a TOFD technique or resolve the limitations entered in the report.

Choose one limitation row and follow its references to the actual source record and any supplementary examination. Confirm that the intended recipient can identify the right event and physical extent. Then work in reverse from a delivered supplementary record to the question it addresses. This exposes records that are present in the folder but not connected to the conclusion. A package can be large and still fail to explain why a particular limitation was considered resolved.

Check that filenames, revision references and dates agree across the table, narrative and external index. Where a document is referenced but not included, describe its actual delivery or access arrangement accurately. Do not label a missing file attached. The report buyer-review guide offers broader closeout checks. For TOFD limitations, the decisive test is whether the evidence relationship supports the precise scope of the report statement rather than merely confirming that several inspection records exist.

A client receiving several inspection reports may read complete as a project status rather than a description of one acquisition task. Define the report language before the handover summary is prepared. If the field crew completed the planned TOFD passes but the combined coverage review remains open, those are two separate states. Preserve both rather than choosing the more favorable word. The coordinator can then schedule remaining work or obtain missing evidence without mistaking administrative completion for a supported technical conclusion.

Use a short explanation where the recipient is unlikely to share the examination team’s vocabulary. For example, describe whether a limitation concerns interpretation close to a named surface, a physical interval without acquisition or an unresolved correlation between records. Keep the reviewed technical terminology as well, so the explanation does not replace its precise meaning. This helps procurement, maintenance and quality personnel understand the practical consequence while leaving the technical boundary and disposition with the responsible reviewer. It also reduces the chance that a qualified report statement becomes an unconditional claim when copied into a broader closeout spreadsheet.

An unresolved entry should say what is needed next and who is responsible for arranging the decision through the actual project process. Separate a request for missing documentation from a need for additional field examination; they have different practical consequences. Do not assign a deadline or imply that access is available unless that information is confirmed. Record the current boundary and the relevant communication reference so the next person can continue the work without reconstructing the entire discussion.

Use the downloadable worksheet as a structured starting point and replace its fictional example with real reviewed evidence. A finished register should make near-surface, backwall and along-weld acquisition questions distinguishable, preserve their technical basis and connect any resolution to the actual supporting event. It remains a reporting aid. The technique, interpretation and acceptance decisions belong to the responsible technical process, while the report makes those decisions and their limits clear enough for the recipient to use correctly.