
12 Oct Document Resubmission
A capsule house supplier document resubmission register connects every revised file with the previous issue, review comments, supplier response, changed content and current approval status. It prevents a newer date from being mistaken for a complete or accepted response.
Resubmission does not equal approval or contractual acceptance. The approved document-control procedure and named technical and commercial authorities determine status.
Reference the Previous Issue
Record the document number, title, discipline, previous revision, review return date and current revision. Preserve the prior file and comments in the controlled system rather than replacing them.
Control the Resubmission
| Field | Record | Review question |
|---|---|---|
| Identity | Document number, title and revision | Is the file uniquely identifiable? |
| Comments | Previous comment references | Is every open comment addressed? |
| Response | Supplier explanation and changed location | Can the reviewer trace the change? |
| Files | Current attachments and superseded issue | Are obsolete files controlled? |
| Status | Received, under review, returned or approved | Is authority recorded? |
Highlight Changes Beyond Comments
If the revision includes additional changes, identify them separately. Do not hide an unrequested departure inside a comment response; route deviations or baseline changes through the approved process.
Close the Review Trail
Record the reviewer, decision date and final status. Distribute only the authorized revision and preserve the complete review history for handover.
Use the supplier submittal register for initial tracking and the clarification register for questions. To discuss supplier records, contact Rovellc.
