A component name is not a complete geometry brief
A procedure request that says inspect a pipe weld leaves many practical questions unanswered. The reviewer still needs to understand the component dimensions, joint form, available surfaces and physical restrictions that shape the examination. A long generated document cannot recover those facts from a short asset label. Begin with a geometry and access brief that describes what is known and what must be confirmed. This guide helps prepare that brief for the free procedure generator. It does not design a scan plan, select examination settings or establish that a particular method can meet the required extent.
The deliverable is a concise map of the component envelope and its boundaries. It should connect dimensions to controlled references, distinguish planned access from confirmed access and identify limitations that must reach the report. This is useful before detailed technique planning because it prevents a generic scope from implying that every surface or region is available. It also helps the buyer, coordinator and technical reviewer ask the same question about the same physical area. The goal is a better input and review conversation, not an unsupported claim that a completed form proves examination coverage.
Identify the component and the source of its dimensions
Describe the product form and the feature of interest using the project’s actual terminology. Identify the drawing, revision or authorized measurement record that supports the dimensions. Keep nominal design information separate from dimensions confirmed on the component when that distinction matters. Do not silently substitute a convenient typical thickness or diameter. If the values remain unavailable, mark the question explicitly in the working brief. The generator can display missing-input prompts, but it cannot verify whether an entered number came from the correct drawing or whether the field condition matches the design assumption.
Where several components are included, define the proposed range and the reason they are grouped. A single procedure brief should not imply that every item with the same asset family name has the same geometry. Ask the reviewer which variations require separate technique information or a different scope treatment. Preserve the actual units and reference basis. A mixed-unit drawing set needs an explicit, checked interpretation through the responsible process rather than casual conversion in a short text field. The brief should help the reviewer locate the controlling information without reproducing a confidential drawing or obscuring its revision.
Separate geometry from the surfaces available for examination
Geometry describes the component; access describes where and how the examination can be performed under the proposed conditions. Keep those descriptions separate. A drawing can show a joint accurately while the installed location prevents use of one surface. Coatings, nearby attachments, supports or enclosure arrangements may create questions that are absent from a shop drawing. Identify the actual restriction and its source rather than writing poor access as a catch-all note. The responsible reviewer needs a physical description that can be related to the intended technique and the examination objective.
Record whether access has been confirmed, is expected after preparation or remains uncertain. A planned removal of an obstruction is not the same as an available surface. Ask who is responsible for that preparation and how its completion will be communicated. Avoid treating a schedule assumption as a technical fact. If access changes on site, the procedure brief should make it clear which assumption needs reconsideration. The generator does not monitor field conditions, and a PDF produced earlier cannot establish that the examination arrangement remains suitable after the component is installed or surrounding work changes.
Separate physical access from permission to use it. An exposed surface can still depend on isolation, site coordination or another work authorization handled by the responsible project team. Record that dependency in the safety or access planning reference rather than implying that an unobstructed photograph authorizes examination. Likewise, an approved access arrangement does not prove that the intended equipment can reach every needed position. These questions have different owners and should remain distinguishable in the brief. If photographs or sketches support the discussion, keep their date, orientation and controlled location available to the reviewer. The generator accepts text inputs rather than interpreting those images. Summarize only the confirmed technical context, and avoid carrying customer identities or unrelated project details into the form. This gives the reviewer a useful connection to supporting evidence without treating a picture, permit or drawing as a complete answer to technique suitability.
Keep requested extent distinct from demonstrated capability
The customer may specify an examination extent, but that request does not by itself establish what a proposed arrangement can demonstrate. Record the required scope in its own statement and identify the source. Then describe the available surfaces and open suitability questions separately. Do not convert a requested percentage or broad coverage phrase into an achieved result before examination. The technical reviewer must establish the applicable technique basis and how limitations will be handled. This guide intentionally supplies no universal detection threshold, beam arrangement or coverage formula for an unspecified component.
ASME’s official BPVC Section V listing identifies the nondestructive examination standard. Its public title is not enough to determine your contract’s edition, applicable provisions or component acceptance criteria. Use the authorized project references for those decisions and identify them in the generator’s separate fields. A familiar standard name should not fill gaps in geometry or access information. Keep the requirement source, the proposed examination arrangement and the reviewer’s suitability decision traceable as different parts of the procedure-development process.
| Item | Describe | Question left for responsible review |
|---|---|---|
| Component geometry | Dimensions, joint form and controlled source | Does the proposed range fit the intended technique basis? |
| Available access | Actual surfaces and preparation status | What arrangement is feasible under these conditions? |
| Required extent | Contract requirement and applicable reference | Can the proposed examination address that requirement? |
| Unexamined region | Location and reason when known | What additional action or reporting limitation applies? |
Give inaccessible regions a usable location reference
A limitation is difficult to review if nobody can locate the affected area. Use the project’s permitted datum, feature identifier or drawing reference to describe it. Avoid relying solely on left side or far end when the viewing orientation is unclear. If a sketch is used in the controlled project record, reference it accurately in the brief; the generator does not import or interpret a drawing. Keep the description sufficiently precise that the examiner and report reviewer can discuss the same region without inventing a coordinate system that conflicts with the owner’s records.
Distinguish an excluded region in the planned scope from a region that became inaccessible during execution. Both may need reporting, but they have different histories. The first should be visible before the work is arranged; the second requires communication when the actual condition is discovered. Do not allow a generic scope statement to erase that distinction. Ask the responsible reviewer what action and documentation are required in each case. The brief can organize the question, while the project process determines whether the proposed work, additional method or scope adjustment is acceptable.
Use the generator’s separate geometry and coverage inputs
The NDT procedure generator has separate fields for dimensions and joint geometry, examination extent and access, material, scope and the governing references. Use those fields for their intended purposes. Put the physical description in geometry, and put the required extent, available surfaces and known restrictions in the coverage input. Keep acceptance-source questions in the acceptance field instead of burying them in a general note. The current form uses short bounded text entries, so prepare a concise brief with controlled references rather than pasting an entire source procedure or confidential project document.
The default output is a structured review draft with 20 planned pages; longer entries can produce up to 25 pages. Missing technical fields remain visible for review. Page count does not establish completeness or authorize examination. The product assembles the supplied context into a draft and provides preview, with free account saving and PDF or editable-text download. It does not calculate geometry coverage, qualify a technique or transfer information automatically into a report. The responsible technical process must resolve the actual examination basis and any open inputs before the document is released for work.
A fictional weld brief exposes a one-sided access assumption
Imagine a fictional fabrication project in which a coordinator requests a generic ultrasonic weld procedure. The initial note identifies the component family but omits the fact that an installed attachment restricts one examination surface. During preparation of the brief, the coordinator separates the drawing geometry from the field access description and records the attachment location using the project’s existing reference. The required extent remains a separate contract question. The technical reviewer can now consider the actual arrangement instead of reading a broad weld-inspection scope that appears to assume access from every intended surface.
In this invented example, the reviewer requests additional technique information and confirmation of whether preparation can change the access condition. The generator leaves those requirements open; it does not invent a beam angle or declare complete coverage. If access is later improved, the brief is revised with the confirmed condition and the reviewer reassesses the affected question. If it is not improved, the project must address the limitation through its responsible process. The example illustrates how to surface a dependency before examination, not a universal solution for one-sided ultrasonic weld access.
Connect equipment questions to the actual physical envelope
Once the geometry and access are described, identify the equipment configuration questions that need review. These may concern whether the intended arrangement can physically reach the examination surface or whether a proposed configuration matches the relevant technique information. State the question without supplying unsupported settings. A catalog description or instrument availability does not establish suitability for the component. Ask the responsible reviewer to connect the actual equipment arrangement to the task and its controlled basis. Keep the answer with the technique information rather than treating the generator’s equipment field as an automatic equipment-selection service.
The equipment tracker can help organize entered asset information, but it does not evaluate access or demonstrate examination capability. Use it for the equipment identity records it actually holds, then manually reference the appropriate equipment information in the project brief. If the equipment arrangement changes, identify which geometry or access assumption may be affected. Do not assume that replacing one instrument or accessory with a familiar alternative leaves every technique condition unchanged. The guide’s worksheet helps preserve those dependencies so the responsible reviewer can determine what needs another look.
Carry the limitation into the reporting plan before fieldwork
Decide how the report will distinguish requested scope, work actually performed and known unexamined areas. The report should be able to preserve the location and reason for a limitation without hiding it in an unrelated comment. Ask the project reviewer what detail is required and who will evaluate its significance. Do not use a broad acceptable status to imply an examination covered regions that were not examined. The reporting plan should make the result understandable to a future reader who was not present during the access discussion and cannot reconstruct it from memory.
The digital NDT reporting editor allows user-entered references, editable tables and PDF output. It does not receive the procedure generator’s geometry brief automatically or decide what coverage was achieved. Build the relevant fields and columns manually from the reviewed requirements. Use the actual procedure revision and location references, and retain supporting records through the project’s authorized process. If a field cannot capture the necessary limitation clearly, adjust the report structure or identify a required supporting record rather than reducing the technical meaning to fit a convenient template.
Review changed field conditions against the original assumptions
A procedure brief should make it possible to recognize when the physical situation differs from the planned basis. Before the examination, the responsible team needs to compare the relevant dimensions, surfaces and preparation status with the actual condition. This guide does not prescribe a universal field-verification checklist or acceptance rule; it asks that the project identify the controlling process. If a difference is found, record it accurately and route it to the person responsible for deciding its effect. A generated draft cannot authorize the examiner to improvise beyond the reviewed scope.
Keep the change record connected to the affected input. A different surface condition, obstructed area or revised component configuration may create a specific question rather than invalidating every page of the draft. Conversely, a small physical change can matter even if the document title remains appropriate. The reviewer determines the consequence. Preserve the original assumption, the actual observation and the decision received so the report and procedure history remain understandable. This is particularly valuable when preparation, inspection and reporting are handled by different teams with different views of the component.
Use the worksheet to hand over unresolved geometry questions
The downloadable worksheet uses fictional rows to show the component feature, source reference, access status, required extent and next decision. Replace those entries with your own general descriptions and retain detailed drawings in their controlled location. Give each open question an owner rather than leaving a generic review required note. The worksheet is not a scan plan or proof of coverage. Its purpose is to prevent an unresolved access assumption from disappearing when a coordinator submits the generator form or a reviewer starts working from the resulting draft.
Before generating, check that the brief answers what component is included, where examination is intended, what is inaccessible and which facts remain unconfirmed. After generating, confirm that the draft preserves those distinctions and has not been interpreted as a released procedure merely because it is substantial. The next useful action may be a drawing clarification, a field-access confirmation or a technical suitability review. A focused question is a better outcome than a confident but unsupported statement of complete coverage. The free generator helps organize the document; the engineering decisions remain with the responsible people.
- Reference the actual geometry source and revision.
- Separate required extent from available access.
- Label planned preparation separately from confirmed conditions.
- Give limitations usable location references.
- Carry unresolved coverage questions into the report handover.
Fictional example: geometry and access brief
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
Can the generator calculate coverage from my dimensions?
No. It organizes entered context into a structured draft. The responsible technical reviewer establishes technique suitability and coverage meaning.
Should I combine geometry and access in one vague scope sentence?
Use the separate fields and keep the physical geometry, available surfaces, required extent and open limitations distinguishable.
Does a 20-page draft mean the procedure is complete?
No. Page count describes the assembled document. Missing and supplied requirements still need qualified review and authorization through the applicable process.
Will coverage notes transfer into the report editor?
No automatic transfer is provided. Build the report fields manually from the reviewed procedure and preserve the actual limitations and references.
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: procedure drafting decisions
- Write Personnel Requirements into an NDT Draft Brief
Replace a bare Level II entry with the applicable qualification source, actual duties and decision responsibilities. Keep personal evidence in its controlled process and use the generator to organize the reviewed requirement.
- Turn Procedure Requirements into an NDT Report Draft
Build a requirement-to-field crosswalk before preparing a report template. The procedure generator and digital report editor are separate tools; users must carry reviewed references, evidence needs and limitations across manually.
- Resolve Review Comments on a Generated NDT Procedure
Use an external comment register tied to the exact draft. Separate a reviewer’s request, the responsible decision, the edited text and verification of that edit; closing comments does not itself authorize examination.
- Remove Company Identity from an NDT Draft Brief
Extract a concise technical brief from material you are permitted to use. The generator accepts text, removes specified names and contact links, and produces an unapproved draft; it is not a complete document-redaction service.
