Simplify Location Incident Tracking Across Multiple Sites

To streamline your data analysis across multiple locations, you can create a function that aggregates incidents per individual rather than by site.

3 min readMicrosoft Excel | Help & Support with your Formula, Macro, and VBA problems | A Reddit Community

This reader's post captures a familiar frustration: the spreadsheet that should be simple, but isn't. They have 20,000 entries, 300 individuals, and nine sites that collapse into four locations. They've already written two unique functions and a SUMIFS. And still, the answer they need, total incidents per person per location, not per site, remains out of reach. We think this is exactly the kind of problem that reveals the limits of traditional spreadsheets, not the limits of the person trying to solve it. The user hasn't failed. The tool has.

The real issue here isn't the complexity of the data. It's the structure. When a location is spread across three sites, and those sites live in a separate lookup table, a standard formula has to manually connect those dots. The user is essentially building a relational database inside a grid of cells. That works for small datasets. For 20,000 rows and 300 individuals, it becomes a maintenance burden. Every new site, every new person, every new incident requires the user to revisit and revalidate their formulas. The spreadsheet becomes fragile. One mistyped reference and the totals shift silently.

What this person needs is a system that understands the relationship between sites and locations as a first-class concept, not as a manual lookup. An AI-native spreadsheet can do that. It can recognize that "Site A," "Site B," and "Site C" all belong to "Location 1" because that association is already defined in a separate table. It can then aggregate incidents per person at the location level without the user having to chain functions together. The solution is not a better formula. It's a smarter foundation, one that treats data as connected, not isolated.

We see this pattern often. Users spend hours building workarounds that a modern tool could handle in seconds. The frustration is real, and it's not the user's fault. The spreadsheet model was designed for a world where data stayed in one sheet, one table, one place. That world is gone. The tools should follow. For anyone managing multi-site incident tracking, the practical takeaway is this: if your spreadsheet is fighting you, it's time to look for a tool that treats your data the way you already think about it, connected, contextual, and ready to answer the question you actually asked.

From Microsoft Excel | Help & Support with your Formula, Macro, and VBA problems | A Reddit Community

So, I've run two unique functions and then a sumifs function to generate a frequency counter for events happening at a location per person.

Problem is, the "location" is actually 3 diffrent sites, (some are 2, some are 1). The site to location actually has it's own table.

Read the original at Microsoft Excel | Help & Support with your Formula, Macro, and VBA problems | A Reddit Community