Quote refresh risk appears when a newer response uses a different revision, quantity, currency, sourcing model, workshare, or test assumption but is compared as though the scope were unchanged. The IPC document revision table illustrates why revision identity must remain explicit; the active buyer and supplier records still control the quotation.
A PCBA quote refresh can be newer without being comparable. The response may use a different BOM revision, quantity, sourcing model, manufacturing scope or test assumption, so the new total and the prior total do not necessarily buy the same work.
At this gate, the risk is a decision-interface problem, not proof of supplier error. Mixed files, an incomplete delta or copied assumptions can enter on either side. Reviewers should trace each difference to its source, affected line and owner before attributing a price, schedule or technical consequence.
Containment starts with the smallest affected decision. Preserve approved engineering work while holding the comparison, award, purchase or build line that depends on an unresolved refresh field.
Find Quote Refresh Risk in Mixed File States
Begin by identifying the files the supplier actually used, not just the files the buyer intended to send. Compare the email attachments, portal submission, and active source index by document identity and revision. A familiar filename can contain different content, while a renamed file may be unchanged. Preserve the received objects before investigating the discrepancy.
Reconcile the supplier’s acknowledged source set with the quotation assumptions register and the quotation reference. If a stale BOM or drawing entered the response, identify the affected configuration and ask which lines require review. Keep a correct response for an unaffected configuration separate. The discovery establishes a source mismatch; responsibility and commercial consequences still require evidence from the issue history and the supplier’s revised explanation.
A practical warning sign is a quotation naming one revision while an attached BOM names another. Preserve both files and ask which set the supplier used; do not rename them into apparent agreement. Check the first affected line in the comparison and whether any purchasing instruction already consumed it. If the inconsistency is only in a cover note, document the correction. If the calculation used the former baseline, obtain a response based on the intended source set.
Find delta lines that the refresh missed
Trace each submitted change to a response line. Added components usually attract attention, but a removed test, changed approved source, altered workshare, or revised quantity can be missed when the request is summarised only as a new BOM. Compare the issued delta list with the supplier’s return and mark unanswered items individually.
Use the engineering change control reference to distinguish an approved technical change from a proposal awaiting decision. Ask whether the supplier included, excluded, or held each affected activity. An unchanged price does not establish that the activity was reviewed. Preserve the original response and obtain a linked correction or clarification, so the buyer can tell which assumptions remain valid and which part of the comparison is still incomplete.
Consider a refresh that adds a programming requirement but returns only a revised assembly total. The missing programming line could mean included work, an exclusion or an unanswered question; the buyer cannot choose among those interpretations. Trace the requirement from the request to the supplier response and assign the gap to the responsible reviewer. Keep the affected comparison open until the work and its commercial treatment are explicit, while continuing review of independently confirmed items.
The impact path separates active, superseded, conflicting, and unknown inputs. Recheck quantity date and currency assumptions
Quote refresh risk increases when quantity, delivery date, currency, or validity changes without a matching update to the comparison basis.
Put quantity, release pattern, currency, validity, and date basis beside both responses. A revised total may reflect a different order size or a different delivery endpoint rather than the technical change being investigated. Record the differing field before calculating or reporting a commercial effect. Ask the supplier to clarify any value that was carried over without a current basis.
Check whether material assumptions in the BOM risk report changed at the same time. Availability, minimum purchase quantities, and buyer-supplied workshare can affect how an offer is interpreted, but their consequences must come from the actual response. Keep scenarios separate until the commercial owner agrees on a common comparison basis. Do not turn an unexplained difference into a claimed price increase or supplier error.
Select one discrepancy, preserve both values and identify the first affected comparison action before asking anyone to correct the record.
Failure path
Mismatch to look for
Reviewer
Containment trigger
Mixed technical revisions
Quoted BOM differs from the version named in the refresh request
Engineering and quotation owner
Stop comparison of affected lines until both parties identify one baseline
Missing cost impact
A changed process has no corresponding included item, exclusion or supplier explanation
Buyer and process owner
Do not treat a blank response as zero cost
Expired commercial basis
Validity date, quantity break or currency basis no longer matches the intended order
Buyer and supplier quotation contact
Obtain a current response before relying on that price
Shifted workshare
Customer-supplied and supplier-sourced responsibilities differ between versions
Buyer and materials planner
Pause the affected purchasing instruction until responsibility is explicit
Compare workshare instead of totals alone
Compare the activities assigned to each party. One offer may include component procurement, programming, fixture work, inspection, or a delivery segment that another offer leaves with the buyer. Build a workshare row for each relevant activity and retain the supplier’s inclusion, exclusion, or conditional wording. Comparing totals before reconciling those rows can conceal a transfer of work.
Use the PCBA production cost drivers as a prompt for questions, not as a formula for adjusting a supplier’s price. Ask who will perform the omitted activity and which separate response or buyer record covers it. Where scope cannot yet be aligned, show the difference alongside the total and leave the dependent award comparison open. A numerical adjustment invented by the buyer would hide the unresolved commercial question.
An apparent price reduction can accompany a change from supplier-sourced material to customer-consigned material. Compare who purchases the parts, who supplies usable quantities and who resolves shortages before calling the new response less expensive. The task is to normalize the responsibilities, not to assume either arrangement is preferable. Keep the original included-scope wording beside the refreshed wording so an approver sees the work that moved as well as the amount that changed.
The scope view exposes changes in quantity, currency, validity, and workshare. Trace Quote Refresh Risk Across Sourcing, Test, and Tooling
Look beyond the assembly line item for dependencies that changed with the refresh. A new component source may need another sourcing review; a test change may require a program or fixture decision; a board revision may affect tooling. Ask the supplier which dependencies were reconsidered and where their treatment appears in the return package.
An absent line can mean excluded work, unchanged work, or an unanswered question. Obtain a specific clarification rather than selecting the most convenient interpretation. Keep the dependency linked to the affected configuration, owner, and release condition. If the supplier can price only part of the scope, preserve that partial response without presenting it as a complete tested-unit or delivery commitment for the project.
Check whether each changed dependency has an answer from the relevant owner. A component change may raise a tooling or test question, but a generic checklist entry does not prove that new tooling or testing is required. Ask the process owner to identify the affected object and the basis for either a change or a no-change response. A quotation that omits the dependency remains incomplete for that decision even when every displayed arithmetic total is correct.
Challenge copied exclusions and validity
Another quote refresh risk appears when copied exclusions, expired validity, or assumed supplier-owned work persists without explicit review.
Read copied conditions against the new source set. An exclusion may refer to an old test method, an earlier workshare, or a configuration that the refreshed request removed. A validity statement may have expired before the buyer received the revised response. Identify the specific condition and ask whether the supplier is retaining, replacing, or withdrawing it.
Keep the original wording and the clarification together so the comparison remains reproducible. Do not silently delete an inconvenient exclusion or extend a date in the buyer’s summary. If a condition limits only one line, make that boundary visible; if its reach is unclear, ask the supplier to define it. The commercial owner needs the current conditions before deciding whether the offer supports the intended purchase.
Choose one copied exclusion or validity term, preserve its prior and current wording, and identify the commercial decision that remains blocked until the supplier clarifies its scope.
Observed problem
First action
Evidence needed to close it
Do not infer
Two source sets
Separate the attachments and identify the controlling request
Supplier response tied to the approved source set
Matching filenames mean matching contents
Unanswered scope change
Assign the missing operation to a reviewer
Included or excluded scope with a stated basis
Silence means the work is included
Stale availability statement
Ask for a dated sourcing response
Named part, quantity, source and validity
An earlier quote reserves current stock
Pressure to place an order
Escalate the specific unresolved purchasing assumption
Authorized decision acknowledging the remaining condition
A deadline transfers technical approval authority
Material basis review: review MPN, source, quantity, validity against the active project records. Prevent Quote Refresh Risk from Hiding in Delta Pricing
Check whether the response is a full replacement or a supplement. A delta price may be valid only when combined with the original quotation and its surviving terms. Treating that delta as a standalone offer can omit unchanged charges, exclusions, or scope. Conversely, adding a replacement quote to the old total can count the same work twice.
Ask the supplier to name the earlier response and identify what the new document supersedes. Reconstruct the resulting commercial basis once, with each active line and condition traceable to its source. Have another buyer verify that reconstruction before it reaches approval. If the relationship between the documents remains ambiguous, hold the combined comparison rather than manufacturing an apparently complete quotation from disconnected numbers.
A price delta needs its baseline. If a supplier states an additional amount for one change, retain the prior quotation and ask which other terms continue to apply. Do not copy the delta into the purchasing system as though it were the complete order price. An approver should be able to reconstruct the resulting scope and amount from the linked records and identify any conditions that the supplier did not reconfirm for the intended order.
Correct the Comparison Without Erasing History
Preserve the flawed response, record the correction, and prevent either version from becoming an uncontrolled quotation baseline.
Contain quote refresh risk by preserving the flawed response, recording the correction, and preventing either version from becoming an uncontrolled baseline.
Contain the discrepancy at the decision that depends on it. Preserve the issued request, received response, disputed field, and the question sent for correction. Assign an owner and a review date, then identify which unaffected comparisons or planning activities can continue. A broad project stop may be unnecessary when the uncertainty is limited to one configuration or work line.
When the supplier answers, link the correction to the earlier response instead of replacing history. Check that the revised field appears consistently in the comparison and intended purchasing record. Record any remaining conditions and communicate the active revision to its users. Close the discrepancy only when the corrected basis can be reproduced; receipt of another email alone does not establish that downstream work has been corrected.
When correcting a refresh, identify the affected comparison version and notify the people using it. Preserve the original response and the correction so a later reviewer can explain why the decision changed. If an order was already prepared, check its references rather than assuming that updating the comparison sheet also updated purchasing. Close the discrepancy only after the active order or decision record reflects the corrected basis and the responsible owner has addressed any remaining consequence.
Incoming exception: review identity, condition, segregate, owner against the active project records. Run a Quote Refresh Risk Drill Before Approval
Start the discrepancy drill at the first value that cannot be reconciled. The analyst records where it appears in the buyer request, supplier return and comparison sheet, without correcting any of those sources. The person then checks the BOM and drawing revisions that shaped the line. This sequence distinguishes a transcription error from a changed scope or stale assumption. A second analyst should be able to repeat the route and find the same break using only the recorded references.
Do not resolve the mismatch by choosing the newest-looking attachment. Mark both values, their dates and their custodians, then identify the commercial decision that consumes the field. Hold that decision while the owner supplies a corrected response or documented explanation. Other quote lines can continue when they do not inherit the disputed basis. The drill is successful when the corrected line points back to its source and the comparison sheet no longer relies on private context.
FAQ
Does a different refreshed total prove an error?
No. Quantity, scope, sourcing, test, tooling, delivery conditions or validity may have changed legitimately. Compare the source and assumption fields before judging the difference.
Why is a delta response risky in a supplier comparison?
It is risky when reviewers treat it as a full replacement. The record must link the delta to the exact prior response and confirm which fields remain active.
Can a copied exclusion remain valid?
Possibly, but it needs readback against the current request. A copied condition should not be accepted merely because it appeared in the previous quotation.
What evidence should accompany a refresh discrepancy?
Preserve old and new quotes, the active file index, delta register, quantities, workshare, sourcing, test and tooling changes, the affected comparison line and authorised correction.
Before accepting the refreshed commercial basis, ask one reviewer who did not prepare the comparison to reopen a changed line and an allegedly unchanged line. The reviewer should identify the controlling request, supplier response, inherited condition and permitted next action without verbal coaching. Any missing connection stays open and blocks only the decision that depends on it.
Bring the active records to the PCBA quote refresh risks review
Provide the old and refreshed responses, buyer request, comparison sheet and the first observed discrepancy through the plain contact page . Preserve the failed comparison state so the review can trace rather than reconstruct it.
A useful result names the broken connection, containment boundary, correction owner and repeated check. It does not assign fault or claim a commercial impact without the relevant source evidence.
Use the risk checklist to trace each quote discrepancy to its source, affected comparison, containment, and correction owner. Confirm any commercial or technical consequence against the current supplier response, contract, quality requirements, and authorised project records.
