Compare NDT Proposals Without Hiding Scope Differences

Start from the issued requirement package

Use the same RFQ revision, component list and clarification record as the baseline for every proposal. If suppliers received different information, resolve that discrepancy before ranking their offers. A comparison table can look precise while comparing different jobs, and the apparent precision makes the underlying problem easier to miss.

Identify the decision the review supports: a shortlist for technical discussion, selection of a preferred proposal or approval of a final purchase. Those stages need different levels of certainty. A preliminary offer may be adequate for planning but not ready for award when important access or acceptance requirements remain unresolved.

Federal purchasing guidance explicitly connects a service request with a statement of work and evaluation criteria [1]. An inspection buyer can use that general planning discipline without treating federal procurement rules as automatically applicable to a private contract. Define what matters to the decision before seeing which supplier appears most attractive.

Build a comparison with separate dimensions

Create rows for the examination objective, component population, governing references, method scope, personnel evidence, equipment configuration, access assumptions, preparation, schedule, deliverables and commercial basis. Use the categories relevant to the actual work. A generic supplier scorecard may omit the dependency that controls whether the examination can be performed.

Record each supplier's response beside the requirement and identify the source page or clarification. Preserve the distinction between explicitly included, excluded, conditional and not stated. A blank proposal field is not the same as agreement, and a sales discussion should not silently replace the written scope without a record of the clarification.

Add a column for unresolved questions and a responsible reviewer. The comparison should make uncertainty visible rather than forcing every row into a green or red status. Some gaps can be resolved by obtaining a document; others may require a technical change or a revised commercial offer.

Reconcile quantities and units

Check what each quoted quantity represents. A supplier may price individual welds, examination length, component count, shifts or a defined package. These bases cannot be compared directly without understanding the work included. Record the unit, quantity and conditions rather than copying only the total into a spreadsheet.

Review boundaries such as mobilization, repeat visits, access delays and minimum work periods where the proposals discuss them. Do not assume a universal commercial convention. Ask the supplier to explain how the quoted basis applies to the actual planned sequence and what would trigger additional review or a changed price.

If you prepare a normalized scenario for comparison, label it as a buyer-created scenario and preserve the supplier's original offer. State the assumptions used and obtain clarification where necessary. The normalized figure is a planning calculation, not a new supplier commitment or evidence of a market-wide inspection rate.

Review technical fit through qualified personnel

Have the designated technical reviewer assess whether the proposed method and technique envelope address the examination objective. Review the material, geometry, access and coverage assumptions. An attractive equipment list does not by itself show that the supplier's configuration is appropriate for the specific application.

Ask for the evidence needed by the project, such as relevant procedure scope, qualification or demonstration records, personnel authorization and a proposed technique basis. The exact evidence depends on the governing requirements. Do not treat this editorial checklist as an additional technical standard or require documents that have no relationship to the work.

Keep technical acceptance criteria and commercial selection criteria separate. A supplier's proposal may describe how it will evaluate examination results, while the buyer's selection process considers capability, schedule and commercial terms. Confusing those meanings of acceptance can lead to a procurement decision being presented as approval of the actual component.

Check access and preparation responsibilities

Compare what each supplier assumes about surface preparation, insulation removal, scaffolding, lifting, isolation and available examination surfaces where relevant. Identify which resources the buyer will provide and when they will be ready. An offer that excludes preparation can be entirely reasonable, but it must be compared with other offers on a transparent basis.

Consider whether the planned work window is compatible with the stated access arrangements. A supplier's availability does not prove that the site can release the component at the same time. Record dependencies that could prevent work and identify the responsible site contact before treating the schedule as confirmed.

OSHA's coordination guidance addresses the exchange of hazard and control information between employers and contractors [2]. In a proposal review, this supports a practical question: has the offer identified the interface needed for safe mobilization, or has it simply assumed that someone else will resolve all site conditions after award?

Compare deliverables at the level of intended use

List the reports, maps, images, native data and supporting records requested, then compare what each offer includes. A report-only quotation may not satisfy a buyer who expects future independent data analysis. Conversely, requiring large native datasets may add work that is unnecessary for a narrowly defined service. The intended use should govern the deliverable comparison.

Check file formats, review stages, submission timing and the responsible recipient. Ask whether any software or access arrangement is needed to use the delivered data. A package can contain all promised files yet remain unusable to the receiving team if the necessary context or viewing capability was never agreed.

Clarify the distinction between a draft report, a reviewed report and any final authorized issue required by the project. Do not assume that every supplier uses those terms in the same way. Record the actual workflow and authority so the buyer can compare equivalent deliverables rather than similar labels.

Read assumptions and exclusions as part of the offer

Review notes, footnotes and attachments with the same attention as the main proposal. Important conditions often appear outside the summary price table. Identify exclusions that transfer work or uncertainty to the buyer, and confirm that the buyer has the capability and resources to handle those responsibilities.

Ask suppliers to clarify ambiguous wording through a controlled question record. Keep the response linked to the specific proposal revision and comparison row. If a clarification changes scope or price, request an updated offer or other appropriate commercial record rather than relying on an informal statement that later readers cannot reconcile.

Avoid treating every exclusion as a negative. A clearly stated boundary can make an offer more reliable than a broad promise with no supporting detail. The question is whether the combined buyer and supplier arrangements cover the required work, and whether unresolved conditions are acceptable to the designated decision makers.

Use evidence-based scoring carefully

If the organization uses scoring, define the criteria and interpretation before applying them. A score should summarize evidence, not replace it. Explain what would justify a particular rating and record the supporting proposal reference. Otherwise different reviewers may assign the same number for entirely different reasons.

Keep critical unresolved technical issues outside an average that could conceal them. A proposal should not appear suitable simply because a high score for administrative presentation offsets an unanswered question about the examination envelope. Have the responsible authority identify the conditions that must be resolved before a recommendation can proceed.

Record reviewer disagreements and how they were resolved. A purchasing reviewer may emphasize schedule certainty while the technical reviewer identifies a limitation in the proposed scope. The comparison is useful when it brings those considerations into a clear decision, rather than forcing an unexplained consensus through a single total score.

Work through a fictional comparison

Suppose two fictional suppliers quote examination of the same fabrication package. Offer A includes a reviewed report and one planned site visit, with surface preparation provided by the buyer. Offer B includes preparation assistance and native data delivery but assumes a different work sequence. Their totals reflect different services and dependencies.

The buyer first confirms the required deliverables and actual site readiness. The comparison records which preparation tasks remain with the buyer, whether native data are needed and how the work sequence affects attendance. Both suppliers receive the same clarification where it changes the common request.

Only after those questions are resolved does the team compare the remaining commercial difference. The example does not establish which supplier should win or claim that one offer is cheaper in a meaningful sense. It shows why a defensible comparison preserves scope and assumptions before drawing a conclusion from price.

Record the recommendation and unresolved conditions

Write a concise recommendation that names the selected scope, proposal revision, material reasons and any conditions to be closed before award or mobilization. Link the supporting comparison rather than reproducing every row in the decision note. The reader should be able to understand both the recommendation and its limits.

Preserve the authority for the decision. Technical suitability, purchasing approval and site release may involve different people. Do not let a preferred-supplier status imply that all subsequent technical and safety checks have been completed. Identify the remaining handover tasks and the person responsible for each.

Use NDT Connect to discover providers and communicate a service request, while maintaining your own controlled proposal review and purchasing records. The platform does not establish that every listed qualification fits your project or guarantee a supplier's response. A completed comparison gives the organization a traceable basis for selection and a clearer starting point for the actual service arrangement.

Use the worksheet without manufacturing comparable prices

Enter each supplier's stated basis in its own words before attempting to normalize the comparison. Record the quantity, unit, included activities and conditions alongside the amount where one is provided. If a proposal prices a defined package and another prices attendance time, do not divide them into an apparently common rate without confirming what each unit actually includes.

Create a separate clarification field for missing information. A blank allowance, an excluded preparation task and an included service are different conditions. Replacing all three with zero can make an incomplete offer appear cheaper while concealing work that the purchaser must arrange elsewhere. The worksheet should expose those differences before any commercial arithmetic is used.

Where an internal estimate is needed to explore an alternative, label it as the purchaser's assumption and keep it separate from the supplier's quoted commitment. Record the source and uncertainty of the estimate. The comparison should never imply that a provider offered a price or service that the purchasing team inserted for convenience.

Examine how an unresolved condition changes the recommendation

Select the open questions most likely to affect the choice and consider plausible outcomes. For example, if site access is available only during a limited window, would both providers still be able to perform their proposed scope? If native data delivery is confirmed as required, does each proposal describe a usable package and the necessary viewing context?

This exercise helps identify decisions that should be resolved before award. It is not a prediction that the most favorable assumption will occur. Record whether the recommendation remains the same under the alternative conditions or depends on a specific answer. A recommendation that is conditional should say exactly what must be confirmed and by whom.

Avoid using a numerical score to hide a decisive unresolved issue. A supplier might obtain a high total while lacking evidence for an essential technical requirement. The responsible reviewer should identify any condition that cannot be traded against convenience or a lower price. The purchasing record should preserve that judgment rather than averaging it away.

Reconcile the final clarification with the supplier's written offer

After discussions, ask the supplier to identify the proposal version that contains the agreed basis. Compare it with the clarification log and the recommendation. Important changes can be lost when a revised commercial page is issued without updating an older technical attachment or when a new exclusion appears in a covering note.

Consider a fictional provider that agrees during a meeting to include a component map, but the final quotation still lists only a summary report. The buyer records the inconsistency and requests an authorized correction. The meeting note is useful evidence of the discussion, yet the award package should not leave the deliverable dependent on two contradictory documents.

Check the purchaser's order or scope instruction as well. A correctly revised proposal can still be undermined if the order refers to an obsolete revision or omits a condition that was central to the selection. Have the responsible commercial and technical owners reconcile the complete award package before treating the comparison as finished.

Preserve the decision rationale in terms that a later project coordinator can use. Identify the chosen deliverables, responsibilities and remaining conditions, with references to the governing documents. A record stating only best value provides little help when the team later needs to determine whether a requested activity was included or represents a change.

Carry the comparison into mobilization

After selection, use the agreed comparison to prepare the service handover. Confirm that the purchase instruction, supplier acknowledgment and technical scope refer to compatible revisions. If the final arrangement differs from the preferred proposal, document the difference and obtain the relevant review instead of assuming the earlier recommendation covers it.

Brief the site coordinator on buyer-provided resources and outstanding dependencies. The person arranging attendance should not have to discover preparation exclusions by reading a quotation after the crew arrives. Retain the comparison as a decision record, but maintain current operational instructions separately. This keeps the historical selection evidence intact while allowing the project team to manage approved changes through the actual work sequence.