Four Thousand Textbooks: Lending Things to People Who Are Not in the System
Four thousand textbooks, issued each January to nine hundred learners who exist in no database you own, and collected each November from whoever still has them. There is no student record — so the question is which of the two custody mechanisms you bend, how far each will bend, and what you can honestly expect to get back.
Textbooks are the largest thing most schools own after the buildings and the buses, and the only major asset class that is deliberately handed to nine hundred people who are not employees, not users, not customers and not recorded anywhere in the system. Every January they go out. Every November some fraction comes back. The gap between those two numbers, multiplied by a few hundred shillings, is a line in your budget that nobody can explain.
This article is about how far you can get without a student record — which is further than you would expect in one direction and not at all in another. Being clear about which is which is the whole point.
The missing entity, stated once
There is no student, class, enrolment or guardian record anywhere in this product. No fee structure, no admission number, no stream, no register. It is not a school management system and does not pretend to be one; it is an operations and finance platform that a school runs its money, stores, assets, staff and procurement on, alongside whatever system holds its learners.
That single absence is what makes textbook custody interesting rather than trivial. In a school information system you would issue a book to an admission number. Here, the person receiving the book cannot be named in the way the system understands people — so the honest question is what you attach the custody to instead.
Four ways to model four thousand books, from strongest to weakest
One pooled asset per title, held by a custodian
One asset record for Secondary Mathematics Form 2, tracked as a quantity pool rather than individually. Balances are held per custodian, per department and per location, and movements shift quantities between them with an expected return date. Forty copies to the Form 2 class teacher is one movement, and the balance says the teacher holds forty.
Individual asset records per copy
Every copy its own record with its own code, condition and history. Correct for a reference library of a few hundred high-value volumes; unworkable for four thousand class sets, where you would be maintaining four thousand histories to learn nothing you could not learn from a pool balance.
Books as consumable stock at locations
A stock item with a quantity per location, where a location stands for a class. It records where books are and it cannot record that they are expected back — stock is consumed, not returned, so there is no due date and no overdue list. Use it for exercise books and stationery, which genuinely are consumed.
Custody attached to the learner
There is no student record to attach anything to. The furthest you can go is a custodian record per learner, which is a person record designed for staff and contractors, created nine hundred times a year and archived nine hundred times a year. Technically possible; do not.
The middle two are real options for specific cases rather than compromises. The first is what the pooled-asset model was built for, and the last is the one to refuse — a custodian record per learner turns your asset register into a shadow student database that nobody maintains after the first term.
What a custodian can be, which is more than you think
The reason the class-teacher model works is that a custodian is its own record rather than a pointer to an employee. It carries a name, a code, an employee number, an email, a phone, a job title, a department and a location, and its type can be employee, contractor, department, vendor, visitor or other. Linking it to an employee is optional.
So a custodian can be a person who is not on your payroll, and it can also be a department — which is the cleanest way to say "the Form 2 book store" or "the library" without inventing a person. In practice a school ends up with a handful of custodians per class or subject, not nine hundred.
Class sets issued to learners for the year
One pooled asset per title, custodian = the class teacher
The teacher signs for forty and is accountable for forty. Who holds each individual copy is the teacher's register, on paper or a spreadsheet, and that is the right place for it — the school's record is the class total.
Library lending, book by book
Individual assets, custodian per borrower — or your library system
If borrowers are staff, individual asset records with expected return dates work properly. If borrowers are learners, this is the case where a purpose-built library system earns its licence, and there is no shame in running one beside this.
Exercise books, pens, chalk, printing paper
Consumable stock, issued to a location
These are consumed and never come back. Stock with locations, reorder points and a low-stock alert is exactly right, and treating them as assets would be the error.
Laboratory equipment and sports kit
Pooled assets with expected return dates
Twenty microscopes or thirty hockey sticks are the ideal pooled case: identical, issued in numbers, expected back, and worth knowing the condition of when they return.
A single expensive item — a projector, a keyboard
Individual asset, individual custodian
One record, one holder, one history, and a condition noted on every movement. This is what individual tracking is for.
The January-to-November loop, honestly
What the system holds
Per title, per custodian
- The total number of copies the school owns, per title
- How many each custodian currently holds
- Every movement: quantity, from, to, who performed it, when
- Condition before and after a movement
- An expected return date, and an overdue list once it passes
- A department or location as the holder where no person should be named
What the teacher holds
Per learner
- Which learner has which copy, by admission number
- The signature collected at issue
- Damage attributable to an individual
- A charge raised against a family for a lost book
- The reminder that goes home before the holidays
What crosses the seam
- One number in each direction: forty out in January, thirty-six back in November
- A reconciliation nobody automates — the difference is entered as a disposal with a reason
This is the seam to design around rather than fight. The school's books are accountable to a custodian; the individual learner is accountable to a teacher. Trying to push learner-level custody into the asset register is what produces nine hundred abandoned custodian records.
The reconciliation at the end of the year is the part to get right, because it is where the number stops being fiction. Thirty-six of forty came back: the teacher's balance is reduced by thirty-six on the return movement, and the remaining four are disposed of with a reason. What you must not do is leave four on the teacher's balance forever, because by Form 4 that teacher notionally holds two hundred books that do not exist and the register has become decorative.
Every uncollected book you leave on a custodian's balance is a lie that compounds. Dispose of the losses annually, with a reason, or the register stops being a record of anything.
What the loss actually costs, and what you can prove
The pooled model gives you a number per title per year: issued, returned, lost. Over three years that is a pattern, and the pattern is what changes behaviour — a title losing 12% a year in one stream and 2% in another is a conversation about a teacher's process, not about learners.
What it will not give you is a charge. There is no fee ledger, no student account and no way to bill a family for a lost book from inside this system. If your school recovers book losses through fees, that recovery happens wherever your fees live, from a list the teacher produces. Do not plan for the asset register to raise it.
The two silences to plan around
First, nothing tells anybody that a return is overdue. An asset past its expected return date appears on an overdue list, and there are no asset notifications of any kind — no email, no in-app notice, nothing scheduled. The list is a page somebody has to open, so put it in a named person's calendar for the week before the holidays.
Second, nothing verifies a register. There is no verification campaign, no sign-off, no exception list produced by a count. A stock-take of your book store is a manual exercise you run, compare and correct by hand. For a school that is an annual event rather than a continuous process, which makes it survivable — but it is work, not a feature.
What we do and do not do
What AWRA OpsHub does today
- Pooled asset tracking — one record per title with balances per custodian, department, warehouse and location, and movements that shift quantities with condition before and after.
- Custodians who need not be employees, including a department as the holder, each with a code, contact details and full movement history.
- Expected return dates with an overdue list you can filter, and a per-custodian count of what they hold and what is overdue.
- Individual tracking where each copy genuinely needs its own history, and conversions between asset and inventory where something changes character.
- Consumable stock with locations and low-stock alerting for exercise books, stationery and anything genuinely used up.
What it does not do
- No student, class, enrolment or guardian record. Custody cannot be attached to a learner, and a custodian record per learner is a shadow database you will not maintain.
- No fee ledger or student account, so a lost book cannot be charged to a family from here.
- No asset notifications at all. An overdue return alerts nobody; the overdue list is a page you visit.
- No verification campaign or sign-off, so an annual count is a manual exercise with a manual exception list.
- No per-copy identity inside a pool. You know a teacher holds forty; which forty is the teacher's register.
- No depreciation, so the register will not reconcile to a written-down value without work outside the system.
Read the split honestly: the school-level accountability is genuinely good and the learner-level accountability does not exist. If your losses are concentrated at the learner level — and in most schools they are — the register tells you the size of the problem and a teacher's paper register is still what tells you the cause.
The year, in six moves
- Before January: one pooled asset per title, with the true owned quantity, counted rather than assumed.
- At issue: one movement per class, to the class teacher as custodian, with an expected return date set to the last week of term three.
- In the same hour: the teacher records which learner has which copy, in their own register, and keeps it.
- Mid-year: the overdue list checked once, deliberately, because nothing will remind you.
- At return: one movement back per class, with a condition, and a genuine count rather than a repeat of the issue figure.
- At year end: the difference disposed of with a reason, and the loss rate per title compared with last year.
Six moves, twice a year, per class. That is a morning of work for a school of nine hundred, and it produces the one number that has been missing from every book budget: what proportion of each title you actually get back.
Our take
Use one pooled asset per title, make the class teacher the custodian, and set the expected return date at issue — that is the model this was built for and it works. Keep learner-level custody on the teacher's register, where it belongs, and resist the temptation to create a custodian per learner. Then do the one thing most schools skip: dispose of the annual losses with a reason, so the register stays honest and the loss rate becomes a number you can manage.
See asset custody and pooled tracking
Pooled assets with balances per custodian, movements with condition and expected return dates, custodians who need not be staff, and an overdue list you can filter.
Explore asset trackingFrequently asked questions
Can we issue a textbook to a specific learner?
Not in a way the system understands, because there is no student, class or enrolment record to attach it to. The workable model is one pooled asset per title issued to the class teacher as custodian, with which learner holds which copy kept on the teacher's own register. You could create a custodian record per learner — custodians are standalone person records — but nine hundred of them created and archived each year becomes a shadow student database nobody maintains past the first term.
Should textbooks be assets or stock?
Assets, because they are expected back. Stock is modelled as consumed rather than returned, so it has no expected return date and no overdue list — which makes it right for exercise books, chalk and printing paper, and wrong for class sets. Use pooled asset tracking rather than individual records: one asset per title with balances per holder, instead of four thousand separate histories.
What does pooled tracking actually give us?
One record per title, with a balance per custodian, per department, per warehouse and per location, and movements that shift quantities between them recording who performed the movement, when, and the condition before and after. Forty copies to a class teacher is a single movement, and the balance then states that the teacher holds forty. That is the level of accountability a school can genuinely sustain twice a year.
Will we be reminded that books are due back?
No. An asset held past its expected return date appears on an overdue list you can filter, and there are no asset notifications of any kind — nothing emails, nothing appears in an inbox, nothing is scheduled. Put the overdue list in a named person's diary for the week before the holidays; that habit is the whole reminder mechanism.
Can we charge a family for a lost textbook?
Not from here. There is no student, no fee structure and no fee ledger, so there is nothing to charge against. What the asset register gives you is the loss count per title per class, which is the list your fees process needs; the charge itself is raised wherever your fees live. If you invoice families as customers for other things, a book charge can be a line on such an invoice — but the link back to the register is a person carrying a number across.
How do we stop the register drifting from reality?
Dispose of the annual losses with a reason instead of leaving them on a custodian's balance. Books never returned that stay on the teacher's balance accumulate year on year until the register shows a teacher holding hundreds of copies that do not exist. There is no verification campaign or sign-off to catch that for you — an annual count is a manual exercise — so the discipline is the annual disposal, done deliberately.
Can a departmental store be the holder instead of a person?
Yes, and it is often the right answer. A custodian record can be typed as a department rather than an employee, so "Form 2 book store" or "Library" can hold a balance without inventing a person to blame. Use a person where somebody genuinely signed for the items, and a department where the accountability is collective — mixing the two arbitrarily is what makes a register hard to read later.
