Fleet records: why spreadsheets break after 10 cars

We do not think spreadsheets are evil. They are a fast, flexible and free tool, and almost every rental company starts with one — that is normal. The problem is not spreadsheets as such but the fact that they have quite specific limits of applicability. Those limits usually run somewhere around ten cars and a second employee, and crossing them almost never gets noticed in time.

What exactly breaks

• Concurrent work: two people edit the same row, and whoever saved last wins.
• No relationships: the "car" row knows nothing about the "fine" row on another sheet beyond a registration number typed in by hand.
• No history: who changed the return date and when is impossible to establish.
• No constraints: nothing stops you from booking a car that is already taken or sitting in the workshop.
• No roles: the mechanic who is looking at servicing has the whole financial sheet open.

The first symptom is reconciliation

The easiest way to tell that the spreadsheet has stopped coping is one sign: you have developed a regular reconciliation ritual. Once a week someone sits down and checks whether the bookings sheet matches reality, whether all returns are marked, whether a car has got lost between statuses. That work creates no value, it only compensates for the fact that the system does not hold its own state. An hour a week turns into a day a month.

What a database does instead of a spreadsheet

In an accounting system the car, the booking, the contract, the fine and the servicing record are not rows on different sheets but linked objects. From the car's card you can see its whole history; from a booking — the contract and the deposit; from a fine — the rental period and the client. This is not "prettier", it eliminates a whole class of errors where the data exists but cannot be found. We described how this set of entities is arranged in Auto555 on Auto555 and in the Auto555 project breakdown.

Access rights — something a spreadsheet has none of

In a spreadsheet access is binary: either the file is open to a person in full or it is not. In a rental company with several employees that is both inconvenient and unsafe. Roles and rights let you give the manager work with bookings, the mechanic servicing, the accountant invoices and corporate clients, and the owner everything. Plus an audit log that records changes and two-factor protection of accounts. Our approach to this is described on cybersecurity.

Multiple branches: when the spreadsheet multiplies

A separate stage of degradation is the appearance of a second location. Usually the spreadsheet is simply copied, and from that moment two versions of the truth exist that only converge in a report once a month. A system with branch support solves this differently: the data is shared, and the branch split is a property of the record, not a separate file. The owner sees the whole fleet, a branch employee sees their own area.

The migration: how not to give yourself a month of hell

The most common mistake when moving is trying to migrate the whole history. Don't. Enter the current fleet and the current bookings and run new deals entirely in the system. Leave the history in the spreadsheet as an archive — you will need it rarely, and in six months you will not need it at all. A migration like that takes an evening, not a quarter, and does not require stopping work.

When to move and what it costs

The practical rule of thumb is simple: if you have more than five to ten cars or more than one person working in the system, the spreadsheet is already in the way. The free Standard plan covers up to five cars and one user, Premium at 2 990 ₽ a month covers up to twenty cars and three users, and Corporate at 10 990 ₽ removes the car limit. The product itself is at auto555.ru, general questions go through technical support.