NDT RFQ Scope Intake: Prepare a Reviewable Inspection Request

Define the examination objective first

Begin with the decision that the examination is intended to support. Is the request concerned with fabrication examination, a scheduled condition survey, a repair review or investigation of a reported concern? Those situations may involve different document sets, access arrangements and technical authorities. A request that says only inspect the welds leaves the supplier to infer the purpose and limits of the work.

State what is already established and what remains to be decided. If the governing documents specify a method and examination extent, identify those requirements accurately. If method selection is still open, describe the objective and ask for a technical proposal or review. Do not turn an initial purchasing preference into an apparently approved technical instruction.

Federal procurement guidance distinguishes a clear description of required results from simply prescribing activity [1]. Private inspection buyers can use that distinction as an editorial planning principle: describe the evidence or deliverable needed, while preserving the role of qualified personnel in selecting and authorizing the examination technique.

Identify the component population

Create an item list with stable identifiers, component types and available drawings. Record the quantity and explain what it counts: welds, components, measurement locations, examination areas or another defined unit. A count without a unit can produce materially different quotations, especially where one supplier assumes individual welds and another assumes complete assemblies.

Include the material and geometry information available to you, such as product form, thickness range, diameter or joint configuration. Mark uncertain information as uncertain. A purchasing coordinator should not estimate a technical dimension merely to complete a form. Identify the person or document that can resolve the missing information and the point at which the quote must be reviewed again.

Avoid embedding the complete item list inside an unstructured email paragraph. A simple controlled attachment can preserve identifiers and revisions more reliably. The request summary should explain the attachment's scope and version so that the supplier knows which list it is being asked to assess.

Establish the document hierarchy

Identify the governing project documents, examination standards and contract editions that the responsible technical authority has selected. Include drawing revisions and any supplementary requirements relevant to the requested service. Do not use a phrase such as latest code as a substitute for identifying the contract basis; different documents can change on different schedules.

Separate examination requirements from acceptance criteria. A standard describing how an examination is performed may not by itself establish the component's acceptance basis. If that basis is unresolved, record an open technical question and identify who must answer it. A supplier should not be expected to infer the correct service category or engineering disposition from the asset name alone.

Provide the necessary references through an authorized document-sharing process. An RFQ does not create permission to redistribute restricted standards, customer drawings or proprietary procedures. You can identify a controlled document and arrange appropriate access without copying every related file into a broadly circulated request package.

Describe actual access and site conditions

Record the surfaces available for examination, known obstructions, preparation status and the physical location of the work. Distinguish expected conditions from conditions already verified. If scaffolding, insulation removal, isolation or cleaning will be arranged later, state who is responsible and whether the planned date is confirmed. These dependencies can affect both feasibility and scheduling.

Explain relevant operating constraints, including restricted work windows, coordination with adjacent activities and the process for site authorization. Avoid promising unrestricted access if you have not checked with the responsible site team. A quotation based on an accessible component may not apply when the supplier arrives and discovers that the agreed examination surface cannot be reached.

OSHA's contractor coordination guidance emphasizes exchanging information about worksite hazards and protective measures before work begins [2]. At intake, the practical task is to identify the responsible contacts and information exchange, not to write a generic safety statement that appears to resolve hazards nobody has assessed.

Define the deliverable package

Specify what the buyer needs to receive and how it will be reviewed. Possible deliverables include an examination report, component or weld map, technique reference, relevant calibration records, images or native data files where the contract requires them. These are examples to assess, not a universal minimum package for every NDT method or project.

For each deliverable, identify the expected format, component references, required review stage and destination. A PDF summary and an editable dataset serve different purposes. If future analysis depends on native files, establish that requirement before award and discuss the software or access needed to read them. Do not assume that a report automatically includes all underlying acquisition data.

Describe the acceptance process for the service deliverables separately from technical acceptance of the component. A buyer may check that a report package is complete while a designated technical authority evaluates the examination result. Keeping those decisions separate prevents an administrative receipt confirmation from being mistaken for an engineering approval.

Make commercial assumptions visible

Ask suppliers to state the basis of their quotation, including the defined quantity, location, work period, included preparation, travel assumptions and deliverables. Record whether the price is preliminary or firm under specified conditions. This guide does not supply market rates; the purpose is to make actual supplier offers comparable.

List exclusions and buyer-provided resources explicitly. If the buyer supplies access equipment or prepares the surface, identify the boundary and the evidence of readiness. If a supplier proposes an allowance because the scope is incomplete, ask what triggers a revised price and how the change will be reviewed. A small initial figure can be misleading when major dependencies remain outside the quoted scope.

Avoid comparing quotations solely by their headline total. First reconcile scope, assumptions and the deliverable package. Where commercial terms or liability allocation require specialist review, involve the appropriate purchasing or legal personnel rather than treating an intake checklist as a substitute for the contract.

Create an open-question register

Give each unresolved question an identifier, a clear description, an owner and a required decision point. Examples include an unreadable drawing revision, an unspecified examination extent or uncertainty about who will provide access. Describe the missing information without assigning blame. The register should help someone act, not merely document that the request was incomplete.

Distinguish questions that prevent a meaningful quotation from those that can be resolved before mobilization. This requires technical and commercial judgment. A missing acceptance basis may affect the proposed service fundamentally; a final meeting location may be a later coordination detail. Do not classify everything as urgent, because that obscures the dependencies that actually control the decision.

Share relevant clarifications consistently with the suppliers participating in the same comparison. If one bidder receives a revised item list and another does not, their offers may no longer address the same work. Keep the question, response and revised document reference together so the comparison can be reconstructed later.

Work through a bounded example

Consider a fictional buyer requesting examination of several fabricated piping assemblies. The first email gives a weld count and a desired completion date, but no drawing revision, preparation status or acceptance reference. One supplier assumes examination in a workshop; another assumes work at the installation site. Their prices cannot be compared fairly because they are describing different jobs.

The buyer creates an intake sheet with the assembly list, confirmed location and a note that the technical authority is still selecting the examination basis. The supplier is asked to identify information needed for a technical proposal, rather than quote a supposedly fixed method. Access and preparation responsibilities are assigned before a final commercial comparison is requested.

The useful outcome is not a claim that the checklist reduced cost by a particular percentage. It is a reviewable record showing which scope each supplier assessed, which questions remain open and what must be confirmed before award. That evidence is valuable even when the eventual price is unchanged.

Review the request with both technical and purchasing owners

Have the responsible technical reviewer check component identity, examination objective, document basis and unresolved engineering questions. Have the purchasing owner check the commercial comparison, submission instructions and decision process. A single person may hold both roles in a small organization, but the two kinds of review still need to occur.

Read the package as a supplier would. Can someone identify the actual work without access to your internal conversations? Are all referenced attachments present and readable? Do file names match the revision list? Does the request explain which assumptions suppliers may make and which matters require clarification first? These checks often reveal ambiguity that is invisible to the team that assembled the package.

Record the issue date and package revision. When the scope changes, issue a controlled update and explain what changed. Do not quietly replace a drawing in a shared folder while leaving the original RFQ description unchanged; recipients need to know which version their response should address.

Reconcile quantities through the worksheet

Use the intake worksheet to identify what each quantity represents and where it comes from. A count of assemblies is not interchangeable with a count of examination locations or individual welds. Record the source document and revision beside the quantity, then explain any relationship between the purchasing unit and the physical work items the provider must examine.

Check whether the same items appear in more than one schedule or attachment. A component shown on a general arrangement and a detail drawing should not be counted twice simply because both files are included. Ask the technical owner to resolve uncertain boundaries, and retain the mapping that explains how the final request quantity was established.

Where the population remains uncertain, state the basis for an initial estimate and the process for confirming it. This may support an early planning discussion, but it should not be presented as a verified final quantity. The worksheet should make the uncertainty visible to the buyer and provider before it is embedded in a fixed scope description.

Separate readiness from the desired attendance date

A requested start date does not establish that the work will be ready. Review the prerequisites that affect the proposed activity, including document availability, component identification, agreed preparation and access arrangements. Assign each prerequisite to the responsible party and identify how readiness will be confirmed before attendance is committed.

Consider a fictional project where the buyer requests examination immediately after fabrication. The completion schedule does not yet account for the time needed to identify the components and make the agreed surfaces available. The intake review records those dependencies and asks the project owner to confirm a realistic readiness point rather than passing an optimistic date to suppliers.

The provider can then distinguish its availability from the site's readiness. Those are separate facts: a team may be available while the work is inaccessible, or the work may be ready while the appropriate provider is unavailable. Keeping both visible helps the parties discuss sequencing without implying that either condition alone guarantees execution.

Review the request from the recipient's perspective

Give a colleague who did not prepare the intake the proposed description and attachments. Ask them to identify the work items, intended outcome, governing references, requested deliverables and unresolved questions. This is a communication review, not a technical approval. Its purpose is to reveal information that the author assumed was obvious but never included.

Have the colleague trace one fictional work item from the item list to its drawing and proposed report reference. If the path breaks, identify the missing relationship before sending the request. A clear narrative can still conceal an unusable attachment package, and a complete folder can still lack a statement of which items are actually in scope.

Record the review findings and obtain the relevant owners' answers. Do not resolve engineering uncertainty through an editorial rewrite. Where the technical basis remains pending, keep the pending status explicit and explain what kind of provider response is currently being sought. This prevents an exploratory request from being mistaken for an authorized execution package.

Before final submission, inspect the actual uploaded copies and the visible request text. Confirm that a filename change, omitted attachment or shortened description has not removed a qualification that mattered to the review. Retain the submitted package reference so a later clarification can identify precisely what the provider received and which information was added afterward.

Submit through the portal with clear expectations

Use NDT Connect's service request form to describe the work and provide the relevant project information supported by the form. Review attachments before submission and avoid including sensitive material that is unnecessary for the initial inquiry. A provider profile can help identify a potential supplier, but its presence does not establish suitability for every method or project.

After submitting, read the reported outcome. A provider email may be sent, queued for delivery or the request may be available through the provider dashboard, depending on the workflow. None of those states is a supplier's technical acceptance, quotation or commitment to attend. Obtain the actual response and reconcile it with the issued scope before proceeding.

Keep a copy of the final request package and subsequent clarifications in your own controlled project records. The intake is complete when another authorized person can identify what was requested, what remains unresolved and who must make the next decision. That is the foundation for a useful quotation and a controlled service handover.