A steel structure repaired component archive link retest checklist helps EPC teams prove that final repair records are still retrievable after the archive environment changes. A link can work during closeout review and fail later after a folder is moved, a permission group changes, a temporary link expires, or a project account is closed.
This checklist is different from a broken-link repair checklist. The purpose here is to schedule and document retesting before users discover failures during site work, warranty review, maintenance, or owner audit. It is a prevention control for repaired component archives.
1. Define when retesting is required
Link retesting should be triggered by specific archive events. If the team waits for a user complaint, the archive may already be unreliable. The retest rule should be part of the document control closeout process.
- Retest after archive folders are migrated to a new project or owner storage location.
- Retest after temporary review links expire or are disabled.
- Retest after user groups, permission roles, or owner handover accounts are changed.
- Retest after project accounts or contractor workspaces are closed.
- Retest after archive indexes, transmittal links, or final handover trackers are edited.
For migration-specific controls, use the archive link migration checklist.
2. Select the links to retest
Not every historical link needs the same level of retesting. Focus first on links that support final acceptance, repair evidence, restricted technical decisions, transferred item closeout, and owner maintenance records.
| Link group | Retest priority |
|---|---|
| Final repair package links | Highest priority because they prove accepted repair status. |
| NCR closeout links | High priority because they support quality closure and audit evidence. |
| Owner acceptance links | High priority because they are used after project handover. |
| Restricted engineering links | High priority but tested only by approved technical roles. |
| Old review links | Retest only to confirm they are expired, disabled, or replaced as planned. |
For source link coverage, use the archive index checklist.
3. Retest using real user roles
A link should be tested by the role that will use it after handover. Testing only with an administrator account can hide permission failures. Retesting should include at least owner, quality, site, and restricted technical roles when those roles exist in the project.
- Owner user can open final accepted repair records from the handover archive.
- Quality user can retrieve inspection evidence, NCR closeout, and release records.
- Site user can retrieve repair notes, limitations, and transferred item status.
- Engineering reviewer can access restricted dispositions through the approved route.
- Expired external users cannot open old temporary review links or restricted records.
For role-based checks, use the archive permission review checklist.
4. Verify the correct record opens
A link retest should confirm more than whether the browser opens a page. It must confirm the opened file is the correct repaired component record. A link that opens the wrong revision or a similar component package still creates archive risk.
- Component mark matches the archive index and repair record.
- Repair number, NCR number, inspection record, and acceptance status match the final package.
- File revision is final or clearly marked as historical where appropriate.
- Transferred item closeout remains connected to the repaired component package.
- Restricted technical records open only under the approved access route.
For evidence relationships, use the repaired component audit trail checklist.
5. Record failed retest results
When a link fails retesting, the result should be recorded before correction. The failure type helps show whether the issue was broken routing, missing permission, expired link, wrong revision, or a migration mismatch.
| Retest failure | Record before fixing |
|---|---|
| Link does not open | Record URL, source document, component reference, error message, and user role. |
| Access denied | Record expected access role, actual role tested, and permission owner. |
| Wrong record opens | Record incorrect file details and the expected component or repair reference. |
| Expired link works unexpectedly | Record why old review access remains active and who approved the extension. |
For correction controls, use the archive broken link checklist.
6. Retest after correction
A corrected link should be retested again with the same user role that found the failure. If a document controller fixes the link but does not retest the owner handover role, the archive may still fail for its intended user.
- Retest the replacement link after the correction is made.
- Retest with the same role that reported or discovered the failure.
- Retest related links in the same repaired component package.
- Confirm old broken links are disabled, redirected, or recorded as historical references.
- Attach the retest evidence to the correction record.
For replacement route control, use the archive link migration checklist.
7. Keep a retest register
The retest register does not need to be complex, but it should prove that link reliability was checked after the archive changed. This record helps owners and EPC teams understand which links were tested, who tested them, and what corrective action was required.
- Record tested link, source document, linked record, component mark, and repair reference.
- Record trigger event, such as migration, expiry, permission change, or account closure.
- Record tested role, tester, test date, result, and evidence reference.
- Record corrective action, retest result, and approval owner for failed tests.
- Store the retest register with the final repaired component archive.
For issue history records, use the transmittal record checklist.
Final archive link retest checklist
Before accepting the retest result, confirm:
- Retesting was triggered by migration, expiry, permission change, account closure, or handover update.
- High-priority final repair links and owner acceptance links were included.
- Testing used real owner, quality, site, engineering, or expired-user roles as appropriate.
- Each opened link was checked for correct component mark, repair reference, revision, and final status.
- Failed retests were recorded before correction and retested after correction.
- Old review links were confirmed expired, disabled, or replaced according to the closeout rule.
- The retest register is stored with the final repaired component archive.
Red flags in link retesting
- Only administrator access is tested, not owner or site access.
- The team records a link as working because a folder opens, but no one checks the specific file.
- Temporary review links still open after their planned expiry date.
- Corrected links are not retested with the role that found the failure.
- Archive indexes are updated after migration, but no post-migration test evidence exists.
- Retest results are stored separately from the repaired component archive.
Buyer note: Retesting turns archive links from assumptions into evidence. EPC buyers should require retesting after migration, expiry, permission change, and handover updates before accepting repaired component archive links as reliable final records.