Microsoft Lists, Excel or Power Apps: Which One to Use?

You need to track something: requests, equipment, job applications, incidents. The reflex is to open Excel. Then someone tells you it should be "an app". In between sits Microsoft Lists, already included in your Microsoft 365 and often overlooked. Three tools, three levels of effort. Here is how to choose in five questions, without oversizing or undersizing.

The three tools in one sentence each

• Excel is a spreadsheet: perfect for calculating, analysing, doing personal or one-off work. It has no row-level permissions, no approvals, and no reliable history of who changed what.
• Microsoft Lists is a simple, shared database with forms, views, notification rules and a mobile app. It is built on SharePoint and included in Microsoft 365.
• Power Apps is a workshop for building applications: custom screens, business rules, approval chains, mobile with offline, connections to your tools. You reach for it when Lists is no longer enough.

Microsoft Lists or Power Apps: the five-question grid

1. How many people enter data? One: Excel. A team: Lists. Several departments with different roles: Power Apps.
2. Are there rules? None, or calculation formulas: Excel. Required fields, choice lists, an alert when a status changes: Lists. Conditional calculations, steps that depend on the role, cross-checks between several tables: Power Apps.
3. Is an approval needed? None: Excel or Lists. A simple, single-level approval: Lists with a Power Automate flow. A multi-level chain, with delegation and reminders: Power Apps and Power Automate.
4. Is mobile needed? Viewing and filling in a form from a phone: Lists has its mobile app. Taking photos, signing, working without a network: Power Apps.
5. What volume? A few hundred rows: anything works. A few thousand: Lists, with indexed columns on what you filter, because a SharePoint list gets temperamental beyond 5,000 items in a view. Tens of thousands of related rows: Power Apps with Dataverse.

Count the answers. If everything points to Excel, keep Excel. If one or two answers point to Lists, try Lists: it is already there and costs nothing extra. If two or more answers point to Power Apps, you need an application.

When Microsoft Lists is enough

Lists is the right tool for most team tracking. An equipment register, internal request tracking, a list of approved suppliers, an action plan after a meeting. You create the list, add typed columns (choice, date, person, yes/no), a view per status, a rule "notify Julie when the status changes to 'to approve'". The entry form already exists, so does the mobile app, so does version history.

Two limits to know about. Fine-grained permissions per row are possible but painful to maintain: if each person must only see their own items, you are at the border of Power Apps. And a list is one table: as soon as you need two related tables (orders and their lines), Lists starts to struggle.

When Excel is still the right choice

Do not let anyone convince you to transform everything. Excel wins when the work is first a calculation: a budget forecast, a pricing simulation, a margin analysis, a capacity plan you redo every quarter. It also wins when the file lives for the duration of a project and dies afterwards. And it remains the analysis tool at the end of the chain: a Lists list or a Dataverse table exports to Excel in one click to be sliced every which way.

The signal that Excel is no longer the right choice: several people enter data into it, the data matters, and rules are needed. Our article on when Excel stops being enough goes through that test.

When you need a Power Apps application

You are in this case if the tracking is a process, not a list: several steps, several roles, rules that decide what happens next, data spread over several tables, or field use with photos and offline. At that level, Lists becomes a pile of workarounds, and every workaround is a weak point.

The good news: a Power Apps application can start on an existing Lists list. You do not lose your data, you add screens, rules and automations on top. And if volumes or relationships grow, you migrate to Dataverse. It is a path, not a leap.

If you want to see what an application looks like once you have crossed that line, our production tracking template shows a classic shop floor case, and our supplier invoices template an administrative one. And to decide with someone, a 30-minute call is often enough to place your need.