Release control and records: To be truly useful and auditable, should released drawings be stored electronically in a way that preserves a static, time-stamped snapshot of the design at the moment of release (i.e., a controlled baseline)?

Introduction / Context:
Drawings evolve across iterations, but organizations must know exactly what configuration was approved and shipped. A released drawing should be preserved as a static snapshot to ensure traceability, regulatory compliance, and clean handoffs to manufacturing, suppliers, and service. This question tests understanding of baselining and records management for technical drawings.

Given Data / Assumptions:

• Designs transition from work-in-progress to released state.
• Auditors, suppliers, and internal teams rely on the exact released definition.
• Electronic storage (PLM/EDM) can lock, version, and time-stamp records.

Concept / Approach:
“Static snapshot” means the released artifact cannot silently change; changes require formal revisions via ECO/ECR processes. Controlled repositories preserve metadata (author, approvers, dates), ensure check-in/out discipline, and enable retrieval of the correct version for production, service, or legal defense. This is essential even when paper copies exist, because electronic control prevents divergence and loss and supports enterprise-wide access.

Step-by-Step Solution:

Verification / Alternative check:
Traceability tests and audits require retrieval of the exact released file and its approvals. Systems that retain immutable snapshots consistently pass such checks.

Why Other Options Are Wrong:
Limiting this to safety-critical products or customer requests ignores internal quality and liability needs; paper binders without electronic control risk inconsistency and loss.

Common Pitfalls:
Letting editable files masquerade as released; poor metadata; uncontrolled local copies; bypassing change processes.

Final Answer:
Correct