Steel structure repaired component archive mixed audience folder checklist

A steel structure repaired component archive mixed audience folder checklist helps EPC teams avoid a common closeout problem: one archive folder contains records meant for different audiences. Owner handover users, quality reviewers, engineering reviewers, site teams, and internal project managers may all need some repaired component records, but not the same records.

When a mixed-audience folder uses one broad permission rule, restricted repair evidence can become visible to users who only need final handover files, or owner users may receive internal comments and draft notes that were never meant for final acceptance.

1. Identify mixed-audience folder signs

Start by reviewing folder contents, not only folder names. A folder called final archive may still contain draft comments, temporary review files, technical decisions, or unrelated repair packages.

• Check whether owner handover files and internal review notes sit in the same folder.
• Check whether repair photos, NCR closeout records, and engineering dispositions share one access rule.
• Check whether multiple repair cases with different owners are stored together.
• Check whether temporary reviewer files remain in the final archive path.
• Check whether folder naming hides mixed content, such as final, closeout, or handover.

For parent-level checks, use the archive parent folder permission checklist.

2. Classify records by audience

Before changing permissions, classify each record type by who actually needs it after closeout. This avoids both over-sharing and under-sharing.

For final record control, use the final acceptance record checklist.

3. Split folders before changing access

Changing one permission setting on a mixed-audience folder usually creates a new problem. If the folder is made broad, restricted records are exposed. If the folder is made narrow, owner users may lose access to final records. Split the folder by audience first.

• Create a final owner handover folder for accepted repair records only.
• Create a restricted engineering folder for dispositions and technical decisions.
• Create an internal review folder for draft comments and non-final notes.
• Create a site closeout folder only for records required during erection or handover.
• Keep obsolete or superseded records outside the active final archive route.

For migration planning, use the archive link migration checklist.

4. Rebuild access rules by folder purpose

After separating folder audiences, assign each folder a permission rule that matches its purpose. Avoid keeping the old broad project group simply because it was already there.

For access matrix review, use the archive access control checklist.

5. Retest after splitting mixed folders

Splitting a mixed-audience folder can break old links or change what users can retrieve. Test the actual access routes after folder changes, not only the folder permissions page.

• Test owner access to final accepted repair records.
• Test that owner users cannot open internal draft comments unless contract scope allows it.
• Test engineering reviewer access to restricted dispositions.
• Test quality access to photos, NCR closeout, and acceptance evidence.
• Test expired temporary reviewers and anonymous link access.
• Test old archive index links and transmittal links after file moves.

For access testing, use the archive access retest checklist.

6. Update archive indexes and closeout references

After folder separation, archive indexes must guide users to the correct new folder. If the index still points to the old mixed folder, users will keep requesting broad access or fail to retrieve the right record.

• Update final archive indexes with separate links for owner, quality, engineering, and site records.
• Update NCR closeout logs, repair registers, and owner acceptance references.
• Record retired mixed-audience folder paths and replacement routes.
• Check for broken links after moving files into separated folders.
• Record which files were excluded from final handover because they were internal or draft records.

For broken route checks, use the archive broken link checklist.

7. Record the mixed-audience correction

The correction record should prove why the folder was split, which records moved, which audiences now have access, and how retrieval was retested.

• Record old folder path, mixed record types, affected component marks, and repair references.
• Record new folder names, folder purposes, and approved access groups.
• Record files moved, files restricted, and files excluded from owner handover.
• Record archive index updates and broken link corrections.
• Attach retest evidence for owner, quality, engineering, site, and denied users.

For traceable closeout, use the repaired component audit trail checklist.

Final mixed-audience folder checklist

Before accepting a repaired component archive, confirm:

• Folders were checked for mixed owner, quality, engineering, site, and internal records.
• Records were classified by final audience before access was changed.
• Mixed folders were split into purpose-based archive folders where needed.
• Folder access rules match the approved access matrix.
• Old index links, transmittals, and registers were updated after folder separation.
• Owner, quality, engineering, site, expired-user, and anonymous access were retested.
• The correction, moved records, replacement links, and retest evidence were logged.

Red flags in mixed-audience folders

• Final owner handover files and internal comments are stored together.
• Engineering dispositions and general repair photos use one broad project group.
• Owner users can browse unrelated repair cases from the same folder.
• Old review files remain in the final accepted archive path.
• Folder separation was done, but archive indexes still point to the old mixed folder.
• No retest proves that restricted records are hidden while final records remain retrievable.

Buyer note: Mixed-audience folders should be corrected before archive acceptance. EPC buyers should require record classification, purpose-based folder separation, access retesting, and updated archive indexes.