A steel structure repaired component comment response checklist helps EPC quality teams close review comments without losing the repair decision trail. Comments may come from the owner, EPC quality reviewer, third-party inspector, engineer, site team, or document controller. Each comment should be logged, assigned, answered, supported with evidence, and linked to any revised repair record before the component is accepted or archived.
This checklist is written for EPC document controllers, quality managers, supplier coordinators, TPI coordinators, owner review teams, and site managers. It applies when repaired steel columns, beams, braces, connection plates, trusses, roof framing, or secondary members have comments on NCR closure, repair method, inspection evidence, release note, owner acceptance, or final archive package.
1. Register every comment
Comments should be controlled in a comment log, not scattered through email threads or marked PDF files only. A controlled log lets the EPC team prove what was raised, who owns the answer, and whether the response was accepted.
- Comment number, reviewer, organization, date received, and response due date.
- Component mark, drawing revision, package, location, and repair record reference.
- Source document: NCR, repair method, inspection report, release note, owner acceptance, or archive index.
- Comment type: clarification, missing evidence, rejected evidence, revised wording, limitation, or re-inspection request.
- Responsible party for answer: supplier, EPC quality, engineer, site team, owner coordinator, or document control.
For formal issue and response tracking, connect the log with the repaired component transmittal record checklist.
2. Classify the comment before answering
Not all comments need the same response. Some require only a document clarification. Others require new repair evidence, engineering decision, site re-inspection, or owner acceptance update. Classification prevents the team from giving a weak answer to a critical issue.
| Comment type | Typical response |
|---|---|
| Missing evidence | Attach missing photos, inspection report, NDT record, coating record, or release evidence. |
| Wrong component reference | Correct mark, location, drawing revision, package, or NCR number across all linked records. |
| Technical concern | Obtain engineering review, concession decision, revised method, or additional inspection. |
| Acceptance condition | Record limitation, monitoring item, owner acknowledgement, or transferred action. |
| Document control issue | Revise file name, revision, transmittal, distribution, obsolete file status, or archive path. |
For document control comments, use the repaired component document control checklist.
3. Prepare evidence-based responses
A good response should answer the comment directly and point to evidence. Avoid vague replies such as "noted" or "done" unless the evidence location and revised document are clear.
- Quote or summarize the original comment in controlled wording.
- State the corrective response, clarification, rejection, or accepted limitation.
- Reference the exact revised document, revision, page, table, photo, inspection record, or archive path.
- Explain if no revision is needed and why the original evidence remains valid.
- Identify follow-up actions, due dates, and owner if the comment cannot close immediately.
For supporting proof, compare the reply package with the steel structure repair evidence checklist.
4. Control revised documents
If a comment changes the repair record, the revised document should be issued under control. The comment response should state what changed and which earlier files are superseded.
| Revised item | Control point |
|---|---|
| Repair method | Show revised repair step, technical approval, and superseded method number. |
| Inspection evidence | Add missing record, new re-inspection result, or corrected acceptance reference. |
| Release note | Update release status, limitation, hold condition, or installation instruction. |
| Owner acceptance | Record accepted comment, remaining limitation, final decision, and signature status. |
| Archive index | Replace obsolete file path and confirm latest response is included in final archive. |
For distribution after revision, use the repaired component distribution list checklist.
5. Track comment status
The comment log should have a clear status for each line. If a comment is transferred or accepted with limitation, that decision should be visible in the final record and archive package.
- Open: response not prepared or evidence missing.
- Answered: response issued but not yet accepted by reviewer.
- Accepted: reviewer accepts the answer and no further action is needed.
- Accepted with limitation: final record must carry a limitation, monitoring note, or transferred item.
- Rejected or reopened: response was not accepted and revised action is required.
- Transferred: item moved to punch list, turnover, maintenance, or another controlled tracker.
For owner acceptance status, use the repaired component owner acceptance checklist.
6. Reissue the response package
After comments are answered, the response package should be issued to the right recipients. This avoids a situation where the answer exists but the owner, site team, or document controller does not have the latest status.
| Recipient | What they need |
|---|---|
| Reviewer who raised the comment | Comment response, revised evidence, and request for acceptance or further comment. |
| EPC quality | Updated NCR, hold, inspection, release, or owner acceptance status. |
| Site team | Changed release condition, limitation, installation note, or remaining hold. |
| Supplier | Required correction, revised evidence request, or final comment closure. |
| Document control | Latest revision, superseded files, response log, and archive inclusion requirement. |
7. Link closed comments to final acceptance
Before final acceptance, closed comments should be visible in the acceptance record or evidence index. If a comment created a limitation, that limitation should not disappear after closeout.
- Final comment status and accepted response date.
- Revised document number, revision, transmittal, and reviewer acceptance.
- Remaining limitation, monitoring item, or transferred punch item.
- Owner or engineer acknowledgement where required.
- Archive location for the response log and revised evidence package.
For final record closure, compare with the repaired component final acceptance record checklist.
8. Final comment response checklist
Use this short checklist before marking repaired component comments closed:
- Every comment is logged with reviewer, document reference, component mark, due date, and owner.
- The comment type is classified before the answer is prepared.
- Responses include evidence references, not only short acknowledgements.
- Revised documents are controlled, reissued, and linked to superseded files.
- Comment status is accepted, transferred, or accepted with limitation before final acceptance.
- The closed comment log is included in the final evidence index or archive package.
Red flags in comment responses
- A comment is marked closed, but the requested photo or inspection evidence is not attached.
- The answer says "revised" but no revised document number or revision date is listed.
- An owner limitation is accepted but missing from the final acceptance record.
- The site team receives a release note before comment rejection is resolved.
- The comment log is separate from the NCR, hold, or archive index and cannot be traced later.
- Multiple reviewers comment on the same repaired component, but no consolidated response register exists.
Buyer note
A repaired component comment response record is useful only when it closes the review loop. EPC buyers should require comments to be logged, answered with evidence, revised under document control, reissued to affected teams, accepted by the reviewer, and included in the final archive. This makes repaired steel structure closeout defensible without relying on scattered email replies.