SCHOOL OPERATIONS · LIBRARY ADMINISTRATION
School Library Overdue Management: A Practical Follow-Up Guide
How library staff can review due dates, borrower records, returns, fines and follow-up while applying school policy fairly.
Conceptual product view · no customer records or performance figures
THE SHORT ANSWER
An overdue review should begin with the item, copy, borrower and due date, then verify whether the resource has been returned or the record needs correction. Apply reminders and any fine policy consistently, preserve issue/return history and restrict borrower information. Reports can help staff organise follow-up, but the school decides exceptions and student communication.
01 / VERIFY THE ITEM
Confirm the copy and due date before treating a loan as overdue.
A catalogue title may have multiple copies, so staff need to identify the particular item issued. Check accession or copy details, issue date and the school’s due-date rule. A date entry error or a return not yet recorded can create an inaccurate notice.
Use the library’s agreed calendar and closure rules when reviewing due dates. If a loan was extended or a book was returned through a hand-off, verify the source record before applying a fine or sending a reminder.
02 / BORROWER CONTEXT
Match the loan to the right student or staff borrower.
Confirm borrower identity and the current school context. Similar names or a changed class can make a record appear to belong to the wrong person. Restrict borrower details to the staff who administer the library.
If the item was transferred or returned by another person, follow the library’s policy for documenting the hand-off. Avoid discussing an individual’s borrowing history in a group notice.
03 / RETURN & CORRECTION
Resolve the item’s status before calculating consequences.
Search for a return record and check the physical item or authorised staff confirmation. If the resource is damaged, misplaced or under review, record the situation under school procedure rather than assuming it is simply overdue.
Correct an issue or return entry through an authorised path and preserve the reason. Confirm which history the product retains before relying on it for accountability. A record correction and a policy exception are separate decisions.
04 / FINES & EXCEPTIONS
Apply school fine rules consistently and review exceptional circumstances.
If the school uses fines, document the approved rule and how a due period maps to an amount. Confirm that any calculation or fine record in the product matches policy before communicating it. Do not create a charge solely because a report labels an item overdue.
Provide a review route for disputed dates, illness, accessibility needs or other exceptions recognised by the school. Apply decisions consistently and keep the authorising person visible.
05 / REMINDERS & HISTORY
Make follow-up factual, proportionate and easy to resolve.
A reminder should identify the borrowed resource and expected next step without revealing other students’ information. Verify the recipient and contact details. Give a library contact path where a family or student can report a return or ask for help.
Confirm whether notices are manual or automated and what history/status is retained. An outbound reminder is not proof of delivery or a two-way conversation. Avoid repeated messages while a correction is already under review.
06 / PERIODIC REVIEW
Use overdue reports to improve circulation practices.
Review overdue patterns by period and item category only where the report supports that view. Check whether dates and return records are complete before concluding that a group has a recurring issue. Use findings to improve due-date communication or hand-off procedures.
Keep reports and exports limited to authorised library and school roles. Confirm the product’s report fields and filters rather than assuming a particular circulation analysis is available.
A FIELD GUIDE FOR YOUR TEAM
A library overdue review
Use this before sending a reminder, recording a fine or escalating an unresolved item.
| Lens | Question to ask | What to record |
|---|---|---|
| VERIFY THE ITEM | Confirm the copy and due date before treating a loan as overdue. | A verified copy, borrower, issue date and applicable due date. |
| BORROWER CONTEXT | Match the loan to the right student or staff borrower. | A checked borrower identity and role-appropriate visibility. |
| RETURN & CORRECTION | Resolve the item’s status before calculating consequences. | A verified return/status check and correction owner. |
| FINES & EXCEPTIONS | Apply school fine rules consistently and review exceptional circumstances. | A verified policy, fine calculation and exception approval route. |
| REMINDERS & HISTORY | Make follow-up factual, proportionate and easy to resolve. | A checked recipient and one accountable follow-up owner. |
| PERIODIC REVIEW | Use overdue reports to improve circulation practices. | A periodic exception review with accurate source records. |
CODEPEX IN CONTEXT
Useful guidance begins with clear scope.
School ERP declares library catalogue and accession/copy records, search, issue/return, due/overdue tracking, fines, borrower records, barcode support and related reporting. Confirm exact overdue fields and reminder behavior. The school determines lending rules and exceptions.
Product-specific statements are based on the current owner-controlled capability declaration. Ask CodePex to confirm any institution-specific configuration or unlisted requirement.