Steel structure repaired component archive restricted copy checklist

A steel structure repaired component archive restricted copy checklist helps EPC teams manage repair evidence that should not be shared like normal closeout records. Restricted copies may contain internal engineering comments, claim discussion, concession review, dispute notes, owner-sensitive observations, or supplier corrective-action material.

The purpose is not to hide valid quality evidence. The purpose is to stop sensitive repair files from being downloaded, forwarded, indexed, or added to owner handover folders before the correct access level and final wording are agreed.

1. Define why the copy is restricted

Before a repaired-component archive copy is marked restricted, document the reason. A vague label creates confusion and may cause teams to over-restrict ordinary quality records.

• Identify whether the restriction is due to engineering review, claim material, concession discussion, owner comments, or internal corrective-action evidence.
• Confirm whether the final accepted repair evidence must still be available in a normal archive folder.
• Record whether the restricted copy is temporary, permanent, or waiting for legal or commercial review.
• List who can approve release, downgrade, or withdrawal of the restriction.
• Record the master archive record connected to the restricted copy.

For general copy status, compare this page with the archive controlled copy checklist and the archive temporary copy checklist.

2. Separate restricted files from normal closeout evidence

Restricted copies should not sit in the same folder as ordinary final repair records without clear labels. A mixed folder can expose sensitive comments and make owner handover review harder.

3. Assign access by role, not convenience

Restricted copy access should be based on project role. Convenience-based access is risky because shared folders often outlive the issue that created them.

• Give full access only to document control, quality lead, engineering lead, or approved project management users.
• Give view-only access where users need reference but not download rights.
• Exclude general site users unless the restricted copy is required for immediate repair control.
• Exclude owner-facing folders until the copy is approved for release or summarized in a clean final record.
• Review inherited access from parent folders before adding the restricted copy.

For inherited permissions, use the archive inherited sharing checklist.

4. Control downloads and forwarding

A restricted copy becomes hard to control after download. The project should decide whether users can download, print, forward, or attach the file to email.

• Disable download where the document system allows view-only restricted access.
• Add a restricted-copy label to the file name, cover note, or watermark.
• Record recipients when restricted copies must be issued outside the archive system.
• Do not allow restricted copies to be forwarded without approval.
• Replace shared links with controlled access when the review period ends.

For download decisions, use the owner download permission checklist.

5. Prepare a clean owner-facing record

Restricted copies should not prevent the owner from receiving necessary final repair evidence. Where possible, prepare a clean record that confirms accepted repair status without exposing internal comments or sensitive dispute material.

• Keep the final inspection, acceptance, and closeout evidence available in the owner handover path.
• Remove internal comment threads from owner-facing copies unless contract rules require them.
• Use approved wording for concession, deviation, or accepted repair summaries.
• Link the clean owner-facing record to the restricted source record for internal traceability.
• Record who approved the owner-facing version.

For owner handover, use the owner handover folder checklist.

6. Review restricted status before final archive closeout

Restricted status should not be permanent by default. Before final archive closeout, review whether each restricted copy should remain restricted, be released as a controlled copy, or be removed as a temporary file.

• Check whether the commercial, claim, concession, or engineering issue is still open.
• Check whether the owner-facing final record has already replaced the restricted copy.
• Check whether restricted links are still active outside the archive system.
• Check whether access logs show users who no longer need the copy.
• Record the final restricted-copy status in the archive index.

For closeout status, use the final archive closeout checklist.

7. Record restricted-copy exceptions

Some restricted copies remain necessary after closeout because of warranty, claim, insurance, or owner dispute requirements. These exceptions should have a documented owner and review date.

• Record why the copy remains restricted after final handover.
• Record who can approve future release or access expansion.
• Record the review date and retention requirement.
• Link the exception to the clean owner-facing record.
• Keep audit evidence for any external issue of the restricted copy.

For traceability, use the audit trail checklist.

Restricted copy checklist

Before accepting restricted copy handling, confirm:

• The restriction reason is documented and not used for ordinary final evidence.
• Restricted copies are separated from normal closeout and owner handover folders.
• Access is assigned by role and inherited folder access has been reviewed.
• Download, forwarding, and external issue rules are documented.
• A clean owner-facing record exists where final repair evidence must be shared.
• Restricted status is reviewed before final archive closeout.
• Long-term exceptions include owner, reason, retention rule, review date, and audit trail.

Red flags in restricted copy control

• Files are labeled restricted without a documented reason.
• Restricted repair records are stored in owner handover folders by default.
• Parent folder permissions expose restricted copies to broad project users.
• Downloaded restricted copies are emailed without a recipient log.
• No clean owner-facing version exists for final accepted repair evidence.
• Restricted status is never reviewed after the issue is closed.

Buyer note: Restricted copies should protect sensitive repair information without blocking the final quality record. EPC buyers should require a restriction reason, role-based access, download controls, clean owner-facing records, closeout review, and exception tracking before accepting restricted copies in a repaired steel structure archive.