Why Your Tracking Spreadsheet Breaks at Fifty Records

Nearly every team tracks its first matters in a spreadsheet, and that is sensible: it is free, flexible and everyone knows how to use it. The trouble starts somewhere around fifty records. Not because the software cannot hold more rows, but because the way people use a tracking sheet stops matching the work. Here are the five places it breaks, in the order most teams notice them.

1. The notes column

A row has one cell for notes. After a few months that cell holds a paragraph of dated updates, pasted email fragments and abbreviations, all in a box that shows two lines at a time. Nobody can read the history of a matter without expanding the cell, and nobody can tell who wrote what. The history of the matter is technically there and practically lost.

2. Columns that mean different things

With ten records, one person fills in the sheet and knows what "Status" means. With fifty, three people fill it in, and "pending" means waiting for the client to one of them and waiting for payment to another. Dates appear in three formats. Someone adds a column for one kind of matter that is empty for all the others. Sorting and filtering, the whole point of a spreadsheet, start returning nonsense.

3. Files live somewhere else

The row holds the facts; the documents are in a folder, the emails are in an inbox, and the link between them is a file path or a reference someone typed. Links rot when folders are renamed. Answering "do we have the signed agreement for this one?" means leaving the sheet and searching.

4. Everyone can see everything

A shared spreadsheet is all or nothing. The person who needs access to five rows can see all fifty, including the sensitive ones. You can split the sheet, but then totals and overviews break. Most teams quietly accept the exposure, which is fine until a matter turns up that really should have been restricted.

5. Nobody knows who changed what

Someone overwrote a date. Someone sorted one column without the others and scrambled three rows. Version history helps if you know when to look, but a spreadsheet has no idea that row 37 is a matter with a history. It only knows cells.

What to change before the next hundred

• Give each matter its own record, with a dated notes history rather than a single cell. Good notes are covered in how to write a case note that lasts.
• Fix the fields. Define each column once, with allowed values for status and a single date format. Remove columns that apply only to some matters, or split those matters into their own type.
• Keep documents with the matter, not in a parallel folder tree.
• Control access per matter, not per sheet.
• Keep a history the system writes, so changes are attributable.

You can get part of the way by adding discipline to the spreadsheet: data validation, protected columns, a separate notes tab. At some point the discipline costs more than a tool built around matters would. That point is usually earlier than people think, and the signs are the five above. The underlying model is explained in what case management means in plain English.