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.
- Library Management System
- Features
- Follow Ups & Reporting
Follow Ups & Reporting
Assign outstanding corrections and read the outcomes of library loan work.
OverviewMy Patron Follow Ups×
Library Management System · Follow Ups & Reporting
New
My Patron Follow Ups
Patron follow ups
| Title | Loan request | Assigned to | Due date | Status | Completed at | |
|---|---|---|---|---|---|---|
| Open pfu-108 | LR-80963 | 17 Oct | Open | |||
| In progress pfu-547 | LR-94777 | 20 Oct | In progress | |||
| Completed pfu-712 | LR-66166 | 18 Oct | Completed | 15 Oct | ||
| Cancelled pfu-209 | LR-86759 | 18 Oct | Open | |||
| Open pfu-644 | LR-21704 | 19 Oct | In progress |
6 of 6 records
Open pfu-108Patron follow ups · PFU-21897
OpenLoan requestLR-80963
Due date17 Oct
What you can do
Keep the loan record understandable
Assign outstanding corrections and read the outcomes of library loan work. 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 is returned for correction after review. The operator creates a follow up with a title, due date and assignee. The assignee moves it through Open and in progress, records a resolution, then completes it. The same request remains connected to its decision and processing history.
How the work is organized
- Ownership. Operators assign and resolve the work. Administrators oversee material and branch context. Analysts use the reports to spot open action and processing patterns.
- 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.
What to agree during setup
Agree who owns follow ups when the request owner and action assignee differ. Make a useful title and resolution mandatory in the team procedure, and decide how due dates will be monitored. Analysts should read branch and decision reports with the request status in view so a returned case is not mistaken for a delivered one.
A returned decision and an assigned follow up answer different questions. The decision records what the reviewer decided about a revision; the follow up names who must correct or investigate it. The Library Circulation Operator tracks the due date, status and resolution, while the Read Only Analyst can read the outcome without editing the action.
Check the handoff on an actual case
Open a returned request and confirm its follow up points to the correct case. Check the assigned person, due date and resolution. Then compare the request status with the decision outcome and any processing run before closing the action. A completed follow up records work done; it does not itself change the review decision.
Hand an open correction to another operator. They should find its assignee, due date and linked request, then read the decision that prompted it. After the correction is recorded, compare the resolution with the case revision and current decision. Closing the follow up should not erase the reason for return or replace a new independent review.
What your team sees
- Open Patron Follow Ups — Assigned actions that remain open or in progress.
- Loan Request Board — Requests grouped by their current status for a quick handoff check.
Follow the work through
Follow request intake, evidence review and decision and delivery. Use the data model to check record ownership and references during setup.
What it keeps track of
Data model- Patron follow ups
- Assigned outstanding actions, corrections and outstanding requests for a case.
- Loan requests
- Loan requests, applications and cases submitted for a library loan.
- Loan decisions
- Independent reviewer decisions recorded against an exact source revision.
- Processing runs
- Workflow-maintained execution runs with operation key, input hash and persisted result reference.
Who uses it
Permissions- Library Circulation Operator
- , Library Administrator, Read Only Analyst.
- Each person should use the permissions associated with their assigned role and branch.
Set up Library Management System your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.