What is a “turnaround document” in information systems operations? Select the most accurate description.

Introduction / Context:
Operational documents often flow between the system and users. A classic example is a utility bill, where one part is mailed out (output) and a remittance stub is sent back by the customer (input). This bi-directional lifecycle defines a “turnaround document.”

Given Data / Assumptions:

• Turnaround documents originate from the system as output.
• Users annotate or detach a portion and return it for further processing.
• They facilitate error reduction via pre-printed IDs and standardized formats.

Concept / Approach:
The distinguishing feature is the reuse of an output artifact as a future input. This preserves identifiers and speeds data capture (e.g., scanning via barcodes), minimizing keying errors and matching payments to accounts.

Step-by-Step Solution:
1) Identify the lifecycle: system prints/sends document.2) User returns part of the document (stub) to the system.3) System processes the returned item to update records.

Verification / Alternative check:
Bank deposit slips, pay-in vouchers, and meter-reading cards are similar cases. All originate from the system and return as inputs.

Why Other Options Are Wrong:
Staff memos or policy notes are one-way communications and not designed to return as structured inputs.

Common Pitfalls:
Confusing turnaround documents with simple receipts; receipts are typically outputs retained by customers and do not loop back as inputs.

Final Answer:
A document produced as system output that later returns as input (e.g., bill stub).