Copy-paste prompts that deliver results from day one
Most managers who try Microsoft 365 Copilot for the first time come away with the same reaction: ‘It seemed useful, but I wasn’t sure what to ask it.’ That is not a Copilot problem, it is a prompting problem. And it is entirely fixable.
The quality of what Copilot produces is directly proportional to the quality of the prompt you give it. A vague prompt produces a generic response. A well-constructed prompt, specific, contextual, and outcome-focused; produces something you could use almost immediately.
This guide gives you five concrete, high-value prompt patterns tailored specifically to managers and team leaders. Each one includes the prompt itself, an explanation of why it is structured the way it is, and variations you can adapt for your own context.
Before You Start: The Anatomy of a Good Copilot Prompt
Copilot responds best to prompts that contain four elements:
Goal— what you want Copilot to produceContext— the background it needs to do the job wellSource— which files, emails, or meetings it should draw fromFormat— how you want the output structured
Think of it as briefing a capable colleague: the more context you give them, the less time they spend asking clarifying questions and the better their first draft will be.
Prompt 1: Catch Up on a Meeting You Missed
Where to use this: Microsoft Teams (after a meeting with transcription enabled)
The prompt:
Summarise this meeting. Include: the main decisions made, any action items with the names of who is responsible, and any unresolved issues or blockers that came up. Format as a bulleted list under three headings: Decisions, Action Items, and Open Questions.
Why it works:
Without specific instructions, Copilot will produce a generic summary, a paragraph or two that tells you what was discussed without telling you what matters. By specifying the three categories, you get a structured output that is immediately actionable. The ‘names of who is responsible’ instruction is important: Copilot will pull these from the meeting transcript if they were mentioned. This turns a summary into an accountability tool.
Useful variations:
- Add ‘Focus on the agenda items that relate to [project name]’ if the meeting covered several topics
- Add ‘Note any items where consensus was not reached’ to surface tensions needing your attention
- Add ‘Write this in a tone suitable to forward to my team as a recap’ to share it directly
Manager use case: You missed your team’s Monday stand-up. You open Teams, navigate to the meeting recording, and ask Copilot this prompt. Within 30 seconds you have a structured summary with your name in the action items list if anything was assigned to you, and you have not had to sit through a 45-minute recording.
Prompt 2: Prepare for a Difficult Conversation
Where to use this: Microsoft Word or Copilot Chat
The prompt:
I need to have a performance conversation with a team member who has been missing deadlines on [project/type of work]. Help me prepare. Draft: (1) three open questions I can use to understand their perspective, (2) a clear statement of the impact the missed deadlines are having on the team, and (3) two or three specific, constructive suggestions for how we could address this going forward. Keep the tone professional, direct, and supportive — not punitive.
Why it works:
Performance conversations are some of the most anxiety-inducing tasks managers face. This prompt forces Copilot to generate a balanced preparation framework: understanding (open questions), impact (clear statement), and forward momentum (suggestions). The tone instruction, ‘professional, direct, and supportive, not punitive’, is doing significant work. Without it, Copilot might default to corporate-HR language that sounds detached.
Useful variations:
- Replace the performance context with any difficult conversation type: ‘a team member who has been consistently negative in meetings’, ‘a client who is unhappy with our delivery’
- Add ‘My organisation values [specific value, e.g. psychological safety]’ to align the tone with your culture
- Add ‘This person responds well to data and specifics’ to adjust the communication approach
Manager use case: You have been putting off a conversation about a team member’s meeting behaviour for three weeks. You open Copilot Chat on a Monday morning, spend two minutes with this prompt, and walk into the conversation 20 minutes later with a clear structure, specific language, and your anxiety measurably reduced.
Prompt 3: Turn Meeting Notes Into a Stakeholder Update
Where to use this: Microsoft Word (with your notes open) or Copilot Chat
The prompt:
Using the notes in this document, write a stakeholder update email for [project name]. The audience is [senior leadership / the client / the board]. The email should: summarise progress in 2-3 sentences, highlight the two most significant achievements, flag any risks with a one-sentence explanation of what is being done about each, and state the next milestone and expected date. Keep it under 300 words. Professional tone.
Why it works:
Writing stakeholder updates is one of the most time-consuming recurring tasks managers face, not because it is intellectually difficult, but because it requires translating messy internal notes into clean external language. This prompt offloads the translation work to Copilot. The word limit instruction is important: without it, Copilot will write at whatever length feels natural, which is often too long for a busy senior audience.
Useful variations:
- Change the audience to change the tone, a board update sounds different from a client update
- Add ‘Do not mention [specific sensitivity] in this version’ to manage what the AI pulls from your notes
- Add ‘End with a clear ask or decision required from the reader’ if you need the stakeholder to act
Manager use case: It is Thursday afternoon. You have a 5pm deadline to send a project update to the executive team. You have your notes from three meetings open. You paste the relevant section into Word, run this prompt, and have a clean first draft in 45 seconds. You spend five minutes checking the facts. You send it at 4:50pm.
Prompt 4: Analyse Your Team’s Workload and Spot Imbalances
Where to use this: Microsoft Excel (with task/project data open)
The prompt:
This spreadsheet contains our team’s current tasks, assigned owners, estimated hours, and due dates. Analyse the data and tell me: (1) which team members have the highest total estimated workload, (2) which tasks are due in the next 14 days, (3) whether any tasks have no assigned owner, and (4) which team member appears most at risk of being overloaded in the next two weeks. Present the results as a summary paragraph followed by a table.
Why it works:
Workload visibility is one of the most common pain points for managers who are too busy to manually tally hours across their team. Copilot in Excel can read the data in your open spreadsheet and answer natural language questions about it; no formula writing, no pivot table required. Asking for both a ‘summary paragraph’ and a ‘table’ gives you two formats: the paragraph tells the story; the table gives you something you can paste into a Teams message.
Useful variations:
- Add ‘Flag any dependencies between tasks that might create a bottleneck’
- Add ‘Which team member has capacity to take on additional work in the next week?’ if you need to reassign urgently
- Follow up with ‘Create a chart showing total estimated hours by team member’
Manager use case: You are preparing for your weekly team meeting on a Friday morning. You have an Excel tracker with 40 tasks across eight team members. You spend two minutes asking Copilot this prompt and walk into the meeting knowing that one person is carrying 60% of the next two weeks’ workload — a fact that would have taken you 20 minutes to extract manually.
Prompt 5: Draft a Team Communication That Lands Well
Where to use this: Microsoft Outlook or Word
The prompt:
Write an email to my team announcing [the change/decision/news]. Context: [2-3 sentences explaining what is happening and why]. The tone should be [transparent and direct / reassuring / motivating]. Anticipate the most likely concern team members will have and address it proactively in the email. End with a clear next step or action for the team. Keep it under 250 words.
Why it works:
Most managers write team communications that are accurate but not effective; they announce what is happening without addressing how people will feel about it. The ‘anticipate the most likely concern’ instruction is the most powerful element in this prompt. It forces Copilot to think about the reader’s perspective, not just the information being conveyed. The output will almost always be more empathetic than a first draft written without that lens.
Useful variations:
- For change management: add ‘Acknowledge that this change may feel uncertain for some team members’
- For positive news: shift to ‘Keep the tone warm and celebratory but grounded’
- For announcements requiring input: add ‘Include two questions at the end to invite the team to share their thoughts’
Manager use case: Your team is moving to a new reporting structure next month. You have the facts but you know people will be anxious. You give Copilot the key details, ask it to anticipate concerns, and get back a draft that addresses the three questions you know people will have; questions you might not have thought to pre-empt under time pressure.
Three Universal Tips to Make Every Prompt Better
Tip 1: Iterate, don’t start over
If Copilot’s first output is close but not quite right, refine the prompt rather than rewriting from scratch. ‘Make this more concise’, ‘Add a paragraph about [topic]’, ‘Change the tone to be less formal’ are all valid follow-up instructions. Think of it as a conversation, not a vending machine.
Tip 2: Give Copilot a role to play
Starting a prompt with ‘You are an experienced communications manager…’ or ‘Act as a senior project manager reviewing this…’ shifts the register of the output. It is a surprisingly effective technique for nuanced communications tasks.
Tip 3: Always read before you send
Copilot is fast and often impressively accurate, but it is not infallible. It can misread context, overstate confidence, or miss nuance that you would catch. Always review the output with your professional judgment before it goes anywhere; especially for anything external or sensitive.
Frequently Asked Questions
The free version can execute most of these prompts for general content generation. However, Prompts 1 (Teams meeting summary) and 4 (Excel workload analysis) require Microsoft 365 Copilot; the paid version — because they rely on reading your organisational data directly.
Follow up in the same conversation. ‘Make this shorter’, ‘Rewrite the opening so it is less formal’, and ‘This missed [specific point]; please add a paragraph about it’ are all effective ways to steer the output without starting over.
Microsoft 365 Copilot (the paid version embedded in Microsoft 365 apps) operates within your organisation’s security boundary. Your data is not used to train AI models. If you are using the free Copilot or ChatGPT, be cautious about including confidential or commercially sensitive information.
The most common issues are: not enough context, too vague a format instruction, or the underlying data is messy or incomplete. Prompting well is a skill; it improves quickly with practice and structured training.
Want to Get Faster Results From Microsoft Copilot?
These five prompts are a starting point. A full day of hands-on training gives you a complete prompt library for your role, deep practical skills across all Copilot applications, and the confidence to use it effectively from day one.
Dynamic Web Training’s Microsoft Copilot training courses are delivered by Microsoft-certified instructors in small groups; in Sydney, Melbourne, and Online Live for participants anywhere in Australia.
Ready to learn Microsoft Copilot?
Instructor-led courses in Sydney, Melbourne & Online Live
View upcoming course dates: dynamicwebtraining.com.au/microsoft-copilot-training-courses
Call 1300 888 724 (Monday to Friday, 8:30am–5:00pm AEST) to discuss group training for your leadership team.
