I Asked Copilot to Build a Tracking List. It Took Under a Minute.

Every few weeks a client asks me some version of the same question: how long would it actually take to build a proper tracker in SharePoint — real columns, a usable view, maybe an automation or two. I used to answer with "it depends." Now I answer with a number: under sixty seconds, if you ask Copilot to build it instead of building it by hand.

What I Watched Copilot Build in Under a Minute

I opened Copilot chat in SharePoint and described what I wanted: a list to track blog posts through drafting, review, and publish. That was the whole request.

What came back was a fully structured list, not a starting point I'd still need to finish. Thirteen columns: Blog Post, Status, Scheduled Publish Date, Draft Due Date, Review Due Date, Content Author, Content Editor, Category, Priority, Channel, Keywords, Summary, Published URL. Each one had the right data type already assigned — dates as dates, status as a choice field, not free text I'd have had to clean up later. Copilot also built an Editorial Calendar view without being asked, and it proactively suggested two automations on its own: notify the editor in Teams the moment a new item lands, and send reminders as the draft and review due dates get close.

I didn't ask for either automation. That's the detail that stands out to me more than the columns. A list-building exercise usually stops at the list — someone has to circle back later and decide the notifications are worth the extra setup, and that circling back is exactly the step that gets skipped when the initial build already took fifteen minutes. Copilot proposed both before I'd finished describing what I wanted the list for.

Then I wanted to see how far this really extended. If the agent could build this from inside SharePoint, could it do the same thing from somewhere I actually live during the day — Teams? I opened Copilot chat there and asked for the same list. What came back wasn't a list. It was a PowerShell script. Copilot told me it couldn't provision anything directly — no connector, no automation context — and offered to write the script instead.

The SharePoint List Agent isn't a capability the default Copilot assistant just has. It's its own agent, and it has to be added — from the Agent Store, or called directly in chat — before Copilot knows to build anything. I had it running in SharePoint without realizing that's what made the first attempt work. Teams didn't have it. Once I added it there, the second attempt built the same kind of list the first one had.

So doesn't matter where you are — SharePoint, Teams, wherever the agent's supported — but "supported" and "already there" aren't the same thing. Check for the agent before you build a workflow around it just showing up.

Building that same list by hand — deciding the columns, setting the types, building the view, wiring up the notifications separately in Power Automate — is a ten-to-fifteen-minute job if you already know exactly what you're doing. Most people building a tracker for the first time don't start there.

The Real Time Sink Was Never the Clicking

Here's what I actually tell clients: building a list properly is planning, not clicking. Deciding what you need to track, what type each field should be, what view makes it usable day to day — that's the part that takes real thinking. It's also the part most people skip, which is why half the trackers I inherit from clients are one column wide with everything crammed into a notes field.

Copilot didn't just save the clicking. It did the planning, and it did a reasonable version of it, informed by what a blog editorial calendar actually needs rather than a generic guess. That's the part worth paying attention to if you run anything that needs a tracker — a content calendar, a project list, a service request queue, an intake log for shipments. Any list that would normally cost ten to fifteen minutes of setup before anyone can actually use it, and that normally sits at the bottom of the priority list precisely because it takes ten to fifteen minutes someone doesn't feel like spending.

That's the pattern I'd watch for across any of those use cases: the tracker never gets built because building it competes with the work the tracker is supposed to be tracking. Lower the cost of building it to sixty seconds and the excuse mostly disappears.

Where It Didn't Quite Land

I'd be doing you a disservice if I stopped there. In the same test, I asked Copilot to apply column formatting to the Status field — the kind of conditional coloring that makes a list scannable at a glance. It tried. But the formatting got routed to the page library not the list itself, and none of it actually took.

Nothing broke. Nothing errored. Copilot just didn't do the one thing I asked it to do last, and I wouldn't have noticed if I hadn't gone back to check. That's the practical takeaway here: check the list after Copilot builds it. Don't assume everything you asked for landed just because nothing complained on the way out.

The Same Platform Showing Up Twice

This isn't a standalone trick. It's the same Copilot in SharePoint umbrella I wrote about when auto-tagging landed in SharePoint's document libraries — same platform, same rebrand, the same idea running underneath both features: describe what you want in plain language, and let Copilot handle the structure.

The List Agent goes a step further than that one does, too. It can take something that already exists — a table Copilot generated somewhere else in a conversation, or data sitting in an email or a Word document — and convert it straight into a governed SharePoint list, no retyping required.

Frequently Asked Questions

Can Copilot build a SharePoint list from something I already have, like a table or a document? Yes. The List Agent can take an existing table — one Copilot generated in a chat, or data pulled from an email or a Word document — and convert it directly into a governed SharePoint list, without you retyping any of it.

Do I need to open SharePoint to build a list this way? No. You can describe the list from Copilot chat in Teams, Word, or anywhere the agent is supported. SharePoint doesn't need to be open, or even involved yet, until the list exists.

Is the formatting Copilot applies to a new list reliable? Not always. In my own test, column formatting got routed to the wrong library and never actually applied to the list itself. The list structure was solid. The formatting needs a second look before you trust it.

The planning used to be the job. Now the job is just knowing what to ask for.

Accurate as of July 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 other industries.

This is the kind of thing we do every day. If you want to dig into what it looks like for your specific situation, feel free to reach out.