Delivery record node changes should be appended, not rewritten. If a status page changes, add a dated status note, keep the earlier row, and connect the package record to the latest visible state. This makes the delivery record easier to audit later.
Status notes are append-only
Create a new line for each visible status change. The delivery node change reference is the closest related page, but this article focuses on the record method: add a row, date it, and do not overwrite the earlier row.
Package record stays tied to photos
A package record should point to photo numbers and label fields. If a status note changes after the package photo is saved, keep both. The photo does not become invalid just because a later page shows another status.
| Change type | Record action | Do not do |
|---|---|---|
| Status page | Add a dated row | Replace older row |
| Package photo | Link to row number | Move into contact notes |
| Follow-up path | Write page or service route | Store private setup material |
Use the hub for multi-row review
When the record has several status rows, the delivery record hub is the right next reading path. It helps group status notes, package notes, and receipt notes without changing the article URL.
Policy context is separate from row details
The delivery policy landing page can provide site-level context, but row details should remain factual: status text, viewed time, package record, and follow-up path.
Close the node-change record
- Every status change has a dated row.
- Package photos keep their original row numbers.
- Follow-up route is written as a stable page or service path.
- Older rows remain visible for later review.
The safest node-change record is plain and chronological. It does not need broad claims; it needs visible rows that another reader can compare later.
