A PCBA quote exclusion decision starts by mapping every requested work line to the supplier response before comparing totals. Show whether the line is included, buyer-supplied, separately priced, pending, or unavailable, then attach its owner and consequence. The comparison is incomplete while an omitted operation or delivery segment remains hidden inside the total.
A blank or “not included” response does not tell the buyer who performs the work or what must happen next. Buyer-supplied scope, optional work, pending data, an explicit exclusion, and a no-bid line lead to different purchasing actions and liabilities.
Suppliers may offer different workshares and business models. The buyer needs enough scope detail to compare those responses and prevent an RFQ assumption from entering the purchase object or build plan without an authorised owner. Keep the source wording and closure state in the quote exclusions checklist , and send technical consequences to the engineering exclusion review .
Ask the supplier to read every exclusion against the requested workshare and response revision. Enter zero only when the supplier explicitly prices that line at zero; otherwise preserve its actual state and required follow-up.
Classify Each PCBA Quote Exclusion Decision
Treat exclusion, assumption, option, and hold as different response states: an exclusion removes work, an assumption prices included work under a condition, an option offers selectable scope, and a hold waits for evidence before the affected line can proceed.
Put each item in the correct state. If functional test is excluded, state whether the buyer performs it, whether development is separate, and what evidence releases a future quote. If test is included under an assumed cycle, record the assumption instead.
Do not hide exclusions inside general terms or an email thread. Link them to the RFQ baseline and response revision.
Use the public project review before quotation page to organise the questions. The active supplier response remains the source for each exclusion.
Map Workshare for the PCBA Quote Exclusion Decision
Create rows for PCB fabrication, component sourcing, buyer-supplied material, assembly, manual operations, cleaning where specified, programming, inspection, functional test, tooling, documentation, logistics, and any project-specific service.
For each row, compare requested, included, conditional, excluded, optional, and pending states. Name the controlling input and authority.
If the supplier offers a different workshare, preserve that difference. Do not fill a blank as included or set an unknown price to zero.
The PCB assembly services page provides general scope context. Use the current RFQ and supplier response for the actual workshare, price, capacity statement, quality result, and delivery basis.
Identify the work line before the buyer accepts it as included, excluded, or separately quoted.
Response state
Meaning
Buyer action
Supplier record
Included
Work is priced within stated basis
Verify scope and acceptance
Method, input, and quote line
Assumed
Work is priced under a bounded condition
Accept, reject, or replace input
Assumption and consequence
Optional
Separate selectable work is offered
Compare and select explicitly
Option price and dependencies
Excluded
Work or responsibility is outside response
Assign owner or request revision
Reason and affected endpoint
Held
Evidence is insufficient for a bounded response
Supply evidence or change request type
Hold and release condition
Expose component and material exclusions
State whether the quote includes all BOM lines, approved alternates, shortages, excess, supplier minimums, freight to the factory, import treatment where applicable, and buyer-supplied-material control. Identify any line priced as a placeholder or omitted.
If the buyer supplies material, record receipt, quantity, attrition treatment, shortage responsibility, and unusable-material disposition. “Consigned” does not answer those questions.
If market availability is unresolved, label the price or date conditional. A public listing does not prove allocation or an authorised source.
The components management page helps frame material questions. Confirm project stock, price, authenticity, allocation, and approved substitution against the active BOM response.
Separate engineering services from routine manufacturing
Clarify DFM review, data correction, panel design, stencil or fixture design, test development, programming setup, component research, alternate evaluation, failure analysis, and change processing.
Some engineering review may support quotation while detailed development belongs after award. State where the boundary lies and what deliverable is included.
Do not treat a supplier question list as completed engineering. It identifies an input or decision gap. The buyer still owns design authority unless a different contractual scope is agreed.
If engineering work is optional, show the prerequisite, output, acceptance owner, and effect on production release.
Grouped assemblies show why quantity, variant, and release pattern belong beside every quoted exclusion. Define Test Scope for the PCBA Quote Exclusion Decision
Programming scope should identify firmware, hardware, method, interface, verification, security handling, tool or fixture, and result record. Test scope should identify procedure, limits, fixture, cycle basis, result, retest, and disposition.
If only continuity or power-on inspection is included, do not label it functional test. If fixture development is excluded but test execution is included, state who supplies a compatible fixture and when.
An excluded test line changes the meaning of delivery and acceptance. Identify who performs the omitted work and which result releases the next stage.
The public quality assurance page supplies control context. The quotation must state the current test coverage, inspection scope, conformity evidence, and acceptance boundary.
Tie exclusions to quantity and release pattern
An exclusion can vary by tier. Prototype pricing may exclude recurring material sourcing, production tooling, or formal records that a later stage requires. A production tier may exclude repeated setup assumed under one consolidated release.
State which quantity, configuration mix, and release cadence the exclusion uses. If the actual order differs, trigger a review.
Separate one-time and recurring exclusions. A fixture can be buyer-owned while maintenance, repair, or duplication remains outside the quote. Record the treatment rather than guessing.
Quantity-tier approval and exclusion approval are related but distinct. A buyer can accept the quantity scenario while rejecting its excluded test or material responsibility.
Exclusion class
Evidence needed
Consequence to record
Requote trigger
Material line
BOM/AML, workshare, availability basis
Buyer buy or unpriced exposure
Part, source, quantity, or responsibility changes
Engineering task
Input, output, owner, acceptance
Separate work before release
Design or deliverable changes
Programming/test
Firmware, method, limits, fixture
Delivery lacks stated verification
Method, fixture, coverage, or cycle changes
Tooling/setup
Tool ownership and recurrence
Added cost or unavailable process
Panel, configuration, or release changes
Delivery segment
Endpoint and responsibility
Buyer arranges omitted segment
Destination, route, or term changes
Keep delivery and acceptance boundaries visible
State whether the response ends at manufactured PCBA, inspected unit, tested unit, carrier handover, or another agreed event. Separate transit and buyer receiving.
If documentation, certificates, test data, or traceability exports are excluded, identify whether the buyer needs them for acceptance. Do not promise records that are not in the scope.
Add finished-product packaging requirements only when the project supplies authorised specifications and current compliance evidence.
FAR Subpart 11.4 applies to government acquisition, not private PCBA contracts. Its schedule-clarity concepts are useful for identifying a delivery endpoint, not for setting commercial terms here.
Name the handling and protection work and assign its owner. Record Authority for the PCBA Quote Exclusion Decision
Assign technical boundaries to engineering, material and commercial workshare to sourcing, verification and records to test or quality, and the endpoint to logistics. The authorised buyer owner accepts the combined scope after those owners state their consequences.
The supplier confirms how the exclusion affects price, date, work, and response validity. Supplier confirmation does not replace buyer acceptance.
Record rejected exclusions and the revised treatment. Do not delete the earlier response; link the new quote revision and changed rows.
ISO/IAF customer-communication guidance addresses review of requirements before commitment and order changes. It supports explicit readback but does not prove project conformity or certification.
Record the PCBA quote exclusion decision
Capture:
RFQ baseline, response revision, product, configuration, and quantity.
Requested work line and current response state.
Excluded object, activity, responsibility, deliverable, or milestone.
Reason and evidence source.
Buyer owner, supplier owner, and approval authority.
Effect on price comparison, schedule, material, verification, and acceptance.
Allowed assumption or optional treatment.
Required closure evidence and due date.
Accepted, rejected, conditional, held, or requote decision.
Validity and re-open trigger.
An independent buyer reviewer should be able to reconstruct what each supplier will deliver without treating a blank line as zero price or included work.
A visible material and setup boundary helps the buyer ask who owns preparation, replenishment, return, and records. Compare two responses without normalising away the exclusions
Create a comparison row for each requested work line. Supplier A may include PCB fabrication, material, assembly, programming, and visual inspection while excluding functional test and fixture development. Supplier B may include test execution under a buyer-supplied fixture but exclude material for several unresolved BOM lines. Treat the responses as comparable assemblies only after those adjustments are visible.
Product and quantity identity establish the comparison baseline. Both responses must use the same PCBA revision, variant mix, build stage, quantity unit, and release pattern. A consolidated lot and several smaller releases remain different commercial objects even when their annual quantity matches.
Material workshare corrects the apparent price. List unpriced BOM lines, buyer-supplied parts, approved alternates, pack minimums, excess, and price-validity conditions. A no-bid line stays open rather than becoming zero; buyer cost or follow-up belongs in a separate planning item supported by evidence.
Compare engineering, test, and delivery scope
Engineering and tooling need their own comparison. One response may include a stencil but exclude panel review, while another treats both as separate non-recurring lines. State the input, output, ownership, and recurrence. A lower setup line can reflect a different scope rather than greater efficiency.
For programming and test, compare method, firmware, interface, fixture, limits, result record, and disposition. If coverage differs, show it beside the price. Do not label a power-on check and a defined functional test as equivalent.
The endpoint determines what the buyer receives. A response for assembled units and one for tested units use different delivery definitions. Add buyer-owned downstream work and its schedule path to the decision record without presenting it as supplier scope.
Open assumptions and holds remain visible beside the price. A response with an unbounded major input stays conditional, while a blank response cannot outrank a documented exclusion merely because it appears simpler.
The resulting workshare identifies the usable response, required revisions, and buyer decision. An incomplete price table cannot support a supplier ranking.
Handoff the PCBA Quote Exclusion Decision into Kickoff
Before project kickoff, transfer every accepted exclusion to the workshare, responsibility matrix, schedule basis, material plan, programming and test plan, documentation list, and purchase object where relevant. The quotation checklist should point to these downstream records.
At kickoff, each owner reads the accepted exclusion into the downstream record under that role’s authority. The supplier confirms the active response basis; the buyer records who now owns every omitted input, operation, result, or endpoint.
Set a selection deadline for every optional or separately quoted line before release. If the buyer intends to supply a fixture, firmware, or test method, record the required delivery date and compatibility evidence. An accepted exclusion without a handoff owner becomes a hidden project gap.
At the first configuration or quantity change, compare the active workshare with the original exclusions. A new variant, approved alternate, panel, firmware, test scope, release cadence, or customer record requirement can invalidate the earlier treatment.
At first-build review, sample one excluded work line and show how the replacement owner completed it. Preserve the evidence and any changed assumption. If the replacement path failed, reopen the exclusion and assess the quote and schedule impact.
Buyer language must retain the accepted response state during handoff. “Excluded” cannot become “supplier will support later” without a newly accepted scope, and a conditional estimate cannot become included work. The state changes only through a revised response.
Choose the documented treatment for each exclusion
The buyer can accept an exclusion when another authorised party owns the omitted work, the interfaces and timing are defined, and the consequence is understood. When the supplier is needed for that work, convert the gap into a separately stated option with its input, output, price basis, schedule relationship, acceptance owner, and validity. Selection of the option must create a revised active workshare.
Full inclusion requires a revised quote rather than a crossed-out note. The new response must show the changed price, schedule, assumptions, dependencies, and endpoint. Preserve the earlier version so the project can reconstruct when responsibility moved and which evidence supported the change.
An exclusion conflicts with the RFQ when it removes a required product, process, verification, regulatory, customer, or acceptance condition and no authorised replacement exists. Reject that treatment with the applicable requirement source. Leave the line on hold when the consequence cannot yet be bounded, and name the missing product data, part approval, fixture interface, test method, record requirement, or endpoint.
Every accepted, revised, rejected, or held treatment needs a re-open trigger. A changed variant, quantity, release pattern, component, firmware, fixture, test method, customer requirement, or endpoint returns the line to review and keeps the decision tied to the condition the buyer actually evaluated.
Read the final scope back in buyer language
Before approval, rewrite each accepted row as an operational statement: who supplies the input, who performs the work, what output is expected, which evidence releases the next gate, and what the supplier will deliver. Compare that statement with the supplier’s wording without changing its meaning.
Request revision when the buyer statement adds excluded work. Restore any supplier condition it removes, and keep the decision open when the endpoints differ.
Use named product and quote revisions during readback. General phrases such as “standard test,” “normal documentation,” or “customer material” are too broad for handoff. The record should remain understandable after staff or suppliers change.
Use the final approval to record each accepted, replaced, rejected, or held decision, the active response, and the owner of buyer-supplied work. A signed summary without these links does not close the scope.
Send that same approved scope to the project owner before kickoff. The handoff should identify each open input, its due date, the supplier’s bounded responsibility, and the event that requires a new quotation.
FAQ
Is an assumption the same as a quote exclusion?
No. An assumption prices included work under a condition. An exclusion removes work or responsibility. Both require a consequence and owner.
Can the buyer accept a quote with exclusions?
Yes, if the buyer understands and assigns the omitted scope, accepts the consequences, and records the decision. A missing core input may instead require a hold.
Should excluded test work reduce the price comparison?
Keep the difference visible. Compare the cost and consequence of obtaining the missing work elsewhere or requesting a revised response; do not normalise it to zero.
When must exclusions be reviewed again?
Review them when product data, quantity, workshare, material, programming, test, documentation, endpoint, or buyer requirement changes.
Send the workshare comparison used for the buyer decision
The buyer should provide the RFQ baseline, response revisions, workshare comparison, product data, quantity tiers, material responsibility, programming and test requirements, requested endpoint, and open exclusions.
Send that workshare comparison and the linked supplier responses through the plain contact page for a bounded first-build quotation review. Project-specific price, capacity, quality, and delivery remain subject to current evidence and approval.
