A steel structure repaired component archive broken link checklist helps EPC teams find records that appear to be archived but cannot actually be opened. Broken links are common after project folders move, personal accounts are closed, temporary review links expire, or final handover indexes are edited without retesting the linked files.
For repaired steel structure components, a broken link is more than a document inconvenience. It can hide repair evidence, NCR closeout files, owner acceptance records, transferred item closure, inspection photos, or final limitations needed during site work, maintenance, warranty review, or owner audit.
1. Identify where broken links can exist
Broken links should be checked across every record that points to final repaired component evidence. The archive index is the obvious starting point, but it is not the only location. Old transmittals, comment logs, review registers, and acceptance forms may also include links that users rely on after handover.
- Check archive index links for repaired component marks, repair numbers, NCR numbers, and final acceptance records.
- Check links in transmittals, email references, comment logs, owner response trackers, and issue registers.
- Check links inside migrated folders that still point back to source workspaces.
- Check photo packages, inspection folders, and final release records for embedded file links.
- Check whether old links are still being used as the only route to a final record.
For source mapping before repair, use the repaired component archive index checklist.
2. Classify the broken link type
Not every broken link has the same cause. Classifying the failure helps the team choose the right correction and avoid creating a second broken route.
| Broken link type | Likely cause |
|---|---|
| File not found | File was moved, renamed, deleted, or not copied during archive migration. |
| Access denied | Permission changed, user group expired, or restricted file moved into a new system. |
| Expired link | Temporary review link reached its expiry date and no final route was recorded. |
| Wrong file opens | Link was updated to a folder or revision that does not match the repaired component record. |
| Personal account link | Link depended on a user account that was removed after project closeout. |
For expiry-related problems, use the archive link expiry checklist.
3. Verify the correct replacement record
A broken link should not be replaced with the first similar file found in the archive. The replacement must be the correct final record for the repaired component, with the same mark, repair reference, revision status, acceptance status, and document purpose.
- Match component mark, repair number, NCR number, inspection number, and final acceptance record.
- Confirm the replacement file is the accepted final version, not a draft or superseded review copy.
- Confirm linked evidence supports the same repair scope and not a different repaired item.
- Confirm transferred item records remain connected to the original repaired component archive.
- Confirm restricted files stay under approved technical or quality access rules.
For traceability checks, use the repaired component audit trail checklist.
4. Fix archive index and historical references
Fixing only the current archive index may not be enough. If historical transmittals or acceptance trackers still point to broken links, future users may continue to open the wrong route. A complete fix should identify the broken reference, replace it where controlled, and record where the old route now points.
- Update the final archive index with the verified replacement link.
- Update handover trackers, acceptance records, and current retrieval guides where controlled edits are allowed.
- Record old links that cannot be edited because they are historical transmittal evidence.
- Add a replacement note or migration log that explains where the record moved.
- Keep the broken link correction record with the final repaired component archive.
For controlled replacement history, use the archive link migration checklist.
5. Retest access after correction
After broken links are corrected, the team should retest access using the roles that will actually use the archive. A document controller may be able to open the replacement link while the owner, site, or quality user still cannot.
| User role | Retest result required |
|---|---|
| Owner handover user | Can open final repaired component package through the archive index. |
| Quality user | Can open inspection evidence, NCR closeout, and final release records. |
| Site user | Can retrieve limitations, repair notes, and transferred item status needed for site work. |
| Engineering reviewer | Can access restricted technical records through the approved route only. |
For role checks, use the archive permission review checklist.
6. Record broken link corrections
Every broken link correction should leave a small audit trail. Without a record, the team cannot prove whether a missing file was restored, replaced, removed as a duplicate, or intentionally restricted.
- Record broken link, failure type, affected record, component mark, and repair reference.
- Record replacement link, replacement file name, revision status, and archive location.
- Record correction owner, approval owner, correction date, and retest date.
- Record whether old links were disabled, redirected, or kept for historical evidence only.
- Attach retest evidence showing that the corrected link opens for the required role.
For issue history, use the transmittal record checklist.
7. Prevent broken links in future closeout work
The best broken link correction is preventing the same failure from recurring. After repairs are closed, the team should define a stable link rule for final archives and avoid relying on temporary review folders, personal accounts, or uncontrolled public links.
- Use final archive links only after migration and retrieval testing are complete.
- Avoid personal-drive links in final handover records.
- Test archive index links after folder moves, account closures, and permission changes.
- Separate temporary review links from final archive links.
- Schedule a post-handover link check for high-risk repair records.
For broader retrieval controls, use the archive retrieval checklist.
Final archive broken link checklist
Before accepting broken link corrections, confirm:
- Archive index, transmittals, comment logs, acceptance records, and migrated folders have been checked.
- Each broken link is classified as missing file, access denied, expired link, wrong file, or personal account link.
- Replacement records match the correct component mark, repair reference, revision, and final status.
- Current archive indexes and controlled handover trackers are updated.
- Historical links that cannot be edited have a replacement note or migration record.
- Access is retested for owner, quality, site, and engineering roles.
- The correction record is stored with the final repaired component archive.
Red flags in broken link correction
- A replacement link opens a folder instead of the exact final record.
- The corrected link opens a draft, superseded file, or unrelated repaired component record.
- Only document control can open the corrected link; owner or site users still cannot retrieve the file.
- Old transmittals still point to dead links with no replacement note.
- Broken links are corrected without recording who approved the replacement.
- Personal account links remain in the final handover archive.
Buyer note: Broken link review should be part of final archive acceptance. EPC buyers should require source checking, failure classification, verified replacement records, permission retesting, and a correction log before accepting repaired component archives as complete.