A PCBA quote exclusions checklist needs one row for each excluded decision object in the supplier response. Tie that row to the RFQ baseline, exact omitted scope, responsible owner, accepted consequence, current decision, and event that requires a revised quote. The next reviewer should see what remains open without reconstructing the discussion from email.
Use the checklist as the operational record for comparing supplier responses and transferring accepted workshare into purchasing and kickoff. Use the engineering exclusion review when an omitted operation needs technical verification, and the buyer exclusion review when the resulting workshare needs commercial acceptance. Its wording must preserve the supplier’s actual condition rather than replace it with a protective phrase or editorial summary.
A blank response remains pending until the supplier confirms whether the work is included, excluded, optional, held, or outside the request. Price and ownership stay open with that state; neither can be inferred as zero.
Keep the source response beside each decision object. The row names the supplier answer, buyer readback, decision date, closure document, and responsible role. Missing confirmation leaves the row open.
Identify the Response for the PCBA Quote Exclusions Checklist
Record RFQ baseline, supplier, response identifier and revision, issue date, validity, product and configuration, quantity, build stage, and requested endpoint. Preserve the original response.
If a revised quote changes exclusions, create a delta. Show added, removed, modified, and unchanged rows. Do not overwrite the earlier record.
Link the checklist to the file index and decision record. A detached checklist can drift from the quotation it describes.
Use the public project review before quotation page to frame the review. Identify current exclusions from the linked supplier response and revision.
Give Every PCBA Quote Exclusions Checklist Row an Identity
Assign an ID and name the requested work line, excluded activity or responsibility, affected configuration and quantity, supplier wording, reason, and source location.
Classify the row as excluded, assumed, optional, held, pending clarification, or not applicable. Define each state so reviewers use it consistently.
Record whether the exclusion applies to price, date, material, engineering, process, programming, test, records, logistics, or acceptance. More than one impact may apply.
The PCB assembly services page supplies general scope context. The active quote line determines whether the supplier provides or prices the omitted work.
Each exclusion row needs a source response, an excluded task, an owner and a closure record. This is a schematic index, not a completed project record.
Checklist field
Required content
Review question
Reject if
Baseline
RFQ and quote revision, product, configuration, quantity
Which response does this row control?
It refers only to an email subject
Excluded scope
Activity, object, responsibility, or deliverable
What will not be supplied?
Wording is “not included” alone
Consequence
Price, schedule, technical, verification, or acceptance effect
What must another owner do?
Consequence is hidden
Authority
Buyer owner, supplier owner, approver
Who may accept or change it?
“Team” is the only owner
Closure
Decision, evidence, validity, and re-open trigger
When can the row be relied on?
No linked response or trigger
Map Material Workshare in the PCBA Quote Exclusions Checklist
Compare the BOM and approved-parts basis with the response. Record supplier-sourced, buyer-supplied, no-bid, placeholder, candidate alternate, excess, minimum, and shortage treatment by line or controlled group.
For each excluded line, state who obtains the material, when it must be available, what identity and quantity evidence the buyer requires, and how a shortage affects the schedule.
Do not allow a candidate part to enter the active basis without buyer authority. Record approved effectivity when an alternate is accepted.
The components management page helps define material questions. Project approval, stock, price, authenticity, allocation, and excess treatment require the active BOM response.
Separate engineering services, tools, and change work
Create separate rows for data review, DFM findings, data correction, panel work, stencil, carrier, programming fixture, test fixture, component research, alternate evaluation, failure analysis, and engineering changes where applicable.
State whether the supplier only reports an issue, proposes a change, develops an output, or implements an approved change. Preserve buyer design authority unless another scope is explicitly agreed.
Record ownership, one-time or recurring treatment, prerequisite, output, acceptance owner, and effect on production release.
If a tool is buyer-owned, include availability, controlled identity, interface, condition evidence, allowed modification, and return or disposition responsibility where applicable.
An inspection work line should state whether the supplier, buyer, or another party owns the method and result. Define programming, test, inspection, and records
Programming rows should cover firmware identifier, target hardware, method, interface, verification, security handling, and fixture. Test rows should cover procedure, limits, development, fixture, execution, records, retest, and disposition.
Inspection rows should identify method, characteristic, acceptance source, coverage or sample basis where defined, result record, and release authority. Do not invent criteria.
Documentation rows may include material traceability, lot or serial records, program revision, inspection, test, nonconformance, and disposition only when requested or applicable.
The quality assurance page provides general control context. The active project defines its coverage, required records, conformity evidence, and acceptance authority.
Tie Quantity and Validity to the PCBA Quote Exclusions Checklist
An exclusion may apply only to one tier, stage, configuration, or release pattern. Record quantity unit, units per panel, variant mix, number of releases, and whether setup or engineering repeats.
State the quotation validity and the technical applicability limit. A commercial price may expire while the product baseline stays unchanged; a technical change may invalidate the scope before the price date.
If the buyer orders between tiers, ask the supplier to confirm the applicable exclusions. Do not interpolate scope from price.
Reopen the row when product data, approved parts, quantity, workshare, programming, test, records, endpoint, or customer requirement changes.
Decision state
Buyer finding
Checklist treatment
Next action
Accept
Omitted work has a defined authorised owner
Record approval and handoff
Verify at project kickoff
Conditional
One bounded input remains
Show assumption, expiry, consequence
Close or requote by deadline
Request option
Buyer wants selectable added scope
Add prerequisite and price line
Compare revised response
Reject
Exclusion conflicts with required scope
Record reason
Request inclusion or select another route
Hold
Consequence or authority cannot be bounded
Stop affected decision
Supply evidence and release owner
State the delivery and acceptance effect
State whether the quoted endpoint is assembled, inspected, programmed, tested, released to carrier, received, or accepted. Identify any excluded transit, customs, receiving, documentation, or buyer acceptance activity.
Do not let an excluded test or record remain invisible beside a “finished PCBA” description. Define what finished means for this response.
Add finished-product packaging scope only after authorised requirements and current compliance evidence are available.
FAR Subpart 11.4 is a government rule, not a private PCBA contract standard. Its emphasis on clear delivery schedules is used only as a clarity check for the endpoint.
A checklist row should point to the applicable inspection record instead of treating a department label as closure evidence. Record Acceptance in the PCBA Quote Exclusions Checklist
Assign product and process consequences to the technical owner, material and commercial scope to sourcing, verification and records to test or quality, and the endpoint to logistics. The authorised buyer owner accepts the combined workshare after those findings are recorded.
The supplier quotation owner reads back the response basis, exclusions, assumptions, options, holds, quantity, validity, and changed rows. This confirms shared understanding but does not approve buyer requirements.
Record names, roles, dates, decisions, and limitations. “Approved by both teams” is not enough for later reconstruction.
ISO/IAF customer-communication guidance supports reviewing requirements before commitment and handling changes. It is not a certificate or project-specific approval.
Add Closure Fields to the PCBA Quote Exclusions Checklist
Closure requires the applicable evidence, authorised decision, updated response where needed, and supplier readback. Record closure date, state, approver, quote revision, and the project handoff destination.
Conditional closure needs an owner, deadline, allowed work, prohibited work, and consequence if the assumption changes. Keep the condition visible in downstream records.
Reopen when a linked object or requirement changes, an assumption is rejected, the response expires, a new quantity is requested, or the project discovers that the replacement owner cannot perform the omitted work.
Preserve the decision history. A row cannot close unless the record shows how the active scope replaced the earlier response state.
A checklist closure should identify the affected lot, status, next route, owner, and release evidence. Run the PCBA quote exclusions checklist
For every row, capture:
Exclusion ID, RFQ baseline, response revision, product, configuration, and quantity.
Requested work line and supplier wording.
State: included, assumed, optional, excluded, held, pending, or not applicable.
Reason, source object, and evidence limitation.
Technical, material, price, schedule, verification, record, and endpoint consequences.
Replacement owner, interface, input, output, and due date.
Buyer technical review and commercial decision.
Supplier readback and revised response where required.
Validity, allowed work, prohibited work, and project handoff.
Closure evidence and re-open trigger.
Keep one clear owner per decision. Several people may contribute evidence, but authority should remain visible.
Populate the checklist from the source response, not from memory
The supplier response supplies the original wording and source location for every exclusion. Ambiguous wording stays pending clarification rather than being translated into an editorial category.
Compare that wording with the buyer’s requested workshare. A requested activity that is absent from the response receives a pending row until the supplier confirms its treatment, preventing a blank from becoming a hidden exclusion or assumed inclusion.
Product identity travels with the row: active assembly, configuration, revision, quantity, build stage, and RFQ baseline. An exclusion limited to one variant or tier retains that boundary beside the supplier wording.
The applicable owner adds the consequence under the authority map above. Technical pathways, material exposure, verification effects, and schedule treatment remain separate fields, while the final buyer owner accepts or rejects the complete treatment.
A supplier revision creates a row-level delta rather than a replacement checklist. Accepted changes must appear in the new response, and a removed exclusion must become included or optional scope with a clear price and basis before its earlier row closes.
The supplier response and buyer records support the decision; public references can only help frame review questions.
Audit the PCBA Quote Exclusions Checklist at Each Gate
Purchase approval compares the purchase object with the chosen response for product, quantity, workshare, endpoint, and accepted exclusions. A conflict keeps the affected line open before acceptance.
Kickoff requires each replacement owner to read back the work received. Programming data, fixtures, buyer-supplied material, test methods, or records due later need dates and release gates so an accepted exclusion cannot become an unassigned action.
First-build review samples the highest-consequence rows. Follow buyer-supplied material from approved part to use, link excluded test development to its authorised method and fixture, and confirm the delivery handover endpoint recorded in the response.
Record observations against the same row ID. If the condition matches, preserve applicability and the next review trigger. If it differs, reopen the row and assess technical, commercial, and schedule impact.
Optional selection, expired conditions, and new hold evidence update the same row ID at the applicable gate. Project progress alone cannot close an unresolved decision.
If several responses leave the same work line ambiguous, add that line to the RFQ response table. If ownership is repeatedly missing, add the owner field to the responsibility matrix.
Keep the checklist readable for a second reviewer
Use short controlled fields and link to evidence instead of pasting long email threads. Plain language should identify the condition, owner action, accepted consequence, and result without a score that hides the decision.
Sort active holds and conditional rows before closed history. Make the response revision and applicability visible without opening attachments. Retain superseded rows for reconstruction.
Do not add promotional statements, supplier rankings, or unsupported capability claims. The checklist is a control record, not marketing copy. When a fact is missing, write the missing fact and the evidence needed.
A second reviewer must reconstruct the excluded work, its reason, replacement owner, accepted consequence, and re-open trigger without verbal help from the original reviewer. A missing answer keeps the row incomplete.
Link exclusions to RFQ questions and supplier answers
When the buyer asks for clarification, assign a question ID and link it to the relevant exclusion row. State the required answer, affected quote line, responsible supplier owner, buyer decision owner, and response deadline.
Preserve the supplier’s answer as a source object. Do not paraphrase away a condition. If the answer changes the response, require a revised quotation or an authorised attachment that clearly controls the active scope.
Separate confirmation from approval. A supplier can confirm that test is excluded; the buyer must decide whether another owner performs it or whether a revised response is needed. A buyer can approve an alternate; the supplier must confirm price, availability, and schedule basis.
Close the question only when the answer is mapped into the exclusion state, consequence, owner, and active response. An answered email that never changes the checklist leaves the operational record incomplete.
Review question aging by decision type. Missing product authority, material input, test method, or endpoint may require different escalation. Do not use one generic reminder that hides the role needed.
If the project proceeds under a bounded answer, copy the condition to the handoff record and identify its expiry. A clarification should not disappear when the quotation moves into purchasing or kickoff.
Export a compact active-scope view for approval
Keep the full history in the checklist, then create an active view containing open, conditional, held, optional, and recently changed rows. Include product, quantity, response revision, owner, due date, consequence, and required next action.
Do not remove closed exclusions that still define buyer workshare. Show them as accepted boundaries in the approval view and link their evidence. Hide superseded details only from the working view, not from history.
Ask engineering, sourcing, test, quality, planning, logistics, and the supplier quote owner to review only the rows within their authority. The final buyer owner receives the consolidated state and unresolved decisions.
After approval, freeze the view with a revision and date. Link it to the purchase and kickoff records. A later change should create a delta so the project can see which workshare moved.
FAQ
Should blank quote lines be entered as exclusions?
No. Mark them pending clarification until the supplier states whether the work is included, excluded, optional, not applicable, or held.
Can one checklist cover several supplier quotes?
Use a common comparison view, but retain a controlled row set linked to each supplier response and revision. Do not merge different scopes into one false baseline.
Who closes a quote exclusion?
The owner authorised for the affected buyer decision approves the treatment, and the supplier confirms the revised or accepted response basis.
What is the most important re-open trigger?
Any change to a linked product, quantity, workshare, material, programming, test, record, endpoint, assumption, or response validity should prompt review.
Send the active checklist used for project handoff
The buyer should provide the active checklist with its RFQ and responses, workshare matrix, product baseline, quantity table, material responsibilities, programming and test requirements, record needs, endpoint, and decision owners.
Send the active checklist and linked supplier response through the plain contact page for a bounded first-build quotation review. Project price, capacity, conformity, and delivery remain subject to current evidence and authorised approval.
