Below are Copilot prompt examples you can copy, fill in and use today. They cover four everyday tasks: writing a client proposal, sending a follow-up email, summarising a long thread and preparing a meeting. After each prompt you will find a short note on why it works, so you can change the details and keep the result useful.
The words in square brackets are yours to replace. The more of your own material you add, the closer the first draft gets to something you can send.
Copilot prompts for client proposals
A proposal is where generic text costs you the most. The client wants to see that you understood their situation, so these prompts all start from your notes or their request.
Write a first draft of a proposal for [client name]. The client wants to [goal]. Our approach has these phases: [phases]. Keep it under two pages, in a plain and confident tone, and end with a short list of next steps. Use only the notes below. Notes: [paste your notes]
This prompt states the goal, the structure, the length and the tone before Copilot writes a word. The last instruction keeps the draft tied to your notes. Without it, Copilot fills the gaps with text that could apply to any client.
Read this proposal and write a summary of no more than 150 words for a decision-maker who will only read this paragraph. Mention the problem, our solution and the investment. Do not add anything that is not in the document.
Naming the reader changes what Copilot puts first. A busy decision-maker needs the problem and the cost; a project lead might need the planning. The word limit forces a choice.
Compare this proposal with the client’s request below. List every requirement from the request and say whether the proposal covers it, partly covers it or misses it. Request: [paste the request]
You ask for a checklist here, and a checklist is easy to verify line by line. Use it before you send the proposal, while there is still time to fill a gap.
Copilot prompts for follow-up emails
Follow-up emails are short, so the risk is that they say nothing. Give Copilot the facts the email has to carry and it will handle the wording.
Write a follow-up email to [name] after today’s meeting about [subject]. Thank them in one sentence, confirm the decisions we made: [decisions], and list who does what by when: [actions]. Keep it under 120 words, friendly and professional.
The decisions and actions come from you, so the email can’t drift into vague thanks. The word limit keeps it readable on a phone.
Write a short, polite reminder to [name]. I sent them [document] on [date] and need their feedback by [deadline] because [reason]. Don’t sound pushy and don’t apologise for following up.
A reminder works when the reader sees why the deadline matters. Telling Copilot what to avoid is just as useful as telling it what to do; it stops the over-apologetic opening many reminders start with.
Draft a follow-up to [client] one week after sending our proposal for [project]. Offer a 20-minute call to answer questions and suggest two time slots: [slot 1] and [slot 2].
Two concrete time slots give the client something to say yes to. Leave them out and you get an email that asks the client to do the planning.
Copilot prompts for summarising long threads
A long email or chat thread hides its decisions between the replies. These prompts ask Copilot to pull them out in a fixed shape.
Summarise this thread in five bullet points. Then list the open questions and who is expected to answer each one.
The second part matters most. A summary tells you what happened; the list of open questions tells you what still has to happen and who owns it.
I was not part of this conversation. Explain in plain language what was decided, what is still being discussed and what I am expected to do.
Starting with your own position tells Copilot what you are missing. You get the background you need to step in, and the last part points straight at your next action.
Summarise this thread for my manager in three sentences. Focus on risks and deadlines.
Same thread, different reader, different summary. When you forward a summary, decide first who will read it and what they will do with it.
Read the original messages before you act on a summary of an important decision. Copilot can miss a detail or a change of mind halfway through the thread.
Copilot prompts for preparing meetings
Preparation is where Copilot saves time you would otherwise spend scrolling through files and old emails.
Create a 45-minute agenda for a meeting with [participants] about [topic]. By the end we need to decide [decision]. Put the item that needs a decision first and give each item a time slot.
The decision you need sets the order of the agenda. Putting it first means it gets discussed while everyone is still fresh.
Based on [documents or emails about the project], list the points most likely to come up in tomorrow’s meeting with [client], and suggest a one-sentence answer for each.
This prompt works as a rehearsal. Pointing Copilot to specific material keeps the list about your project; the one-sentence answers show you where you are not yet ready.
Suggest questions I can ask [person] in our meeting to find out [what you want to learn]. Avoid questions that can be answered with yes or no.
Open questions get you information. The restriction at the end is small, and it changes the quality of the list.
Why do these Copilot prompts work?
Each example above gives Copilot four things: a goal, context, the source material to use and clear expectations for the result. The goal says what you want. The context says who it is for and why. The source tells Copilot which notes, documents or messages to work from. The expectations set the format, the length and the tone.
Leave one out and the output gets more generic. A prompt with a goal and nothing else returns text that sounds fine and fits nobody in particular. A prompt with all four usually returns a first draft you only need to edit.
The examples also limit what Copilot may add. Lines such as "use only the notes below" or "do not add anything that is not in the document" keep the result anchored to your own material, which makes it easier to check.
How to adapt an example to your own work
Start by replacing every bracket with real details. A prompt with [goal] still in it will get you a draft with a hole in it.
Then treat the first answer as a draft. Ask follow-up questions in the same conversation: "make it shorter", "use a more formal tone" or "move the price to the end". Copilot keeps the earlier context, so you don’t need to repeat the whole prompt.
Finally, save the prompts you use every week. A follow-up email after a client meeting or a thread summary for your manager comes back often, and a saved prompt with your preferred length and tone turns it into a two-minute job.
