stepbase
← Blog

Replacing spreadsheets & forms

SharePoint List as a Request Tracker: Where It Works and Where It Stops

A SharePoint list is a good first request tracker. Here is what it does well, the four places it stops, and when you don't need to switch.

stepbase Team·November 10, 2026
SharePointMicrosoft ListsRequest trackingApprovals

You set up a SharePoint list as a request tracker because it was already there. Every branch has Microsoft 365, so nobody needed a new login. You added columns for Branch, Request, Requested by, Assigned to and Status, shared the link, and for a few weeks it was much better than the spreadsheet it replaced.

Now it's Tuesday morning. A request from the east branch has said "In progress" for nine days, and nobody can tell you who it's with. Someone at another branch changed a status to "Approved" because the customer was waiting. The area manager wants to know why the north branch's requests take twice as long, and the answer is somewhere in the version history of 300 items.

This isn't a complaint about SharePoint. A list is a good place to keep records. The trouble starts when you ask it to run a process.

What a SharePoint list does well

Give it credit, because it does a lot for something you didn't have to buy:

  • It's already in your Microsoft 365. No new account, no procurement, no IT ticket, and your company's sign-in already covers it.
  • It's a real table, not a spreadsheet. Columns have types: choices, dates, people, yes/no. That alone stops a lot of the mess a shared Excel file collects.
  • Views are easy. "My branch", "Open requests", "Assigned to me": anyone can save a filtered view in a few clicks, including a board view grouped by status.
  • It keeps version history. You can see what an item looked like before someone changed it.
  • It can send simple alerts. Notify me when an item changes, or when a new one is added.
  • It works with the rest of Microsoft 365. Microsoft Forms can feed it, Teams can show it in a tab, and Power Automate can add approvals on top.

For a team that just needs one shared list of things to do, that's enough. Keep reading only if it's starting to feel like a lot of work.

Where it stops

1. Anyone can change the status

In a list, Status is a column, and anyone who can edit the item can set it to anything. You can trim permissions, but the column still records whatever someone typed, not what actually happened. "Approved" means someone chose "Approved" from a drop-down. It doesn't mean the person who should approve it did.

Once there's more than one branch, that's the gap that hurts. You can't tell an approval from a hopeful click without opening the version history.

2. Nothing moves the request to the next person

A list holds requests; it doesn't pass them on. When the branch manager approves, someone still has to change "Assigned to" to the area manager, and remember to tell them. If they forget, the request sits on "Approved" with no next owner, and it doesn't look stuck because nothing ever looks stuck in a list.

Power Automate can fill that gap, and for one approval it often does. But each extra step is another automation for someone to build, and another thing that breaks quietly when a column is renamed or the person who built it moves on.

3. The person who asked can't see where it is

Your branch staff submit a request and then ask you about it. To see its status themselves, they need access to the list. With access they can see everyone else's requests too, and often edit them. Giving people "only my own items" in SharePoint is possible but fiddly, so most teams don't, and the questions keep coming to you.

4. "How long does it take?" has no answer

When the area manager asks how long requests wait at each step, the list can't tell you. It knows when an item was created and last modified. To work out time spent with each person, you'd be piecing together version history item by item. The question that justifies fixing the process is the one the tracker can't answer.

You don't need to switch if…

Be honest with yourself here. A SharePoint list is the right tool if:

  • There's no approval. Requests come in and one team does them. Nobody has to sign anything off.
  • One person owns every request from start to finish, so there's no handover to miss.
  • People only need to see what's open, not who signed what or how long it waited.
  • You're happy with one Power Automate flow and someone on your team can keep it running.

If that's your process, tidy your columns and views and stop there. The rest of this post is for when requests pass through two or three people, at more than one branch.

What to use instead: a Form, a Workflow and one Table

What's missing from the list is someone who owns the status. Not a column people type into, but a process that moves the request on and records who did what. Here is how to build that in stepbase, keeping the parts of your list that already work.

  1. Start from your list's columns. Create a project and describe the process in a sentence, for example "Branch requests: branch manager approves, then the area manager for anything over budget, then facilities does it." stepbase drafts the Table, the Form and the Workflow. Check the Table's columns against your list's and adjust them.
  2. Make one Form for every branch. Branch, what's needed, why, any photos or quotes. Share it as a link, or as a QR code on the staffroom wall. People don't need to see the Table to submit.
  3. Add the people as Steps. In the Form's Workflow, add an approval Step for the branch manager. Assign it from a field on the form, so each request goes to that branch's manager. Add a second Step for the area manager, with a Rule so only requests over your limit reach it. Then add a Step for the team that does the work.
  4. Let the Workflow own the status. The Table gets a status column that the Workflow fills in as the request moves. It's locked: nobody can type "Approved" into it. If a builder has to move a request by hand, they move the Submission itself, and the move is recorded.
  5. Give each person their own view. Approvers see their Tasks in My Work. The person who asked opens the app and sees their own requests and where each one sits, without seeing anyone else's.
  6. Add a deadline where things wait. On the branch manager's Step, set a time after which the Task passes to someone else, so a manager on leave doesn't hold up every request.
  7. Keep your board. Tables have Board views, grouped by status, so the at-a-glance view your team liked in the list is still there. Now the cards move because someone acted, not because someone dragged them.

Everything that happens to a request is in its history: who submitted it, who approved it and when, what was sent. When the area manager asks how long requests wait, the builder's Analytics shows the time spent at each Step.

One thing to know: stepbase doesn't read or sync your SharePoint list. Its Tables are its own. Most teams start new requests in stepbase and leave the old list as an archive. If you want the old requests in stepbase too, export the list to a CSV file and import it into a Table of past requests.

Start with your busiest branch

You don't have to move every branch at once. Put your own branch's requests through the Form for a couple of weeks, alongside the list. When the questions to you stop, show the other branch managers their Tasks in My Work. That usually does more than any announcement.

The short version

A SharePoint list is a good tracker and a weak process. If your requests pass through more than one person, give them a Workflow that owns the status, and keep the list for what it's good at. Describe your process at stepbase, or start from the Employee Requests template to see one app take several kinds of request.

Ready to build your first app?

stepbase gives you a visual designer, conditional routing, and a full audit trail. No code required.