In acceptance testing, which option best describes how deviations are handled?

In acceptance testing, which option best describes how deviations are handled?

• A. Only the final test results, with no deviations noted.
• B. Maintenance schedules and spare parts lists.
• C. Deviations with corrective actions.
• D. Electrical wiring diagrams.

Answer: (C)

In acceptance testing, any difference between what’s required and what’s actually built is treated as a deviation that must be addressed. You document the deviation, identify the cause, propose a corrective action, assign responsibility, and set a timeline. After the corrective action is implemented, you re-test to confirm the deviation is resolved before acceptance. This approach ensures the system truly meets the specifications and safety requirements. Recording only final results with no deviations would hide problems, while maintenance schedules, spare parts lists, or wiring diagrams aren’t how deviations are managed.

In acceptance testing, any difference between what’s required and what’s actually built is treated as a deviation that must be addressed. You document the deviation, identify the cause, propose a corrective action, assign responsibility, and set a timeline. After the corrective action is implemented, you re-test to confirm the deviation is resolved before acceptance. This approach ensures the system truly meets the specifications and safety requirements. Recording only final results with no deviations would hide problems, while maintenance schedules, spare parts lists, or wiring diagrams aren’t how deviations are managed.