Steel structure repair archive cancelled copy checklist

A steel structure repaired component archive cancelled copy checklist helps EPC teams control repair records that were prepared but not formally issued, accepted, or used as final evidence. Cancelled copies often appear during document preparation, draft handover, internal review, or planned reissue work.

The risk is that a cancelled draft, pre-issue package, or prepared-but-unused copy may later be mistaken for a withdrawn, superseded, or final accepted record. The archive should make clear that the copy was cancelled before formal use.

1. Define what cancelled means

Cancelled copy status should mean the file was stopped before it became a valid issued repair record. This makes it different from withdrawn, obsolete, or superseded records.

• A cancelled copy should not be used for acceptance, owner handover, site decision, or audit closeout.
• The cancellation reason should be recorded before the copy is removed or retained.
• The record should show whether it was never issued, never accepted, or replaced before issue.
• The file should be separated from active final evidence.
• Users should be directed to the current prepared, issued, or accepted record if one exists.

For files already issued and then stopped, use the archive withdrawn copy checklist.

2. Record why the copy was cancelled

The cancellation reason should make it clear whether the copy was stopped for document preparation reasons, technical reasons, or handover reasons.

3. Check whether the copy was distributed

Before closing a cancellation, confirm whether the copy stayed internal or was shared. If it was already sent outside the preparation group, it may need withdrawal instead of simple cancellation.

• Check whether the copy was sent by email or transmittal.
• Check whether the copy was placed in owner, consultant, or inspector folders.
• Check whether site teams downloaded or printed the copy.
• Check whether shared links were generated before cancellation.
• Escalate to withdrawn-copy control if recipients must be formally notified.

For recipient notice, use the withdrawn copy checklist.

4. Mark or remove the cancelled copy

Cancelled copies should not remain in active folders without clear status. The project should decide whether to delete them, retain them internally, or restrict them as preparation history.

• Remove cancelled copies from final repair record folders.
• Move retained cancelled copies to an internal history folder.
• Add cancelled status to the file name or archive index where retained.
• Block owner-facing access to cancelled preparation files.
• Record who approved deletion or retention.

For obsolete retained files, use the archive obsolete copy checklist.

5. Link to the current record if one exists

A cancelled copy may have no replacement, but when a corrected or accepted record exists, users should be pointed to it.

• Name the current file, package, revision, or transmittal.
• Update the archive index so cancelled copies do not appear as current evidence.
• Replace draft links with current record links.
• Check owner package references if the cancelled copy was prepared for handover.
• Record no-replacement status if the issue was cancelled completely.

For index updates, use the archive index checklist.

6. Control retention of cancelled drafts

Some cancelled drafts should be retained to explain the document-control trail. Others can be deleted to reduce confusion. The decision should be intentional.

• Retain cancelled drafts when they explain why a repair package changed.
• Delete drafts that have no audit value and were never issued.
• Restrict cancelled copies that contain internal comments or rejected wording.
• Separate cancelled preparation files from accepted final records.
• Record retention period and archive owner.

For sensitive cancelled files, use the archive restricted copy checklist.

7. Close the cancelled-copy action

A cancelled-copy action is ready to close only when the team confirms the copy was not relied on as a final repair record.

• Confirm the file was never formally issued or accepted.
• Confirm any accidental distribution was handled through withdrawal control.
• Confirm active folders no longer show the cancelled copy as current.
• Confirm the current record or no-replacement status is documented.
• Confirm the archive index and closeout notes show the cancellation decision.

For final closeout, use the final archive closeout checklist.

Cancelled copy checklist

Before closing a cancelled-copy action, confirm:

• The cancellation reason, scope, date, and approver are documented.
• The copy was not formally issued, accepted, or used for final evidence.
• Any accidental distribution was checked and escalated if needed.
• Cancelled copies are removed from active final, owner, and site folders.
• The current replacement record or no-replacement status is visible.
• Retention, deletion, or restriction decisions are approved.
• Closeout review confirms no cancelled copy is used as an accepted repair record.

Red flags in cancelled copy control

• A cancelled draft remains in the owner handover folder.
• The team cannot confirm whether the copy was issued.
• The cancellation reason is missing from the archive index.
• A cancelled package has active shared links.
• The accepted replacement record is not identified.
• Cancelled drafts are stored beside final accepted repair evidence.

Buyer note: Cancelled copies should not enter the final repair record trail by accident. EPC buyers should require cancellation reason, distribution check, active-folder removal, replacement status, retention decision, and closeout confirmation before accepting cancelled repaired steel structure archive records.