The nonprofit's request is a classic case of good intentions meeting bad architecture. Giving each grant its own tab might feel organized, but it actively works against the very thing they need: a clear, consolidated view of their entire portfolio. This approach guarantees manual work, repeated errors, and a dashboard that requires constant, fragile maintenance.
The core problem isn't the data itself, it's the structure. Each tab creates a silo. To build a dashboard, you would need to write formulas that pull from every single sheet, and every new grant means updating those formulas. The moment a grant's scope changes or an expense is reclassified, the whole system risks breaking. The user is left troubleshooting spreadsheets instead of managing grants. There is a smarter path. The solution is a single, well-designed data table. One sheet, one set of columns. Every grant becomes a row. Columns should capture the fixed attributes, grant amount, funder, start and end dates, alongside the dynamic ones like cumulative costs and allowed activities. This is the foundation that makes dashboards possible, not a chore to work around.
This shift requires a conversation with the team. The instinct to compartmentalize is strong, especially when grants have very different rules. But a single table does not mean losing detail. A column for "allowed activities" can use a simple tag system, text or a dropdown, that the dashboard can filter and count. A column for "scope of services" can hold a brief description. If a grant truly needs its own detailed ledger for line-item costs, keep that as a supporting tab linked by a unique grant ID. The main tracking sheet remains the single source of truth. The user can build pivot tables and charts directly from that one table, and every new grant is just a new row.
Start with the end in mind. Ask the team what one question they want answered most: total grant funding active this quarter? Percentage of budget spent? Number of grants that allow indirect costs? Design the single table to answer that question first. Then add columns only as they prove necessary. This is not about losing control of the details. It is about designing a system that surfaces insight without demanding constant manual reconciliation. The single table is the tool that transforms tracking from a burden into a strategic advantage.