Keep the reason, approval, implemented configuration and verification evidence connected.
Identify request, requester and current configuration. Describe the problem separately from the proposed change; attach references.
List affected components, documents, batches, spare parts and teams. Record impacts awaiting review, including interfaces, inspection and training.
Document the decision, authority and conditions before implementation. A registered request is not an approval.
Record what was implemented, by whom, when and at which revision or batch it becomes effective. Preserve links to previous versions and withdrawn documents.
Verify against previously agreed criteria. Record results, evidence, open items and follow-up before closing the change.
Fictional example
FICTIONAL: EC-DEMO-11 requests connection identification changes from revision B to C. Drawing, inventory and workstation copy need updating. The proposal is approved, but verification of installed labels is pending; the change stays open.
Fill in the fields in your browser. “Save completed copy” downloads an HTML file with your entries: reopen it to keep editing. “Print / PDF” lets you print or save your entries as a PDF through the print dialog. There is no autosave; save again after each change and before closing. No data is sent to VYRCO.
Use
Free for professional use and personal or internal adaptation. Retain VYRCO attribution and label changes. Do not resell or redistribute a modified version as an original VYRCO resource.
Sources
NASA · Configuration Management · Principles for identifying, reviewing and verifying changes. VYRCO formats are original, not NASA forms.