Loading...
operations

Interlibrary Loan Request Tracking Log

Track interlibrary loan requests, due dates, shipping, returns, and condition notes in one place. This log helps library staff follow each borrowed or loaned item from intake through audit trail.

Trusted by frontline teams 15 years of frontline software AI customization in seconds

Built for: Public Libraries · Academic Libraries · Special Libraries · Consortia And Resource Sharing Networks

Overview

This Interlibrary Loan Request Tracking Log template is built for libraries that need one record for each borrowed or loaned item. It captures request intake, item details, lending and borrowing library contacts, shipping method, due dates, return status, and notes so staff can see the full lifecycle of a request without searching through email.

Use it when your team handles recurring ILL requests, needs to track who has the item, or wants a consistent audit trail for follow-up and returns. The structure works well for both incoming loans and outgoing lending, especially when multiple staff members touch the same request. The fields support clear status tracking and make it easier to spot overdue items, renewal requests, or items that arrived with condition issues.

Do not use this template as a patron intake form or as a general acquisitions log. It is not meant to collect unnecessary personal data, and it should not be expanded into a catch-all record with every possible note field visible at once. If your workflow only needs a few fields at first, use conditional logic or progressive disclosure so shipping, return, and condition fields appear only when relevant. That keeps the form easier to complete and reduces missing data. The best version of this log is specific, searchable, and easy to update at each handoff.

Standards & compliance context

  • Keep the log aligned with GDPR data minimization by collecting only the contact and request details needed to process the loan and return.
  • If the form is public-facing or shared outside staff, make required fields and any PII collection clear and include a brief disclosure about how the information will be used.
  • Use an accessible field order, labels, and validation that support WCAG 2.1 AA so staff can complete the log without relying on visual cues alone.
  • If the template is adapted for patron requests, avoid collecting unnecessary personal data and use the minimum-necessary principle for any sensitive information.

General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.

What's inside this template

Request Intake

This section captures the basic request record so every ILL item has a unique, searchable starting point.

  • Request Type (required)
  • Request Date (required)

    Date the interlibrary loan request was submitted or received.

  • Request ID

    System-generated tracking number for this ILL request.

  • Request Status (required)

Item Details

These fields identify exactly what was requested or loaned, which prevents mix-ups between similar titles or editions.

  • Item Title (required)
  • Author / Creator
  • Item Format (required)
  • ISBN / ISSN / Call Number

    Enter the most relevant identifier for the item. Do not include unnecessary PII.

  • Loan Period (Days)

    Number of days the item may be kept before return.

Lending and Borrowing Library

This section records who is sending and receiving the item so staff can coordinate handoffs and follow up quickly.

  • Borrowing Library Name
  • Lending Library Name
  • Library Contact Name
  • Library Contact Email
  • Shipping / Delivery Method

Due Dates and Return Tracking

These fields show where the item is in the workflow and make overdue or missing items easy to spot.

  • Date Shipped
  • Date Received
  • Due Date
  • Renewal Requested?
  • Return Status
  • Date Returned

Notes and Audit Trail

This section preserves exceptions, condition details, and supporting documents so staff can explain what happened later.

  • Condition / Damage Notes
  • Follow-Up Notes
  • Supporting Documents

    Optional attachments such as shipping receipts, correspondence, or damage documentation.

How to use this template

  1. 1. Create a new record for each interlibrary loan request and assign a unique request ID at intake.
  2. 2. Enter the item title, author, format, identifier, and loan period so staff can match the record to the physical or digital item.
  3. 3. Record the borrowing and lending library names, contact person, email, and shipping method when the request is confirmed.
  4. 4. Update the shipped, received, due date, renewal, return status, and returned date fields as each handoff occurs.
  5. 5. Add condition notes, follow-up notes, and supporting documents only when they are needed to explain an exception or preserve the audit trail.

Best practices

  • Use a date picker for every date field and a numeric input for loan_period_days so the record stays consistent and searchable.
  • Mark only the fields you truly need as required, and keep optional fields available for exceptions rather than forcing every request into the same shape.
  • Use conditional logic to show renewal and return fields only after an item is shipped or received.
  • Record the item identifier exactly as it appears in the source record, such as an ISBN, ISSN, barcode, or local call number.
  • Write condition notes at the time of receipt or return, not from memory later, so the audit trail stays accurate.
  • Keep follow-up notes brief and factual, and avoid repeating data already captured in structured fields.
  • Attach supporting documents only when they clarify a shipment, condition issue, or lender communication that may need later review.

What this template typically catches

Issues teams running this template most often surface in practice:

Missing or inconsistent request IDs that make it hard to match a shipment to the original request.
Blank due dates that leave staff unable to tell when a loan is overdue.
Using free-text notes instead of structured fields for shipping method, return status, or renewal requests.
Forgetting to update date_received or date_returned after the item changes hands.
Recording condition issues only after the item is returned, which weakens the audit trail.
Overusing required fields so staff skip the form or enter placeholder data.
Attaching documents without a clear note explaining why they matter to the request.

Common use cases

Academic library borrowing desk
Track faculty and student ILL requests from intake through receipt, renewal, and return. The log helps staff coordinate with lending libraries and keep due dates visible across shifts.
Public library resource sharing
Document incoming and outgoing loans between branch libraries or partner systems. Staff can record shipping method, contact details, and return status without relying on email threads.
Special library document delivery
Manage article, report, or book requests where the item format and identifier matter for routing. The template keeps condition notes and supporting documents attached to the same request record.
Consortium lending workflow
Use the log to standardize request handling across multiple institutions. Shared fields make it easier to compare status, follow policies, and preserve an audit trail for each transaction.

Frequently asked questions

What is this Interlibrary Loan Request Tracking Log template used for?

Use it to record each ILL request from intake through return, including request status, item details, lending and borrowing libraries, shipping method, and due dates. It gives staff a single record for tracking borrowed and loaned materials and for documenting follow-up. The log also supports an audit trail when questions come up about timing, condition, or missing returns.

Who should fill out this log?

It is usually maintained by interlibrary loan staff, circulation staff, or a resource-sharing coordinator. In smaller libraries, one person may enter the request and update it through return; in larger systems, different staff may handle intake, shipping, and receiving. The key is to assign one owner for each record so status changes stay current.

How often should the log be updated?

Update it at each workflow milestone: when the request is received, when the item is shipped or received, when the due date is confirmed, and when the item is returned or renewed. If a renewal is requested or a package is delayed, record that change immediately. Delayed updates are a common cause of overdue items and unclear responsibility.

What fields should be required in an ILL tracking log?

At minimum, require the request ID, request date, request status, item title, item identifier, borrowing and lending library names, and due date. Other fields such as condition notes, supporting documents, and return status can be optional unless your workflow needs them. Keep the form aligned with data minimization by collecting only the details you actually use.

Can this template be customized for different library workflows?

Yes. You can add fields for patron-facing status updates, courier tracking numbers, lender policies, or local routing notes. If your process includes progressive disclosure, you can show shipping fields only when an item is marked as sent or received. That keeps the log shorter and easier to complete.

How does this template help with overdue or missing items?

The due date, renewal requested, return status, and date returned fields make it easier to spot items that need follow-up. Condition notes and supporting documents help staff document damage, packing issues, or lender communication. This reduces guesswork when a record needs to be reviewed later.

What should be included in the notes and audit trail section?

Use it for brief, factual updates such as lender instructions, exceptions to the normal loan period, damage observed on receipt, or reminders sent. Supporting documents can include shipping confirmations, lender correspondence, or scans of item condition records. Avoid free-form notes that repeat data already captured in structured fields.

How is this better than using email or a spreadsheet thread?

A dedicated log keeps the same fields in the same place for every request, which makes status checks and handoffs faster. It also reduces missed due dates, duplicate follow-ups, and lost shipping details. Compared with ad hoc email chains, it creates a cleaner audit trail and is easier to search by request ID or item title.

Go deeper on the topic

Related concepts
  • A standard operating procedure (SOP) is a documented, step-by-step procedure for a repeatable task — the written version of "how we do this here." Good SOPs...
  • Workforce management (WFM) is the operational discipline of getting the right employees, with the right skills, in the right place, at the right time — and...
  • A daily huddle is a brief (10–15 minute) standing meeting held at the start of a shift or workday to align the team on priorities, surface issues, and...
  • A deskless worker is any employee whose job happens without a desk, a company laptop, or a fixed workstation. They're roughly 80% of the global workforce —...
Related guides

Ready to use this template?

Get started with MangoApps and use Interlibrary Loan Request Tracking Log with your team — pricing built for small business.

Ask AI Product Advisor

Hi! I'm the MangoApps Product Advisor. I can help you with:

  • Understanding our 40+ workplace apps
  • Finding the right solution for your needs
  • Answering questions about pricing and features
  • Pointing you to free tools you can try right now

What would you like to know?