Copilot Prompts for Business

28 copy-paste prompts for Microsoft 365 Copilot. They brief a review, describe a pipeline, and draft a note from files you can open. They do not send mail or invent the forecast.

Last updated September 26, 2026

What these prompts are for

Business work in Copilot goes wrong when the prompt asks for a strategy and the file is a spreadsheet. These prompts stay on the file. A weekly review uses the pack for that week. A forecast note quotes the commit that is already in the workbook. A customer email stays a draft.

This is a new page because the older shared business URL was the wrong place for Copilot prompts. The general guide, how to use AI for business, still covers tool choice across products. It is not this prompt set, and this page does not replace it.

Inbox triage sits on Copilot for administrative assistants. A full meeting record sits on Copilot for detailed meeting minutes. Writing that is not tied to a business file sits on Bing AI and Copilot writing prompts.

What Copilot may and may not do

JobCopilot mayCopilot may not
Operating reviewSummarise the pack and list open decisionsAdd a metric that is not in the pack
PipelineSort the export and show incomplete rowsInvent a win rate or a commit
ProposalOutline from the approved SOWAdd a discount or a case study
VarianceDescribe actual versus plan from cellsChange a formula or explain a gap with no driver
Customer noteDraft from notes and stopSend, promise a date, or guess an owner

How to brief Copilot

Open the app that holds the file. In Excel, start from the workbook. In Word, start from the SOW. In Outlook or Teams, start from the thread you are allowed to read. Paste one prompt. If Copilot says it cannot see the file, treat that as the result and fix access before you ask again.

Microsoft describes better Copilot answers as a goal, context, a source, and clear expectations. These prompts follow that shape and add a refusal rule for missing numbers. App-specific steps live on the Excel, Word, Outlook, and Teams guides linked below.

28 copy-paste Copilot prompts

Replace the brackets with files you can open. Delete a line you cannot support. Leave DRAFT ONLY on anything a customer could read.

Weekly operating review

Start from the files for this week. Copilot should brief the meeting, not invent the state of the business.

You are preparing a weekly business review. Use only the files I attach or that are already open: [name the workbook, deck, and notes]. Audience: [leadership team]. Decision needed: [one decision]. Return: sources you can actually see, three changes since last week that are in those files, decisions already made, decisions still open, and numbers you cannot find. Write NOT IN SOURCE instead of estimating. Do not email anyone.

From this operating deck [attach or name it], draft a 150-word pre-read. Include only slides I list: [slide numbers or titles]. For each point, name the slide. Flag any chart you cannot reconcile to a table in the file. Do not add market color or a competitor claim.

Compare this week's workbook to the notes from the last review: [paste notes]. List metric, last review value, this week value, direction, and whether the definition changed. If either value is missing, write NOT IN SOURCE. Do not explain a variance you cannot see.

Turn this review pack into a decision log with columns: decision, owner, date stated, source file, status (proposed or recorded), follow-up. Do not promote a suggestion into a recorded decision. Pack: [files].

Pipeline and forecast

The export is the source. Copilot may sort and describe it. It may not create a commit number.

Here is a CRM export I am allowed to use: [attach]. Columns I trust: [list]. Build a pipeline table: stage, count, value, next step, close date, owner. Exclude rows missing a stage or an amount and list them separately as incomplete. Do not forecast a win rate.

Using only this forecast workbook [attach], write commentary for the gap between commit and target. Quote the cell or named range for every figure. If commit is not labelled, stop and say which tab is missing. Do not propose a new commit.

Read this pipeline export and this forecast tab. List deals that appear in one and not the other, deals whose amount differs, and deals whose close date moved. Show both values. Do not pick the "right" number. Export: [attach] Forecast tab: [attach]

Draft three questions a sales manager should ask about this pipeline before the forecast call. Each question must point at a row, stage, or missing field in the export. Do not give coaching tips that are not tied to a row. Export: [attach].

Customers, proposals, and QBRs

Customer language stays inside the account files. Nothing here is approved to send.

Prepare a QBR brief for [customer]. Use only these files: [success notes, usage export, open issues]. Sections: what they bought, what the files show they used, open issues with owners, and questions I should ask. Write NOT IN SOURCE for renewal date, NPS, or revenue if those fields are absent. Do not draft a renewal quote.

Draft a proposal outline in Word from this approved statement of work and this pricing sheet: [attach both]. Use their headings. Do not add services, discounts, or case studies that are not in the files. Mark any sentence that would need legal or finance review. Do not send it.

From these call notes [paste or attach], list commitments we made, commitments the customer made, and lines that are still ambiguous. Keep names as written. Do not assign an owner who is not in the notes.

Compare this draft proposal to the approved SOW. Return a table: section, SOW language, draft language, mismatch, risk. Do not rewrite the commercial terms. Draft: [attach]. SOW: [attach].

Excel variance and commentary

Commentary follows the cells. If the cell is empty, the sentence stays empty.

In this workbook [attach], write variance notes for tabs [names]. For each line: actual, plan, difference, and a cause only if a note or driver tab states one. Otherwise write CAUSE NOT IN FILE. Do not change formulas or values.

Explain this bridge chart in plain language for a non-finance reader. Use only the categories and amounts on the chart's data tab. Define acronyms that appear in the file. If a category has no amount, say so. Chart tab: [name].

Check this commentary against the workbook. List every number in the commentary, the cell it should match, and MATCH or MISMATCH. Do not correct the workbook. Commentary: [paste] Workbook: [attach]

Build a month-end checklist from this close calendar and this workbook: [attach]. Items: what is tied out, what is still open, who the file names as owner. Do not mark the close complete.

Pricing, vendors, and risk

Comparisons use the quotes in front of you. They do not browse for a market price.

Here are vendor quotes I can share: [attach]. Normalise them into a table: vendor, scope, price, term, what is excluded, open question. Do not fill a missing price. Do not recommend a winner. Flag scope that is not comparable.

Review this discount request: [paste the request and the pricing rules]. Say which rule it hits, which approver the rules name, and which fact is missing. Do not approve the discount.

From this risk register [attach], list risks with no owner, no date, or a status that contradicts the latest note. Quote the row. Do not close a risk or invent a mitigation.

Read this contract summary I pasted, not the full contract unless I attached it. Extract commercial obligations, notice periods, and renewal mechanics that the summary actually states. Label anything that needs the signed PDF as NEEDS THE CONTRACT. Summary: [paste].

SOPs and leadership updates

Update the procedure that exists. The leadership note asks for a decision. It does not announce one.

Here is the current SOP: [attach]. Here are the changes we agreed in this note: [paste]. Produce a revised SOP that marks each change and leaves unchanged steps as they were. Do not add steps that were not in the note. List questions for the process owner.

Draft a one-page leadership update from these approved numbers and this decision list: [attach]. Structure: what changed, what we need decided, what is blocked, source of each figure. Tone: direct. Do not add a rallying close or a metric that is not in the pack. Do not distribute it.

Turn this project plan into an executive slide outline: title, the decision on that slide, the source tab, and the chart to show. Maximum six slides. If a decision has no source, drop the slide and list it under missing. Plan: [attach].

Write a post-incident summary from this timeline: [paste]. Separate facts, customer impact stated in the timeline, and hypotheses. Do not assign blame and do not invent a root cause that the timeline does not state.

Messages that stay unsent

Outlook and Teams drafts are for review. The prompt forbids sending.

Draft an email to [role, not a guessed address] about [decision]. Facts I may use: [paste]. Ask for [one action] by [date or "date not set"]. Do not add a discount, a legal promise, or a cc list. End with DRAFT ONLY. DO NOT SEND.

Rewrite this internal Teams update so a busy operator can see the ask in the first two lines. Keep every number. Remove tone. Do not add a new deadline. Update: [paste]. Output the message and a list of facts you removed as unsupported.

From this mailbox thread I have open, list the asks, the dates, and who has not replied, using only the thread. Draft a reply that answers the open asks I mark as mine: [list]. Leave other asks unanswered. DRAFT ONLY. DO NOT SEND.

Prepare a customer follow-up after this meeting, using the meeting notes and the approved next steps only: [attach]. If a next step has no owner, write OWNER NOT SET and do not invent one. DRAFT ONLY. DO NOT SEND. For full minutes, I will use the meeting-minutes workflow instead of this prompt.

Tips for a reviewable business draft

  • Name the file, the tab, or the thread. 'Look at the business' is not a source.
  • Write NOT IN SOURCE in the prompt so a missing number stays missing.
  • Separate a proposal from a recorded decision. Copilot should not promote one into the other.
  • Keep customer sends and forecast commits behind a person. The prompt ends before send.
  • Use the admin-assistant guide for inbox triage and the meeting-minutes guide for a full record.
  • If Copilot cannot see the site, stop. Do not paste restricted data into an account that should not have it.
  • Check the figure in the workbook after the sentence sounds right.
  • GitHub Copilot is for code. These prompts are for Microsoft 365 work.

Primary sources

Copilot business prompt FAQ

Is this Microsoft 365 Copilot or GitHub Copilot?

These prompts are for Microsoft 365 Copilot in Word, Excel, PowerPoint, Outlook, Teams, and Copilot Chat grounded in work files you are allowed to open. GitHub Copilot is a coding product. Do not use these prompts for pull requests, tests, or IDE completions.

Why is this a separate page from how to use AI for business?

How to use AI for business is a general guide across tools. It is not a Microsoft 365 Copilot prompt library, and it is the wrong URL for this keyword. This page is the Copilot leaf: prompts that name a workbook, a deck, a mailbox thread, or a SharePoint file, then stop before anything is sent or saved as the official number.

How is this different from ChatGPT prompts for business?

ChatGPT business prompts start from a brief you paste into ChatGPT. They do not see your tenant. These Copilot prompts assume the model can use the work context your licence and permissions allow, and they require you to name that context. If Copilot cannot open the file, the prompt tells it to stop rather than guess a pipeline or a margin.

Will Copilot see all company data?

No. What Copilot can open depends on your licence, tenant settings, and the permissions on each file, mailbox, and meeting. Ask it to list the sources it actually used. If a folder is missing, do not paste confidential material into a personal account to get around the gap.

Can these prompts send email or update a forecast?

No. Every customer-facing prompt on this page ends with a draft and a do-not-send instruction. Forecast prompts may describe numbers you already calculated. They must not write a new total, change a cell, or mark a commit as approved. A person who owns the number still publishes it.

What if Copilot invents a metric?

Reject the sentence. The prompts say to write NOT IN SOURCE when a figure, owner, or date is absent. If a draft contains a percentage you cannot find in the workbook or the export, delete it before the review meeting. A fluent commentary is not a reconciliation.

Do I need a particular Copilot licence?

Features differ by product and tenant. Microsoft's own pages describe Microsoft 365 Copilot and the prompting pattern of goal, context, source, and expectations. Check the app you opened and your admin's policy before you promise a colleague that a prompt will see a given mailbox or site.

Where do meeting minutes and inbox triage belong?

Detailed meeting minutes have their own Copilot guide, and administrative assistants have a guide for inbox, calendar, and document triage. Use those pages for that work. Use this page when the output is a business decision: a forecast note, a proposal, a variance comment, a customer review, or a leadership update.

Related pages

Don't stop here

What to read next

Hand-picked guides our readers explore right after this one.