Key takeaway
A shipment delay and a driver’s regulated duty history are different scopes. Preserve regulated originals, then review any optional derivative and its permissions separately.
Define the shipment exception, not a driver profile
Choose a bounded operational question, such as how a missed receiving window was handled for one shipment. The minimum descriptive sequence may be expected event, exception, operational response and delivery evidence. It need not begin with a driver’s full route, communications, payroll or duty history.
FMCSA’s supporting-document guidance includes transport and driver-related categories. Section 395.11 addresses their duty-status role and prohibits obscuring or altering existing supporting-document information. This US review agenda therefore keeps regulated originals untouched. It does not recommend redacting those originals to create a licensing package or treat required retention as commercial reuse permission.
A delivery timeline with distinct evidence states
In this hypothetical shipment S-042, a planned receiving window is missed because the receiving location cannot accept the consignment. Operations arranges another window. A later receiving event confirms acceptance. An internal delay code initially attributes the event to a vehicle issue, but the dispatch note contradicts it. The inconsistency is preserved for review instead of becoming a confident driver-fault label.
The illustration records shipment events without reproducing real documents. Relative times retain sequence for this exercise; they are not a recommended transformation for required duty-status records. Exact timestamps and location may still be necessary in the original regulated environment.
| Relative event | Evidence in the illustration | Preparation treatment |
|---|---|---|
| Planned window | Appointment entry for S-042 | Expected event; not proof of arrival |
| Exception | Receiver unavailable; dispatch note E3 | Keep cause as reported and source-linked |
| Conflicting code | Vehicle issue code D2 | Mark conflict; no verified driver attribution |
| Response | New receiving window arranged; action A5 | Action recorded; completion not yet established |
| Outcome | Consignment accepted; receiving event R8 | Recorded delivery result with stated scope |
Do not copy entry time into occurrence time
GS1’s EPCIS standard separates asserted event time from repository recording time. Apply that distinction to the dictionary you actually hold: an exception may occur before a clerk enters it. If only entry time is available, label it as entry time and avoid calculating a precise delay from an invented occurrence timestamp.
Keep each time’s basis, time zone and source. For S-042, the late code could reflect a correction or simply delayed administration. The reviewer must not decide which explanation is true from ordering alone. If a calculation needs both arrival and appointment times, disclose when either is estimated or absent. A date-range description may be sufficient for an initial fit conversation.
Keep the regulated record and optional preparation apart
For applicable supporting documents, § 395.11 includes driver-linked fields and effective matching to duty-status records. It also contains a prohibition on destruction or alteration of existing information. Ask the motor carrier’s compliance owner which obligations apply, where originals must remain and whether a separately created external derivative is permitted at all.
Create an internal disclosure register with the original category, governing obligation or agreement, proposed derivative, named recipient and approval state. “Retained for compliance” and “approved for external evaluation” are different decisions. This article does not clear that derivative under privacy, employment, customer confidentiality or transport rules. If separation cannot be reliably maintained, pause the external scope and resolve it with the actual responsible reviewers.
Test the exception labels before promising a history
An internal spot review should include conflicting codes, rescheduled deliveries, damaged consignments and entries without a receiving confirmation. Distinguish the reported cause from a later verified interpretation. Distinguish attempted delivery from acceptance, and acceptance from complete or undamaged delivery when the evidence does not establish all three.
For the hypothetical S-042, the next task is to reconcile D2 against E3 and confirm what R8 means. The defensible description is “receiving acceptance recorded; cause conflict unresolved.” It is not “vehicle failure repaired and delivery successful.” That narrower label retains useful operational structure without inventing a mechanical event or attributing fault to a person.
- Keep source categories and occurrence/entry timing in the dictionary.
- Flag disputed causes instead of normalizing them to the most frequent code.
- Review necessary shipment fields separately from driver-level detail.
- Retain original compliance records under their applicable controls.
A description can precede a sample
The inventory tool can describe a shipment-exception category and its limits. The rights review tool helps organize questions for the company’s actual approver. VOID’s initial route exploration concerns permissioned descriptions and a named introduction, with no upfront seller referral fee. A receiving program’s possible referral payment is separate from any seller license proceeds. A request for real transport records, a sample or a license must still receive its own scoped decision.