A steel structure repaired component overdue comment checklist helps EPC teams control review comments that have passed their response or acceptance date. Overdue comments can delay release, hide missing evidence, or create conflict between the quality log and the final acceptance record. The checklist should separate low-risk document comments from overdue items that block repaired component use or owner acceptance.
This checklist is written for EPC quality managers, document controllers, site coordinators, supplier quality teams, TPI coordinators, and owner review coordinators. It applies when repaired steel columns, beams, braces, trusses, plates, connection parts, or secondary members have comments that remain open after the planned response date.
1. Confirm why the comment is overdue
Do not treat all overdue comments the same. Some are late because the supplier has not provided evidence. Others are waiting for owner acceptance, engineering review, or site access for re-inspection.
- Missing repair photo, inspection report, NDT record, coating repair record, or release evidence.
- Reviewer has not accepted the response or returned comments.
- Engineering decision, concession approval, or limitation wording is still pending.
- Site team cannot confirm installed condition or access for inspection.
- Document control has not issued the revised record, transmittal, or archive update.
For the full open-item log, use the repaired component open comments register checklist.
2. Decide if the overdue comment is blocking
An overdue comment should be marked as blocking only when it affects safety, release, owner acceptance, required evidence, or final archive completeness. This helps the team escalate real blockers without stopping the project for minor wording issues.
| Blocking level | Decision guide |
|---|---|
| Blocks repair acceptance | Required inspection, test, engineer approval, or repair evidence is missing. |
| Blocks site release | The component should not be shipped, stored for erection, installed, or handed over. |
| Blocks owner acceptance | Owner or TPI approval is required before final acceptance can proceed. |
| Blocks archive only | The physical repair is accepted, but the final evidence package is incomplete. |
| Non-blocking correction | Minor wording or reference correction that can close after acceptance if approved. |
For closure rules, compare with the repaired component comment closure checklist.
3. Assign escalation ownership
An overdue comment needs a named escalation owner. The owner should have authority to obtain the missing response, approve a transfer, or decide whether the comment blocks release.
- Supplier escalation for missing repair evidence or revised documents.
- EPC quality escalation for NCR closure, quality hold release, or acceptance criteria.
- Engineering escalation for technical comments, concessions, and accepted limitations.
- Owner or TPI escalation for approval delays or unresolved review comments.
- Site escalation for access, installed condition confirmation, or field evidence.
4. Update due dates with reason codes
If the due date changes, the register should show why. Repeated extensions without reason can hide a real closeout problem.
| Reason code | Use case |
|---|---|
| Evidence pending | Photos, inspection records, NDT, coating evidence, or site confirmation are not complete. |
| Reviewer pending | The response has been issued and the reviewer has not accepted or rejected it. |
| Revision pending | A document needs revision, transmittal, or withdrawal of an obsolete file. |
| Decision pending | Engineering, owner, or EPC management decision is needed before closure. |
| Transfer pending | The comment can move to another tracker, but the receiving owner has not accepted it. |
For formal reissue after a due-date change, use the repaired component transmittal record checklist.
5. Control conditional release risk
Sometimes the project asks to release a repaired component while a comment is still overdue. This should be controlled as a risk decision, not treated as normal closure.
- Confirm whether the overdue comment affects safety, function, installation, coating durability, or owner acceptance.
- Record who approved conditional release and what evidence supports the decision.
- State whether the component can be installed, stored only, held at site, or handed over with limitation.
- Carry the open item into the final acceptance or transferred item register if not closed.
- Prevent archive closure until the overdue comment is accepted, transferred, or reopened.
For release status controls, use the steel structure post repair release checklist.
6. Recover the closure path
The overdue comment should have a defined path back to closure. This path may require additional evidence, revised documents, reviewer approval, accepted limitation, or transfer to another tracker.
- Required action and responsible owner.
- Revised response due date and escalation date.
- Evidence or approval needed for closure.
- Whether closure requires reviewer acceptance or only document control update.
- Final status expected: accepted, accepted with limitation, transferred, rejected, or reopened.
For response preparation, use the repaired component comment response checklist.
7. Review overdue comments before final acceptance
No repaired component should reach final acceptance with unresolved overdue comments unless they are formally transferred or accepted with limitation. The final acceptance record should reflect the real status.
- No overdue comments remain marked as blocking final acceptance.
- Conditional releases have approval, limitation, and follow-up owner.
- Transferred overdue comments have receiving tracker number and due date.
- Archive package includes the latest overdue comment register and closure evidence.
- Final acceptance decision matches the comment register status.
For final record alignment, use the repaired component final acceptance record checklist.
8. Final overdue comment checklist
Use this short checklist before releasing or accepting a repaired component with overdue comments:
- The reason for each overdue comment is recorded.
- Blocking and non-blocking comments are separated.
- Every overdue comment has an escalation owner and revised target date.
- Conditional release decisions are documented with authority and limitation.
- Transferred overdue comments have accepted receiving trackers.
- The final acceptance record does not contradict overdue comment status.
Red flags in overdue comment control
- Overdue comments have no reason code or escalation owner.
- A comment blocks owner acceptance but is treated as a minor document correction.
- The component is released while missing inspection evidence is still overdue.
- Due dates are repeatedly extended without management review.
- Conditional release is approved by email but not included in final records.
- The archive package closes while overdue comments remain unresolved.
Buyer note
Overdue comments are warning signals in repaired steel structure closeout. EPC buyers should require every overdue comment to show reason, owner, revised due date, blocking level, and closure path. This keeps repair acceptance from moving ahead while important review issues are still unresolved.