Hartwell & Pryce Engineering wants to investigate an aluminium lot. Its ERP calls the lot ERP-AL-008; the factory records call it RAW-AL-008. This invented scenario illustrates declared evidence. Similar codes alone do not prove that the two references identify the same material.
Declare the actual capture
The Supervisor creates an ERP dataset for receipt observations and a separate factory dataset for explicitly recorded operations and shipment contents. Each has its own source instance, generation, scope, owner, authority, retention basis and readers.
The ERP receipt dataset does not claim to record production relationships. The factory dataset declares those relationship types it actually captures. Approved source envelopes are reviewed and admitted through the normal scanned intake.
Establish the cross-source identity
An investigation beginning at ERP-AL-008 initially has no route into the factory dataset. The Supervisor checks the actual receipt-to-factory assignment document, then approves the exact same-kind identity pair with its evidence reference and reason.
An Operator selects both permitted datasets and saves a new physical forward investigation. The reviewed bridge is separate from factory transformation, split, build and rework facts. The original source identities remain visible.
Keep the gap explicit
The factory evidence splits the lot into two branches and records units and shipment contents. Suppose a declared source sequence is missing. The related shipments can still be useful leads, but the result remains partial. Quantities do not allocate material between branches or prove unused fractions.
A later file adds a shipment recorded late with an earlier occurrence time. A new current run can include it. The original saved run remains unchanged at its earlier local cutoff.
Correct without erasing
The source later sends a separate supersession notice for a wrong shipment relationship. The old relationship becomes inactive in a new current view while its replacement is pending. LotTrail shows that gap rather than guessing the corrected shipment.
After explicit replacement evidence is admitted, a new run can show the corrected related set. The Supervisor attaches relevant runs to a local case and explains the change. Closing that case records review, not a recall or source-system hold.
If a required dataset grant is removed, the saved cross-source report and case are withheld under current rights. Already downloaded copies remain subject to the organisation's source-data handling agreement.
Hand over the unresolved work
The Supervisor hands the investigation to the next shift as a question with bounded evidence, rather than a list of definitively affected or unaffected stock. Sarah checks that the receiving Supervisor and Viewer have current access to both declared datasets before referring them to the case.
| Point to hand over | Expected position | Next responsibility |
|---|---|---|
| ERP-AL-008 and RAW-AL-008 | Separate exact source identities connected by a reviewed identity decision | Supervisor preserves its evidence reference; readers do not infer a production link from matching text. |
| Missing source sequence | Saved run remains partial at its original cutoff | Receiving investigator obtains the source owner's explanation or admitted missing evidence, then saves a new current run. |
| Wrong shipment relationship | Superseded relationship inactive; explicit replacement may still be pending | Supervisor reviews and admits the source correction and replacement through the proper intake. |
| Case review | Both earlier and later runs retained with their different cuts | Supervisor explains the changed conclusion in case history and records the local review status. |
If adding the later run expands the case's dataset scope, check the assignee's grants before attaching it. A case that is closed must be explicitly reopened before notes or attachments; reopening also needs current new-work authority. The case does not acquire a smaller scope when an earlier run is inconvenient.
An uncertain accept-file or save-run answer must be reconciled using the original command before creating another action. If any required grant is removed during the handover, stop disclosure and ask the responsible Supervisor to resolve access. The source teams separately decide any physical containment or despatch action; LotTrail's local case status records none of those actions.