Ledger delivery record hub is a place to organize visible facts: package state, page time, receipt note, and follow-up route. It should not turn the record into a warning page. The goal is to help the reader find which line still needs a photo, a timestamp, or a reply record.
Build the hub around visible records
Use one row per visible record. The delivery record hub can be used as the main related reference, but this page explains how to keep the hub table readable.
| Hub row | Required fields | Useful evidence |
|---|---|---|
| Package state | Label, photo, item name | Box and label images |
| Page time | Viewed time and status | Screenshot number |
| Receipt note | Received by, location note | Record without private setup data |
Page time should not overwrite package photos
If a tracking page changes after the package photo is saved, add a new page-time row instead of overwriting the photo note. That keeps earlier records visible and makes the review table easier to follow.
Order-to-arrival checkpoints provide the sequence
When the reader wants the full sequence, use the order-to-arrival checkpoints as the next step. The hub keeps records; the checkpoint page explains the sequence.
Policy pages stay as context
For site-level delivery wording, the delivery policy landing page is context only. Do not paste its broader wording into every package-specific row.
Hub cleanup before closing the record
- Every package photo has a row number.
- Every page-time entry has a screenshot number.
- Receipt notes avoid private device information.
- Follow-up routes point to pages or service paths, not informal instructions.
A delivery record hub works best when it stays factual and compact. It shows what was seen, when it was saved, and what still needs a follow-up route.
