A school does not have a warehouse. It has corridors, shared laboratories, a gym, a stack of rooms that get rearranged every September, and a staff whose job is teaching rather than counting. That is why asset projects in education fail in a way that warehouse projects rarely do: the technology works, and the organisation quietly gives up on it.
Why school assets are hard to count
The difficulty is distribution and custody, not read range.
- Assets sit in rooms that are locked, shared, repurposed or temporarily occupied by another department.
- Custody is informal: a projector moves from room twelve to the lab and nobody records the move.
- The register was built from purchase orders, so it describes what was bought rather than what exists.
- One annual count consumes weeks of staff time and produces a variance list nobody has capacity to resolve.
- The realistic target is continuous control of high-value items, not a perfect count of every cable.
Tag placement by asset class
A tag that falls off in the first term costs more than the tag.
- Laptops and tablets: tag inside the battery compartment or under a screw-fixed cover, never on the lid.
- Projectors and instruments: tag the chassis, away from vents, lamps and heat sources.
- Furniture: tag under the seat or on the rear face, where cleaning does not scrub.
- Small kit and adapters: tag the container rather than the item, or accept a high loss rate.
- Textbooks and consumables: keep them out of the RFID register and count them another way.
The asset register is the real project
Tagging is the easy half; cleaning the register is the half that decides success.
- Reconcile duplicates, already-disposed items and items that were ordered but never delivered before any label is printed.
- Define the asset identifier scheme first, and keep it stable across years and suppliers.
- Hold one record per physical object, with a status that includes lost, disposed and in repair.
- Link the tag identifier to the asset record, not to the purchase order line.
- Assign a custodian per room, because an asset without a custodian is an asset nobody counts.
A counting calendar that respects the school year
The calendar is a design constraint, not an administrative detail.
- Do the main count before term starts, when rooms are empty and staff are on site.
- Run a light rolling check each half term for high-value categories only.
- Never schedule a full count during exam weeks; the data quality collapses and goodwill with it.
- Use the summer closure for the deep audit of laboratories and storage rooms.
- Align the calendar to the finance year if it differs from the academic year, and say so in writing.
Classrooms: handhelds beat fixed readers
Doorway readers sound modern and generate unusable data.
- A handheld pass through a classroom takes minutes and produces a room-level list immediately.
- Fixed readers at every door produce enormous event volumes with no custody context.
- Walk a defined route per floor, so coverage is repeatable and gaps become visible.
- Read at reduced power so the corridor and the adjacent room are not captured.
- Photograph exceptions on the spot, because the photo is the evidence for a later write-off.
Laboratories: custody matters more than quantity
A lab has fewer assets and much higher value per unit.
- Instruments move between rooms more often than furniture does, and usually without a record.
- Require a scan on issue and return, tied to a named person and not just to a room.
- Keep the most sensitive items in a locked store with a reader at the door.
- Check calibration and maintenance records against the physical item during the count.
- Treat an instrument found in an unregistered location as an incident, not as a rounding error.
Loans, moves and phantom assets
Most variances are moves, and the fix is a fast move transaction.
- Give staff a two-tap way to record a move from a phone, or the register will drift again within a term.
- Reconcile inter-campus and inter-school loans monthly; they are the classic source of phantom assets.
- Age a variance before escalating it, because a two-week-old move is not a missing asset.
- Write off only after a documented search and a second, independent count.
- Report moves and losses separately, or the loss rate will look worse than it is and nobody will trust it.
Disposal, transfer and audit trails
Disposal is a financial event, and auditors read trails rather than counts.
- Require an approval step before an asset leaves the register, not just after.
- Remove the tag physically and record the removal, or it will reappear as a ghost read.
- Keep disposed assets in a separate view, never mixed into the active list.
- For transfers, record both the sending and the receiving confirmation.
- Design the system for the audit trail, because that is what an inspection actually asks for.
Staff who are not warehouse staff
Adoption is a usability problem before it is a technology problem.
- Teachers will not adopt a tool that adds five minutes to a lesson changeover.
- Train one asset champion per building rather than every member of staff.
- Keep the handheld app to three actions: find, move, count.
- Explain the benefit in their terms: fewer lost projectors, faster replacements, less arguing in September.
- Accept uneven adoption and design the process so one untrained person cannot corrupt the register.
Metrics and a realistic rollout
Measure whether the school can now answer where an asset is, not whether the tags are clever.
- Track count duration, variance rate, time to resolve a variance and the share of assets with a named custodian.
- Start with one building and the laptop fleet, which has the clearest ownership and the highest value.
- Expect the first count to produce a large variance list; that is the register being corrected, not the project failing.
- Publish results to finance, because the budget argument is what sustains the programme after the pilot.
- Aim for a monthly cycle on high-value items rather than an annual count of everything.





