If you manage a team of 5 or more people across multiple projects, your resource tracker is probably a spreadsheet. It might even be a good one. Someone on your team spent a week setting it up, the formulas work, the columns line up, the conditional formatting highlights overallocations in red.
And it still can’t answer the questions you actually have.
The Spreadsheet Ceiling
A client of mine builds templates for the PM market. He came to me with two sheets he’d been using for years — a planned-vs-actual hours tracker and a resource assignment matrix. Both were polished. Both held real data. Both failed him the moment he needed to look at that data from a different angle.
Here’s what spreadsheets do well: they hold a grid. A row per person, a column per day, a number in every cell. You can read left-to-right and see a week. You can read top-to-bottom and see the team. That’s it. That’s the whole shape.
Here’s what a PM actually asks:
- Who’s free Thursday?
- What is John working on this month?
- Is the team overallocated next week?
- How much unplanned work did we absorb this month?
- Which projects are eating the most hours?
Every one of these questions requires rearranging the grid. And spreadsheets don’t rearrange. They get filtered, copy-pasted, exported to pivot tables, or — more often — ignored until someone asks the question in a meeting and the PM says “let me get back to you.”
That’s the ceiling. Spreadsheets hold data well. They don’t serve it back to you in the shape you need.
What Actually Works
Resource management needs three things a spreadsheet can’t give you together:
Fast daily input. Because PMs enter hours every day and nothing slows adoption faster than a clunky input flow. A spreadsheet gets this part right — click the cell, type the number, done. Any replacement has to match that speed.
Multiple angles on the same data. The week view, the person view, the project view, the month view. Not four separate sheets. The same data, reshaped on demand.
A person-level source of truth. One place per team member where everything about that person lives — their assignments, their utilization, their overallocations. Not a row in seven different tabs.
The client I worked with had all three problems. His utilization sheet handled input fine but couldn’t show a person’s month without manual filtering. His assignment matrix used checkboxes for a week, and extending it to a second week meant copying the entire block. He couldn’t see his team from any angle except the one he originally designed for.
I rebuilt both sheets as a connected Notion system. Three databases: utilization, assignments, and a per-person dashboard. The input stayed manual — because that’s what PMs expect and what the client asked for. What changed was the viewing layer. The same numbers could now answer “who’s free Thursday” without a single new entry. Filters replaced copy-paste. The per-person dashboard replaced tab-hopping.
What Most PMs Get Wrong About Replacing Spreadsheets
Two mistakes show up in almost every team that tries this on their own:
They automate the input. They build forms, rollups, timers, auto-calculations — and then wonder why no one uses the system. Manual input isn’t the problem. Manual filtering is. Keep the input fast, fix the output.
They copy the grid. They rebuild the exact same wide-grid layout in Notion and call it done. Notion can hold a grid, but that’s the weakest thing it does. The whole point is that data doesn’t have to live in one shape. If your Notion system looks like your spreadsheet, you’ve just made a slower spreadsheet.
The fix for both is the same: split the data into connected databases, keep input simple, and let the views do the work.
What I Learned
Resource tracking hits the spreadsheet ceiling faster than almost any other PM workflow. Because resource questions are always multi-angle — who, what, when, how much — and a grid can only show one angle at a time. If you’re managing a team of 5 or more and you find yourself dreading the “quick question” about availability, that’s the ceiling talking. It’s not your spreadsheet that’s broken. It’s the shape.