How the advisory team should use Microsoft Loop and Copilot Pages — to turn ephemeral conversations, meeting outputs, and collaborative drafts into living canvases that stay synchronised wherever they're shared. Six distinct surfaces, six advisory workflows, and the single feature that genuinely has no equivalent anywhere else in Microsoft 365.
Before the features, the reframe. For thirty years the fundamental unit of collaboration has been the document — a static file you email around, revise, send again, argue about versions of. Loop and Copilot Pages propose a different model: content that stays live, editable in place, and synchronised wherever it appears. It takes a beat to internalise; once you do, email attachments start to feel anachronistic.
Think about what a typical advisory deliverable looks like today. Someone drafts a Word doc in SharePoint. Shares a link. Three colleagues open it, comment, tweak. The version in OneDrive gets forked to someone's desktop. An old PDF gets emailed around. Two weeks later the team has four versions, no clarity on which is current, and the live tracker of actions has been transcribed into three different Teams messages with no single source of truth.
"Loop is not another document format, but a new working principle. Content is used modularly, dynamically, and across contexts."
Three specific shifts that Loop + Pages enable:
Old pattern: each document is a snapshot at a moment in time. Updating it means creating a new snapshot. New pattern: the page is the current state. Edit it, everyone sees the edit. There is no v1, v2, v3-final-FINAL. The content has one representation and it's always current. For fast-moving engagements where three people are trying to keep a status tracker accurate, this is structurally different from Word.
The Loop component is the unique capability in Microsoft 365. A table, task list, or checklist you create in Loop can be pasted into Teams chat, Outlook email, Word document, or another Loop page — and every instance stays live and synchronised. Someone updates a task status in the Teams chat; the same task updates in the email, in the Word doc, in the Loop page. The content doesn't belong to a file — it belongs to itself, and shows up wherever it's useful.
Copilot Pages close the awkward gap between "Copilot gave me a useful answer" and "I need to turn this into something I can share with the team." Click Edit in Pages at the bottom of any Copilot response and the answer becomes a live, shareable page you can refine side-by-side with Copilot chat. No copy-pasting into Word, no rebuilding formatting, no losing structure. Chat → Page → team, in one unbroken flow.
For an advisory team producing workshop outputs, status trackers, stakeholder maps, decision logs, and collaborative proposals week after week, these three shifts compound. The savings aren't one-off features — they're a different way of doing the same work.
"Loop" and "Copilot Pages" are related but structurally distinct — with Microsoft actively unifying them. Understanding what each surface does today (and where the unification is heading) matters for knowing which to reach for.
.loop files — they appear in the Loop app, use Loop's compliance mechanisms (sensitivity labels, DLP, eDiscovery, audit logs), and live in SharePoint/OneDrive storage. Share via link, or — more powerfully — copy individual sections as Loop components and paste into Teams, Outlook, or Word where they stay live and synced. Requires only SharePoint/OneDrive storage — accessible without a full M365 Copilot licence, though AI features are better with one.loop.microsoft.com). Create a page in a workspace. Mix narrative text with live components — a meeting page might have a paragraph of context at the top, a decision log component in the middle, a task list component at the bottom, with the task list also visible in your Teams channel. Real-time co-authoring — multiple people edit simultaneously with visible cursors. Mentions work (@someone triggers a notification). Pages live inside Workspaces (Tool 4) and can be shared individually. Differentiated from Copilot Pages (Tool 1) by starting point: Loop pages are created in the Loop app; Copilot Pages are created from a Copilot chat response — but technically they're the same file format, and Microsoft is unifying the experiences.Three AI-enabled canvases in the same stack. Different jobs. Choosing the right one for the task is a skill worth building up front; choosing the wrong one wastes time and creates sprawl.
Real-time collaboration on a project with flexible structure — pages, components, narrative text mixed with live data.
You've been chatting with Copilot and want to capture and refine the output into a persistent, editable, shareable form.
You're working on a project that requires gathering multiple sources and asking Copilot questions grounded in that curated content.
Three practical rules for picking:
These aren't mutually exclusive. A real engagement often uses all three: Notebooks for research context (source documents, meeting transcripts), Pages for turning Copilot's answers into team-shareable drafts, and Loop workspace for the live project brain where pages sit and components distribute to Teams/Outlook. The three are complementary — the skill is knowing which role each plays.
Worth stating clearly: a Copilot Page is a .loop file. It lives in SharePoint/OneDrive under the Loop technology. Opens in the Loop app. Uses Loop's sensitivity labels, DLP, eDiscovery, audit. The only difference between "Copilot Page" and "Loop page" is the starting point: one was created from a Copilot Chat response, the other was created inside the Loop app. Microsoft is actively converging the two experiences. For advisory teams, this means: don't agonise over which "one" to use. They're the same file under the hood — use whichever entry point is closest to what you're doing right now.
Loop has been available in most M365 tenants for years. Copilot Pages requires only SharePoint/OneDrive storage. The prerequisites aren't technical — they're organisational: making sure the team knows it's available, knows where to use it, and knows the sensitivity boundaries.
1. Confirm Loop is activated for your tenant. IT may have disabled Loop at the tenant level. Test: go to loop.microsoft.com and sign in. If you land in the Loop app, it's on. If you get a message about admin policy, ask IT to enable. Default for most modern M365 tenants is on, but some regulated organisations disable it by default.
2. Check your Copilot Pages access. Pages requires SharePoint or OneDrive storage on your account — which almost every Arup consultant has. Pages does not strictly require the M365 Copilot (Premium) licence; even Copilot Chat (Basic) users can create Pages from their chat outputs (with web-grounded content). The Premium licence unlocks work-data grounding for the chat, which makes the Pages more useful — but Pages as a capability is broadly accessible.
3. Understand the storage model. Loop pages and Copilot Pages are stored in your OneDrive by default, unless created inside a Loop workspace (which has its own SharePoint-based storage). This matters for governance: pages in OneDrive inherit your personal permissions; pages in a workspace inherit the workspace's membership. Loop content is subject to all the usual Microsoft Purview governance — sensitivity labels, DLP, eDiscovery, audit logs — same as any other M365 file.
4. Decide on workspace strategy. Three sensible models:
Avoid: having no strategy and creating workspaces ad-hoc. Loop sprawls fast if nobody manages it.
5. Pin Loop to the team's awareness. The biggest prerequisite is that the team knows Loop exists and why to use it. One-hour internal briefing with three worked examples (chat → Pages, live component in Teams, project workspace) is enough to shift adoption from rare to routine. Without that briefing, the activation button stays on and nobody uses it.
The bread-and-butter Copilot Pages workflow. You asked Copilot for something, the answer is useful, you want to turn it into something the team can edit and own. Historically a copy-paste-reformat loop; now a one-click transition into a live canvas.
Copilot Pages has a specific failure mode: if you say "add an executive summary to this page", Copilot often regenerates the whole page and tacks the summary on. You lose your edits, your structure, your careful formatting. The fix is a precise verbal distinction:
After you've iterated through two or three regeneration disasters, you'll internalise the pattern. The shorthand: create separately, then add manually. Don't ask Copilot to modify the page in place unless the change is narrow and explicit.
Pattern 1: Share the whole page. Click the share button top-right, copy the link, send via Teams or email. Recipients open the page in their browser, edit directly, see your edits in real time. Best when the recipient's work is on the whole document.
Pattern 2: Paste specific components into their context. Hover over a table, task list, or structured block — grab the handle at the top-left — copy. Paste into a Teams channel or Outlook email. Now that specific piece is live in the chat, still synchronised with the page. Best when you want a particular section visible in the place where work happens, not requiring recipients to click through to a separate page.
Most advisory consultants default to Pattern 1 (share the link). Pattern 2 is often the higher-value move — the component in the Teams channel is more immediately visible and actionable than a link to "yet another page I need to open."
The single most distinctive capability in Microsoft 365 and the least-used one. A live task list, table, or checklist that lives simultaneously in a Teams chat, an Outlook email, a Loop page, and a Word document — all editable, all synchronised. Once the team experiences this, static attachments feel archaic.
1. The meeting action list. Create a task list component during the meeting in the Teams meeting chat. Everyone can see it, add items, assign owners, tick them off as the meeting progresses. After the meeting, paste the same component into a follow-up email to non-attendees or external stakeholders. The email and the Teams chat now show the same live list; updates in either propagate. This is the single highest-value adoption pattern for advisory teams because it replaces the "someone writes up actions after, emails them, actions drift" loop with a live artefact everyone edits during the meeting.
2. The running status table. Create a table component in your project channel with columns for workstream, owner, status, next milestone, risks. Pin it to the channel. The project lead updates it weekly; team members can update their rows directly. Paste the same component into a weekly client email. Client sees the latest status without anyone having to "prepare an update" — the update is just the table, always current.
3. The collaborative decision log. Bulleted list or numbered list component in the engagement's Teams channel. Every time the team makes a decision together, someone adds a one-line entry ("decided Thursday 17 April: we're going with option B because…"). Paste the component into a Loop page for the engagement archive. The decision log lives in the channel where people see it daily; the page is the canonical home; both stay in sync.
4. The voting/prioritisation table. When the team needs to prioritise options, create a voting component in the channel. Everyone votes in-line; results visible to all in real time. Works well for: retrospective prioritisation, risk severity voting, options ranking, new-idea triage. Beats polls because the votes and the options live in the same artefact, editable, durable.
5. The client-facing status tracker. Table component pasted into Outlook email to the client. Rows for key deliverables; columns for owner, status, date. The client can edit the component directly in the email — no need to click through to a SharePoint link. Update from Arup's side happens in any instance of the component, syncs to the client's view. Replaces the "attached please find the latest status report" email with something the client can interact with.
Permissions on a Loop component follow its original creation context. A component created in a private 1:1 Teams chat can be pasted into a broader channel, but people in the channel who weren't in the original chat won't see the component's contents. They'll see a placeholder. That's correct security behaviour, but it confuses first-time users. Rule of thumb: create components in the broadest context that should be able to see them. Starting in a channel is usually safer than starting in a 1:1 chat if you think the content might move.
The workshop or brainstorm that lives in a Loop page while it's happening. Everyone sees the same canvas. Nobody's taking notes as a separate task. The output document is the meeting, not something produced after.
Before the meeting starts, the facilitator creates a Loop page with the template for the session's output. Good templates for advisory workshops:
For a brainstorm: A heading at the top stating the question. Below it, a bulleted list where anyone can add ideas as they're raised. Then a voting table for the second half of the session where the group prioritises. Then a task list for the concrete next steps.
For a stakeholder-mapping workshop: A table with rows for stakeholder groups and columns for role, interest, influence, current sentiment, Arup relationship. Team members fill in rows live during discussion. A bulleted list below for cross-cutting themes.
For a risk-identification session: A table with columns for risk, likelihood, impact, mitigation, owner. A task list below for the "we need to follow up on X" items.
For a retrospective: Three bulleted list sections: what went well, what didn't, what to try differently. A voting table for the group to prioritise which changes to actually make.
Fifteen minutes of pre-meeting setup. During the session, everyone works in the same page simultaneously — seeing each other's cursors, edits appearing in real time. The facilitator spends the meeting facilitating, not transcribing.
Part IX covered Teams Intelligent Recap — transcription-based meeting summary. That's the right tool for meetings where the output is what was said. Loop pages are the right tool for meetings where the output is what was produced together. Workshops, brainstorms, planning sessions, retrospectives — the value of the session is in the emerging artefact, not the transcript of who said what. Live co-authoring produces the artefact directly; transcription produces a record of the conversation about the artefact.
For some meetings — structured workshops especially — you might use both: transcription running in the background (for the record), and a Loop page as the live output document (for the product). Afterwards, the Teams recap gives you the narrative; the Loop page is the deliverable.
At the end of the session, the Loop page is immediately shareable. Paste the whole link into the meeting follow-up email. Paste specific components (the action list, the decision log) into the team's project channel. The "writing up the workshop" task that used to consume the day after the session is gone — the page is the write-up, built collaboratively in real time.
One Loop workspace per engagement. All the engagement's pages live there. Components distribute to Teams and Outlook wherever the team works. Replaces the scattered "where does this live?" pattern with a single structural answer.
For a typical Arup advisory engagement workspace:
1. The engagement overview page. Top-level narrative: what the engagement is, who the client is, what we're trying to achieve, team roster, key dates. New joiners read this page first. Updated when scope or team changes materially.
2. The live status page. Weekly updated. Status table component (workstream, owner, status, next milestone) — this component also pastes into the team's Teams channel and into weekly client emails. Risk register component. Key decisions log.
3. The meetings page. A running page where each meeting gets a section with the workshop outputs, decisions, actions. New meetings append at the top. Links to Teams Recap recordings for transcribed meetings. The "state of what we've done with the client" in one place.
4. The working drafts page. Where in-progress pieces live before they're ready to be formal Word/PowerPoint deliverables. Collaborative drafting, comments, iteration. Moves to a proper Word doc when mature.
5. The knowledge and context page. Notes from research, relevant precedent, useful links to external sources, Arup capability references. Lighter than the Copilot Notebook (Part X) but complementary — the Notebook is for AI-grounded querying; this page is for human-scanning reference.
Five pages is a sensible opening set. Workspaces sprawl fast; start tight, expand only when a clear purpose emerges.
The workspace is the canonical home; the components are the distribution. From the live status page, the status table component gets pasted into the engagement's Teams channel (visible daily) and into weekly client emails (visible externally). From the meetings page, the latest action list component gets pasted into the team's Teams channel. From the working drafts page, specific bullet-list sections pasted into Teams for targeted input. The workspace holds the structure; the components reach into the surfaces where people actually look.
[Client] · [Project name] · [Year] — e.g. Harrow Council · Estates Modernisation · 2026. Searchable, unambiguous.When the engagement ends, the workspace owner:
Anywhere four or more people need to contribute to the same document in real time, Loop pages meaningfully outperform Word — simpler permissioning, faster editing, visible presence. The "collaborate in Loop, not in Word" insight is real for certain use cases and worth building as the team's default.
1. Simultaneous editing with visible presence. Word supports co-authoring, but you can only really see one or two others' cursors; more becomes chaotic. Loop is built for multi-presence — five cursors in the same paragraph works fine. For genuine group editing sessions, the UX is meaningfully better.
2. Simpler permissioning model. A Loop page in a workspace has one permission set (the workspace membership). Word documents in SharePoint have layered permissions (site, folder, document, possibly item-level). For ad-hoc collaboration that doesn't need the governance overhead, Loop's flatness is a feature.
3. Faster to iterate on structure. Adding sections, moving things around, restructuring — feels lighter in Loop than Word. Word's formatting apparatus is powerful but costs time when you're in "shape the content" mode rather than "polish the deliverable" mode.
4. Native components. Need a quick status table, task list, or voting block inside the document being co-authored? Word can embed Loop components, but it's cleaner to start in Loop if you know you'll want them.
5. Better mobile experience. Loop pages work well on mobile for quick edits from team members on the move. Word on mobile is functional but less natural.
Loop is not a Word replacement for formal deliverables. Word wins on:
A sensible workflow for most substantial advisory documents: draft collaboratively in Loop → migrate to Word for formal polish and template application → deliver from Word. The Loop phase is about shaping the content with the team. The Word phase is about applying Arup's templates, Track Changes, and formal export. Each phase takes the right tool; neither is forcing the wrong one.
To migrate: select the content in Loop, copy, paste into Word. Some formatting transfers; you'll spend a few minutes in Word applying Arup heading styles. Faster than trying to collaborate in Word from the start.
The specific pattern worth establishing across every Arup advisory engagement. Kill the "weekly status email with an attached PDF" pattern. Replace with a single live component that lives in Teams and email and updates itself. One thing, always current, always visible.
A table component with the following columns:
Create it once in the engagement's Loop workspace. Paste it into the team's Teams channel. Paste it into the weekly client email template.
Every Monday morning, each workstream lead updates their row directly in whichever instance is most convenient (Teams, email, Loop page). Updates propagate instantly. The engagement manager reviews; the table is the status update. No document gets attached. No version gets argued about.
The entire weekly status cycle takes collectively less than an hour of Arup time across the whole team, vs the 2-4 hours a traditional "someone prepares a status report" cycle takes. And the client sees continuous current state rather than a weekly snapshot.
Each of these is a live component pasted into the surfaces where it's most visible. The risk register lives in the project Teams channel, updated whenever someone identifies a new risk. The action log lives in the meetings page of the Loop workspace. Decisions accumulate in the decision log as they happen rather than being reconstructed later.
Six use cases, six surfaces, one table.
| Your scenario | Use this | Surface | Time |
|---|---|---|---|
| Copilot just gave me a useful drafted response | Edit in Pages | Copilot Chat → Pages | ~1 min |
| Meeting action list everyone needs to update | Task list component in meeting chat | Teams chat | ~30 sec |
| Weekly client status update without email attachments | Live status table component | Teams + email + Loop | ~5 min/week |
| Multi-workstream engagement with 3+ team members | Loop workspace | Loop app | ~20 min setup |
| Internal workshop — brainstorm + prioritise + actions | Pre-built Loop page template | Loop page | ~15 min prep |
| Five people co-authoring a collaborative draft | Loop page for draft; migrate to Word later | Loop page | Varies |
| Running risk register the whole team updates | Table component in project channel | Teams channel | ~5 min setup |
| Decision log for the engagement | Numbered list component | Project channel + Loop page | Minutes to set up |
| Formal client deliverable with Arup template | Word, not Loop | Word | n/a |
| Research-heavy project with reference sources | Copilot Notebook (Part X) | Notebooks | ~30 min build |
| Refine Copilot output with side-by-side chat | Copilot Pages | Copilot Chat | ~5 min |
| Live voting on options with the team | Voting component in Teams chat | Teams chat | ~2 min |
Patterns from training advisory teams on Loop and Copilot Pages. Almost every bad outcome maps to one of these.