Steel structure repair archive markup copy checklist

A steel structure repaired component archive markup copy checklist helps EPC teams control repair record files that contain annotations, redlines, highlighted items, handwritten notes, PDF markups, or drawing callouts. These copies can be useful for review, but they are not clean final evidence until the markup is resolved or intentionally retained.

The main risk is that a marked-up file is stored beside the final issued repair package and later used as if it were the approved record. Markup copies should have a defined purpose, owner, cleanup action, and archive status before the repaired component file package is accepted.

1. Identify the markup source

The archive should show who added the markup and why. This helps the project decide whether the note is a required correction, a review question, or only a temporary working mark.

• Record whether the markup came from engineering, quality, site, document control, owner, or consultant review.
• Identify the file type: repair report, sketch, photo sheet, NCR response, drawing extract, inspection record, or handover package.
• State whether the markup is open, answered, transferred, rejected, or already incorporated.
• Keep marked-up copies separate from clean issued records.
• Record the current clean file if one already exists.

For comment tracking, use the archive comment copy checklist.

2. Classify markup meaning

Not every markup has the same weight. Some markups require technical revision; others are internal navigation marks that should be removed before issue.

3. Transfer valid markup into the response trail

A markup copy should not be the only place where a repair decision is recorded. Valid comments, corrections, and decisions should be transferred into a response log, revised record, or approval note.

• Move each valid markup item into a comment response log or action list.
• Assign an owner and due date to unresolved markup items.
• Link the markup item to revised repair evidence when it changes the final record.
• Record rejected or not-applicable markups with a short reason.
• Confirm the response trail is accessible from the final archive index.

For response traceability, use the repair audit trail checklist.

4. Restrict marked-up working files

Markup copies may reveal internal review notes, rejected repair options, incomplete evidence, or unapproved wording. Access should be narrower than the access used for clean final records.

• Limit markup-copy access to reviewers, response owners, and document control.
• Remove public or anyone-with-link sharing from markup folders.
• Restrict copies that include internal notes or claim-sensitive remarks.
• Keep markup copies out of owner final handover folders unless expressly agreed.
• Retest access after the clean file is issued.

For sensitive copies, use the archive restricted copy checklist.

5. Produce the clean final file

Before a repaired-component archive is accepted, the final record should be clean unless retained markup is intentionally part of the evidence trail. Most owner and site handover files should not contain unresolved annotations.

• Remove temporary highlights, comments, sticky notes, and handwritten review marks from the final file.
• Incorporate approved corrections into the clean repair record.
• Confirm photo sheets, inspection records, and drawing extracts match the approved response trail.
• Check the final revision, issue date, and package reference after cleanup.
• Update the archive index to point to the clean file.

For clean final folders, use the final record folder checklist.

6. Decide whether to retain the markup copy

Some markup copies are useful evidence because they show how a repair record was reviewed and corrected. Others should be deleted or superseded to reduce confusion.

• Retain markup copies that explain major repair decisions.
• Restrict retained markup copies that include internal comments.
• Supersede markup copies when the clean final file replaces them.
• Delete duplicate markup copies that add no audit value.
• Record retention or deletion approval by the archive owner.

For replaced non-current files, use the archive superseded copy checklist.

7. Close the markup-copy action

Markup-copy closeout is ready only when the archive can prove that the marked file is not being used as the active final repair record.

• Confirm all valid markup items were transferred, answered, or rejected.
• Confirm the clean final file exists and is linked from the archive index.
• Confirm unresolved markups are not present in owner-facing records.
• Confirm access to retained markup copies is restricted where needed.
• Confirm superseded, deleted, or retained status is recorded.

For final archive closure, use the final archive closeout checklist.

Markup copy checklist

Before accepting or closing a repaired-component archive markup copy, confirm:

• The markup source, type, date, file scope, and owner are documented.
• Each valid markup item is transferred to a response trail or revised record.
• Temporary notes and unresolved annotations are removed from the clean final file.
• Marked-up working files are kept outside final owner and site folders.
• Access to internal or sensitive markup copies is restricted.
• The clean issued record is linked from the archive index.
• The markup copy is retained, restricted, superseded, or deleted intentionally.

Red flags in markup-copy control

• A marked-up repair report is used as the owner handover record.
• PDF comments remain unresolved in the final issue package.
• Markup items are not copied into a response log or action tracker.
• Old annotated files remain linked from the archive index.
• Internal notes are visible in owner-facing folders.
• The project cannot identify the clean final file that replaced the markup copy.

Buyer note: Markup copies can explain review decisions, but they should not replace clean final repair evidence. EPC buyers should require markup ownership, response transfer, clean-file issue, restricted access where needed, and archive index updates before accepting repaired steel structure archive packages.