What is the purpose of a 'read-back' to a supervisor for critical directives?

• A. To confirm that the directive was accurately heard and will be executed as instructed.
• B. To delay action.
• C. To log the directive for later.
• D. To confuse the supervisor.

Answer: (A)

In critical directives, the read-back is a verification step that makes sure the directive was heard exactly as given and will be carried out as instructed. This practice catches mishearing or ambiguities right away, confirms you understood the exact actions required, and establishes a clear, accountable record that the order was understood and will be executed. If the supervisor hears a mismatch, they can correct it on the spot, preventing errors that could endanger safety or complicate the operation.

This isn’t about delaying action, logging for later, or causing confusion. It’s about accuracy and accountability in high-stakes communication, ensuring everyone is on the same page and that mission-critical commands are executed correctly.