A steel structure site issue log template for EPC projects helps teams control many small site problems before they become installation delays. Missing parts, damaged members, wrong marks, bolt issues, drawing gaps, and replacement requests should not be scattered across emails, chat groups, and private photo folders.
This template is written for EPC site teams, project buyers, logistics coordinators, quality inspectors, and installation supervisors. It is intended as a practical tracking structure, not as a software product or formal legal claim format.
1. Use one log for all site steel issues
The log should capture all reportable delivery and site issues related to steel structure packages. Separate detailed reports can still exist, but the master log keeps status, responsibility, and due dates visible.
- Missing steel members, plates, bolts, accessories, labels, or documents.
- Damaged coating, galvanizing, packages, threads, or components.
- Wrong marks, wrong package references, or unclear bundle labels.
- Wrong bolt size, bolt shortage, hole mismatch, or tightening issue.
- Drawing, mark list, packing list, or certificate discrepancies.
- Replacement requests and site closeout actions.
For discrepancy classification, use the site discrepancy report checklist.
2. Recommended issue log fields
The issue log should be simple enough for site teams to update every day, but detailed enough for buyers and suppliers to act on. The fields below work for most EPC steel structure delivery and erection follow-up.
| Field | What to record |
|---|---|
| Issue ID | Unique number used in emails, photo folders, replacement requests, and closeout files. |
| Issue type | Missing part, damage, bolt issue, wrong mark, document gap, discrepancy, or replacement. |
| Reference | Package number, component mark, drawing number, bolt list, shipment batch, or area. |
| Description | Short, specific description of what is wrong and where it was found. |
| Impact | No impact, site sorting, quality hold, installation block, or engineering decision required. |
| Owner | Site team, buyer, supplier, logistics, quality, engineering, or installation supervisor. |
| Due date | Target date for clarification, replacement, repair, approval, or final closeout. |
| Status | Open, under review, waiting for supplier, replacement arranged, repaired, accepted, or closed. |
3. Add evidence links, not just comments
Issue logs become weak when they only include text comments. Each issue should connect to evidence folders, reports, drawings, and shipment records.
- Photo folder link or file path.
- Related missing parts report, damage report, bolt issue report, or discrepancy report.
- Packing list, mark list, drawing, bolt list, or certificate reference.
- Replacement request number if correction requires new parts.
- Approval email, inspection record, or closeout document reference.
For photo evidence structure, use the delivery photo checklist.
4. Define issue status clearly
Clear status values help the project team understand what is actually moving. Avoid vague status labels such as "noted" or "pending" unless the next action is also recorded.
| Status | Meaning |
|---|---|
| Open | Issue is reported but not yet assigned or reviewed. |
| Under review | Owner is checking evidence, drawings, package records, or site condition. |
| Waiting for supplier | Supplier clarification, repair instruction, document, or replacement plan is needed. |
| Replacement arranged | Replacement item is approved and shipment or local purchase is being tracked. |
| Repaired or corrected | Physical repair, label correction, sorting, or document correction is completed. |
| Closed | Evidence confirms the issue is accepted, corrected, or transferred to a controlled record. |
5. Track installation impact separately
Not every issue blocks installation. The log should separate severity from status so the team can prioritize issues that affect erection sequence, quality hold points, or inspection release.
- No immediate impact: track and close before handover.
- Site sorting required: issue can be resolved by labels, package checks, or document correction.
- Quality hold: item cannot be used until inspection, repair, or approval is complete.
- Installation block: current erection sequence is delayed unless action is completed.
- Engineering decision required: modification, substitution, or use-as-is approval is needed.
For handover documents, use the installation package checklist.
6. Link common issue types to detailed reports
The issue log is the master tracker, but detailed issue types should still use focused checklists. This prevents the log from becoming too long while keeping each issue traceable.
| Issue type | Detailed checklist to link |
|---|---|
| Missing items | Missing parts report checklist |
| Damage | Damage report checklist |
| Bolt issue | Bolt issue report checklist |
| Replacement request | Replacement parts request checklist |
| Site discrepancy | Site discrepancy report checklist |
7. Review the log before weekly coordination
The issue log should be reviewed regularly, especially before coordination calls with suppliers, site teams, and installation supervisors. The goal is to move open issues into clear owner actions.
- Filter open issues by installation impact.
- Check items with overdue due dates.
- Confirm whether supplier responses are still missing.
- Group issues by shipment batch, area, package number, or root cause.
- Prepare a short action list for the next coordination meeting.
8. Close issues with evidence
Closing an issue should require evidence, not only a verbal update. Closed issues should remain searchable for final handover, claims, and project lessons learned.
- Photo or inspection evidence confirms physical correction.
- Replacement package is received and accepted.
- Updated drawing, mark list, packing list, or certificate is filed.
- Engineering or quality approval is attached where required.
- Installation team confirms the affected area is released.
- Closeout date and responsible person are recorded.
Red flags in site issue logs
- Issue descriptions are too vague to identify the package or component.
- Statuses say "pending" but do not show owner, next action, or due date.
- Photos and reports are stored outside the log without references.
- Closed issues do not include repair, replacement, or approval evidence.
- The log is not reviewed before installation handover.
- Different teams maintain separate logs with conflicting status.
Buyer note
A site issue log is a simple control tool, but it only works when every entry is specific, assigned, evidence-linked, and closed with proof. EPC buyers should keep one master log for steel structure delivery and site issues, then link each item to the detailed report or checklist that proves closeout.