Delivery & Trace

Follow the issued request through its processing evidence and delivery reference. The team should be able to start at a request and reach the branch, material, people and evidence that explain the next decision. The main work screen is the Loan Requests Workspace, where the status board and selection-driven request detail keep the current case beside its history, requirements and pending decisions.

After an approved decision, a processing run records the operation key, source revision, input hash and result reference. Its steps and attempts show when work started, what external receipt was retained and whether an attempt succeeded. The issued request carries its delivery reference and completion date.

• Ownership. Operators inspect the delivery trace. Reviewers read the decision and source revision that authorized it. Analysts can inspect run outcomes and exceptions without editing the source records.
• Evidence. Keep the request’s linked records and source revision together so a later reader can reconstruct the action.
• Status. Read the saved status and decision values before moving the case forward or assigning a correction.

Agree what external source supplies a receipt and how staff verify it. A provider reference on an attempt and a receipt on a step should be checked against the intended request before delivery is recorded. Assign someone to investigate a reconciliation-required run and to retain the result reference when that work closes.

Processing evidence links a decided request to an operation key, run, ordered steps and attempts. The Library Circulation Operator checks whether the result reference and any external receipt agree with the request before relying on a delivery reference. A failed or uncertain attempt is a reconciliation task, even if a later attempt succeeded.

Take one decided request through the recorded processing path. Match its revision to the run, the run to ordered steps, and each receipt to the right operation. Check the attempt status and failure reason if an earlier try failed. Only then check the delivery reference and completion date on the request.

Ask an operator to trace the request from its approved decision through the run and each attempt. They should name the operation key, identify any failure reason and show the saved result or receipt used for delivery. Have a second person compare the request revision with the run source revision and confirm the delivery reference belongs to that case.

• Processing Runs Requiring Reconciliation — Execution records needing investigation before staff rely on a final result.
• Loan Request Board — Requests grouped by their current status for a quick handoff check.

Follow request intake, evidence review and decision and delivery. Use the data model to check record ownership and references during setup.