Storage tank projects can involve many inspections, documents, packages, site interfaces, and responsibility boundaries. When a quality issue or project mismatch is found, the team needs more than an informal message. A non-conformance report, often called an NCR, gives the owner, EPC contractor, inspector, installer, and tank supplier a structured way to record the issue, review impact, assign responsibility, approve corrective action, and close the record with evidence.
NCR management is different from a procurement-stage deviation register. A deviation register records exceptions before award. An NCR usually records a discovered issue during manufacturing, inspection, shipment, receiving, installation, or handover.
What an NCR should record
A useful NCR should identify the project, tank number if relevant, inspection stage, related drawing or specification, issue description, evidence, affected part or document, responsible party, proposed correction, approval route, and closure status. Without these fields, the issue may remain scattered across emails, photos, and messaging apps.
The goal is not to create paperwork for its own sake. The goal is to make the issue traceable so that the project team can decide whether the problem needs correction, acceptance with justification, replacement, rework, documentation update, or further technical review.
Separate NCRs from RFIs and change orders
An RFI is normally used when the team needs information or clarification. A change order is used when approved scope, cost, delivery, or responsibility changes. An NCR is used when something does not conform to an agreed requirement, inspection expectation, approved drawing, packing record, site condition, or quality standard.
These records may connect. A non-conformance may create an RFI if the team needs technical judgment. It may create a change order if the approved correction changes scope or schedule. The articles on RFI and technical clarification logs and change order control explain those related workflows.
Use evidence before assigning blame
NCR review should start with evidence. Useful evidence may include inspection photos, measurement records, drawing references, packing list, container loading record, receiving photos, foundation handover record, site storage notes, installation records, and communication history. This helps the team understand when and where the issue appeared.
For example, a damaged package found at site should be reviewed against receiving photos and packing records. A nozzle interface issue should be reviewed against the latest drawing revision and piping layout. A foundation concern should be reviewed against civil handover measurements and photos.
Classify project impact
Not every NCR has the same impact. Some issues are documentation corrections. Some require rework before shipment. Some need replacement parts. Some affect installation sequence, site safety, commissioning, or final handover. The NCR should therefore show whether the issue affects quality, schedule, cost, safety, inspection status, shipment, installation, or warranty discussion.
This classification helps project managers prioritize. A small labeling issue may need quick correction, while a dimensional mismatch or missing critical component may need formal approval before work continues.
Assign corrective action and approval
A corrective action should be specific. It should state what will be done, who will do it, which document or part is affected, what evidence will prove completion, and who approves closure. Vague actions such as "check again" or "handle on site" are usually not enough for international storage tank projects.
Approval may come from the owner, EPC contractor, consultant, third-party inspector, installer, tank supplier, or another authorized project representative. The approval route should match the project contract and responsibility matrix.
Connect NCRs with site records
Many NCRs are discovered at site. Site receiving inspection, temporary storage records, foundation handover records, and installation logs can all provide important context. These records help separate factory issues, transport issues, civil interface issues, site storage issues, and installation handling issues.
The articles on site receiving inspection, temporary storage protection, and civil foundation handover records show how those site records support later issue review.
Practical NCR register fields
- NCR number, project name, tank number, date, and inspection stage
- Requirement reference: specification, drawing, packing list, inspection plan, or site record
- Issue description with photos, measurements, or document evidence
- Impact classification: quality, schedule, cost, shipment, installation, safety, or handover
- Responsible party and required response date
- Proposed correction, replacement, rework, acceptance, or further review route
- Approval person, closure evidence, closure date, and remaining open items
Close the record with evidence
An NCR should not remain open after the correction is done. Closure evidence may include revised drawings, replacement part photos, reinspection records, packing updates, site correction photos, signed approval, or updated handover documents. The closure record should be stored with the project file so future operation and after-sales teams can understand what happened.
For projects with third-party inspection or consultant review, closure evidence may also need to be shared before shipment, installation, or commissioning can proceed.
Where product scope fits
NCR management is easier when the selected tank route, supply scope, and responsibility split are clear. Buyers reviewing storage tank options can start with product information such as GFS tanks, then connect the selected package with inspection plans, packing records, site records, NCR control, and final handover documents.
Practical takeaway
A non-conformance report gives storage tank projects a disciplined way to handle quality and project issues. By recording the requirement, evidence, impact, responsibility, corrective action, approval, and closure proof, project teams can reduce confusion and keep manufacturing, shipment, site work, commissioning, and handover aligned.