Jay Moo · Independent record-keeping notes

A tracking event is evidence of an event, not a continuous location report

A parcel page may show a recent update while leaving the current physical location uncertain. Preserve what the carrier actually reported before adding your own interpretation.

Keep the event and your interpretation apart

Write the original event wording and the time shown by the source. If a translation helps, put it beside the original wording instead of replacing it. Mark whether the time zone is known. A scan recorded at a particular facility does not establish that the parcel is still there when you read the page.

For example, a departure scan describes a recorded departure. It does not tell you that the next vehicle has arrived, that an onward connection was made or that a customs procedure is complete. Those are separate claims that require their own evidence.

Use a compact event record

These fields help you compare updates without silently turning an assumption into a confirmed movement. Keep the tracking identifier in your private log rather than publishing it with the example.

Handle apparently conflicting updates

Two services can display different timestamps because one reports a local scan time and another reports the time it received the update. Preserve both records and identify their sources. Do not choose the later-looking time simply because it seems more reassuring.

A missing scan is also ambiguous. It may reflect a reporting delay, a stage without a public scan or an issue that needs support. The absence alone does not prove loss or successful delivery. Check the carrier guidance and the relevant support process before describing an outcome.

Separate estimates from completed events

An expected delivery day is a forecast. Keep it in a different field from a delivery scan. If the estimate changes, record the revised estimate without rewriting the history of completed events. A delivered status can still need follow-up if the recipient cannot locate the parcel; preserve the reported event and document that separate issue.

The order and parcel tracking guide provides wider process context. The buying guide helps keep purchase stages separate from later transport stages. These references are maintained by this same independent project; they do not verify a particular shipment.

When requesting help, share the necessary identifier only through the provider’s appropriate private channel. A public explanation can describe the sequence and uncertainty without exposing an address, tracking number or private conversation.

Distinguish event time from retrieval time

A tracking page may show when an event happened and when you refreshed the page. Keep those times separate. A recently retrieved page can still contain an old event; the refresh time alone does not prove new movement.

Method note updated 28 October 2026.

Keep the source event and the lookup separate

Illustrative timeline: an event was recorded at 09:00, but you retrieved it at 14:00. Store both timestamps with their timezone or stated source convention. The retrieval time does not show when the parcel moved. If another system reports a later status, retain the sources separately until their event meanings are aligned. A tracking record is not a forecast or proof of an unreported physical location.

Related research guide

Read a Tracking Update as an Event, Not a Prediction

Jacket research note

Track jacket wear notes as a sequence of events

New jacket guide

Build a Jacket Event Log That Does Not Confuse Shipping With Review