How to Build and Maintain an Asset Register for a School

An asset register sounds like a corporate artefact and is actually the most practical document
a school estate can have. It answers the questions that otherwise get answered by guesswork:
what do we have, where is it, how old is it, and what has happened to it.

Most schools do not have one, or have one that was compiled once by a consultant and has been
fiction for years. Both situations are fixable in about a day of walking.

Walk the site once, and write down what you see

Start with a notebook or a phone, not a template. Go building by building, room by room, and
record the things that will cost money when they fail.

You are not inventorying furniture. You are looking for: heating and hot water plant, ventilation
and air conditioning units, electrical distribution, water storage, lifts and hoists, fire
systems, roofing by section, external doors and security, kitchen equipment, and anything with a
motor.

A medium school takes a few hours. Two people go faster than one, because one writes while the
other looks.

Six fields, and resist the seventh

For each item, record:

1. Identifier — a simple code you invent. Building, room, sequence.
2. What it is — plain description, plus make and model if visible.
3. Where it is — specific enough to find without asking.
4. Roughly how old — a year, a decade, or "unknown" honestly recorded.
5. Condition now — your own judgement, three levels is plenty.
6. Notes — anything a successor would want to know.

Every additional field reduces the chance the register is ever completed or updated. Teams
routinely design a twenty-column register, fill in three rows, and abandon it. Six columns
completed for the whole estate is worth incomparably more.

Write the identifier on the thing

This is the step that gets skipped and the one that makes the register usable. Put the code on
the asset physically — a label, a marker, a tag.

Without it, every future reference involves someone describing a location in prose, and the
gap between the register and reality opens immediately. With it, a report can name the item, a
contractor can confirm which unit they worked on, and evidence can be filed against something
unambiguous.

Record "unknown" rather than guessing

There is a strong pull toward filling every cell. Resist it for age and condition in particular.

A register with honest gaps is a working document that tells you where to look. A register with
invented dates is worse than none, because decisions get made on it and nobody knows which
numbers are real.

Mark unknowns clearly and fill them in opportunistically — when a contractor opens a unit, when
a nameplate is found, when a file turns up.

Update it as a by-product of work

The register decays if updating it is a separate task. It stays current if it is touched
whenever work happens.

Make it a small step in closing a job: if the work changed an asset — replaced, repaired
significantly, condition altered — update the row. One line, at the moment the job closes, by
the person who already has the information.

Anything that requires a periodic review to catch up will drift, because the review is always
the thing that gets dropped in a busy term.

Use it for the one decision it is best at

The register earns its keep the first time you face repair-versus-replace. Age, condition, and
the history of work against that identifier together answer a question that is otherwise
argued from impressions.

That is also the argument for filing maintenance records against the asset identifier rather
than only by date. Cost history per item is the single most persuasive evidence available when
asking a board to fund a replacement.

Review it once a year, briefly

Once a year, walk the estate again with the register in hand. You are not re-surveying — you
are checking that what is listed still exists, that nothing significant has appeared, and that
condition ratings still look right.

An hour or two, once a year, is what keeps it from becoming the consultant's document that
nobody trusts.