Make the reported zone physically identifiable
A pressure vessel nozzle examination can involve several nearby features that should not be treated as one undifferentiated location. The nozzle neck, its connection to the shell or head, an attachment and a surrounding examination area may require different references. Start with the actual vessel drawing and identify the feature being reported. A statement such as nozzle checked gives the recipient little help when the finding needs to be relocated or compared with a repair record. The first objective is to make the relationship between component, zone and examination result understandable without relying on the inspector's memory.
The free digital NDT reporting workspace can organize these relationships in text fields and editable tables, then generate a numbered PDF. It does not calculate nozzle reinforcement, assess pressure-vessel fitness for service or determine acceptance from an entered result. This guide provides a zone-reference worksheet for an actual reviewed examination. Use the project's applicable procedure, drawings and technical requirements for the work. The worksheet is a documentation aid: its fictional examples explain the structure and must be replaced with the real vessel and examination references before use.
Identify the vessel and the nozzle separately
Record the vessel identity from the approved project records, then identify the nozzle using the designation on the relevant drawing or asset record. A nozzle label such as N-4 may repeat across many vessels. Keep enough surrounding context to prevent the report from being assigned to the wrong item. If the owner uses an equipment tag while the fabricator uses a different serial or drawing reference, preserve the supported relationship. Avoid choosing whichever identifier is shortest without considering how the recipient will retrieve the record later.
Check that the nozzle designation refers to the actual physical connection examined. A drawing revision, replacement or field modification may create a mismatch between an old report and the current arrangement. If labels differ, obtain a controlled cross-reference or clarification rather than silently renaming the feature. The report should show which configuration and document state supported the examination. An updated identifier can be useful for retrieval, but it should not erase the historical reference needed to understand work performed before the change. Resolve uncertainty before combining results under one nozzle entry.
Map the physical features included in the scope
Describe the zones using terms that match the actual design and examination instruction. Where the design includes a neck, connection weld, reinforcement feature or attachment, distinguish the relevant surfaces and boundaries. Do not assume every nozzle has the same construction. A generic template can introduce a feature that is absent or omit a feature important to the work. Compare the template with the drawing before entering results. The zone map should reflect what exists and what was examined, not a standard-looking arrangement copied from another vessel.
For each zone, identify the drawing reference or local sketch that allows a reviewer to locate it. If a result concerns the surrounding shell rather than the connection itself, say so clearly. Keep the examined area distinct from an adjacent area that merely appears in a photograph. The report can reference a controlled diagram or describe the relationship in a table. It does not need to reproduce every design detail, but it should contain enough information for a qualified recipient to understand which physical feature the observation concerns and where the scope ends.
Define direction and orientation before using coordinates
Use the project's approved orientation convention and state the reference origin. A clock position, distance or angular location is meaningful only when the viewing direction and datum are understood. A nozzle viewed from outside the vessel can be described differently from the same feature viewed from an internal access position. Do not leave the reader to infer the direction from an unlabeled image. Identify the surface and viewing convention in the report or its referenced sketch, and keep that convention consistent across the results, photographs and repair records.
When a source record uses a different convention, retain its original reference and document the supported translation. Avoid changing coordinates by intuition, especially where a mirrored view could reverse the apparent location. The responsible reviewer should resolve any uncertain mapping before it supports a technical conclusion. If the available evidence establishes only a general area, describe that area honestly rather than inventing a precise coordinate. The worksheet can distinguish confirmed location references from unresolved ones, making the next review action clear without disguising uncertainty as exact measurement.
Identify the governing basis without borrowing a generic rule
Record the procedure and evaluation references applicable to the actual examination, including the relevant document revisions or editions required by the project. ASME's Section VIII Division 1 publication page identifies rules for construction of pressure vessels. That publication identity does not establish the governing basis for every nozzle examination or an in-service assessment. Determine applicability from the authorized project documents and responsible review. Do not substitute a remembered criterion simply because the component is a pressure vessel.
Keep the examination procedure reference separate from the source of acceptance or disposition where they serve different purposes. A list of standard names does not explain which requirement was applied to a particular zone. Associate the relevant basis with the actual result or result group. If different zones have different requirements, make that distinction visible. Where the basis is unresolved, leave the question open in the working review and obtain clarification. The reporting tool checks selected fields for presence before issue, but it does not decide which technical requirement governs the observation.
Keep method and access boundaries attached to the zone
Identify the method and actual examination event for each reported zone. One nozzle area may be examined by more than one method, while another area may be outside the accessible scope. Do not let a completed result for one surface imply complete examination of every adjacent feature. Record the actual coverage and any limitation using the terminology supplied by the approved procedure and review. If a supplementary examination addresses part of a limitation, reference its specific scope rather than describing it as a general completion of all missing coverage.
Where access changes between events, preserve that context. A shop examination before assembly and a later field examination may have different available surfaces or configurations. The report should not present them as equivalent without a supported technical assessment. Keep the source records for each event and identify what comparison, if any, the responsible reviewer has accepted. The software can organize the entered information, but it cannot infer examination capability from a method name or determine whether a later test compensates for an earlier limitation. Those decisions need their own evidence.
Separate observations from zone-level conclusions
Enter the reported observations with their object and location references before summarizing the result. Preserve the units and measurement meaning where values are included. A dimension can refer to a surface indication, a location offset or another quantity; label it clearly so the reader does not mistake one for another. Keep the original inspection evidence available through the approved record system. A report table should summarize accurately without removing the context needed to understand how the observation was obtained and what it represents.
The conclusion should remain within the examined zone and the supported evaluation. A result for a connection weld should not become an unqualified statement about the entire nozzle assembly or vessel. If an engineering disposition is referenced, identify the actual record and its scope. Do not infer a release decision from a lack of reportable indications in one area. Where a finding requires further review, state the unresolved action and responsible process. Clear boundaries help the recipient use the report appropriately without giving the software-generated document a broader technical meaning than the evidence supports.
Preserve repair events and changed configuration
If a repair affects the nozzle area, identify the repair event and its physical boundary separately from the document revision. A report revision can correct wording without any physical work, while a physical repair may require several examination records. Keep both sequences traceable. Retain the initial finding, the authorized repair reference and the subsequent examination evidence as distinct events. Do not overwrite the first result with a later result and remove the history that explains why the repair occurred.
NASA's configuration management guidance discusses identifying configurations and controlling changes to them. Used here as general information-management context, that principle supports recording which physical and document state an examination represents. It does not impose NASA requirements on a pressure-vessel project. Apply the project's own controls to identify a replaced nozzle, changed attachment or revised drawing. If the physical arrangement changed, a later observation may need a new baseline relationship. Make that event visible rather than assuming that an unchanged nozzle label proves an unchanged examination context.
Build a zone-to-evidence crosswalk
Use one row per meaningful zone and examination event. Include the vessel and nozzle identifiers, physical feature, orientation reference, method, source report, coverage statement and disposition or open question. Where a single report covers several zones, identify the relevant table or result group so the recipient can find the correct evidence quickly. Avoid a row that lists several reports without explaining which one supports which feature. The crosswalk should reduce the need to search through a package, while preserving the actual technical record as the source of detailed results.
Add a repair-event column when the history requires it, and keep the relationship to any local sketch clear. If an attachment and the main connection share a similar shop label, distinguish them in the index before delivery. A concise reference system is useful only if it prevents ambiguity. Review the crosswalk in both directions: from a zone on the drawing to its evidence, and from a delivered report back to the zone it covers. This can reveal an orphaned report, a missing examination or an incorrect association that would not be found by proofreading individual PDFs alone.
Work through a fictional nozzle-zone record
Consider a fictional vessel V-204 with nozzle N-4. The examination package includes a result for the main connection and a separate observation on a nearby attachment. An early summary places both under nozzle N-4 without identifying the features. The reviewer cannot tell whether the attachment observation affects the connection result or a different scope. The author returns to the drawing and source records, assigns separate zone rows and preserves the actual method and coverage for each event. The report now distinguishes the findings without inventing a technical relationship between them.
In the same fictional example, a later repair modifies only the attachment area. The main connection's earlier result remains a separate record, while the repair and subsequent examination are linked to the attachment zone. If the responsible reviewer determines that additional examination is needed elsewhere, that requirement becomes an explicit action rather than an assumption hidden in the summary. This example supplies no acceptance limits or repair instruction. It demonstrates how zone identity prevents a local finding or repair from being incorrectly attributed to an entire nozzle assembly.
| Reference layer | Record to identify | Misinterpretation to prevent |
|---|---|---|
| Vessel and nozzle | Approved asset and drawing designation | Same nozzle label on a different vessel |
| Physical zone | Actual neck, connection or attachment feature | Local observation attributed to the entire assembly |
| Orientation | Datum, surface and viewing direction | Mirrored or unrelocatable indication position |
| Examination event | Method, date and actual coverage | One method treated as complete coverage of all features |
| Repair history | Physical repair and related examination records | Document revision confused with a repair cycle |
Prepare and proof a readable report
Enter the vessel, nozzle and drawing references in the reporting workspace, then add the zone table and explanatory observations. Use the scope field to describe the actual work and the conclusion to summarize the supported evaluation. Reference equipment and personnel evidence relevant to each event where required. The equipment tracker and certificate manager can help organize entered information, but the report author must verify and transfer the appropriate references manually. The tools do not synchronize those records or determine technical suitability for the nozzle examination.
Download a draft PDF and inspect long identifiers, orientation notes and table headings. Confirm that a reader can tell which zone each conclusion concerns. If the table is too wide, divide the location map and result index into connected tables using a stable zone identifier. Do not remove important context merely to fit every field into one row. After changes, save the intended draft and create a fresh proof. The issued status preserves the saved report version; it is not a pressure-vessel certificate, engineering acceptance or authorization to operate the equipment.
Close the record with clear unresolved actions
Before delivery, identify any remaining location question, missing source record or pending disposition. Assign the next action through the actual project process and retain the evidence that closes it. An entry marked complete should mean something defined, such as the required report received and reviewed, rather than simply that a file exists. If a package is delivered under an authorized arrangement with outstanding items, explain that boundary accurately. The recipient needs to understand both the available evidence and the work still required without reconstructing the author's private notes.
Keep the zone crosswalk, controlled references and issued report retrievable for future work. When another examination occurs, confirm the component configuration and add its event rather than overwriting earlier observations. If a report error is found, preserve the issued version and use a draft revision with the project's correction process. The free reporting, equipment and procedure tools can support this organization, while technical decisions remain with the responsible parties. A useful nozzle-zone record makes a local observation relocatable and keeps its meaning tied to the feature, stage and evidence that actually support it.
Nozzle zone to examination evidence crosswalk
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
Does a result for one nozzle zone cover the whole assembly?
No. Associate each result with its actual feature, method and examination boundary. Do not broaden a local result beyond the evidence reviewed.
Can the tool determine nozzle reinforcement or fitness for service?
No. It organizes entered information. Design, integrity assessment and operating decisions require the responsible technical process.
How should clock positions be recorded?
Use the project’s defined datum, surface and viewing direction. Preserve the source convention and document any supported mapping to a different reference.
Is a repair event the same as a report revision?
No. A repair changes the physical item; a report revision changes the document. Keep both sequences and their relationship identifiable.
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: industry closeout workflows
- Link Rail Test Suspects to Field Verification
Keep acquisition, suspect identification, field verification and the owner’s response as distinct events. This workpaper preserves their relationship without turning a suspect list into a confirmed-defect register or operational authorization.
- Record Untested Segments in a Rail Examination Run
A completed vehicle run does not establish a valid internal examination of every location traveled. Keep the actual untested or unresolved lengths visible and connect each to the track owner’s responsible action and follow-up evidence.
- Prepare a Sanitary Weld Borescope Closeout Record
Build a retrievable relationship between each weld, its recorded views, the examination basis and the responsible review outcome.
- Keep Solar Thermal Anomalies Linked to Strings and Modules
Turn a thermal observation into a retrievable maintenance record: identify the asset, preserve the source, record the conditions and keep follow-up decisions distinct.
