There's a smarter way to build that league table, and it doesn't require wrestling with Excel's formula labyrinth. The problem here isn't the data, it's the tool. You've got a form feeding results into a spreadsheet, players appearing in either column, and a manual points field that needs cross-checking. That's a lot of conditional logic, lookup gymnastics, and error-prone manual verification. Excel can do it, but it will fight you the whole way.
The real issue is that your data is structured for collection, not analysis. Each row represents a match, but your league table needs player-centric totals. That means unpivoting the data, extracting Player 1 and Player 2 into separate rows, then aggregating points and holes won per player. In a traditional spreadsheet, you'd need a combination of INDEX-MATCH, SUMIFS, and possibly array formulas or a pivot table with calculated fields. And that's before you add conditional formatting to validate that the submitted points match the holes-won logic. It's doable, but it's fragile. One misplaced column reference or a new form field breaks everything.
An AI-native spreadsheet changes the equation. Instead of writing formulas that describe *how* to transform the data, you describe *what* you want. Something like: "For each player, sum points from all matches where they appear as Player 1 or Player 2, then sort descending by total points, and flag any row where points don't match holes-won logic." The tool handles the unpivoting, the aggregation, and the validation. You get a live league table that updates automatically when new form submissions arrive. No manual shuffling, no broken references, no second-guessing.
The conditional formatting check is the part that really reveals the gap. You want to ensure the points submitted are correct based on the holes-won data. In Excel, that means writing a rule that compares two columns, then applying it across hundreds of rows. In an AI-native environment, you simply ask: "Highlight rows where the points don't match the expected outcome from holes won." The system understands the relationship between the columns and applies the logic consistently. That's not a feature, it's a fundamental shift in how you interact with data.
Stop fighting the spreadsheet's limitations. The league table you want is a straightforward data transformation. The tool you're using makes it complicated. Explore an approach where the data works for you, not the other way around.