Review & Decision

Record an independent judgment against the exact request revision. 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.

A request reaches Verified after its requirements are checked. A Library Reviewer examines that revision and records Approved, Returned or Rejected on the decision, along with a reason and evidence reference. A returned case goes back to the operator for correction rather than silently changing the reviewed evidence.

• Ownership. The reviewer makes the decision. The operator prepares the record and resolves returns. Administrators can inspect the history without substituting an administrative change for a reviewer decision.
• 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 which person can be the independent reviewer for each branch and what evidence reference supports a decision. The source revision matters: changing the request after review should lead to another review, with the earlier decision still explainable. Staff need a clear rule for returning a case versus rejecting it.

The decision belongs to one request revision. The Library Reviewer reads its requirement outcomes, supporting documents and prior status before entering Approved, Returned or Rejected. The operator remains responsible for preparation and any returned work. The reviewer records a reason and an evidence reference so later readers can reconstruct the judgment.

Use a verified request with a named owner. Check that the reviewer is independent of the preparation, record the decision for the displayed source revision, and read the status history to confirm the transition. Then alter a requirement in a rehearsal case and confirm the former decision cannot be treated as approval of the new revision.

Have a different reviewer reopen the same case after the decision. They should match the decision source revision to the request revision and find the reason and evidence reference. Change a requirement in a rehearsal copy and repeat the check: the earlier decision must remain linked to the earlier revision rather than appear to approve the changed case.

• Pending Loan Decisions — Reviewer decisions awaiting a final value and supporting reason.
• 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.