School Asset Registers: Labs, Buses, Dorms & the Equipment You Keep Rebuying
Labs, buses, kitchens, dormitories, sports stores — schools are asset-heavy institutions that replace what they cannot find. How to run registers with custodians, term checks, and maintenance that beats breakdown.
Walk any school in January and you will hear the same conversations: the lab is missing thermometers it bought in triplicate last year, the sports store's new balls lasted one term, two dormitory mattresses left over the holidays, and the bus is in the garage for something the mechanic mentioned in July. None of these are crises. Together they are a permanent tax — schools budget annually for equipment they already bought, because owning things is not the same as keeping them.
The school asset map
| Asset group | The specific risk | The control that works |
|---|---|---|
| Lab equipment | Small, valuable, walks easily | Departmental custodian + term-end verification against the register |
| ICT (laptops, projectors, tablets) | High value, high demand, loaned constantly | Issue/return records per loan — to named staff, not "the staffroom" |
| Kitchen & dining | Heavy use, quiet attrition | Annual count with condition notes; write-offs recorded, not assumed |
| Dormitory (beds, mattresses, lockers) | Holiday shrinkage | Pre-holiday and post-holiday counts per dorm, variance owned by the dorm master |
| Vehicles | The most expensive and least documented | Movement logs in the register; fuel-to-mileage and the service schedule on your own sheet |
| Sports & music | Seasonal use, off-season disappearance | Season-start issue to the department, season-end return count |
Custody: departments are not custodians
The register entry "30 microscopes — Science Department" guarantees exactly nothing. The entry that works is "30 microscopes — Mr. Otieno, Biology lab, verified 28 March". A named custodian signs for what they hold, hands over formally when roles change, and clears at exit — the same discipline that works in any institution, applied to chalk-dust reality. Teachers accept it quickly for one reason: it also protects them from inheriting other people's losses.
The term rhythm
- Term start: issue from stores to departments against the register — what the lab, kitchen, and sports office hold is now on record.
- Mid-term: spot-check one asset group, rotating — twenty minutes with a phone, using mobile verification.
- Term end: departments return or re-confirm holdings; variances explained while the term's memory is fresh.
- Holidays: dormitory and high-risk counts before the school empties, again before it refills.
Maintenance is an asset register feature
The bus service, the generator overhaul, the fire extinguisher dates, the science gas lines — schedule them against the asset, not against someone's memory. A school that services on schedule spends materially less than one that repairs on failure, and the difference compounds for a decade.
What the board should see annually
The one-page asset report
- Register value by group, with the year's additions and write-offs.
- Verification coverage: what percentage was physically confirmed this year.
- Variance summary by department — trends, not witch hunts.
- Maintenance compliance: scheduled vs completed, and the breakdown costs avoided.
- Replacement plan: what reaches end-of-life next year, budgeted from condition data instead of surprise.
Assets are one leg of school operations; the others — term procurement, stores, and fees — share the same governance spine. The school ERP buyer's guide shows how they fit together.
What AWRA OpsHub does today
- An asset register with serial number, purchase date and cost, status, warranty and retirement with a reason.
- Named custodians per asset — a teacher, a lab, a department — with full movement history.
- Assets created from stock through a recorded conversion.
- Offline-capable mobile capture, so a walk-round with a phone is workable.
- Role-based permissions and audit logging over every movement.
More we can add to your workspace
- A verification campaign: a term-verification workflow, a sign-off and an exception list. A verification round is a manual exercise you run and record as movements today.
- Maintenance scheduling, and a maintenance record: a service schedule, a due date, a reminder, and somewhere to log a service against the asset when it happens. Today the only representation is the asset's status, which overwrites.
- Depreciation, so the register will not reconcile to a written-down value without work outside the system.
- Barcode label printing built into the asset flow.
"Term verification by phone" overstated it: you can walk the school with a phone and record movements, but nothing drives a verification round or tells you which assets were missed. Until that exists, run verification as a named termly task with a checklist, and treat the register as the source you are checking against rather than the thing doing the checking.
Anything above that you need, we can build for you
Everything listed above as something we can add describes what ships in the standard product today — it is a starting point, not a limit on what AWRA OpsHub can do for your organisation. Kenya's eTIMS integration and its maintained payroll engine are both in the product because clients needed them and commissioned them; neither appeared by itself, and the same door is open for whatever you just read about. One qualification so this is worth what it claims: a small number of things on this blog we deliberately leave to a specialist rather than build — a statutory ledger we will not sign our name to, a rule that would decide a tax question for you, a clinical or member-funds record that belongs in a regulated system — and where that is true the post says so in those words. Everything else is a scope, a timeline and a price.
The operational work, which is what most commissions actually are
An extra approval stage in a chain that does not match the standard one, a custom field set on employees or assets that only your sector needs, an expiry that has to block an order rather than send an email, a report your board asks for in a shape nothing produces, or a scanner or weighbridge feeding the goods-in door. These are the commissions we are asked for most often and the smallest ones we quote — and unlike a revenue-authority pipeline, none of them waits on a regulator.
The module-shaped additions, which are the ones readers ask for most often
A price list with real discount authority, a customer-facing quotation that expires, a bill of materials or recipe costing, a staff advance that is issued, acquitted and chased, a member or unit ledger, a matching rule that holds a payment. Each of these is a build rather than a setting, and each has been quoted before — a bigger piece of work than a custom field, with a written spec and a date instead of a roadmap slide.
The report, document or pack nothing currently produces
The board pack in the shape your board actually asks for, a donor or funder layout, an invoice or receipt template carrying what your regulator or your customer expects, a dataset the report builder cannot reach yet. Usually the fastest thing on this list to deliver, because the data is already in the system.
Systems, rails and hardware you already run
The accounting package, CRM, online store, core banking or custom database you intend to keep — connected through our API so a fact is entered once and appears everywhere it is needed. Plus the physical edge: a scanner, a scale, a weighbridge or a till peripheral feeding the door it belongs to.
How it works: you describe the requirement, we return a written scope, timeline and cost, and once agreed it is built into your environment and maintained as part of the product. Nothing here waits on a regulator or a published specification, which is why operational builds are the ones we quote fastest. Tell us the requirement that would otherwise rule us out — that is a better first conversation than a demo.
Tell us what your operation needsStop rebuying what you own
An asset register with custodians, movement history and retirement reasons — walkable on a phone, across every department.
See school assets in AWRAFrequently asked questions
Textbooks too, or is that overkill?
Track textbooks as bulk stock per title per class, not as individual assets — issue counts at term start, return counts at term end, loss charged per the school's book policy. Individual tagging is for the atlas set and the teacher editions, not every copy.
Who runs the register in a school with no procurement office?
The bursar owns the register; departmental custodians own their holdings; verification is delegated per group (dorm masters, HoDs, the driver for vehicles). The system's job is making each person's slice small — twenty minutes a term, not a week in December.
How do we start when nothing has been tracked for years?
A whole-school count over one holiday — group by group, with photos and condition notes — becomes your opening register. Expect gaps against old purchase records; take the write-off once, with board approval, and measure from the new baseline. The alternative is another decade of the invisible tax.
Do donated assets need different treatment?
Register them like purchases, with the donor recorded and any conditions noted (some donations carry usage or disposal terms). Donors who see their equipment on a live register with photos tend to donate again — the register is quietly a fundraising asset.
