When corrective action is taken due to a ticket discrepancy, what documentation is required?

When corrective action is taken due to a ticket discrepancy, what documentation is required?

• A. Verbal confirmation only.
• B. Documented corrective action per contract and proper records.
• C. A new batch ticket generated by the plant.
• D. An on-site inspection report only.

Answer: (B)

When a ticket discrepancy requires corrective action, it must be formalized in documented corrective action records that follow the contract requirements and are kept as part of the project records. Verbal confirmations don’t leave an auditable trail, and relying on an on-site inspection report alone doesn’t capture the full corrective action process. Issuing a new batch ticket might address the issue operationally, but without documented details of what was wrong, what corrective steps were taken, who approved them, and when, the action isn’t properly recorded. The documented corrective action should specify the discrepancy, the corrective steps implemented, the responsible personnel, dates, and any verification activity that confirms the issue is resolved. This creates traceability, accountability, and compliance with QA/QC procedures, and supports any needed audits or future deliveries.

When a ticket discrepancy requires corrective action, it must be formalized in documented corrective action records that follow the contract requirements and are kept as part of the project records. Verbal confirmations don’t leave an auditable trail, and relying on an on-site inspection report alone doesn’t capture the full corrective action process. Issuing a new batch ticket might address the issue operationally, but without documented details of what was wrong, what corrective steps were taken, who approved them, and when, the action isn’t properly recorded. The documented corrective action should specify the discrepancy, the corrective steps implemented, the responsible personnel, dates, and any verification activity that confirms the issue is resolved. This creates traceability, accountability, and compliance with QA/QC procedures, and supports any needed audits or future deliveries.