What evidence may show that a transfer completed?¶

Completion is best established when the receiver accepted a complete object and source records describe the same operation. A connection, upload request or progress display may show only the sender's attempt.

Compare both sides¶

Source success events, application status and byte counts can be joined with destination object creation, provider audits, server receipts, matching size or hash and later access. A timeout or partial upload may leave a local success impression but an incomplete remote object.

Protocols using chunks or deduplication can create several events for one file, while retransmission and encryption make raw network volume unreliable. Use protocol and provider semantics when interpreting status.

Report the actual outcome¶

Classify the transfer as full, partial, failed or unknown. Where only one side survives, say whether completion is confirmed or merely supported and identify the missing evidence.

For email, provider delivery is not recipient reading. Similarly, remote object creation does not prove its contents match the selected source unless metadata or content links them.