Report Inaccessible NDT Areas Without Implying Coverage

Describe the requested area that could not be examined and connect it to a location reference. A general note such as limited access does not tell the recipient which part of the request lacks evidence. Identify the component, surface, zone or volume affected at the level the source records support. Keep the performed examination boundary separate from the unexamined boundary. The report should make both understandable without implying that the accessible portion represents the condition of the inaccessible portion.

Do not convert an access limitation into a numerical result or a technical disposition. Not examined is different from no reportable indications and different from a completed examination that produced an unusable reading. Preserve the actual state. If the source record cannot establish the precise boundary, say that the extent requires clarification. A rough estimate can be useful for planning when labelled appropriately, but it should not become an exact coverage statement merely because the report template contains a percentage field.

Use the agreed scope list or examination plan to identify what was intended. Record the relevant document and revision alongside the inaccessible area. This prevents an uncompleted request from disappearing when the final report lists only the locations where data was obtained. The scope intake guide helps establish the starting boundary. The exception register then preserves the difference between that request and what was actually possible during the documented examination event.

Where the request itself used a broad phrase, resolve the intended location through the responsible project process. Do not assume that entire component means every surface, every volume and every possible technique. Equally, do not narrow the request after the fact to match the accessible area without an authorized basis. Record the original ambiguity and the clarification reference. The purpose is a faithful account of the work, not a retrospective scope definition that makes every assignment appear complete.

Record the condition that prevented the planned examination: an installed obstruction, unavailable access arrangement, restricted work area or another supported circumstance. Use factual language grounded in the field record. Avoid diagnosing why the obstruction exists or assigning blame unless that information is established and relevant. A concise description should help the responsible planner understand the issue. It should not direct an examiner to remove equipment, enter a restricted space or improvise an access method outside the project’s authorized process.

Separate the observation from a proposed remedy. A crew may suggest that another access arrangement could help, but that suggestion needs the appropriate site and technical assessment. Record it as a proposal if it is useful. The report itself does not issue permits, approve isolation or establish safe access. A clear limitation can support planning while leaving the actual access decision with the responsible people. This avoids turning a reporting worksheet into an informal work instruction that nobody has reviewed.

Being able to touch or see an area does not automatically establish that the intended examination can be performed there. The required equipment arrangement, surface condition or technique geometry may impose a different practical boundary. Record the actual limitation supplied by the responsible technical process rather than equating physical reach with examined coverage. Conversely, some authorized techniques may obtain relevant information from a different access surface. The report should describe the method and supported coverage rather than infer coverage solely from where the examiner stood.

Keep this distinction clear when a photograph shows apparent access. The image may locate the work area without demonstrating that the required examination arrangement was possible. A technical coverage question needs the relevant procedure, setup and event evidence. NASA’s product verification guidance treats configuration and supporting verification conditions as part of the evidence in its program context. For this register, the practical point is to describe the actual examination conditions instead of relying on an impression from an overall site photograph.

Connect the exception with a controlled drawing, sketch, grid or component feature that the recipient can use later. Temporary markings may disappear after cleaning, coating or routine work. Record the relationship to a durable reference where available. If the location is described from one viewing direction, define that direction. A note saying behind the bracket can be ambiguous when several brackets are present or when the next team approaches the component from a different side.

Keep the map’s level of precision honest. Do not add dimensions that were not measured or assume that a schematic drawing is to scale. If the field record supplies an approximate boundary, label it accordingly and identify what further information would establish the exact extent. A useful map can distinguish the area well enough for planning without pretending to be a survey. The technical reviewer determines whether the available location evidence is sufficient for the required examination and reporting decisions.

An overall image and a detail view can help a recipient understand why a location was inaccessible. FHWA’s LTBP photography protocol illustrates the value of location context and a photo log in its bridge research work. Use that idea proportionately: connect the image to the exception and its location reference. The photograph does not establish the condition of the area it cannot show, and it should not be captioned as evidence that the obscured region was examined.

Keep originals and annotated copies distinguishable in the external package. A marked arrow can identify the obstruction without defining an exact examination boundary. State what the markup represents. The current reporting tool’s image fields are company and client logo fields, so record inspection photo references as text and supply the files through the agreed separate arrangement. Do not imply that the PDF contains attached site photographs when it contains only their filenames or a description of where they can be retrieved.

If a customer requests a percentage, define what is being measured and how the denominator was established. Surface area, weld length, examination volume and number of planned locations are different measures. Examining nine of ten locations does not necessarily mean ninety percent of the requested surface or volume was covered. A percentage without a defined basis can look precise while hiding the most important limitation. Where the source evidence supports only a location list, report that list rather than manufacture a percentage.

Keep the quantity statement consistent with the method and the authorized scope. A technical reviewer may need to assess coverage in a way that cannot be reduced to a simple geometric fraction. The register can reference that assessment rather than inventing its own calculation. If the extent is estimated for scheduling, distinguish that estimate from a verified examination coverage statement. Planning quantities should not migrate into the technical conclusion without the supporting basis and responsible review required by the project.

In a fictional assignment, component P-62 has three requested zones. Zone A is examined within the recorded scope. Zone B cannot be reached because the planned access platform is unavailable. Zone C can be reached physically, but the intended examination arrangement is obstructed by an installed feature. The coordinator records B and C separately because their next decisions differ. It does not describe the component as fully examined or combine both exceptions under one unexplained difficult access note.

For B, the responsible site planner must resolve the access arrangement. For C, the responsible technical and site participants must assess the actual examination options and any required changes. The report records the supported limitation and references the location evidence for each zone. This hypothetical example establishes no particular access remedy or alternative technique. It shows why a useful exception register distinguishes an unavailable work position from a method-specific arrangement problem, even when both ultimately leave requested examination evidence incomplete.

A different technique or access arrangement may be proposed to address the limitation. Preserve that proposal and the required technical assessment instead of presenting it as an automatic equivalent. The applicable requirements, geometry, material and examination objective determine whether the alternative is suitable. The report preparer should not promise full coverage from a different method without the actual supporting decision. Record the approved instruction and its scope when the responsible process establishes it.

If the alternative is performed, give the event its own reference and describe what it establishes. It may address all, part or a different aspect of the original question. Do not erase the original limitation simply because additional data now exists. Link the new evidence to the exception and record the supported current state. The resulting history should show why the later work was needed and how it relates to the original requested area, rather than making the initial event appear more complete than it was.

A customer may defer an inaccessible area, remove it from the assignment or request another plan. Those are different outcomes and need the actual instruction reference. A deferral usually means the question remains for later action; a scope removal changes the current request but does not create examination evidence. Do not use a commercial exclusion or a scheduling decision to imply that the hidden condition is acceptable. The report should preserve the technical evidence boundary regardless of how the work is contracted.

The quote comparison tool can organize real access assumptions and exclusions when planning a follow-up. It does not decide whether the original supplier is responsible for additional work or whether a technical requirement can be waived. Keep those decisions with the applicable contract and technical process. In the exception register, record the outcome and reference clearly enough that a future coordinator can tell whether the area still needs attention rather than assuming every closed purchase order means completed examination.

An inaccessible area creates a limitation in the available evidence. The significance of that limitation depends on the actual examination objective and applicable requirements. Do not infer that the component is unsafe, safe, compliant or noncompliant solely from the existence of the access problem. Route the question to the responsible technical authority. The register should identify what is unknown and what decision is required, without pretending to supply an engineering assessment that was never performed.

If the project’s actual process establishes a restriction, hold or required notification, reference that decision accurately. Do not invent a standard hold duration or a universal permission to proceed. The procedure draft workspace can help organize proposed limitation-reporting responsibilities for review, but it does not approve them. A well-written exception is useful because it tells the responsible people exactly where the evidence stops and what information they need to evaluate the next step.

A detailed table may describe the exception correctly while an executive summary says all work completed. Check every summary that relies on the report, including quantity totals and status updates. Use language that preserves the difference between completed accessible work and unresolved requested areas. If a dashboard accepts only a simple status, establish a representation that does not hide the limitation and link to the detailed record. Do not let a restrictive format force an inaccurate claim.

When the report is excerpted for a client meeting or planning note, carry the relevant limitation with the extracted result. A measurement from an accessible region can be misunderstood when separated from its coverage boundary. The report preparer cannot control every future use, but the delivered record can make the intended scope clear and easy to retain. A concise exception reference near the result is often more useful than a broad disclaimer placed far from the table it qualifies.

When access becomes available, connect the follow-up examination to the original exception. Confirm what area was actually examined and whether any portion remains unresolved. Do not close the whole exception merely because the crew returned to site. A later visit can encounter another limitation or complete only part of the planned work. Record the event and current boundary at the level needed to support the conclusion. Preserve the original access record where it explains the sequence of the assignment.

If the follow-up uses a revised drawing or location convention, retain a cross-reference so the recipient can recognize the same physical area. An exception that changes names can be lost between work packages even when everyone intends to address it. The completed register should make that relationship explicit. Where a later report supersedes a previous statement, follow the actual document process and identify the affected versions. The new evidence should resolve a defined question, not merely replace an old file without explanation.

Use the free digital reporting workspace to enter the performed results and a clear exception table. The worksheet below helps organize location, reason, evidence and next action before export. Read the downloaded PDF to confirm that the limitation remains visible beside the relevant component and that page breaks do not detach it from the result. The app does not determine examination coverage or technically approve a proposed alternative; those inputs must come from the responsible project process.

The report buyer-review guide supplies broader completeness questions. For this particular workflow, the final test is simple: can another person identify what was not examined, why, and what decision remains? If the answer requires guessing from a blank cell or a generic note, improve the location and evidence references. A useful inaccessible-area register preserves the limits of the examination while giving the owner a practical starting point for the next authorized action.