Resource

Borrowing a Book

One loan, end to end — a pupil finding a title that is already out, joining the queue, collecting it when it comes back, keeping it too long, and the fine appearing where a school actually collects money: on the family’s invoice, and on the clearance list when that pupil tries to leave.

StudentLibrary Staff
Borrowing a Book

A library is a lending business with no invoices of its own

Every school library runs on two things it cannot do by itself: it has to know who a borrower is, and it has to be able to charge them. Run as its own system, it gets a card index that goes stale the day a pupil changes class, and a fines book nobody ever collects on. EaseAcademia’s library borrows both from the platform — the borrower IS the pupil record, and a fine is a line on the family’s fee invoice — which is why the last two screens of this walkthrough are not library screens at all. Library Management is a paid module; the invoice it posts to is Finance, and the exit it blocks is base platform.

On this page
Step 1 · Student

Wanting a book somebody else has

The interesting case is not the book on the shelf — it is the one that is out. What a library does with the queue is most of what a reader thinks of it, and it is the part a card index handles worst.

1

Search the catalogue

The whole catalogue, searchable by title, author and category, with how many copies exist and how many are on the shelf right now. A pupil does not sign up for the library — they are a member because they are a pupil, which is the first thing the platform gives it.

Every title with its author, category and shelf location
Copies held against copies available, live
The same endpoint the librarian queries — the server decides which fields each of them gets
No membership to apply for: the pupil record IS the borrower record
2

Join the queue

A hold on a title whose copies are all out. The pupil sees their position, and — when a copy comes back and is shelved for them — how long they have to collect it before it goes to the next reader.

Place a hold when every copy is on loan; cancel it when you no longer want it
Position in the queue, so “when will I get it?” has an answer
A copy shelved for you expires if it is not collected — the walkthrough’s later stat row counts exactly that
Their own holds only; the queue as a whole is the librarian’s screen
3

What I have out, and when it is due

The pupil’s own loans with their due dates — and, when one has slipped, what it is now costing. Showing the charge to the person who can stop it growing is the cheapest fine-collection mechanism a library has.

Every current loan with its due date, and the days remaining
Overdue items and the fine accruing on them, visible to the borrower
Renew where the membership tier allows it
Their own history too — what they have read this year
4

What I owe, before somebody tells me

The reader’s own charges, in the same figures the librarian is reading. Until 2026-08-30 nobody could see what they owed the library except the librarian, so the first a pupil heard of a fine was at the desk — usually while somebody was waiting behind them.

Overdue fines, lost-item and damage charges, with what each is for
What has been settled and what has not, so a disputed balance is a short conversation
The same page exists for staff, because a teacher owes the library the same way a pupil does

Ready to run your school on this?

Every screen in “Wanting a book somebody else has” is the live product, not a mockup. Create your school account, or have us walk you through it on a call.

Step 2 · Librarian

The other side of the counter

The librarian’s screens are the same records with the whole school in them. Issuing and returning are row actions, not wizards — because at a lending desk with a queue behind it, the number of clicks is the product.

1

The catalogue, with the things only staff see

The same titles the pupil searched, plus what a lost copy is charged at, how the title was acquired, and every physical copy with its own barcode and condition. One endpoint, two answers — the server projects the fields, so there is no second “admin catalogue” to keep in step.

Title-level bibliographic data, and copy-level condition and location
A procurement SUMMARY, not the purchase itself: how often the title has been taken in and most recently from whom. A title can be bought many times, so the intakes live in their own register and this card says how many there were
The replacement cost a borrower is charged for losing a copy — a different number from what the school paid, and from what finance expensed
Copies counted as on the shelf, on loan, lost or in repair
Add a copy of an existing title without re-cataloguing the title
2

The queue, from the desk

Every hold in the school: who is waiting, for what, and which ones now have a copy shelved and waiting to be collected. The card that matters is “expiring within two days” — a copy nobody collects is a copy nobody could borrow.

Pending holds, ready-to-collect holds and expired ones in one queue
Shelve a returned copy against the next reader in line
Expiring holds surfaced before they lapse, not after
Cancel a hold on the reader’s behalf when they ask at the desk
3

Issue, return, renew

The lending desk itself. Every loan in the school with its borrower, its due date and its state — and the three actions that make up a library day, taken on the row rather than through a form. A scanner types the barcode and presses Enter, and one lookup answers both directions: the copy, whatever loan it is on, and whoever is next in its queue.

Issue a copy to any borrower — pupil, staff member or external reader
Take a return, which also settles or raises whatever the loan owes — and shows the hold it has just satisfied before the reader walks away with it
Renew, bounded by the borrower’s membership tier — resolved per loan against the tier they are actually on, not the default for their type
Select an overdue batch and renew or remind them in one action
“Due within 7 days” and “overdue” are server-computed over the whole school, not counted off the page

See this on your own school’s data.

Every screen in “The other side of the counter” is the live product, not a mockup. Create your school account, or have us walk you through it on a call.

Step 3 · Librarian & bursary

A fine a school can actually collect

Here is the part a standalone library system cannot do. A fine is only real if somebody can be made to pay it, and a library has no way to bill a family. The platform does — so a student charge becomes a line on their invoice, and the bursary collects it with everything else.

1

What the library is owed

Every charge across every borrower type, with what is outstanding and what has been collected. Waiving is a first-class outcome rather than a deletion: a forgiven fine stays on the record with the reason, because a charge you can erase is not a record.

Overdue fines, lost-item charges, damage charges and deposits in one ledger
Outstanding and collected shown as money, in the school’s own currency
Waive with a reason — waived money never reaches the ledger as revenue, which is why it is not the same as settling
Settle at the desk for a reader paying cash
2

Where the fine is really collected

The family’s invoice, with the library charge on it. Nobody re-typed anything: the charge carries the invoice it was posted to, so the bursary chases one balance per family instead of the library chasing children for coins.

The library line sits beside tuition and every other fee on one invoice
Paid through the same gateway as the rest of the school’s money
The library’s charge and the finance ledger entry are one record, not two
A parent sees what it is for — the title, and why it was charged

Set this up for your team.

Every screen in “A fine a school can actually collect” is the live product, not a mockup. Create your school account, or have us walk you through it on a call.

Step 4 · Librarian

The last thing a library gets to say

The other end a standalone system cannot reach. When a pupil leaves, somebody has to ask whether they still have the school’s books — and the library has to be able to say no without being the office that stops the exit.

1

Who the library is holding up

Two registers behind one tab strip: everybody who owes the library something right now, and the leavers whose exit is waiting on the library to sign. The first is live — computed from loans and charges as they stand — and the second, one tab across, is the queue the librarian actually works.

The debt list is computed live from the loans and fines, never from a stored verdict
The sign-off tab is the leavers only, and it is what an exit is blocked on
Sign off, or waive with a reason, from the row of that queue
The library signs for the library — no office can clear another’s line

Ready to run your school on this?

Every screen in “The last thing a library gets to say” is the live product, not a mockup. Create your school account, or have us walk you through it on a call.

Run your whole school on one connected platform

Start with the base package, switch on the modules you need, and give every parent, student and staff member a single place to log in.