When Your Art Inventory Outgrows Your Spreadsheet

There is a quiet moment every spreadsheet user knows. You are staring at a file that once felt simple, a clean grid of columns and rows, and suddenly it is not simple anymore. The artist cataloguing four years of botanical illustrations hit that moment when the row count passed 300 and the questions started multiplying faster than the entries. What started as a list of titles and mediums now demands to be seen by client name, by deposit date, by revision round, by availability. And the spreadsheet, once a faithful servant, has become a wall. This is not a problem with the person. It is a problem with the shape of the data. The artist is wrestling with something fundamental: records that do not share the same fields. A commissioned piece carries client names and deposit dates. A piece made for the shop does not. Cramming both into one flat table means columns full of blanks, a kind of negative space that quietly erodes the usefulness of every row. Splitting them into separate sheets solves the blank problem but breaks the overview. The artist is caught between two imperfect structures, and the instinct to reach for XLOOKUP or SUMIFS is understandable, but those tools only work well when the underlying structure is sound. You cannot query your way out of a design flaw. This echoes a tension we have seen before, such as in Beyond Similarity Scores: Deduplicating Data with Deterministic Stages, where the hard part is not computing a score but deciding what the score means. Here, the hard part is not writing a formula but deciding what a row means. The honest answer is that neither option the artist proposed is right, and that is the point. This is not a binary choice between one flat table and two separate ones. It is a prompt to step back and ask what the data actually is. A commissioned piece is not a variation of an available piece. It is a different entity entirely, with its own lifecycle and its own obligations. Forcing them into the same schema is like asking a poem and an invoice to share a page. The better structure is probably a core table for the artwork itself, holding the fields that are genuinely universal, and then a linked table for commission-specific details, tied by an ID. That way the availability overview survives because it lives in the core table, and the commission details live where they belong, out of the way but always reachable. This is a pattern familiar to anyone who has worked with relational thinking, even if they have never used a database. It is also a lesson that applies beyond art. When a tool starts to feel like it is holding you back, the answer is rarely to work harder inside it. The answer is to reconsider the structure you are pouring your effort into. We saw a similar dynamic in Excel not filtering unique values, where a simple task became a headache because the data was not shaped for the question being asked. What we would tell this artist, and anyone else feeling that wall close in, is to stop optimizing the current layout and start questioning it. The spreadsheet is not the source of truth. The artwork is. The spreadsheet is just a lens, and a lens that distorts is worse than no lens at all. The moment a file stops supporting the questions you want to ask, that is the signal to restructure, not to add more columns or build a cleverer lookup. The artist is right to feel that something is wrong. That feeling is data too. The practical takeaway is simple: when records diverge in shape, split them by entity, not by convenience. Keep the universal fields together, park the special cases in a linked table, and let the overview follow from there. The alternative, tolerating a broken structure because it is familiar, is a cost that compounds with every new row. And in a catalogue of four years of work, that is a price no one should keep paying.