We want you to get immediate value from Copilot in Microsoft Teams, without unnecessary theory. We will guide you step by step to turn meetings, chats and documents into actionable results: executive minutes, tasks in Planner, reliable summaries and presentations ready for committee.
We use Copilot as a contextual assistant, not as magic. That means preparing the ground: clear meeting titles, a brief agenda, recording and transcription enabled, and project files organised in SharePoint/OneDrive. With this minimum level of discipline, Copilot summarises, structures and proposes decisions with a precision you will notice from day one.
Our approach is 100% practical. You will find ready-to-copy prompts, reusable templates (minutes, briefs, dashboards) and real role-based examples (sales, customer service, operations/IT and finance). In each example we indicate what to do, what to ask Copilot and what output to expect within Teams.
The guide is designed for Microsoft 365 environments with active governance and security. We highlight where to enable access controls, sensitivity labels, DLP and auditing, because the quality of context and permissions determines the quality of responses. Our goal is for you to launch a pilot in 15 minutes, measure impact with adoption and productivity KPIs, and scale to your organisation with confidence.
Setting the stage in 15 minutes
We define a controlled pilot so that Copilot has context, permissions and quality data from day one. In 3 blocks we get everything ready: licences and policies, work structure and meeting checklist.
1) Licences and policies
- We assign Copilot licences to a pilot group and enable Teams policies specific to that group. We avoid enabling it for the entire organisation until we measure impact.
- We configure sensitivity labels, DLP and auditing in Microsoft 365. We review permission inheritance in SharePoint/OneDrive to avoid exposing information.
- We establish a responsible use policy: human validation of critical deliverables, no sharing of confidential data outside the team’s scope, and source logging when Copilot synthesises.
2) Work structure in Teams
- We create a team “Copilot Project – Pilot” with channels: #meetings, #documentation, #tracking, #prompt-bank. We centralise files in the team’s SharePoint site.
- We define naming conventions: meetings “[Project] – [Objective] – [Date]“, documents “_v1, _v2” with properties (status, owner, date).
- We enable recording and transcription by default for pilot meetings and save the transcript in the project channel. This way Copilot will have verifiable sources.
3) Meeting preparation checklist
- Brief agenda with objective, participants and linked documents in the invitation.
- Note-taker role (us) to validate Copilot’s summary and create tasks in Planner.
- Meeting exit criteria: decisions, tasks (RACI), risks and next milestones. Copilot should generate this structure automatically.
Operational prompts ready to copy
.prompts-copilot { max-width: 920px; margin: 0 auto; padding: 16px; font-family: system-ui, -apple-system, “Segoe UI”, Roboto, Arial, sans-serif; } .prompt-card { border: 1px solid #e5e7eb; border-radius: 10px; padding: 16px; margin-bottom: 16px; background: #ffffff; box-shadow: 0 1px 2px rgba(0,0,0,0.04); } .prompt-header { display: flex; align-items: center; justify-content: space-between; gap: 12px; } .prompt-title { margin: 0; font-size: 18px; line-height: 1.3; } .prompt-actions { display: flex; gap: 8px; } .btn { appearance: none; border: 1px solid #d1d5db; background: #f9fafb; padding: 8px 12px; font-size: 14px; border-radius: 8px; cursor: pointer; } .btn:hover { background: #f3f4f6; } .btn:active { transform: translateY(1px); } .prompt-text { width: 100%; margin-top: 12px; border: 1px solid #e5e7eb; border-radius: 8px; padding: 12px; background: #fbfbfb; font-size: 14px; line-height: 1.5; white-space: pre-wrap; } .hint { font-size: 12px; color: #6b7280; margin-top: 8px; } @media (max-width: 640px) { .prompt-header { flex-direction: column; align-items: flex-start; } .prompt-actions { width: 100%; } .btn { width: 100%; text-align: center; } }Pre-meeting briefing
Copy Summarise in 6 bullet points the context of this meeting using the latest documents from the channel and related emails. Highlight risks and open questions. Include links to the sources. Tip: Launch this prompt from the meeting chat with the transcript and files already linked.Structured minutes with tasks
Copy Generate the minutes in executive format with: 1) objective 2) decisions (with timestamp) 3) tasks in RACI format 4) risks and next milestones. Propose owners and dates based on the conversation. Convert the tasks to the team’s Planner and mention each owner in the channel. Tip: Ask for timestamps to jump to key moments in the recording.Document normalisation and control
Copy Review the channel files and apply the naming convention and properties (owner, status, date). Return a table with inconsistencies, a proposed correction and links to each document. Tip: Use this at the start of the pilot to organise the repository and improve Copilot’s context. function copyPrompt(elementId) { const el = document.getElementById(elementId); if (!el) return; const text = el.innerText.trim(); if (!navigator.clipboard) { const temp = document.createElement(‘textarea’); temp.value = text; document.body.appendChild(temp); temp.select(); document.execCommand(‘copy’); document.body.removeChild(temp); } else { navigator.clipboard.writeText(text); } // subtle feedback const btn = event.currentTarget; const original = btn.textContent; btn.textContent = ‘Copied ✓’; btn.disabled = true; setTimeout(() => { btn.textContent = original; btn.disabled = false; }, 1600); }function copyPrompt(elementId) { const el = document.getElementById(elementId); if (!el) return; const text = el.innerText.trim(); if (!navigator.clipboard) { const temp = document.createElement('textarea'); temp.value = text; document.body.appendChild(temp); temp.select(); document.execCommand('copy'); document.body.removeChild(temp); } else { navigator.clipboard.writeText(text); } // subtle feedback const btn = event.currentTarget; const original = btn.textContent; btn.textContent = 'Copied ✓'; btn.disabled = true; setTimeout(() => { btn.textContent = original; btn.disabled = false; }, 1600); }
Meetings in Teams: before, during and after (with real examples)
Objective: we turn every meeting into decisions, tasks and next milestones, reducing documentation and follow-up time.
Before: briefing in 60 seconds
- What we do: we open the meeting chat and ask for context.
- Ready prompt: “Summarise in 6 bullet points the context using the latest documents from the channel and related emails. Flag risks and open questions with links to the sources.”
- Expected output: 6 bullets with relevant files, risks, questions and links to review in 1–2 minutes.
- Tip: we add the agenda and objectives to the invitation so that Copilot has quality semantic context.
During: actionable notes in real time
- What we do: we mark decisions and tasks without interrupting the conversation.
- Ready prompt: “Capture decisions, owners and deadlines as we progress; return a table decision | owner | date. Add timestamps.”
- Expected output: structured table that we convert into Loop and pin in the #meetings channel.
- Tip: if a complex topic arises, we ask “explain pros and cons in 3 bullets per option” to facilitate the decision.
After: executive minutes and action plan
- What we do: we generate the minutes and create tasks in Planner.
- Ready prompt: “Generate the minutes in executive format: 1) objective 2) decisions (with timestamp) 3) tasks in RACI 4) risks and next milestones. Create tasks in Planner and mention each owner in the channel.”
- Expected output: minutes ready to share, tasks created, channel summary with mentions.
- Tip: we ask “extract dependencies and blockers” to feed a risk log in Excel.
Real scenarios (quick templates)
- Project committee: “Summarise in 5 points today’s decisions, affected budget and next milestones. Prepare a summary slide for management.”
- Sales discovery: “Extract pains, budget, decision-makers, success criteria and next steps. Draft a follow-up email with 3 value arguments.”
- IT post-mortem: “Build a timeline, root cause (5 whys), corrective/preventive actions, owners and dates. Flag evidence in the transcript.”
Recommended reading
Data, privacy & security for Microsoft 365 Copilot → supports security, privacy, data residency and compliance referenced in this guide. Microsoft Learn
Executive minutes template
Instruction: We ask Copilot to fill in each block from the meeting transcript and the channel files.
.acta-ejecutiva { max-width: 980px; margin: 0 auto; padding: 20px; font-family: system-ui, -apple-system, “Segoe UI”, Roboto, Arial, sans-serif; color: #111827; background: #ffffff; } .acta-ejecutiva h2 { font-size: 28px; margin: 0 0 16px 0; } .acta-ejecutiva h3 { font-size: 18px; margin: 24px 0 8px 0; } .acta-ejecutiva .card { border: 1px solid #e5e7eb; border-radius: 10px; background: #fff; padding: 16px; margin: 12px 0; box-shadow: 0 1px 2px rgba(0,0,0,0.03); } .hint { font-size: 13px; color: #6b7280; margin: 8px 0 16px 0; } .meta { display: grid; grid-template-columns: 1fr 1fr; gap: 12px; } .meta .field { display: flex; gap: 8px; align-items: center; } .meta .label { width: 140px; font-weight: 600; color: #374151; } .editable { min-height: 44px; border: 1px dashed #d1d5db; border-radius: 8px; padding: 10px; background: #fafafa; } .table-wrap { overflow-x: auto; } table { width: 100%; border-collapse: collapse; } th, td { border: 1px solid #e5e7eb; padding: 10px; text-align: left; vertical-align: top; } th { background: #f9fafb; font-weight: 700; } .pill { display: inline-block; padding: 2px 8px; border-radius: 999px; font-size: 12px; border: 1px solid #d1d5db; background: #f3f4f6; } .refs ul { margin: 0; padding-left: 20px; } .refs a { color: #0a63ff; text-decoration: none; } .refs a:hover { text-decoration: underline; } @media (max-width: 640px) { .meta { grid-template-columns: 1fr; } .acta-ejecutiva { padding: 12px; } } @media print { .acta-ejecutiva { box-shadow: none; padding: 0; } .editable { border: 1px solid #e5e7eb; background: #fff; } } Project Date Meeting ParticipantsObjective
We ask Copilot: “Summarise the meeting objective in 1–2 sentences from the transcript and the invitation.”
Decisions
| Decision | Owner | Date | Timestamp | Notes |
|---|---|---|---|---|
| Adopt v3 proposal for sprint scope | María P. | 2025-11-05 | 00:23:41 | Subject to cost validation |
We ask Copilot: “Extract decisions with owner, date and timestamp from the transcript.”
Tasks (RACI)
| Task | R (responsible) | A (accountable) | C (consulted) | I (informed) | Due date | Status |
|---|---|---|---|---|---|---|
| Update budget and send to finance | J. Gómez | Project Dir. | Sales Team | Stakeholders | 2025-11-07 | Not started |
We ask Copilot: “Convert tasks to Planner and mention each owner in the channel.”
Risks
| Risk | Probability | Impact | Mitigation | Owner |
|---|---|---|---|---|
| Delay due to external dependency | Medium | High | Escalate contract and add 3-day buffer | PMO |
We ask Copilot: “Extract blockers and propose mitigation measures.”
Next milestones
| Milestone | Planned date | Success criterion | Dependencies |
|---|---|---|---|
| Committee presentation | 2025-11-12 | Deck approved without reservations | Budget validated |
We ask Copilot: “Build the milestone plan with dependencies and success criteria.”
Source links
-
<!–
- Meeting transcript (00:23:41 decision #2)
- Proposal_v3.docx (SharePoint)
- Financial summary Q4.xlsx –>
We ask Copilot: “Include direct links to the transcript and cited documents for quick verification.”
window.hsFormsOnReady = window.hsFormsOnReady || []; window.hsFormsOnReady.push(()=>{ hbspt.forms.create({ portalId: 7555051, formId: "69ee043b-74a0-4723-8133-9ea7d8275ca1", target: "#hbspt-form-1791756538000-4959432931", region: "na1", })});
Chat and channels: we synthesise noise, write better and decide faster
Objective: we turn long threads into actionable decisions, normalise tone according to the recipient and locate context without leaving Teams.
We summarise long threads into clear decisions
- What we do: we ask for an actionable summary with decision proposals.
- Ready prompt: “Summarise this thread in 5 points, label ‘blockers’, propose 2 decision options and recommend the best one with a brief justification.”
- Expected output: 5 bullets with blockers, options and recommendation; we pin it in the channel as a Loop.
We draft messages with the right tone and length
- What we do: we adapt the message to the recipient’s role (finance, management, technical).
- Ready prompt (CFO): “Rewrite this message for a CFO: executive tone, 120–150 words, clear CTA to approve budget today.”
- Expected output: concise text with a measurable CTA and risks/cost clearly explained.
We extract context from files without opening them all
- What we do: we compare versions and highlight relevant changes.
- Ready prompt: “From the channel files, compare v2 and v3 of the proposal and highlight changes affecting price, scope and timeline. Return a differences table.”
- Expected output: comparison table with impact and next step recommendation.
We convert ideas into tasks without leaving the chat
- What we do: we ask for Planner tasks with owners and dates.
- Ready prompt: “Convert this list into Planner tasks (project X), assign owners, add a due date and label ‘Q4’; mention each owner.”
- Expected output: tasks created and automatic mentions in the channel.
Quick prompt snippets (to pin in the channel)
- “Summarise in 5 bullets and extract blockers with owners.”
- “Adapt the message to ‘executive-client’ tone, 130 words, no technical jargon.”
- “Generate a checklist of next steps with due dates and dependencies.”
- “Explain pros and cons of the 2 options in 3 bullets each and recommend one.”
Files in Teams: Word, Excel and PowerPoint with Copilot inside
Objective: we produce ready deliverables (briefs, control tables and executive decks) without leaving Teams, leveraging Copilot inside each application.
Word and Loop: from notes to a 1-page brief
- What we do: we convert scattered minutes and notes into an executive brief.
- Ready prompt: “Generate a 1-page brief with objective, scope, deliverables, KPIs, risks and assumptions from the transcript and channel files. Use H2 headings and concise lists.”
- Expected output: document ready for review; we pin it as a Loop in the #meetings channel.
- Tip: we ask “add a RACI table at the end” to close owners without ambiguity.
Excel: operational tracking and forecasts
- What we do: we create an operational dashboard with tasks, priorities and progress.
- Ready prompt: “Create a task table with columns: Task, Priority (MoSCoW), Owner, Due date, % complete, Dependencies. Add a % complete formula and a progress chart.”
- Expected output: structured table + chart inside the workbook in the #tracking channel.
- Tip: we add data validations for Priority (MoSCoW list) and conditional formatting on Due date.
PowerPoint: from summary to executive presentation
- What we do: we generate a decision deck from the minutes and risks.
- Ready prompt: “Create an 8-slide presentation: Problem, Options, Recommendation, Plan, Risks, Budget, ROI, Next steps. Use content from the minutes and cited documents, with a final annexes slide.”
- Expected output: presentation ready for committee with key messages per slide.
- Tip: we ask “add speaker notes with 3 bullets per slide” to facilitate the presentation.
Real role-based examples
- Sales: “Build a 1-page Word proposal with client pains, value approach and estimated ROI; generate a 5-slide PowerPoint summary to send today.”
- Customer service: “From the ticket and chat, create a Word template response with mitigation steps; in Excel, prioritise tasks by impact and urgency.”
- Operations/IT: “Generate an Excel backlog with severity, SLA and owner; in PowerPoint, create a 6-slide post-mortem with timeline and preventive actions.”
- Finance: “Summarise variations >3% in Excel with a chart; create 3 PowerPoint slides for the monthly close committee with risks and decisions.”
Data shows how AI-driven automation not only improves support indicators, but also drives a cultural shift towards digital efficiency and data-driven decision-making. Copilot transforms the customer service area into a strategic knowledge centre, capable of anticipating trends, identifying risks and strengthening loyalty.
From agreement to action: Planner, To Do and Loop without friction
Objective: we turn decisions into live tasks with owners, dates and status visible in the channel, without leaving Teams.
We create and sync tasks from the summary
- What we do: we move from minutes to Planner/To Do in one step.
- Ready prompt: “Convert these decisions and pending items into Planner tasks (plan ‘Project X’), assign owners, add a due date and label ‘Q4’. Post a summary with mentions in the channel.”
- Expected output: tasks created in Planner, automatic mentions to each owner and confirmation message in the channel.
We keep status live with Loop
- What we do: we anchor a Loop component in the #tracking channel.
- Ready prompt: “Create a Loop ‘Weekly Tracking’ with columns: Task | Owner | Date | Status (Not started/In progress/Done) | Dependencies | Notes. Initialise with the Planner tasks.”
- Expected output: synchronised table that the team updates online; the PM uses this view as a stand-up.
We close the loop with reminders and dependencies
- What we do: we control due dates and blockers without chasing anyone.
- Ready prompt: “Generate reminders 48 h before each due date and mention the owners. Identify tasks with cross-dependencies and mark priority ‘High’ if they affect a milestone.”
- Expected output: chat reminders, adjusted priorities and blockers list
Recommended reading
Data, privacy & security for Microsoft 365 Copilot → supports security, privacy, data residency and compliance referenced in this guide.
Team prompt bank
Objective: we centralise the organisation’s operational prompts, ready to copy, classified by use case and with instant search.
.banco-prompts { max-width: 1060px; margin: 0 auto; padding: 20px; font-family: system-ui, -apple-system, “Segoe UI”, Roboto, Arial, sans-serif; color: #111827; background: #ffffff; } .banco-prompts h2 { margin: 0 0 12px 0; font-size: 28px; line-height: 1.2; } .bp-intro { margin: 0 0 16px 0; color: #374151; font-size: 14px; } .bp-toolbar { display: grid; grid-template-columns: 1fr 1fr; gap: 12px; margin-bottom: 16px; } .bp-search { display: flex; align-items: center; gap: 8px; border: 1px solid #e5e7eb; border-radius: 10px; padding: 10px 12px; background: #fafafa; } .bp-search input { width: 100%; border: 0; outline: 0; background: transparent; font-size: 14px; color: #111827; } .bp-filters { display: flex; flex-wrap: wrap; gap: 8px; justify-content: flex-end; } .bp-chip { appearance: none; border: 1px solid #d1d5db; background: #f9fafb; padding: 8px 12px; font-size: 13px; border-radius: 999px; cursor: pointer; transition: background 0.15s ease; user-select: none; } .bp-chip:hover { background: #f3f4f6; } .bp-chip[aria-pressed=”true”] { background: #eef2ff; border-color: #c7d2fe; } .bp-grid { display: grid; grid-template-columns: 1fr 1fr; gap: 12px; } .bp-card { border: 1px solid #e5e7eb; border-radius: 12px; padding: 14px; background: #ffffff; box-shadow: 0 1px 2px rgba(0,0,0,0.04); display: flex; flex-direction: column; gap: 10px; } .bp-head { display: flex; align-items: start; justify-content: space-between; gap: 12px; } .bp-title { margin: 0; font-size: 16px; line-height: 1.3; } .bp-meta { display: inline-flex; gap: 6px; flex-wrap: wrap; } .bp-pill { display: inline-block; padding: 2px 8px; border-radius: 999px; font-size: 11px; border: 1px solid #e5e7eb; background: #f9fafb; color: #374151; } .bp-actions { display: inline-flex; gap: 8px; flex-wrap: wrap; } .bp-btn { appearance: none; border: 1px solid #d1d5db; background: #f9fafb; padding: 8px 10px; font-size: 12px; border-radius: 8px; cursor: pointer; } .bp-btn:hover { background: #f3f4f6; } .bp-text { border: 1px solid #e5e7eb; border-radius: 8px; padding: 10px; background: #fbfbfb; font-size: 13px; line-height: 1.5; white-space: pre-wrap; color: #111827; } .bp-hint { font-size: 12px; color: #6b7280; margin: 0; } .bp-empty { display: none; text-align: center; padding: 24px; color: #6b7280; border: 1px dashed #e5e7eb; border-radius: 10px; background: #fafafa; } @media (max-width: 900px) { .bp-grid { grid-template-columns: 1fr; } .bp-toolbar { grid-template-columns: 1fr; } .bp-filters { justify-content: flex-start; } } All Summary Decision Tone Tasks Documents Meetings ComparisonActionable thread summary
Summary Meetings Copy Summarise this thread in 5 points, label “blockers”, propose 2 decision options and recommend the best one with a brief justification. Include links to the key messages.Use: we pin the result as a Loop in the channel.
Executive minutes with tasks (RACI)
Decision Meetings Tasks Copy Generate the minutes in executive format: objective, decisions (with timestamp), tasks in RACI, risks and next milestones. Convert the tasks to Planner (plan “Project X”) and mention each owner in the channel.Use: we launch this after the meeting ends and the transcript is validated.
Tone adaptation for CFO
Tone Copy Rewrite this message for a CFO: executive tone, 120–150 words, with a clear CTA to approve the budget today. Highlight cost and risk impact.Use: we reduce back-and-forth with financial management.
From decisions to Planner and Loop
Tasks Copy Convert these decisions into Planner tasks (plan “Project X”): assign owners, add a due date and label “Q4”. Create a Loop component with columns Task | Owner | Date | Status and publish it in the channel.Use: we close the gap between agreements and execution.
Document comparison v2 vs v3
Documents Comparison Copy Compare v2 and v3 of the proposal and highlight changes affecting scope, price and timeline. Return a differences table with a next step recommendation.Use: we speed up reviews without opening all the files.
Weekly summary with KPIs
Summary Copy Generate a weekly team summary with productivity and Copilot adoption KPIs: % meetings with minutes, tasks created/completed, time to decision and open blockers. Add trends and 3 recommendations.Use: we publish in the project channel every Monday.
Pre-meeting briefing
Meetings Summary Copy Summarise in 6 bullet points the context of this meeting using the latest documents from the channel and related emails. Flag risks and open questions with links to the sources.Use: we launch this from the meeting chat.
Normalise tone for executive client
Tone Copy Adapt this message to “executive-client” tone, 130 words, no technical jargon. Keep the decision proposal and the CTA with a date.Use: we reduce friction in external communications.
No prompts match the filters or search. (function () { const q = document.getElementById(‘bp-q’); const list = document.getElementById(‘bp-list’); const empty = document.getElementById(‘bp-empty’); const chips = Array.from(document.querySelectorAll(‘.bp-chip’)); let activeFilter = ‘all’;function normalize(s) { return (s || ”).toLowerCase() .normalize(‘NFD’).replace(/[\u0300-\u036f]/g, ”); }function applyFilters() { const term = normalize(q.value); const items = Array.from(list.querySelectorAll(‘.bp-card’)); let visibleCount = 0;items.forEach(card => { const tags = normalize(card.getAttribute(‘data-tags’)); const text = normalize(card.innerText); const matchFilter = activeFilter === ‘all’ || tags.includes(activeFilter); const matchSearch = !term || text.includes(term); const show = matchFilter && matchSearch; card.style.display = show ? ” : ‘none’; if (show) visibleCount += 1; });empty.style.display = visibleCount === 0 ? ‘block’ : ‘none’; }// Chip filters chips.forEach(btn => { btn.addEventListener(‘click’, () => { chips.forEach(c => c.setAttribute(‘aria-pressed’, ‘false’)); btn.setAttribute(‘aria-pressed’, ‘true’); activeFilter = btn.dataset.filter || ‘all’; applyFilters(); }); });// Search q.addEventListener(‘input’, applyFilters);// Copy document.addEventListener(‘click’, (ev) => { const btn = ev.target.closest(‘.bp-btn[data-copy]’); if (!btn) return; const sel = btn.getAttribute(‘data-copy’); const el = document.querySelector(sel); if (!el) return; const text = el.innerText.trim();if (navigator.clipboard && window.isSecureContext) { navigator.clipboard.writeText(text); } else { const ta = document.createElement(‘textarea’); ta.value = text; document.body.appendChild(ta); ta.select(); document.execCommand(‘copy’); document.body.removeChild(ta); }const original = btn.textContent; btn.textContent = ‘Copied ✓’; btn.disabled = true; setTimeout(() => { btn.textContent = original; btn.disabled = false; }, 1400); });// Initial application applyFilters(); })();We automate with Power Automate from Teams (3 quick flows)
Objective: we move from summary to execution without manual work, orchestrating Planner, Calendar and Teams with simple triggers and clear messages.
Flow 1: From approved minutes to Planner tasks
- When: when the message “[MINUTES APPROVED]” is posted in the project channel.
- Trigger: Microsoft Teams → When a new channel message is added (keyword: [MINUTES APPROVED]).
- Actions:
- Parse content of the message with Compose → we extract Task | Owner | Date (Copilot can return this as a table).
- Create task in Planner → project Plan; Assign to owner; Due date; Labels (e.g. Q4).
- Update task detail with link to evidence (files or transcript timestamps).
- Post confirmation in Teams with mentions to owners.
- Prompt to Copilot that we paste in the source message:“Convert the decisions into a table Task | Owner | Date | Evidence. Use real usernames and ISO dates.”
- Value: bulk task creation in seconds and traceability from the minutes.
Flow 2: Milestones to calendar with smart reminder
- When: if a task contains “delivery“, “presentation” or “milestone“.
- Trigger: Planner → When a task is created or updated (filter by keywords in the title).
- Actions:
- Create event in Channel Calendar (or team Exchange) with title, due date and link to the card.
- Add 48 h reminder before and same-day reminder.
- Send Adaptive Card to the channel with Milestone | Owner | Success criterion.
- Adaptive Card template (summary):Milestone | Date | Owner | Success criterion | Link to Planner
- Value: no one misses a critical milestone and the committee receives actionable context.
Flow 3: Automatic weekly summary with productivity KPIs
- When: every Monday at 09:00 (team time).
- Trigger: Recurrence (weekly).
- Actions:
- Query Planner: tasks created/completed in the last 7 days.
- Query Teams: number of post-meeting summary posts.
- Calculate KPIs: % meetings with minutes, tasks completed, time to decision (if we use a label in the summaries).
- Generate text with Copilot: “Week synthesis + 3 recommendations“.
- Post in channel and attach CSV with the detail (optional, SharePoint).
- Prompt to Copilot within the flow:“Draft an executive summary ≤120 words with these KPIs and their trend. Propose 3 prioritised actions (MoSCoW).”
- Value: weekly transparency and continuous improvement without manual intervention.
Real role-based examples: quick templates ready to execute
Objective: we apply Copilot in Teams to concrete scenarios for Sales, Customer Service, Operations/IT and Finance, with ready prompts, expected output and next action.
Sales: active opportunity in progress
- What we do: we prepare post-meeting follow-up and the next commercial touch.
- Prompt to Copilot: “Summarise the last discovery call for OPP-{{ID}}: pains, budget, decision-makers, success criteria, risks and next steps. Draft a follow-up email with 3 value bullets and a CTA to close a proposal meeting.”
- Expected output: executive summary + email draft with links to notes and documents.
- Next action: “Convert the next steps into Planner tasks (plan ‘Sales’) and pin a Loop ‘OPP-{{ID}} Status’ with Task | Owner | Date | Status.”
- Enrichment proposal: Excel dashboard “Forecast by stage” with probability, amount, next event and opportunity age; we ask Copilot to generate the funnel chart.
Customer service: critical case with SLA
- What we do: we synthesise the case and respond with empathy and a plan.
- Prompt to Copilot: “From the client chat and ticket #{{ID}}, generate an empathetic response with ETA, mitigation steps and a request for evidence (logs, screenshots). Flag risks if we do not receive the information before {{date}}.”
- Expected output: message ready to send through the case channel and task list for L1/L2.
- Next action: “Create tasks in Planner (plan ‘Support’) with SLA-based priority; post an Adaptive Card in #critical-cases with status and next milestones.”
- Enrichment proposal: response macro with variables (client, product, version, ETA) for reuse; Dynamics 365 Customer Service connector to sync notes.
Operations/IT: incident post-mortem
- What we do: we generate a complete and actionable post-mortem.
- Prompt to Copilot: “Build the post-mortem for incident INC-{{ID}}: timeline with timestamps, root cause using 5 whys, corrective (CAPA) and preventive actions, owners and dates. Flag evidence in the transcript and related PRs.”
- Expected output: Word/Loop document with sections and RACI table for actions.
- Next action: “Convert the actions to Planner (plan ‘Operations’) and create a review event in 14 days.”
- Enrichment proposal: runbook in Wiki/SharePoint with repeatable steps, detection metrics and verification check; Power Automate for reminder if a preventive action is due in <72 h.
Finance: monthly close and committee
- What we do: we prepare a summary of variances and close decisions.
- Prompt to Copilot: “Summarise the close committee: variances >3%, treasury risks, pending adjustments and reconciliations by owner. Generate 3 slides for management with decision, impact and next step.”
- Expected output: executive summary and 3-slide deck with key messages.
- Next action: “Create reconciliation tasks in Planner (plan ‘Finance’) and a calendar event for the ‘Committee Presentation’ with a 48 h reminder.”
- Enrichment proposal: Excel with variance table and column chart; control prompt: “Explain the 3 most likely root causes of this variance and propose corrective actions.”
Quick role-based templates (copy and paste in the channel)
- Sales – follow-up email:“Draft an email in consultative tone, ≤150 words, reinforcing 3 detected pains, proposing 2 concrete benefits and closing with a CTA for a proposal meeting this week.”
- Support – client update:“Generate a clear and empathetic update: current status, ETA, steps taken, request for evidence and next milestones. Avoid technical jargon and offer an alternative channel if urgent.”
- IT – CAPA table:“Return table Action | Type (Corrective/Preventive) | Owner | Date | Required evidence, derived from post-mortem INC-{{ID}}.”
- Finance – executive summary:“Summarise for CFO in 100 words: key variances, cash-flow impact, required decisions and resolution date.”
Minimum weekly metrics per role that we ask Copilot for
- Sales: % opportunities with a defined next step, average age per stage, win rate by segment.
- Support: first response SLA, time to resolution, reopenings.
- Operations: MTTR, overdue preventive actions, incidents by category.
- Finance: close tasks completed, open variances >3%, decisions pending committee.
Measurement and adoption: what we measure every week
Objective: we verify the real impact of Copilot in Teams with operational KPIs, clear sources and weekly routines that allow us to correct and scale.
Minimum productivity and usage KPIs
- % of meetings with Copilot-generated minutes = published minutes / total meetings.Source: transcripts and “Post-meeting summary” messages in the channel.
- Time to decision = minutes from meeting start to first marked agreement.Source: transcript timestamps and the Decisions block.
- Tasks created vs. completed (week) in Planner by project.Source: Planner Graph or CSV export of the plan.
- Open blockers and average blocker age.Source: Loop “Decisions and blockers” and labels in Planner.
- Adoption by team = users who have launched “summary/minutes/tasks” prompts at least once/week.Source: messages with keywords and Adaptive Cards log.
Operational dashboard in Power BI (inside Teams)
- Connectors: SharePoint/Teams (messages and files), Planner, optional Graph Reports.
- Visible metrics: % minutes trend, cumulative task chart, time to decision by team, blockers by category.
- Slicers: team, project, meeting type (committee, discovery, post-mortem).
- Formatting rules: green if % minutes ≥ 80%, amber between 60–79%, red < 60%. Target time to decision ≤ 15 min.
Weekly routine (30 minutes)
- Monday 09:00: Copilot posts KPI summary in the channel with 3 recommendations.
- Monday 12:00: quick review of the Power BI dashboard; we agree on 2 corrective actions.
- Wednesday: automatic reminder to owners of blockers >72 h.
- Friday: task status and preparation of next milestones for the following week.
Ready prompts to measure and improve
- Weekly summary: “Generate an executive summary ≤120 words with % meetings with minutes, tasks created/completed, time to decision and open blockers. Add 3 prioritised actions (MoSCoW).”
- Findings and actions: “From the dashboard, identify 3 bottlenecks and propose actions with owner and date (table).”
- Minutes quality: “Evaluate 5 random minutes with this checklist: clear objective, decisions with timestamp, complete RACI, risks, next milestones. Return a score 0–5 and suggestions.”
Deployment health checklist
- Minutes ≥ 80% of meetings; overdue tasks = 0; blockers with owner = 100%.
- Permissions reviewed on the project site; sensitivity labels
- Team prompts updated in #prompt-bank with real examples.
Dataset template (Power BI · Teams · Planner)
Objective: we define a canonical schema to measure adoption and productivity of Copilot in Teams. It includes Meetings, Summaries, PlannerTasks, Blockers and Users tables, with keys and relationships ready to model.
.dataset-template { max-width: 1120px; margin: 0 auto; padding: 20px; font-family: system-ui, -apple-system, “Segoe UI”, Roboto, Arial, sans-serif; color: #111827; background: #ffffff; } .dataset-template h2 { margin: 0 0 10px 0; font-size: 28px; line-height: 1.2; } .ds-intro { margin: 0 0 18px 0; color: #374151; font-size: 14px; } .grid { display: grid; grid-template-columns: 1fr 1fr; gap: 16px; } .card { border: 1px solid #e5e7eb; border-radius: 12px; background: #fff; box-shadow: 0 1px 2px rgba(0,0,0,0.04); padding: 14px; } .card h3 { margin: 0 0 10px 0; font-size: 18px; line-height: 1.3; } .meta { display: flex; gap: 12px; flex-wrap: wrap; margin-bottom: 10px; font-size: 12px; color: #6b7280; } .pill { display: inline-block; padding: 2px 8px; border-radius: 999px; border: 1px solid #e5e7eb; background: #f9fafb; color: #374151; font-size: 11px; } .table-wrap { overflow-x: auto; } table { width: 100%; border-collapse: collapse; font-size: 13px; } th, td { border: 1px solid #e5e7eb; padding: 8px 10px; text-align: left; vertical-align: top; } th { background: #f9fafb; font-weight: 700; white-space: nowrap; } code { font-family: ui-monospace, SFMono-Regular, Menlo, Monaco, Consolas, “Liberation Mono”, monospace; font-size: 12px; background: #f8fafc; padding: 0 4px; border-radius: 4px; border: 1px solid #eef2f7; } .relations, .notes, .exports { margin-top: 18px; } .relations ul, .notes ul { margin: 6px 0 0 18px; } .exports pre { margin: 8px 0 0 0; padding: 10px; background: #0b1220; color: #e5e7eb; border-radius: 8px; overflow: auto; } @media (max-width: 960px) { .grid { grid-template-columns: 1fr; } } @media print { .dataset-template { box-shadow: none; padding: 0; } }Meetings (meeting facts)
Key: MeetingId Grain: 1 row per meeting Source: Teams/Graph| Column | Type | Description | Example | Required |
|---|---|---|---|---|
| MeetingId | Text (PK) | Unique identifier of the meeting. | MTG-2025-10-29-1432 | Yes |
| TeamId | Text | Team/channel ID. | TEAM-OPS-01 | Yes |
| ProjectKey | Text | Project key for segmentation. | PRJ-COPILOT | No |
| StartDateTime | DateTime | Meeting start (UTC or normalised local TZ). | 2025-10-29T09:00:00Z | Yes |
| EndDateTime | DateTime | Meeting end. | 2025-10-29T09:45:00Z | Yes |
| MeetingType | Text | Type (Committee, Discovery, Post-mortem…). | Committee | No |
| HasTranscript | Boolean | Transcript/recording exists. | true | No |
| ActaPublished | Boolean | Minutes published in channel. | true | No |
| FirstDecisionMinute | Number | Minute of the first agreement (timestamp). | 12.5 | No |
| ParticipantsCount | Number | Number of attendees. | 7 | No |
Summaries (Copilot summaries/minutes)
Key: SummaryId Relation: Meetings.MeetingId Source: Teams/SharePoint| Column | Type | Description | Example | Required |
|---|---|---|---|---|
| SummaryId | Text (PK) | Unique identifier of the summary/minutes. | SUM-2025-10-29-01 | Yes |
| MeetingId | Text (FK) | Associated meeting. | MTG-2025-10-29-1432 | Yes |
| PublishedDateTime | DateTime | Publication date/time. | 2025-10-29T10:02:00Z | Yes |
| DecisionsCount | Number | Number of extracted decisions. | 3 | No |
| TasksExtracted | Number | Derived tasks. | 5 | No |
| SummaryUrl | Text | URL in Teams/SharePoint. | https://…/minutes_2025_10_29 | No |
PlannerTasks (execution tasks)
Key: TaskId Relation: Meetings.MeetingId optional Source: Planner Graph| Column | Type | Description | Example | Required |
|---|---|---|---|---|
| TaskId | Text (PK) | Unique identifier of the task. | PLN-93841 | Yes |
| MeetingId | Text (FK) | Origin (if it comes from a meeting). | MTG-2025-10-29-1432 | No |
| Title | Text | Task title. | Update Q4 budget | Yes |
| OwnerUserId | Text (FK) | Owner (Users). | USR-jgomez | Yes |
| ApproverUserId | Text (FK) | Approver (RACI=A). | USR-dirproj | No |
| Priority | Text | MoSCoW: Must/Should/Could/Won’t. | Must | No |
| DueDate | Date | Due date. | 2025-11-07 | No |
| Status | Text | Status (Not started/In progress/Done). | In progress | No |
| EvidenceUrl | Text | Link to evidence/file/clip. | https://…/evidence.pdf | No |
| Labels | Text | Labels (CSV: Q4;Risk). | Q4;Finance | No |
Blockers (blockers and risks)
Key: BlockerId Relation: Meetings and/or PlannerTasks Source: Loop/Planner| Column | Type | Description | Example | Required |
|---|---|---|---|---|
| BlockerId | Text (PK) | Unique identifier of the blocker. | BLK-1203 | Yes |
| MeetingId | Text (FK) | Meeting where it is detected. | MTG-2025-10-29-1432 | No |
| TaskId | Text (FK) | Impacted task (if applicable). | PLN-93841 | No |
| Title | Text | Concise description of the blocker. | External vendor dependency | Yes |
| OwnerUserId | Text (FK) | Owner to resolve it. | USR-pmo | No |
| Probability | Text | Low/Medium/High. | Medium | No |
| Impact | Text | Low/Medium/High. | High | No |
| Mitigation | Text | Proposed mitigation action. | Add 3-day buffer | No |
| AgeDays | Number | Days since detection. | 5 | No |
| Status | Text | Open/In progress/Resolved. | Open | No |
Users (people dimension)
Key: UserId Role: dimension Source: AAD/Graph| Column | Type | Description | Example | Required |
|---|---|---|---|---|
| UserId | Text (PK) | Unique identifier of the user. | USR-jgomez | Yes |
| DisplayName | Text | Display name. | Javier Gómez | Yes |
| Department | Text | Department/area. | Operations | No |
| Role | Text | Business role (PM, CFO, Support…). | PM | No |
| Text | Corporate email. | jgomez@example.com | No | |
| Country | Text | Country/Region (segmentation). | ES | No |
Table relationships
- Meetings 1—N Summaries by MeetingId.
- Meetings 1—N PlannerTasks (optional) by MeetingId.
- Meetings 1—N Blockers by MeetingId.
- PlannerTasks 1—N Blockers by TaskId (if the blocker affects a task).
- Users 1—N PlannerTasks by UserId = OwnerUserId and/or ApproverUserId.
Suggested directionality: dimensions (Users) and masters (Meetings) → facts (Summaries, PlannerTasks, Blockers).
Modelling notes
- Time zone: we normalise StartDateTime and PublishedDateTime to UTC and derive date/time columns (Year, Month, Week, Day, Hour).
- Data quality: if there is no Summary for a Meeting, ActaPublished = false and DecisionsCount = 0.
- MoSCoW: we standardise Priority in PlannerTasks to segment by criticality.
- Privacy: we avoid sensitive content in free-text columns; we use internal URLs with inherited permissions.
Sample CSV headers
We can export from Graph/SharePoint and conform these CSVs for the initial ingestion.
Meetings.csv MeetingId,TeamId,ProjectKey,StartDateTime,EndDateTime,MeetingType,HasTranscript,ActaPublished,FirstDecisionMinute,ParticipantsCount Summaries.csv SummaryId,MeetingId,PublishedDateTime,DecisionsCount,TasksExtracted,SummaryUrl PlannerTasks.csv TaskId,MeetingId,Title,OwnerUserId,ApproverUserId,Priority,DueDate,Status,EvidenceUrl,Labels Blockers.csv BlockerId,MeetingId,TaskId,Title,OwnerUserId,Probability,Impact,Mitigation,AgeDays,Status Users.csv UserId,DisplayName,Department,Role,Email,Country| Indicator | Initial situation | With Copilot (6 months) | Impact |
|---|---|---|---|
| Mean time to resolution (MTTR) | 4.2 hours | 2.5 hours | ↓ 40% |
| Customer satisfaction (CSAT) | 78% | 93% | ↑ +15 pp |
| Tickets resolved automatically | 5% | 32% | ↑ +27 pp |
| Internal escalations | 1,200/month | 780/month | ↓ 35% |

Intelligent summaries
Copilot analyses conversations and generates precise case syntheses, accelerating understanding and response.
Knowledge suggestions
It proposes relevant articles based on the client’s context and the type of incident.
Sentiment analysis
It detects emotions and helps prioritise critical cases with AI-assisted emotional intelligence.
Best practices and common mistakes
Objective: we maximise Copilot’s performance in Teams by avoiding the most common failures and establishing usage, governance and quality standards.
Essential best practices
- Context first, prompt second: we anchor the agenda and documents in the invitation and in the channel. We ask for clear output formats: “in 5 bullets“, “table with X/Y/Z“, “≤150 words“.
- Repeatable structure: we use templates for minutes, RACI, risks and milestones. Copilot fills in, we validate.
- Permissions up to date: we review inheritance in SharePoint, apply sensitivity labels and DLP. Less is more: minimum necessary access.
- Task with evidence: in Planner, we always add a link to the evidence. We define DoD (Definition of Done) by task type.
- Tone and recipient: we normalise messages with role-based guides (CFO, Management, Technical, Client). Consistency > creativity.
- Light and constant measurement: % minutes, time to decision, tasks created/completed, blockers. Weekly 30-minute review.
Mistakes we must avoid
- Vague prompts without format: “What do you think?” generates noise. We ask for structure and output limit.
- Meetings without transcript/files: without sources, Copilot hallucinates or omits. We enable transcription and upload material.
- Chaotic channels: inconsistent names, uncontrolled versions and files in email break context. Everything to the channel with a convention.
- Lax permissions: sharing with “Everyone” by default or inviting external users to sensitive channels. We segment and apply labels.
- Tasks without due date or owner: Copilot creates perfect lists that are not executed. Owner + date always, RACI when applicable.
- Not validating critical deliverables: Copilot does not replace judgement. We validate financial data, legal commitments and sensitive communications.
Operational checklist "ready to use"
- Before meeting: agenda with objective, linked files, transcription enabled.
- During: we mark decisions and ask for table decision | owner | date with timestamp.
- After: executive minutes + Planner + Loop in the channel; mentions to owners.
- Every Monday: KPI summary with 3 recommendations and 2 actions
- Every month: permissions audit of the site and clean-up of prompt bank.
Quality prompt snippets
- Mandatory structure: “Return output in 5 bullets with action verbs and priority (High/Medium/Low).”
- Standard table: “Convert into table Task | Owner | Date | Status | Evidence, sorted by ascending date.”
- Permission control: “Before proposing files, verify they are in the team site and link only locations accessible to the channel.”
- Role-based writing: “Rewrite for CFO in ≤140 words, risks and cost explicit, CTA with date.”
Recommended readings
How to use Copilot in Teams meetings → supports practical use cases for summary, decisions and tasks during and after the meeting.
Monthly review assisted by Copilot
Objective: we audit the real use of Copilot in Teams to improve quality, compliance and productivity, with a monthly cycle that analyses minutes, tasks and blockers, proposes corrective actions and leaves traceable evidence in the project channel.
Scope and preparation (30 minutes prior)
- Samples to evaluate: 10 minutes and 20 tasks randomly selected from the last month by team/project.
- Sources: transcripts, published minutes, Planner, Loop “Decisions and blockers”, and post-meeting messages.
- Reference checklist: clear objective, decisions with timestamp, complete RACI, risks with mitigation, milestones with success criterion, tasks with evidence and due date.
- Permissions and security: we work within the team site; we do not extract data outside the scope; we review sensitivity labels
Step 1 · Automatic sample selection
- Prompt to Copilot (channel #tracking):“Randomly select 10 minutes and 20 tasks from the last month in this team. Return two lists with: title/URL, date, owner, and labels.”
- Expected output: two tables with internal links and metadata ready for audit.
Step 2 · Guided quality evaluation
- Prompt to Copilot (per set of minutes):“Evaluate these minutes with the checklist: 1) clear objective 2) decisions with timestamp 3) tasks with RACI 4) risks + mitigation 5) next milestones with success criterion. Score 0–5 and suggest 2 concrete improvements. Link to the transcript at each decision.”
- Prompt to Copilot (per Planner task):“Evaluate this task: 1) actionable title 2) owner 3) due date 4) linked evidence 5) MoSCoW priority 6) dependencies. Score 0–5 and suggest 1 improvement.”
- Expected output: evaluation table with score, gaps and links to evidence.
Step 3 · Findings and prioritised actions
- Prompt to Copilot (synthesis):“Group the detected gaps and propose 5 corrective actions prioritised with MoSCoW. Return table Action | Owner | Date | Expected impact | Evidence to generate.”
- Expected output: improvement plan with owners and dates, ready to convert to Planner.
Step 4 · Conversion to execution and traceability
- Prompt to Copilot:“Convert this plan into Planner tasks (plan ‘Copilot Improvement – {{Project}}’) with due dates and label ‘Audit’. Post a summary in the channel with mentions to the owners.”
- Expected output: tasks created, summary posted and mentions to owners.
Quality checklist template (copy and paste)
- Minutes: Objective defined, decisions with timestamp, RACI in tasks, risks with mitigation, milestones with success criterion, links to sources.
- Tasks: Actionable title, owner + due date, linked evidence, MoSCoW priority, dependencies, status consistent with progress.
Metrics we record every month
- Minutes with score ≥4/5 and tasks with score ≥4/5.
- % decisions with timestamp and % tasks with evidence.
- Time to decision P50 and average blocker age.
- Compliance with corrective actions from the previous cycle.
Standard audit report (structure)
- Executive summary (≤150 words) with 3 key findings and 3 actions.
- Evaluation table (minutes and tasks) with score and links.
- Improvement plan with owner, date and impact.
- Annexes: CSV export of audited minutes/tasks, screenshots or links to transcripts.
Recommended automation (Power Automate)
- Trigger: monthly recurrence (day 1, 09:00).
- Steps:
- Obtain samples (SharePoint/Planner).
- Invoke Copilot with the evaluation prompts.
- Generate audit table (Adaptive Card) and post in #tracking.
- Create task plan “Copilot Improvement – {{Project}}” and assign owners.
- Save CSV and audit minutes in /Audits/{{YYYY-MM}}.
Roles and responsibilities (review RACI)
- R (Responsible): Project PM — executes the review and validates Copilot’s outputs.
- A (Accountable): Team owner — accepts the action plan.
- C (Consulted): Security/Compliance — reviews permissions and labels.
- I (Informed): Involved team — receives summary and tasks.
Ready prompt snippets to anchor in the channel
- Sample selection: “Select 10 minutes and 20 tasks from the last month and return them in a table with links.”
- Minutes evaluation: “Score 0–5 with checklist and suggest 2 improvements; link to timestamps.”
- Task evaluation: “Score 0–5 and suggest 1 improvement; verify evidence and dependencies.”
- Improvement plan: “Group gaps and return 5 MoSCoW actions with owner, date and impact.”
- Execution: “Convert actions to Planner (label ‘Audit’) and post summary with mentions.”
Cycle success criteria
- ≥80% of minutes and ≥80% of tasks with score ≥4/5.
- 100% of decisions with timestamp in audited minutes.
- 100% of tasks with evidence and due date.
- ≥90% closure of corrective actions before the next cycle.
Governance and compliance note
- We always work within the team context, respecting permission inheritance and sensitivity labels. We do not export sensitive content outside SharePoint/Teams. We humanly validate findings before communicating them to management.
Quick templates (ready to paste)
We provide
reusable micro-templatesthat you can
copy and paste as-isinto
OneNote/Loop,
Teams (channels and chat)and
Outlook. They are designed so that
you do not waste time structuringand so that
Copilot completes or transformsthe content with
a minimal prompt. Below are the
three templatesreferenced, ready for immediate use, with
markersthat Copilot can fill in from the
transcriptand the
channel files.
Executive minutes (OneNote/Loop)
we paste this structure into
Loopor
OneNoteand ask Copilot:
“Fill in each block from the transcript and cited documents. Add timestamps in Decisions.”Executive minutes — [Project: {{PROJECT}}] · [Meeting: {{TITLE}}] · {{DATE}}
.acta-ejecutiva{max-width:920px;margin:0 auto;padding:16px;background:var(–bg);font-family:inherit;color:#111827} .acta-ejecutiva .card{border:1px solid var(–b);border-radius:12px;background:#fff;padding:14px;margin:10px 0} .acta-ejecutiva h4{margin:0 0 8px 0;font-size:18px;line-height:1.35} .acta-ejecutiva p{margin:0} .acta-ejecutiva ul{margin:8px 0 0 18px;padding:0} .acta-ejecutiva li{margin:6px 0} .acta-ejecutiva .hint{font-size:12px;color:var(–muted);margin-top:8px} .acta-ejecutiva .table-wrap{overflow-x:auto;margin-top:8px} .acta-ejecutiva table{width:100%;border-collapse:collapse;font-size:14px} .acta-ejecutiva th,.acta-ejecutiva td{border:1px solid var(–b);padding:10px;text-align:left;vertical-align:top} .acta-ejecutiva th{background:#f9fafb;font-weight:700;white-space:nowrap} @media (max-width:640px){.acta-ejecutiva{padding:12px}} Objective{{1–2 clear sentences}}
Decisions (with timestamp)- {{Decision 1}} — {{Owner}} — {{Date}} — {{00:12:34}}
- {{Decision 2}} — {{Owner}} — {{Date}} — {{00:27:10}}
- {{Decision 3}} — {{Owner}} — {{Date}} — {{00:35:02}}
| Task | R (responsible) | A (accountable) | C (consulted) | I (informed) | Date |
|---|---|---|---|---|---|
| {{Task 1}} | {{Name}} | {{Name}} | {{Name}} | {{Name}} | {{YYYY-MM-DD}} |
| {{Task 2}} | {{Name}} | {{Name}} | {{Name}} | {{Name}} | {{YYYY-MM-DD}} |
Tip: convert these rows into Planner tasks with Copilot.
Risks and mitigation- {{Risk}} — Prob: {{Low/Medium/High}} · Impact: {{Low/Medium/High}} · Mitigation: {{Action}} · Owner: {{Name}}
- {{Milestone}} — {{Date}} — Success criterion: {{Definition}}
Post-meeting message in channel (Teams)
Use: we paste the prompt as-is in the meeting chat or in the project channel. Copilot generates the summary and, if indicated, creates Planner tasks and mentions the owners.
Prompt to Copilot
.prompt-copilot { max-width: 920px; margin: 0 auto; padding: 16px; font-family: system-ui, -apple-system, “Segoe UI”, Roboto, Arial, sans-serif; color: #111827; } .prompt-card { border: 1px solid var(–b); border-radius: 12px; background: #fff; padding: 14px; box-shadow: 0 1px 2px rgba(0,0,0,0.04); } .prompt-head { display: flex; align-items: start; justify-content: space-between; gap: 12px; } .prompt-head h4 { margin: 0; font-size: 18px; line-height: 1.35; } .prompt-actions { display: inline-flex; gap: 8px; } .btn-copy { appearance: none; border: 1px solid #d1d5db; background: #f9fafb; padding: 8px 10px; font-size: 12px; border-radius: 8px; cursor: pointer; } .btn-copy:hover { background: #f3f4f6; } .prompt-text { margin-top: 10px; border: 1px solid #e5e7eb; border-radius: 8px; padding: 12px; background: #fbfbfb; font-size: 14px; line-height: 1.55; white-space: pre-wrap; } .hint { margin: 8px 0 0 0; font-size: 12px; color: var(–muted); } @media (max-width: 640px) { .prompt-head { flex-direction: column; align-items: flex-start; } .btn-copy { width: 100%; } } Summary + task table + publication Copy Summarise in 5 bullets the decisions and add a task table (Task | Owner | Date). Post the summary in the #{{project-X}} channel, convert the tasks to Planner (plan ‘{{Project}}’) and mention each owner.Tip: launch it in the meeting chat or in the project channel with the transcript and files already linked.
(function () { document.addEventListener(‘click’, function (ev) { const btn = ev.target.closest(‘.btn-copy[data-copy]’); if (!btn) return; const sel = btn.getAttribute(‘data-copy’); const el = document.querySelector(sel); if (!el) return; const text = el.innerText.trim();if (navigator.clipboard && window.isSecureContext) { navigator.clipboard.writeText(text); } else { const ta = document.createElement(‘textarea’); ta.value = text; document.body.appendChild(ta); ta.select(); document.execCommand(‘copy’); document.body.removeChild(ta); }const original = btn.textContent; btn.textContent = ‘Copied ✓’; btn.disabled = true; setTimeout(() => { btn.textContent = original; btn.disabled = false; }, 1400); }); })();Post-meeting summary (to publish in the channel)
.resumen-post { max-width: 920px; margin: 0 auto; padding: 16px; font-family: system-ui, -apple-system, “Segoe UI”, Roboto, Arial, sans-serif; color: #111827; } .rp-card { border: 1px solid var(–b); border-radius: 12px; background: #fff; padding: 14px; box-shadow: 0 1px 2px rgba(0,0,0,0.04); } .rp-head { display: flex; align-items: start; justify-content: space-between; gap: 12px; } .rp-head h4 { margin: 0; font-size: 18px; line-height: 1.35; } .rp-actions { display: inline-flex; gap: 8px; } .btn-copy { appearance: none; border: 1px solid #d1d5db; background: #f9fafb; padding: 8px 10px; font-size: 12px; border-radius: 8px; cursor: pointer; } .btn-copy:hover { background: #f3f4f6; } .rp-block { margin-top: 10px; } .rp-title { font-weight: 700; margin: 0 0 6px 0; } .rp-list { margin: 0; padding-left: 20px; } .rp-table-wrap { overflow-x: auto; margin-top: 8px; } table { width: 100%; border-collapse: collapse; font-size: 14px; } th, td { border: 1px solid #e5e7eb; padding: 10px; text-align: left; vertical-align: top; } th { background: #f9fafb; font-weight: 700; white-space: nowrap; } .rp-note { margin-top: 10px; font-size: 13px; color: var(–muted); } .rp-copy-src { display: none; } @media (max-width: 640px) { .rp-head { flex-direction: column; align-items: flex-start; } .btn-copy { width: 100%; } } Publication template Copy textPost-meeting summary — {{Project}} · {{Date}}
- {{Decision 1}}
- {{Decision 2}}
- {{Decision 3}}
- {{Key blocker}} (owner: {{Name}})
- Next milestone: {{Milestone}} → {{Date}}
Tasks created in Planner
| Task | Owner | Date |
|---|---|---|
| {{Task}} | @{{User}} | {{YYYY-MM-DD}} |
Note: please review dependencies and update status in the pinned Loop.
**Post-meeting summary — {{Project}} · {{Date}}** • {{Decision 1}} • {{Decision 2}} • {{Decision 3}} • {{Key blocker}} (owner: {{Name}}) • Next milestone: {{Milestone}} → {{Date}}**Tasks created in Planner** | Task | Owner | Date | |——|——-|——| | {{Task}} | @{{User}} | {{YYYY-MM-DD}} |Please review dependencies and update status in the pinned Loop. (function () { document.addEventListener(‘click’, function (ev) { const btn = ev.target.closest(‘.btn-copy[data-copy]’); if (!btn) return; const sel = btn.getAttribute(‘data-copy’); const el = document.querySelector(sel); if (!el) return; const text = el.innerText.replace(/\n\s+\n/g, ‘\n’).trim();if (navigator.clipboard && window.isSecureContext) { navigator.clipboard.writeText(text); } else { const ta = document.createElement(‘textarea’); ta.value = text; document.body.appendChild(ta); ta.select(); document.execCommand(‘copy’); document.body.removeChild(ta); }const original = btn.textContent; btn.textContent = ‘Copied ✓’; btn.disabled = true; setTimeout(() => { btn.textContent = original; btn.disabled = false; }, 1400); }); })();Client follow-up email (Outlook)
Use: we paste the prompt so that Copilot drafts the email from the minutes and the channel documents. We also include a subject and body template ready to send after review.
Prompt to Copilot: “Create a follow-up email in professional tone with 3 value bullets, next steps with dates and a confirmation request. Use the minutes and documents from the {{DATE}} meeting.”
How to get the most out of it (3 quick guidelines)
- We ask for format and sources: “Return it in 5 bullets / RACI table and link the transcript/documents used.”
- We keep standard markers: {{PROJECT}}, {{DATE}}, {{Milestone}}, {{Name}} so that Copilot fills them in without ambiguity.
- We close the loop to execution: after generating minutes/message/email, we convert tasks to Planner and anchor Loop with live status in the channel.
Client follow-up email (Outlook)
.correo-seguimiento { max-width: 920px; margin: 0 auto; padding: 16px; font-family: system-ui, -apple-system, “Segoe UI”, Roboto, Arial, sans-serif; color: #111827; } .cs-card { border: 1px solid var(–b); border-radius: 12px; background: #fff; padding: 14px; box-shadow: 0 1px 2px rgba(0,0,0,0.04); margin-bottom: 12px; } .cs-head { display: flex; align-items: start; justify-content: space-between; gap: 12px; } .cs-head h4 { margin: 0; font-size: 18px; line-height: 1.35; } .cs-actions { display: inline-flex; gap: 8px; } .btn-copy { appearance: none; border: 1px solid #d1d5db; background: #f9fafb; padding: 8px 10px; font-size: 12px; border-radius: 8px; cursor: pointer; } .btn-copy:hover { background: #f3f4f6; } .cs-text { margin-top: 10px; border: 1px solid #e5e7eb; border-radius: 8px; padding: 12px; background: #fbfbfb; font-size: 14px; line-height: 1.55; white-space: pre-wrap; } .cs-note { margin-top: 8px; font-size: 12px; color: var(–muted); } .cs-copy-src { display: none; } .cs-fields { margin-top: 8px; font-size: 13px; color: var(–muted); } .cs-fields code { background: #f3f4f6; border: 1px solid #e5e7eb; padding: 0 6px; border-radius: 6px; } @media (max-width: 640px) { .cs-head { flex-direction: column; align-items: flex-start; } .btn-copy { width: 100%; } } Prompt to Copilot Copy prompt Create a follow-up email in professional tone with 3 value bullets, next steps with dates and a confirmation request. Use the minutes and documents from the {{DATE}} meeting of project {{Project}}.Tip: launch it from the meeting thread so that Copilot has the transcript and linked files.
Template ready for Outlook Copy email Subject: Follow-up {{Project}} — next steps and confirmationHi {{ClientName}},Thank you for the meeting on {{DATE}}. Here are the key points: • {{Benefit/Value 1}} • {{Benefit/Value 2}} • {{Benefit/Value 3}}Next steps: 1) {{Action}} — owner {{Name}} — {{YYYY-MM-DD}} 2) {{Action}} — owner {{Name}} — {{YYYY-MM-DD}}Can you confirm that we move forward with {{Step/Date}}? We look forward to your feedback.Best regards, {{Your Name}} · {{Title}} · {{Company}} Subject: Follow-up {{Project}} — next steps and confirmationHi {{ClientName}},Thank you for the meeting on {{DATE}}. Here are the key points: • {{Benefit/Value 1}} • {{Benefit/Value 2}} • {{Benefit/Value 3}}Next steps: 1) {{Action}} — owner {{Name}} — {{YYYY-MM-DD}} 2) {{Action}} — owner {{Name}} — {{YYYY-MM-DD}}Can you confirm that we move forward with {{Step/Date}}? We look forward to your feedback.Best regards, {{Your Name}} · {{Title}} · {{Company}} Available markers: {{Project}} {{DATE}} {{ClientName}} {{Benefit/Value 1}} {{Action}} {{Name}} {{YYYY-MM-DD}} {{Step/Date}} {{Your Name}} {{Title}} {{Company}} Short variant (≤120 words) Copy short version Subject: {{Project}} — confirmation of next stepsHi {{ClientName}},In the meeting on {{DATE}} we agreed: • {{Value 1}} • {{Value 2}} • {{Value 3}}We propose to move forward with: 1) {{Action 1}} — {{Name}} — {{YYYY-MM-DD}} 2) {{Action 2}} — {{Name}} — {{YYYY-MM-DD}}Can you confirm {{Step/Date}}? We will send the calendar invite as soon as you give us the go-ahead.Thanks, {{Your Name}} — {{Company}} Subject: {{Project}} — confirmation of next stepsHi {{ClientName}},In the meeting on {{DATE}} we agreed: • {{Value 1}} • {{Value 2}} • {{Value 3}}We propose to move forward with: 1) {{Action 1}} — {{Name}} — {{YYYY-MM-DD}} 2) {{Action 2}} — {{Name}} — {{YYYY-MM-DD}}Can you confirm {{Step/Date}}? We will send the calendar invite as soon as you give us the go-ahead.Thanks, {{Your Name}} — {{Company}} (function () { document.addEventListener(‘click’, function (ev) { const btn = ev.target.closest(‘.btn-copy[data-copy]’); if (!btn) return; const sel = btn.getAttribute(‘data-copy’); const el = document.querySelector(sel); if (!el) return; const text = el.innerText.replace(/\n\s+\n/g, ‘\n’).trim();if (navigator.clipboard && window.isSecureContext) { navigator.clipboard.writeText(text); } else { const ta = document.createElement(‘textarea’); ta.value = text; document.body.appendChild(ta); ta.select(); document.execCommand(‘copy’); document.body.removeChild(ta); }const original = btn.textContent; btn.textContent = ‘Copied ✓’; btn.disabled = true; setTimeout(() => { btn.textContent = original; btn.disabled = false; }, 1400); }); })();


