Freeze one design baseline after concept selection
The verified catalogue identifies the Detachable Rack Flight Case, its owner page and its supporting rack-case site. It does not define the ordered separation layout, dimensions, materials, fit, mechanism or performance. After a concept has been selected, create a buyer-controlled baseline that names the applicable drawing revision, requirement IDs, equipment configuration, accessories, intended states, open assumptions and evidence still due. Treat every unverified technical or commercial item as open rather than completing it from the product name.
Give the baseline an effective date and identify who may request, assess and authorize a change. Separate buyer requirements, supplier proposals and accepted evidence in the register. A marked drawing or meeting note is not a release by itself: the controlled package must show which revision supersedes which, why the change is proposed and which order lines or deliverables it affects. This prevents parallel copies from becoming competing instructions during detailed design.
Make every proposed change declare its impact
Require a change notice before the supplier alters a baseline item. The notice should cite the affected requirement and drawing IDs, describe the before-and-after states, give the reason, identify dependent interfaces and list the evidence proposed for review. It should also state whether equipment data, buyer actions, quotation scope or the planned first-article check changes. If an impact is unknown, record it as unknown; silence is not evidence of no impact.
Review the notice across purchasing, equipment ownership, operations and service roles that own the affected requirements. Classify each linked item as unchanged with evidence, changed and requiring verification, or unresolved. Keep dimensions, materials, load assumptions, protection results, conformity, price, warranty and timing outside the approved baseline until order-specific evidence confirms them. Approval of one drawing detail must not be interpreted as approval of unrelated performance or commercial terms.
Hypothetical worked record — not a fact about this product: baseline BR-01 cites drawing D-01 Rev A and order line 20, where fictitious interface item I-07 is assigned to a removable rack section RS-1. Change notice CH-04 proposes moving I-07 to fixed section FS-1 in Rev B. The impact record reopens separation and reassembly access, the buyer-defined connection sequence and custody of any removed item; actual reach, clearance and sequence remain unknown. The supplier owns the marked before-and-after drawing, the buyer equipment owner owns the access recheck, the named buyer technical authority owns the decision, and purchasing holds order line 20 and first-article build release until those checks have a recorded disposition.
Assign verification from the changed requirement
Build the verification response from the impact record rather than applying a generic test. For each changed requirement, name the document review, marked comparison, sample observation or buyer-defined workflow check that can answer it, plus the responsible party and acceptance evidence. Include dependent requirements when the change could alter access, custody, sequence or the selected configuration. A point that cannot be examined at the present stage remains a hold point for later evidence.
Preserve the original result and the new result when a change triggers re-evaluation. Record the revision, observation, exception and authorized disposition; do not overwrite the history with a clean final table. Evidence from another product, configuration or order may inform questions but does not automatically verify this one. Any claimed rating, durability, environmental protection or certification needs an applicable source and agreed method before it can close a requirement.
Release the first article against the reconciled package
Before authorizing first-article production, reconcile the current drawing, requirement matrix, accepted change notices, open-point log, quotation scope and verification plan. Every incorporated change should point to an authorized decision; every deferred item should have an owner and a later gate. Stop release if the supplier and buyer are working from different revisions or if an affected requirement has no disposition. The release confirms the document baseline only, not a finished product result.
Carry the frozen package into first-article inspection and later handover as the comparison source. Physical interfaces, reassembly and operational steps must still be witnessed separately against the built item; this change-control record does not replace that acceptance. When a later change is proposed, reopen only the affected requirements and dependencies while retaining the earlier decisions. The result is a traceable path from selected concept to build release without inventing product specifications.