When a spreadsheet stops working for asset operations
For the assistant or manager whose tracker worked for six months and has quietly stopped.
Spreadsheets are good at the wrong half
A spreadsheet is an excellent way to hold a list of things and their attributes. Asset operations is not a list of things. It is a list of things that keep changing, each with work attached, money attached, documents attached and people attached, where the interesting question is almost always about the intersection rather than the list.
That is why the spreadsheet works for six months and then stops. Nothing broke. The job changed shape.
The signs, in roughly the order they show up
- A tab per asset. The moment there is one, "what is due across everything next month" requires opening all of them and reading by eye.
- Colour as data. Yellow means waiting, unless it means check with Sarah. The key is in somebody's head and it is not the same key everyone else is using.
- A second copy circulating. Someone emailed a version out and edits landed in both. Now there are two truths and no way to reconcile them.
- The date columns stop being trusted. Nobody has been through the registrations since March, so everyone checks the source document anyway, which means the column is decoration.
- Money that does not add up. One column for quoted and one for paid, and no agreed way to record a job that is done and unpaid, so it sits in both or neither.
- The person who maintains it goes on leave and the sheet visibly decays for three weeks.
None of those is a reason to panic. Together they mean the sheet is being asked to be a database by people who quite reasonably do not want to run one.
What a spreadsheet genuinely cannot do
Three things, and they are the ones that cost money:
- Tell you what changed. A cell edited is a cell edited. Who moved that date, when, and what was it before? Version history on the file is not the same as a record on the row.
- Hold two states at once. Work and money move independently: a service can be finished and unpaid, a deposit paid before anything starts. One status column forces a lie in one direction or the other.
- Show the same fact to different people differently. Your internal note and the vendor's job description are not the same text, and a shared sheet cannot hold that distinction without someone remembering to be careful.
What actually goes wrong
The failures are boring and expensive. A renewal that lapsed because it was on a tab nobody opened. An invoice paid twice because one person marked it paid in the sheet and another paid it from the inbox. A survey the insurer asked for, agreed in a call, and never written anywhere. A contractor who read a note they should not have seen.
Each of those is recoverable on its own. What is not recoverable is the reason they happened, which is that the record was a description of the work kept beside the work, rather than the place the work happened.
Before you replace it, do this
Whatever you move to, the migration is easier if you can answer these first, and answering them sometimes buys you another year of the spreadsheet:
- Which dates actually matter, and where is the document for each?
- What work is open right now, and who owns each one?
- Which money is committed and which is spent?
- Which of your people and which outside companies touch each asset?
If those four are hard to answer today, that difficulty is the thing to fix. A new tool with the same four gaps is the same problem with a better font.
What this looks like in Meridian
The intersection is the default rather than the query. Every module is a view over the same work: Operations is all of it, Maintenance is the servicing half plus the rules that raise it, Horizon is every dated thing on one runway, and the asset's own file is everything attached to that asset.
Work carries one stage and separately a money state, so done and unpaid is a state you can hold and count rather than a compromise. Blocked and waiting are flags, so an item can be underway and stuck on someone at the same time, which is what is actually true. Every change is recorded with who made it, and archived items stay on the record because for marine and aviation the history is part of what the asset is worth.
Money stays in the currency it was booked in and is never converted, so a US yard invoice and an Australian berth fee remain two figures rather than one invented one.
See how the operations view works, or read what to ask for in your first week, which is the same problem from the other end.
Run this across a whole portfolio.
Meridian keeps the dates, documents, owners and vendors for every asset in one operating record, so the work above stops living in a spreadsheet and an inbox.