From an unlistable estate to a register that holds up
Representative scenario — illustrativeA 2,000-student campus spread over three blocks owns science labs, an auditorium, a bus fleet and gensets — and “what do we own, and where” is answered by walking the corridors.
Physical verification is reinvented from memory at every audit. The generator’s last service is a guess until it fails mid-exam. The auditorium gets promised to annual-day rehearsal and the inter-school match on the same evening, and the clash is discovered on stage.
The budget ERP handed them an item list — a spreadsheet with a login. No location tags, no maintenance schedule, no depreciation, and no facility calendar at all. Six months in, AMC dates still live in a diary, the hall is still double-booked, and the admin officer is back to walking the blocks before the auditor arrives.
ez.school makes the register the source everyone trusts — assets carry category, location, value and depreciation, and maintenance surfaces what is due before it breaks. Shared facilities book on a calendar where a clash is impossible to save, so the annual day and the match never meet on one stage.
| By hand | Ordinary ERP | ez.school | |
|---|---|---|---|
| Physical verification | Invented from memory each audit | A flat list, no locations | Scan a location’s own list |
| Maintenance | Serviced only after it breaks | No schedule — dates in a diary | Due-list surfaces before failure |
| Booking a facility | Two events, one stage | Not covered at all | Clashes impossible to save |
| Book value | Recomputed by hand | Cost only, no depreciation | Depreciation by category policy |
- One listAssets located
- Before it failsMaintenance surfaced
- ZeroDouble-bookings
Fiction turns 4× a term; reference sits idle — rebalance the acquisition budget toward what moves.
The register by location and category — physical verification becomes reading each location’s own list, not inventing one on the day.