From Site Walkthrough to Action List: Owners and Due Dates with Microsoft 365 Copilot

Every property team does the walkthrough. Five people walk the building for an hour, point at things, agree on who does what, and walk out with good intentions. Then the notes go out three days later, half the dates are "next week", and the one item nobody took ("somebody should look at that") is still there in February.

The meeting isn't the problem. The minutes are. Someone has to turn a rambling conversation into a list with an owner and a real date on every line, and notice the things that never got either.

In this guide we give Microsoft 365 Copilot the transcript of a quarterly walkthrough and ask for exactly that: an action list with owners and calendar dates, the items that still need an owner or a date, and the decisions, including the one that was changed halfway through. Then it drafts the follow-up email.

Here it is, sped up:

What you'll need

• A Microsoft 365 Copilot licence.

• A meeting transcript. In Teams, turn on recording and transcription when the walkthrough starts, and the transcript is saved with the meeting.

• For this guide we used a ten-minute transcript of a fictional walkthrough at Harbourfront Office Tower, saved as a Word file, so you can see exactly what Copilot was given. In a real Teams meeting you can ask Copilot the same questions during or after the meeting.

The walkthrough

Five people: the property manager, the chief building engineer, tenant services, the security supervisor and a technician from the HVAC contractor. They walked from the roof to the loading dock and covered ten things: a blocked terrace drain, the rooftop units, a warm floor, worn lobby carpet, a faulty revolving door, fire extinguisher tags, parking garage lighting, a tenant notice, a torn dock door seal and the boiler room.

We wrote it the way walkthroughs really go. Some dates are exact ("Friday the 9th"), some are relative ("end of next week"), and some aren't dates at all ("next week sometime"). One decision is made and then reversed a few seconds later when the budget comes up. And one problem gets a "good catch" and no owner.

Step 1: Ask for the action list

In Copilot Chat, attach the transcript and ask:

This is the transcript of our Q4 site walkthrough at Harbourfront Office Tower on October 6, 2026. Turn it into: 1) an action list as a table with Action, Owner, Due date and Location, using the exact dates people agreed and converting relative dates to calendar dates; 2) a list of anything that needs an owner or a firm date because the meeting didn't set one; 3) the decisions made, including anything that was changed or deferred during the meeting. Don't invent owners or dates.

The last sentence matters most. Without it, an AI will happily give "check the dock door seal" to whoever was standing closest.

Step 2: Check the action list

Copilot came back with seven confirmed actions, each with an owner, a calendar date and a location:

We checked every row against the transcript. All seven owners are right. All the dates are right too: "today" became October 6, "Friday the 9th" became October 9, "next Tuesday, the 13th" became October 13, "end of next week" became October 16 and "this week" became October 9. Copilot listed every conversion it made under the table, so you can check them in ten seconds.

Step 3: The items nobody owns

This is the part that makes the minutes worth sending:

• The dock door seal: "Somebody should look at that before winter." Everyone agreed, and nobody took it. Copilot flagged it: no owner, no date.

• The warm floor on level 9: the HVAC technician said "next week sometime, I'll confirm the day." Copilot didn't turn that into a date. It flagged that a firm date is still needed, and that tenant services can't give the tenant one yet.

• The garage lighting: the installation depends on a quote that hasn't arrived, and the tenant notice depends on the installation date. Copilot kept both out of the confirmed list and explained the dependency.

Step 4: The decision that changed

Halfway through, the property manager said "let's plan to replace the carpet this quarter", then checked the budget and said "actually, let's not, put it in the Q1 capital plan." A careless summary lists the carpet as a Q4 action. Copilot got it right:

It recorded the change, the reason (the Q4 repairs budget) and the new plan, and kept the carpet replacement out of the action list. The only carpet action is the one somebody actually agreed to: photos and measurements by October 16.

Step 5: Send the follow-up

One more prompt drafts the email:

Draft the follow-up email from Priya to everyone who attended. Keep it short: thank them, include the action table, then ask Kevin for a firm date for the VAV rebalance and ask Daniel to own the dock door 2 seal with a date before November 15.

From the end of the meeting to a follow-up email ready to send took about three minutes. Review it, paste it into Outlook, send.

Where it slipped

Not much, which surprised us. Two things to watch.

First, "before the end of October" became October 30. That's a reasonable reading, and Copilot told us it had made that call, but if your security supervisor meant October 31, the table is a day early. When Copilot lists its date conversions, read them.

Second, a transcript only records what people say. If someone nodded at an action instead of answering, Copilot can't see it, and it will correctly report that item as having no owner. That's the right behaviour, but it means the walkthrough habit worth building is simple: say your name when you take something.

A quick game: owner or not?

Three lines from a walkthrough. Does the action have an owner?

• "Kevin, can you have a look at that?" "Yep."

• "Someone from Brightline should quote that."

• "I'll get my team up here and clear it by Friday."

Ours: yes, no, yes. "Yep" counts. A company isn't a person, so the Brightline quote still needs someone to request it. And "my team" has an owner: the person who said it.

Lessons from the build

• Say "don't invent owners or dates." It's the difference between minutes you can trust and minutes that create arguments.

• Ask for what's missing, not just what's agreed. The unowned items are where problems hide until winter.

• Give it the meeting date. Every "next Tuesday" depends on it.

• Ask for decisions separately. Reversed and deferred decisions are where summaries go wrong.

Ideas to take it further

• Put the actions in Planner: ask Copilot to format the table for import, or have a Power Automate flow create a task for each row.

• Track them on a checklist: add the walkthrough actions to the Copilot Pages month-end checklist so the status updates itself.

• Compare quarters: keep every walkthrough transcript in one SharePoint folder and ask Copilot which issues keep coming back.

• Brief the tenant: the warm-floor item is a tenant complaint. Ask Copilot to draft the update to Northwind Legal once Kevin confirms the date.

Why this matters

A walkthrough produces decisions, but they live in five people's memories, a few photos and someone's notebook. Bring your data from different systems into one place and put AI in front of it, and the meeting's output is a list with an owner on every line, sent before everyone is back at their desks.

Need help?

Smart Solutions sets up Microsoft 365 Copilot, Teams and facilities workflows for Canadian property and facilities teams. If you'd rather have work orders, purchase orders and vendor performance in one product, take a look at ProcuraCloud, our procurement platform for small and mid-sized businesses. Contact us to talk about your site walkthroughs.