An alternate rule freeze should occur before a quotation, material commitment, build release, or repeat order relies on the substitution boundary.
Freeze PCBA alternate rules before a quotation, purchase, build release or repeat order relies on those rules. The frozen object is the rule set, not a proposed replacement part. It states which BOM lines may use an alternate path, which sources or component classes are permitted, what evidence is required, who decides, when the decision becomes effective and what conditions reopen the rule.
Staggered decisions can leave sourcing, engineering, purchasing, and manufacturing working from different versions of the alternate rule. Sourcing may compare offers while engineering is still reviewing a component. A buyer may reserve constrained material before production is released. A manufacturer may receive a BOM note that describes an approved family but does not identify whether the note applies to the current revision. Without a versioned rule, each team can follow a different assumption while believing that the same policy applies.
A freeze does not prove that any candidate is electrically, mechanically or commercially acceptable. It creates a stable decision path for the next action. If the product baseline, component notice, applicable compliance scope, supporting evidence or approval authority changes, the affected rule returns to review. The buyer then decides whether to re-freeze it, narrow it or hold the related action.
Separate the Alternate Rule Freeze from Candidate Approval
A rule defines the conditions under which a candidate may be considered. A candidate record identifies the actual manufacturer part number, source, proposed use and evidence for one decision. Keep these objects separate. Otherwise, a statement such as “alternates allowed” can be mistaken for approval of every part that appears to match a description.
At minimum, give the rule a controlled identifier, version, owner, issue date and status. State the product or product family, BOM revision, affected reference designators or part classes, permitted source conditions, prohibited cases, required evaluations, final approval authority, effectivity point and expiry or reopen triggers. Mark unknown fields as open. Do not convert silence into permission.
Candidate evaluation begins after the active rule has routed the request. The article on evaluating component alternatives in PCBA covers the technical comparison of package, pinout, electrical behavior, firmware, manufacturing and compliance effects. This article does not repeat that evaluation. Its subject is whether the rule that requires and controls the evaluation is valid for the next project gate.
Use explicit response states. A practical set is draft, under review, frozen, conditionally frozen, reopened and superseded. “Approved” by itself is too vague because it may refer to a rule, a candidate, a BOM revision or a deviation. Record the object beside the status and make the permitted next action visible.
Record the rule fields used at the gate
Rule field
What the team records
Unsafe interpretation to prevent
Identity
Rule ID, version, owner and date
A note copied from an old BOM is still active
Scope
Product, revision, BOM lines and excluded cases
One rule covers every product or reference designator
Permitted route
Allowed source class and evaluation path
Availability is enough to use a part
Evidence
Required technical, quality, sourcing and compliance inputs
A distributor cross-reference proves equivalence
Authority
Review roles and final decision owner
Any project participant can approve a change
Effectivity
Quote, order, lot, build or date boundary
Approval applies to prior or later material automatically
Reopen rule
Change, expiry and missing-evidence triggers
A frozen rule never needs another review
A rule can route a component proposal without approving the reel, lot or manufacturer part number shown in a later candidate record. Set the Alternate Rule Freeze Before Quotation
Quotation comparison is the first common freeze point. If one supplier prices only the released manufacturer part number, another assumes broker sourcing, and a third assumes preapproved alternates, their totals do not represent the same material basis. The OEM should either issue one frozen alternate rule with the RFQ or label the rule as open and require each response to state its assumption.
The rule at this stage does not need to approve a future candidate. It needs to state what the quotation may assume. For example, the RFQ can require pricing against the released BOM, permit separately priced options, prohibit unapproved purchases, and identify the evidence needed before an option can move to purchase approval. The response should distinguish included material, proposed alternatives, unpriced exposure and buyer decisions.
Check the receiving entity and permitted data use before sharing a sensitive BOM or rule set. The guide on questions to ask before sharing a PCBA BOM owns that disclosure decision. A valid rule does not identify the legal receiver, authorize onward disclosure or establish retention terms.
After responses arrive, compare them against the rule ID and version issued with the RFQ. If a supplier used another basis, keep the response conditional. Do not repair the difference silently in an internal spreadsheet. Ask the supplier to confirm the affected quote lines, proposed source route, expected technical review and commercial effect. That confirmation becomes part of the quote comparison record.
Freeze again when an RFQ clarification changes the permissible route. A later email that allows one exception can affect several suppliers differently. Update the controlled rule or issue a bounded clarification that names the affected product, line, response and expiry. Then obtain readback from every party whose quotation depends on it.
Reconfirm the rule before material commitment
The alternate rule freeze should state which part attributes may vary, which must remain fixed, who can approve an exception, and what evidence is required.
A commercial action can create exposure before a build begins. Reserving stock, placing a noncancelable order, accepting excess material liability or authorizing a supplier to procure an alternate can make a preliminary rule costly. Reconfirm the active rule before the buyer approves that action.
The commitment record should name the exact requested and proposed manufacturer part numbers, quantity, source category, lead-time evidence date, affected BOM lines, disposition if approval fails and the person authorized to accept the commercial condition. State whether the action permits reservation, purchase, receipt, inspection or production use. These permissions are different.
Product-change and end-of-life notices can trigger a new review. Manufacturer notices may identify affected products, timing, qualification information and expected impact, but the notice does not approve a replacement for the OEM’s assembly. Link the notice to the rule and candidate records, check its date and affected item, and decide whether the current rule still routes the event correctly.
Use a hold when the permitted source, traceability requirement, technical review or disposition responsibility is missing. The hold can be bounded to an item, quantity, source, order or build. It does not need to stop unrelated work. Record what may continue, what must not start and what evidence releases the affected action.
Inspection evidence supports review; an authorized decision and defined effectivity are separate requirements before an alternate reaches the affected build. Confirm the Alternate Rule Freeze Before First-Build Release
Before the first build, connect the rule to the released product state. The active BOM, placement data, assembly drawing, firmware and test inputs may reveal that a broad RFQ assumption no longer fits. A rule that permitted quotation options may still prohibit production use until a named candidate passes the required review.
The PCBA PO production release gate separates commercial authority from technical production release. Apply that separation here. A purchase order can authorize a bounded material action without making an alternate part effective on the line. The production release should identify the current rule, the candidate decision, the BOM revision, the affected quantity or lot and the approving authority.
Before kitting or line issue, perform a readback rather than relying on a meeting summary. Compare the rule ID and version in the release package with the version used for the candidate review. Confirm that excluded reference designators remain excluded and that conditional evidence has closed. Check whether existing stock, open purchase orders or work in process fall inside or outside the effectivity boundary.
If a rule was reopened, prevent its previous version from reaching the line. Mark it superseded in the active project index, retain it for traceability and distribute the new state to sourcing, quality, production control and the external party that holds affected material. A newer file on one person’s computer is not a release control.
Before first-build release, read back the active rule, candidate state, BOM revision and effectivity boundary. Define effectivity without approving an unknown part
Effectivity states where a decision begins and ends. It may use a BOM revision, purchase-order line, material lot, work order, serial range, build date or another controlled boundary. Choose an object the affected teams can retrieve and apply. “From next build” is weak when different teams use different definitions of a build.
A frozen rule can be effective even when no candidate has been approved. It can say that specified BOM lines require case-by-case evaluation and that no alternate may be purchased or used until the candidate record reaches a stated approval state. This is useful because it makes the route stable without pretending the unknown candidate is acceptable.
Conditional effectivity needs an end condition. Name the evidence still due, the permitted interim action, the owner, the affected quantity or period, the expiry and the result if the condition does not close. Examples include permission to request samples but not purchase production quantity, permission to receive segregated material but not issue it, or permission to run a controlled engineering build but not ship product. Actual permissions must come from the OEM’s authorized process.
The project interface described in the PCBA BOM engineering support guide can route findings, responses, approvals and released updates. The rule freeze is one object within that interface. It does not replace the complete input, finding and closure model.
Reopen the Alternate Rule Freeze When Its Basis Changes
Do not schedule a full review merely because time passed. Reopen the affected scope when an identified condition changes or when the team discovers that the original evidence was incomplete. The trigger should point to the rule field that may no longer be valid.
Common triggers include a new BOM or PCB revision, a changed reference-designator use, a product variant, a supplier PCN or EOL notice, a different manufacturer or source route, expired qualification evidence, changed firmware dependence, revised test coverage, a new customer restriction, an applicable regulatory or restricted-substance requirement, a changed approval owner, or discovery that prior material falls outside the recorded traceability boundary.
Treat external requirements by scope. NASA standards can impose strict parts and substitution controls on covered high-assurance work. FDA’s Quality Management System Regulation applies to finished medical-device manufacturers within its scope and includes documented change and supplier controls. EU RoHS applies to covered electrical and electronic equipment and restricted substances. These sources show why product context can change a rule; they do not create one universal approval method for every PCBA.
Bound the reopened scope and interim state
Reopen only the affected portion when the evidence supports a bounded change. A PCN for one manufacturer part number does not automatically invalidate unrelated rules. A new product variant may share some rules but require a separate decision for safety-related, RF, firmware-dependent or mechanically constrained parts. Record the impact assessment that sets the boundary.
Reopen trigger
Question to answer
Evidence to retrieve
Interim state
BOM or product revision
Does the rule still match the design use?
revision delta, affected lines and engineering response
hold affected use
PCN or EOL notice
Which product, lot, timing or characteristic changed?
manufacturer notice and current project impact review
review source and candidate
New source route
Does permitted traceability and condition still apply?
source identity, lot records and buyer requirement
segregate or hold purchase
Compliance-scope change
Does the existing evidence cover the new market or product?
applicable requirement and current declarations/test evidence
hold affected release
Expired or missing evidence
Can the original decision still be supported?
qualification, validation or approval record
reopen decision
Authority or contract change
Who can now accept the risk and commercial condition?
current authority matrix and contract-reviewed term
hold approval
Repeat order after change
Did material, files, process or acceptance basis change?
rule readback against the repeat-order package
re-freeze or clarify
Assign freeze and reopen authority by decision type
Assign alternate rule freeze and reopen authority by decision type so purchasing, engineering, quality, and the buyer cannot silently substitute for one another.
The person coordinating the request does not automatically own every decision. Engineering may assess electrical, mechanical, thermal or firmware effects. Quality may determine required evidence, traceability and exception controls. Sourcing may verify the commercial source condition and material exposure. Regulatory or product-compliance owners may decide whether the proposed scope needs additional evidence. Commercial owners approve price, liability and schedule terms. The OEM should name who has final authority to freeze or reopen the rule.
Avoid a workflow in which every reviewer can change the rule directly. Collect their findings against controlled fields, resolve disagreements and issue one authorized version. If authority is split by component class or product, record that division. A general sourcing rule should not silently overrule a design restriction, and a technical acceptance should not authorize a commercial commitment.
For urgent shortages, define the escalation route before an event occurs. State who may approve a bounded deviation, the maximum quantity or period, required verification, disposition of unused material and the event that ends the deviation. Urgency can shorten the response time; it does not supply missing evidence or authority.
Read Back the Alternate Rule Freeze at Each Gate
A gate readback confirms that the action, rule and product state agree. Start with the intended action: compare a quote, reserve material, place a purchase order, issue material, build an engineering lot, release production or repeat an order. Then retrieve the active rule from the controlled index rather than from an old email attachment.
Check five links. First, the rule identity and version match the current project package. Second, its scope includes the product, BOM lines and action. Third, every candidate used by the action has the required status and evidence. Fourth, the effectivity boundary includes the material and build. Fifth, the named authority has approved the state or bounded exception. If one link is missing, classify the result as clarification, conditional permission or hold.
For a repeat order, do not accept “same as last time” without a delta check. Compare the current and prior BOM, rule version, source, PCN/EOL state, open deviations, firmware and test inputs, applicable product scope and material still on hand. A no-change result can be short, but it must name what was compared and who accepted the readback.
Record the gate outcome and next action
When the decision basis changes, reopen the affected rule scope and review the resulting engineering action before release. Close the gate with a concise record: action requested, active rule, product and BOM revision, affected items, candidate status, evidence references, permitted scope, effectivity, open conditions, decision owner and timestamp. Retain superseded versions so the team can explain an earlier build without allowing the old rule to re-enter the active package.
The result should be one of four states. Freeze when the rule is complete for the action. Freeze conditionally when a named, bounded action may proceed while specified evidence remains due. Reopen when the decision basis changed. Hold when the team cannot establish scope, evidence, authority or effectivity. These states give procurement and production an instruction they can apply without guessing.
FAQ
When should PCBA alternate rules first be frozen?
Freeze them before suppliers prepare comparable quotations or before any commercial or production action relies on alternate sourcing. Reconfirm the rule before material commitment, first-build release and a repeat order when the baseline may have changed.
Does a frozen rule approve a proposed component?
No. The rule defines which candidate path, evidence, authority and effectivity are required. The proposed manufacturer part number still needs its own technical, quality, sourcing and project-specific approval record.
What events require an alternate rule to reopen?
Reopen the affected scope after a relevant BOM or product revision, PCN/EOL event, source-route change, expired evidence, new compliance scope, changed authority, failed condition or discovery that the prior decision basis was incomplete.
Can one alternate rule cover every BOM line?
Only if the OEM’s evidence and authorized process support that scope. Many products need narrower treatment for safety-related, firmware-dependent, RF, mechanical, thermal or customer-restricted parts. Record exclusions instead of assuming broad coverage.
Prepare the rule package for a bounded review
Collect the active BOM and revision, proposed rule ID and version, affected and excluded lines, permitted source conditions, required evidence, current candidates, approval owners, effectivity point, expiry and reopen triggers. Include the next intended action so the reviewer can distinguish quote comparison, material commitment and production release.
Send that bounded package through the plain contact page if you want to discuss the rule structure for a specific PCBA project. Confirm the receiving and contracting entity, technical scope, commercial terms, applicable requirements and final approval authority before relying on any response. A review response remains project information to verify; it is not an automatic alternate approval or supply commitment.
Supplier-specific product-change notices, such as the TI policy and Microchip notices , can reopen an alternate rule freeze when the affected part is in scope. Contract, regulatory, environmental, or customer requirements should be added only after the project confirms their current applicability.
