Stop Using Spreadsheets to Track Things That Aren't Numbers
I get a version of this question constantly: "Is there a way to track this without building something custom?" Usually "this" is a spreadsheet somebody put together two years ago that quietly became the unofficial system of record for something important — client onboarding, equipment, vendor contracts — and now everyone's afraid to touch it because nobody's sure what breaks if they do.
My answer is almost always the same: yes, and it's already sitting in your subscription. It's called Microsoft Lists, and most of the businesses I work with have never opened it.
How a Spreadsheet Becomes an Accidental System
Here's the pattern I see over and over. A spreadsheet starts as one person's way of keeping track of something. It works fine — until two more people start using it, because it's the only place the information lives. Then someone emails a copy to a client by mistake. Someone filters it and forgets to clear the filter before saving, so the next person opens it thinking half the data is gone. Someone adds a column that breaks a formula three tabs over. Nobody designed this to be a shared system. It became one by accident, and now everyone's stuck maintaining something nobody actually built.
That's not a spreadsheet problem. Excel does exactly what it was built to do — math, modeling, analysis. The problem is using it for something it was never designed for: tracking the status of things. Who owns this. What stage it's in. What's overdue. A spreadsheet tracks values in cells. It doesn't have a concept of a lifecycle — submitted, in progress, complete — and that distinction is the entire reason Microsoft Lists exists.
The Difference Between a Spreadsheet and a Record
Microsoft Lists is a structured data tool built natively into Microsoft 365. It lives inside SharePoint and Teams, which means it's available to everyone on your plan at no extra cost, automatically version-controlled, accessible from a browser or the Teams app, and shareable with specific people instead of "whoever has the file." Multiple people can edit it at the same time without file conflicts, without someone stuck in read-only mode, and without anyone accidentally overwriting someone else's row.
The real shift is that Lists treats each row as a record with a lifecycle, not a spreadsheet cell. A record can move from submitted to in-progress to complete. A cell just holds whatever you typed into it.
Three Things I Build With Lists Constantly
A client onboarding tracker. Every new client goes through the same steps — contract signed, credentials collected, kickoff scheduled, first deliverable sent. Build a list with those steps as columns and clients as rows, assign ownership to each step, set a color-coded status, and anyone on the team can see exactly where a client stands without asking around.
An IT or facilities request queue. Someone needs a new laptop, a desk moved, software installed — they submit a request through a simple form connected to the list. It shows up automatically. You assign it, work it, close it. No email threads, no sticky notes, no "did you ever hear back on that?"
A vendor or contact registry that doesn't go stale. Columns for contract renewal date, primary contact, service category, account status. Filter to show only the vendors whose contracts expire in the next 90 days, and you've turned a static list nobody checks into something that actually flags what needs attention.
The Feature That Actually Changes the Workflow
The businesses that stick with Lists almost never start by importing their existing spreadsheet as-is. They start by asking what stage each row is actually in — because that question is what a spreadsheet can't answer and a list can.
Once that's in place, the feature that changes how a team actually works is views. The same underlying data can display as a grid for data entry, a gallery of cards for visual browsing, a calendar by due date, or a Kanban-style board for status tracking — and everyone can use whichever view fits how they think, without the data ever getting out of sync between them. Add conditional formatting on top — rows that turn red when a deadline passes, yellow when something's in review, green when it's done — and nobody has to ask where things stand. The list tells them.
Getting Started Takes About Ten Minutes
Open SharePoint or Microsoft Teams. In Teams, click the plus sign at the top of any channel and add the Lists app. Choose "New list," pick a template if one fits, or start from scratch. If your team can use Excel, they can use Lists — the learning curve is genuinely that shallow. The difference is that Lists is built for tracking, not calculating.
You're Already Paying For This
Microsoft 365 Business Standard includes Microsoft Lists at no additional cost — see exactly what's included at each subscription tier if you're not sure which plan your business is on. If you're managing any kind of process — onboarding, support, procurement, project tracking — with a shared spreadsheet, there's a better tool already in your subscription, and it was built specifically for this.
The businesses that get the most out of Microsoft 365 aren't the ones with the biggest budgets. They're the ones who actually use what's already there — which is the whole premise of this series. Start with the post that maps out the rest of your subscription if this is the first time you're hearing that.
Frequently Asked Questions
Do I need any technical skill to build a list? No. If you can build a spreadsheet, you can build a list. Templates handle most of the setup, and the column types — text, choice, date, person, yes/no — cover almost everything a small business tracker needs without any configuration beyond picking from a menu.
Do I have to abandon the spreadsheet I already have, or can I migrate it? You can import an existing spreadsheet as a starting point, but I usually tell clients not to. A direct import brings the spreadsheet's bad habits with it — no lifecycle, no status column, cells instead of records. Rebuilding it as a list, even a simple one, is where the actual value shows up.
What if my team is used to Excel and resists switching? This is normal, and it's usually not really about the tool. Show them the outcome, not the feature list — "no one has to ask where this stands anymore" lands better than "it has conditional formatting." Once one person on the team feels the friction disappear, adoption tends to take care of itself.
Most businesses have at least one spreadsheet quietly running their operations that was never built to. Lists is the fix that's already paid for.
Accurate as of June 2026. Microsoft updates its products and pricing regularly.
J. Scott Clark is the President and CEO of The 365 Collective, Inc., a Microsoft 365 consulting and training firm serving small and mid-sized businesses across healthcare, finance, construction, engineering, publishing, and retail.
This is exactly the kind of fix we help clients spot before it becomes a bigger mess. If you want a hand figuring out what's already covered in your subscription, feel free to reach out.