An asset register that survives a staff change

The test is a resignation, not an audit

Most asset records are built for an owner's question, which is "what did that cost". The harder test is a person leaving. The estate manager who has been there six years, the captain who knows which bilge pump is temperamental, the assistant who knows which invoices go to the accountant and which go to the family: when one of them leaves, the register either carries what they knew or it does not.

Almost every register passes the audit and fails the resignation. The facts are there. What is missing is the state: what is open right now, what is due next month, who was going to do it, and what was decided and never written down.

Start from the questions, not from the fields

A register designed as a list of fields grows forever and answers nothing. Design it backwards, from the half dozen questions someone actually asks:

• What do we own, and where is it right now?
• What has to happen on it, and when?
• Who is responsible, and who is doing the work?
• What is it costing, and what is owed?
• What paperwork exists, and when does it expire?
• What is stuck, and who is it stuck on?

If a field does not help answer one of those, it is a field somebody will stop filling in within a quarter. That is not laziness; it is the register telling you it was never load-bearing.

The four layers worth separating

Registers that fall over usually collapse these into one sheet:

1. The asset, which changes rarely. Identity, registration or hull or VIN numbers, make and model, where it is based, who owns it on paper.
2. The work, which changes constantly. What is due, what is underway, what is blocked and on whom.
3. The money, which is a separate axis from the work. A job can be finished and unpaid, or paid before it starts.
4. The people, meaning both your team and the vendors, with what each is actually responsible for.

Keeping them separate is what lets you answer "what is due this month across everything" without opening four spreadsheets, and it is what stops one person's naming convention becoming institutional knowledge.

Dates are the part that decays

Every asset carries dates that expire whether or not anyone is looking: registrations, insurances, certificates, licences, inspections, warranties, contracts and their notice periods.

Two habits make that list useful rather than decorative:

• One list across all assets, sorted by date, not one list per asset. Sorted per asset it reads as several tidy short lists and hides the fortnight where four things land together.
• Record where the document lives, not just when it expires. A date with no document behind it means the next person has to find the paperwork before they can act on it, and finding it is most of the work.

Write down what was decided

The single most valuable thing in a well kept register is not a date. It is a short note saying why something is the way it is: why the yard was changed, why that quote was declined, why the insurer asked for a survey, why the pool contractor is on a different arrangement from the gardener.

Those decisions live in people's heads and in email threads nobody else can find. They are also what a successor most needs, because without them they will either repeat a settled argument or quietly undo a decision that had a good reason.

What it costs to keep

Be honest about maintenance. A register nobody updates is worse than none, because people trust it and it is wrong. The realistic minimum is:

• Updating the work as it moves, not weekly in a batch
• Adding a document when it arrives rather than at the annual tidy-up
• Reviewing the expiry list once a month
• Correcting the register when reality disagrees with it

If that sounds like more discipline than the current arrangement can carry, the answer is a smaller register rather than a more ambitious one. Fewer fields, maintained, beats more fields, abandoned.

The handover itself

When someone does leave, the handover is a conversation over the register rather than instead of it. Walk it together: every open item, every date in the next quarter, every vendor and what they are contracted for, and every decision note that needs explaining.

Anything the leaver has to explain from memory is a gap in the register, and the handover is the last moment anyone will be able to close it. Write those down as they come up, during the conversation.

What good looks like

Someone competent, on their first week, can answer from what is written down: what we own, what is due in the next ninety days, what is open and on whom, what each thing costs, where the documents are, and what was decided and why.

That is the standard, and it is not exotic. It is just numerous.

What this looks like in Meridian

The four layers are four facets of one record rather than four systems. An asset carries its identity and its current state; the work on it carries a stage, an owner and separately a money state; the documents attach to the work or to the asset; the people are recorded against the work they actually do.

The expiry question is a screen rather than a report. Horizon puts every dated thing from every source on one runway, across all assets and sorted by date, and tells you which of those expiries has no work raised against it yet, which is the gap a per-asset list hides.

Nothing is deleted. Archiving hides a record from the working views and keeps it, because for marine and aviation the service history is part of what the asset is worth, and because the successor's question is usually about something that finished years ago.

See how the operations view works, or read who is responsible for what, which is the half of this that people argue about.