Steel structure repair archive superseded copy checklist

A steel structure repaired component archive superseded copy checklist helps EPC teams prevent older repair evidence from being used after a corrected or replacement record is issued. A superseded copy may still be kept for history, but it should not be treated as the current acceptance record.

This topic appears after a repair report is corrected, an owner handover copy is replaced, a concession wording is revised, or a final archive index is updated. The goal is to keep the record trail visible while guiding users toward the current repaired-component archive master.

1. Define what superseded means

Superseded should have one project meaning. Without a clear definition, site teams may delete useful history or continue using old records as if they are still current.

• A superseded copy is no longer the current record for acceptance decisions.
• The replacing record should be named, dated, and linked.
• The superseded copy may remain in archive history if the project requires traceability.
• Users should verify the current record before relying on the old copy.
• The status should be visible in the file name, cover note, index, or watermark.

For copy status before superseding, compare the archive controlled copy checklist and the owner controlled copy checklist.

2. Identify why the copy was superseded

Every superseded status should have a reason. This helps future reviewers understand whether the change was clerical, technical, contractual, or owner-driven.

3. Mark the old copy visibly

A superseded copy should be obvious even if the file is downloaded, printed, or moved out of its original folder.

• Add "superseded" to the file name where project naming rules allow it.
• Add a cover note naming the current replacement record.
• Add a watermark or first-page note when the document format allows it.
• Update the archive index so searches show old and current status.
• Record the superseded date and approving person.

For index updates, use the archive index checklist.

4. Link the current replacement record

The most important control is the link from old to current record. A superseded label is incomplete if users cannot find the replacement.

• Record the current file name, revision, package number, and issue date.
• Link old and new records in the archive index.
• Update owner handover registers when the owner copy is replaced.
• Update shared links that still point to the old file.
• Keep the replacement record easy to find from the related component mark.

For broken or outdated links, use the archive broken link checklist.

5. Control old copies in owner and site folders

Superseded copies often remain in owner folders, site folders, meeting packs, or downloaded records. These locations should be checked after a replacement is issued.

• Check owner handover folders for older repair evidence packages.
• Check site closeout folders and commissioning packages.
• Check shared links previously sent to owner, consultant, inspector, or contractor teams.
• Check local copies attached to issue logs or NCR closeout files.
• Record whether each old copy was replaced, marked, restricted, or retained for history.

For owner packages, use the owner handover folder checklist.

6. Decide whether to retain or remove the old copy

Not every superseded copy should be deleted. Some must remain to prove what was issued at the time, while others should be removed to prevent confusion.

• Retain old copies when they support audit trail, dispute history, or revision traceability.
• Remove old copies from user-facing folders when they are likely to be mistaken for current evidence.
• Restrict old copies if they contain sensitive comments or rejected wording.
• Keep one controlled historical copy rather than many uncontrolled duplicates.
• Record the retention decision in the archive closeout notes.

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

7. Review superseded records before closeout

Before final archive closeout, review all superseded repair records to confirm users can identify the current file and understand why the older copy remains.

• Confirm every superseded copy has a replacement reference.
• Confirm old owner copies are replaced or clearly marked.
• Confirm old links are removed, redirected, or labeled.
• Confirm the archive index shows current, superseded, and retained-history status.
• Confirm no superseded record is still used for final acceptance decisions.

For final review, use the final archive closeout checklist.

Superseded copy checklist

Before accepting superseded copy control, confirm:

• The meaning of superseded copy is defined for the project.
• The reason for superseding is recorded.
• The old copy is visibly marked in file name, cover note, watermark, or index.
• The current replacement record is clearly linked.
• Owner, site, and shared-link locations have been checked.
• Retention, removal, or restriction decisions are documented.
• Closeout review confirms superseded copies are not used as current acceptance records.

Red flags in superseded copy control

• An old repair report remains in the owner folder without a superseded label.
• The current replacement record is not linked from the old file or index.
• Old shared links still point to superseded repair evidence.
• Superseded records are deleted without audit-trail approval.
• Site teams continue using an older inspection package after reissue.
• No closeout check confirms that current records replaced old owner copies.

Buyer note: Superseded copies are useful for history but risky when they look current. EPC buyers should require visible status, replacement links, owner-folder checks, shared-link review, retention decisions, and closeout confirmation before accepting superseded repaired steel structure records.