Microsoft Copilot Cheat Sheet: Write Prompts That Actually Work

Most Copilot frustration comes down to vague prompts. "Summarize this" gets a generic answer; "Summarize this thread in 3 bullets, flag any action items assigned to me" gets a useful one. Print this, keep it by your desk, and swap in your own details where you see brackets.

The pattern that works everywhere: give Copilot a role or goal, the specific content to act on, a format for the output, and any constraints (length, tone, audience).

Copilot in Outlook#

Use it to draft faster and cut through long threads.

• "Summarize this email thread in 3 bullet points. Call out any deadlines or decisions I need to make."
• "Draft a reply declining this meeting request. Suggest [Tuesday or Wednesday afternoon] as alternatives. Keep it friendly and brief."
• "Write a follow-up email to [client name] recapping our call: we agreed on [scope], next step is [action], due [date]. Professional tone, under 150 words."

Tips: Reference the thread directly ("this email," "this thread") so Copilot pulls context instead of guessing. Always specify tone (friendly, formal, brief) — Copilot's default is generic.

Copilot in Word#

Best for first drafts and cleanup, not final copy — always read what it gives you.

• "Draft a one-page internal memo announcing [policy change]. Audience is non-technical staff. Include why it's changing and what they need to do differently."
• "Rewrite the highlighted section to be more concise and remove jargon. Keep the same meaning."
• "Review this document for clarity and consistency. List any sections that contradict each other or repeat the same point."

Tips: Highlight the specific text before asking Copilot to revise it — it narrows the edit instead of rewriting the whole document. Ask for an outline before a full draft on anything longer than a page; it's faster to fix structure early.

Copilot in Excel#

Great for formulas you'd otherwise Google, and for asking plain-English questions about a dataset without building a pivot table.

• "Write a formula that flags any row in column D where the value is more than 10% over the value in column C."
• "Which sales rep in this table had the highest total revenue in Q2, and what was the amount?"
• "Create a formula to pull the most recent date per customer from this list without duplicates."

Tips: Copilot needs the data in a proper Excel Table (Insert > Table) to reason about it reliably — raw ranges give inconsistent results. Name your columns clearly ("Revenue," not "Column D") so prompts can reference them by name.

Copilot in Teams#

Use it to catch up without scrolling, and to turn meetings into action items automatically.

• "Summarize what I missed in this channel since yesterday. Only include messages that mention me or need a response."
• "Summarize this meeting: key decisions, open questions, and action items with owners."
• "Did anyone raise concerns about [project name] in this chat? Quote the relevant messages."

Tips: Meeting summaries only work well if transcription was turned on for the call — check this before the meeting starts. For long-running channels, narrow the time window ("since Monday," "in the last 20 messages") so the summary stays focused.

The one habit that makes every prompt better#

After you get a response, don't start over if it's close but not right — refine it. "Make this shorter," "more formal," "add a line about the budget" all work as follow-ups in the same conversation. Copilot remembers context within a chat, so iterating beats re-prompting from scratch.

Comfort with tools like Copilot is a Culture and Talent issue as much as a technology one — teams that build daily AI fluency get compounding returns, while teams that treat it as a novelty leave most of the value on the table. If you're not sure where your organization stands, the AI Business Maturity Assessment is a quick way to find out.