How should delivery and read-status evidence be worded?¶

Delivery and read indicators often appear more conclusive than they are.

Evidential caution: that “delivered” means the intended person received the message and “read” means they personally understood it.

What this means¶

A linked device, shared account, background process or another person may have generated the event.

The service’s meaning may also vary. Delivery could refer to reaching the provider, recipient account or recipient device. Read status could reflect opening the conversation rather than deliberate attention to the specific content.

Where the distinction matters, compare sender-side and recipient-side records and verify the platform’s terminology.

Then explain what further evidence supports personal awareness, if any.

What to check or do next¶

• Use the exact service wording where possible.
• If the application records “delivered”, report that the service recorded a delivery event to the account, device or session identified by the system.
• If it records “read” or “seen”, report that the service recorded the message as read or seen.
• Do not automatically convert that into a statement about the human user.
• Preserve the icon, label, timestamp, account, device and service involved.
• Use cautious wording such as: “The service recorded the message as delivered at 14:32” or “The account displayed a seen status.”
• Preserve the source and collection method so another investigator can test the same conclusion.
• Preserve the source and collection method so another investigator can test the same conclusion.

Evidential limits¶

Where uncertainty remains, identify what further evidence would be needed and why it would matter.