A steel structure repaired component reviewer acceptance checklist helps EPC teams prove that the person or organization who raised a comment has accepted the response. A repaired component comment may be answered, but it is not fully closed until the reviewer acceptance is recorded or the project procedure allows another closure authority. This acceptance record protects release, final acceptance, and archive decisions.
This checklist is written for EPC quality managers, owner review coordinators, TPI coordinators, engineers, document controllers, site teams, and supplier quality teams. It applies to repaired steel columns, beams, braces, truss members, connection plates, roof framing, wall supports, and secondary members that have repair comments, inspection comments, owner comments, or closeout comments.
1. Identify the correct reviewer
Reviewer acceptance should come from the party with the right authority. A supplier reply cannot close an owner comment unless the project procedure allows it. A document controller cannot accept an engineering limitation unless the engineer or owner has approved the decision.
- Original reviewer name, organization, role, and comment number.
- Reviewer authority: owner, EPC quality, engineer, TPI, site manager, or document control.
- Whether acceptance can be delegated and who approved the delegation.
- Contract, ITP, NCR procedure, or document control requirement that defines acceptance authority.
- Reviewer contact route and response due date.
For unresolved reviewer issues, use the repaired component comment escalation checklist.
2. Confirm what the reviewer is accepting
The acceptance record should state what is being accepted. This avoids unclear approval of only part of the response while another issue remains open.
| Acceptance scope | What to confirm |
|---|---|
| Response wording | The reviewer accepts the explanation, correction, or rejection basis. |
| Evidence | Photos, inspection records, NDT, coating repair, or site confirmation are sufficient. |
| Revised document | The latest revision resolves the comment and supersedes earlier files. |
| Limitation | The reviewer accepts a concession, monitoring note, condition, or transferred action. |
| Final closure | The comment can move to closed status before acceptance, turnover, or archive. |
For response preparation, compare with the repaired component comment response checklist.
3. Capture acceptance evidence
Reviewer acceptance should be captured in a controlled format. Informal verbal acceptance is weak unless the project records it in the comment log, transmittal response, meeting minutes, or final acceptance package.
- Signed comment sheet, approved register status, or document control workflow status.
- Email acceptance with date, reviewer, document reference, and component mark.
- Owner or TPI approval stamp on the revised repair evidence package.
- Meeting minute that states the comment is accepted and identifies remaining limitations.
- Transmittal response showing accepted, accepted with comment, or accepted with limitation.
For formal issue history, use the repaired component transmittal record checklist.
4. Separate full acceptance from conditional acceptance
Conditional acceptance can be useful, but it must be visible. If a reviewer accepts the response with a limitation or transferred action, the final record must carry that condition.
| Reviewer decision | Required follow-up |
|---|---|
| Accepted | Close comment and update final acceptance or archive evidence. |
| Accepted with limitation | Record limitation, approving authority, affected component, and archive reference. |
| Accepted with transferred item | Move item to punch list, turnover, maintenance, or warranty tracker with owner. |
| Rejected | Reopen comment, revise response, escalate if needed, and reissue evidence. |
| No response | Keep item open or overdue until reviewer acceptance is received or formally escalated. |
For accepted limitations, use the repaired component final acceptance record checklist.
5. Update registers after acceptance
Reviewer acceptance should update the same records that were affected by the comment. Otherwise, the project may have an acceptance email while the open comments register still shows the item as unresolved.
- Comment log status, acceptance date, reviewer, and evidence reference.
- Open comments register, overdue comment status, and escalation log where applicable.
- NCR, quality hold, punch, turnover, and final acceptance records.
- Document control register and superseded file status.
- Archive index and final evidence package.
For final closure status, use the repaired component comment closure checklist.
6. Review acceptance before final release
Before repaired component release or final acceptance, the EPC team should verify that reviewer acceptance is complete for comments that affect safety, quality, owner approval, or archive completeness.
- All blocking comments have reviewer acceptance or approved transfer.
- Conditional acceptance is visible in final records.
- Revised evidence has been issued to the reviewer and accepted.
- Rejected or no-response comments are not treated as closed.
- The archive package includes acceptance evidence and the latest comment status.
For open item review, use the repaired component open comments register checklist.
7. Final reviewer acceptance checklist
Use this checklist before closing reviewer acceptance for a repaired component:
- The correct reviewer or approved delegate is identified.
- The acceptance scope is clear: response, evidence, revision, limitation, or final closure.
- Acceptance evidence is stored in a controlled record.
- Conditional acceptance and transferred items remain visible.
- Comment log, NCR, hold, release, acceptance, and archive records are updated.
- Final acceptance does not conflict with reviewer acceptance status.
Red flags in reviewer acceptance
- A comment is closed by the respondent, not by the reviewer or authorized closer.
- The reviewer accepts a response, but the revised document is not issued.
- Conditional acceptance is missing from final records.
- No-response comments are treated as accepted because the due date passed.
- Acceptance evidence exists in email but not in the archive package.
- The reviewer acceptance status conflicts with the open comments register.
Buyer note
Reviewer acceptance is the proof that a repaired component comment has been accepted by the right party. EPC buyers should require a clear acceptance record showing the reviewer, scope, evidence, conditions, and final status. This keeps repaired component release and archive decisions defensible.