These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
Feature · Review
Example screen with sample data
Review
Keep decisions on a specific loan revision with a reviewer and reason.
OverviewReview Decision History×
Public Library System · Review
New
Review Decision History
Review decisions
| Parent | Reviewer | Source revision | Decision | Decided at | Reason | |
|---|---|---|---|---|---|---|
| LNS-71588 | 320 | Approve | 20 Oct | Approve rd-407 | ||
| LNS-26044 | 250 | Return | 25 Oct | Reject rd-641 | ||
| LNS-46472 | 490 | Approve | 22 Oct | Return rd-922 | ||
| LNS-32904 | 420 | Return | 27 Oct | Approve rd-348 | ||
| LNS-45968 | 360 | Approve | 21 Oct | Reject rd-696 |
6 of 6 records
Approve rd-407Review decisions · RD-22493
ApproveParentLNS-71588
Source revision320
Decided at20 Oct
Operation keyOK-158
What you can do
Let the reviewer decide the actual revision
A review decision links a decision to a loan, a source revision and a reviewer. It records whether the reviewer approved, rejected or returned the case, along with the date, reason and operation key. The Collection Reviewer needs the submitted interlibrary request, linked loan, custody record and attachments in view before making that judgment. A decision about one revision should not be reused after the underlying work changes.
A coordinator may prepare a handoff for a borrowed copy. Before approval, the reviewer checks the patron reference, requested copies, item and custody trail. A reason explains why the handoff can proceed or what must be corrected. A rejected or returned case stays understandable to the next person who opens it. The reviewer does not have to reconstruct the decision from chat messages.
How the work is organized
- Source. The source revision identifies the loan revision considered in the decision.
- Authority. The reviewer points to the responsible team member rather than a generic approval label.
- Reason. The decision, date and reason show what was decided and why.
What to agree during setup
Define which handoffs need independent review and who is eligible to act as Collection Reviewer for each organization. Agree what evidence is sufficient for an approval, including the custody state and the identity of the owning library. A reviewer should return incomplete work with a usable reason so the coordinator knows what to correct. Decide how the team confirms that a changed loan or request receives a new review rather than inheriting an old approval.
The App Administrator maintains team membership and organizational scope. The coordinator prepares operational records, while the reviewer decides the frozen case. The Auditor reads the decision trail. These responsibilities should be rehearsed with real access settings before work reaches an outside library.
Check the handoff on an actual case
Submit an interlibrary request with a loan and supporting attachment. Have one coordinator prepare it and a different reviewer inspect it. Record an approval tied to the source revision and operation key. Then change the underlying loan in a rehearsal. The earlier decision should remain in history, but the changed work should not be treated as though that earlier decision covered it. Record a fresh decision for the revised case.
Try a rejected case as well. The reason should tell the coordinator whether the copy count, custody detail or evidence needs correction. Review Decision History should let an Auditor identify the reviewer and source revision. A successful review ends with a defensible decision and a clear next action; it does not by itself establish that a physical transfer occurred.
What your team sees
- Review Decision History — Decisions with reviewer, source revision, date and reason.
- Handoff Review Inbox — Submitted interlibrary requests requiring a decision.
Follow the work through
See interlibrary handoff for the submitted case. Use review and reconciliation to connect the decision to its later effects.
What it keeps track of
Data model- Review decisions
- Independent review decisions on frozen revisions
- Interlibrary requests
- Interlibrary loan handoff requests and their review lifecycle
- Loans
- Circulation loans with copy custody and patron entitlement
- Loan events
- Custody and condition events recorded against a loan
- Record attachments
- Linked evidence files for loan records
- Team members
- Staff members with role scope per organization
Who uses it
Permissions- Collection Reviewer
- , Collection Coordinator, Auditor, App Administrator.
Set up Public Library System your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.