When spreadsheets stop working for equipment maintenance

Spreadsheets are the universal starting point for equipment maintenance tracking — and that's fine. At 5 assets a single tab in Excel is the right tool. The friction is low, the cost is zero, and your foreman already knows it. The problem isn't that spreadsheets are bad. The problem is that they break in specific, predictable ways once the fleet grows past about 20 units. Here are the six failure signs we see over and over — and how to tell when your Excel/Google Sheets PM tracker has crossed the line from “working” to “the bottleneck.”

The six signs your spreadsheet has stopped working

1. PM dates drift. Nobody updates the row when service actually happens.
2. Concurrent edits collide.Two people open the file, one overwrites the other's changes.
3. Nobody knows which file is canonical. fleet_PM_v3_FINAL_REALLY.xlsx wins because it was emailed last.
4. Meter readings get fat-fingered. A decimal-point mistake turns 4,820 hours into 48,200.
5. Tabs proliferate.One tab per truck works at 5. At 20 you can't find anything.
6. Nobody trusts the data enough to act on it. You make decisions from your gut instead of the file.

Why each sign shows up at roughly the same fleet size

We see these six signs cluster between roughly 15 and 30 assets, almost regardless of vertical. The reason isn't the spreadsheet — it's the people. At 5 assets one person owns the file and the workflow lives in their head. Past 20 units, the workflow has to live somewhere multiple people can see and update simultaneously, and that's where a flat file starts to lose.

1. PM dates drift

The mechanic changes the oil on Truck 12 in the yard at 4:45 PM on a Friday. The PM tracker is on the office computer. Monday morning the spreadsheet still says “due,” the manager calls the mechanic, the mechanic says “I did it Friday,” and now nobody trusts the spreadsheet. After this happens three times the spreadsheet is a polite fiction.

2. Concurrent edits collide

Google Sheets fixes some of this (multi-user cursors). Excel on a network share doesn't — the second person to save wins, and the first person's morning of work disappears. Even with Sheets, two people editing the same row at the same time produces undefined behavior; the value that lands depends on who blinks first.

3. Nobody knows which file is canonical

Email a copy, then someone makes changes, then someone else forwards the old one. Six months in there are four files with almost-the-same name and the only person who knows which one is “the truth” is on vacation. We've seen fleets manage this for years; we've never seen anyone enjoy it.

4. Meter readings get fat-fingered

Spreadsheets do not validate. A driver types 48200 instead of 4820, the PM threshold for a 5,000-hour service trips immediately, the mechanic pulls the unit, the unit was nowhere near service-due — half a day burned because there was no “wait, that can't be right” check. The opposite is worse: a missed zero hides a unit that's actually overdue.

5. Tab proliferation

One-tab-per-truck is the most common mistake. It feels organized at 8 units. At 25 units the tab bar is unreadable, the cross-tab rollup formula is fragile, and adding a new column to “all trucks” means editing 25 sheets by hand. The shop foreman gives up trying to add the column and starts tracking the new field on a sticky note.

6. Nobody trusts the spreadsheet enough to make a decision

This is the terminal sign. When the owner asks “which unit should we sell?” and the answer is “let me ask the mechanic what he thinks” instead of “let me check the cost-per-hour column,” the spreadsheet has already failed. It still exists. It still gets updated. It's no longer the source of truth — the mechanic's memory is.

What replaces it

The thing that replaces a spreadsheet isn't a fancier spreadsheet. It's a system with three properties Excel structurally can't give you:

• Real concurrency.Two people editing the same asset at the same time both see each other's changes, with row-level locks, not last-write-wins.
• An audit trail.Who changed what, when, and from where. You can answer “why does this row show 48k hours” without polling everyone in the shop.
• A single source of truth.One URL. The office and the yard hit the same record. There is no “v3_FINAL” because there is no file.

Why this doesn't have to mean an enterprise rollout

The bad news historically was that the spreadsheet replacement was a CMMS suite with a $40k implementation, a consultant, six weeks of onboarding, and a per-seat model that punishes you for having a crew. We watched a lot of shops postpone the replacement for years because the replacement cost was worse than the spreadsheet pain.

That math has changed. A modern lightweight system designed for the 25-asset fleet onboards in an afternoon, prices the whole org flat (not per-seat), and doesn't require IT to deploy. The decision point isn't “spreadsheet vs. SAP” anymore. It's “spreadsheet vs. a sensible step up.”

How DirtFleet fits

DirtFleet was built for the fleet that's hit these six signs and needs to move off Excel without buying an ERP. Flat pricing per org (not per-seat), a mobile app operators use in 30 seconds (hour logs queue offline when signal drops), a real audit trail, and full export endpoints so you're never trapped in our format either.

We don't pretend it's for everyone. If you have 5 assets, stay on the spreadsheet — the friction isn't worth it yet. If you have 500 assets and a procurement team that wants SAML SSO and a dedicated account manager, you're ahead of where we are today. Between those two ends is the sweet spot we built for.

→ The 25-asset fleet: why this size is the sweet spot · → No data lock-in: every endpoint that lets you leave · → Pricing