Excel Copilot Data Analysis: 12 Prompts for Finance, Marketing, Operations, and HR

The useful Excel Copilot data analysis examples in 2026 are not evenly distributed across the org chart. Finance, marketing, operations, and HR can all ask Copilot to summarize, classify, clean, chart, or explain workbook data. The difference is what happens after the impressive first answer: whether the output can be checked, handed off, refreshed, and trusted inside the workflow that actually owns the spreadsheet.

As of Q3 2026, finance has the strongest new case because Microsoft has started adding finance-specific Skills, data connectors, and pre-execution traceability to Copilot in Excel. That does not make every finance workbook safe to automate. It does mean finance prompts can now point at more realistic work: DCF modeling, variance explanations, and monthly reporting packages, rather than toy revenue tables. The same update does much less for HR teams trying to merge department files or process personnel rows at scale.

Use the prompts below as starting points, not as proof that a workbook is ready for autopilot. Each prompt assumes the data is already in a structured Excel table with clear headers. If the real job requires comparing separate files, interpreting screenshots, or running hundreds of row-level AI calls, the boundary matters more than the wording of the prompt.

Finance: where Copilot has become more than a demo

Finance is the function where the June 2026 update changes the practical conversation. Microsoft’s new Excel Copilot finance Skills are described as pre-built workflows for DCF modeling, variance analysis, and monthly reporting packages, created through SKILL.md files in OneDrive, with partner skills expected in Q3 2026. The same update adds connector announcements for CB Insights, Daloopa, FactSet, Morningstar, PitchBook, and S&P Global, with FactSet described as in preview and generally available in July 2026; separate subscriptions may still be required. Plan with Copilot also matters because it shows intended range and formula changes before execution, which is much closer to how finance teams review workbooks before numbers leave the team. [1]

That traceability is not a cosmetic feature. Older reviews found Copilot weaker at financial-modeling tasks when it had to infer model structure or produce reliable finance logic from broad instructions. The safer pattern is to use Copilot where the workbook already has labeled assumptions, historical periods, operating metrics, and reviewable formulas. [2]

Prompt 1: DCF model setup and formula review

Prompt: “Using the historical financials and assumptions tables in this workbook, draft a DCF model with revenue growth, operating margin, tax rate, working capital, capex, terminal value, and discount rate assumptions. Before making changes, show the ranges and formulas you plan to create.”

The expectation here should be structure and first-pass formulas, not a finished valuation. With Plan with Copilot, the useful part is seeing which ranges and formulas Copilot intends to touch before anything is written into the model. That gives an analyst a chance to reject a wrong range, catch a terminal-value assumption going to the wrong cell, or stop Copilot from building on a table that was meant for presentation only. [1]

Check whether the finance Skills have actually reached your tenant and whether your workbook layout matches the Skill’s assumptions. If the model pulls market data from FactSet, PitchBook, S&P Global, or another connector, verify the subscription and data lineage separately. Connector access is not the same as model correctness. [1]

Prompt 2: variance analysis for close or forecast review

Prompt: “Analyze actuals versus budget and latest forecast by department and account. Identify the largest favorable and unfavorable variances, separate volume, price, timing, and one-time explanations where the data supports it, and create a summary table for review.”

This is a good Copilot task because the output is bounded. It can sort variance size, group drivers, and draft explanation language that a finance owner can challenge. The June 2026 Skills update explicitly names variance analysis as one of the finance workflows Microsoft is targeting, so this prompt lines up with the direction of the product rather than fighting it. [1]

The weak spot is causality. If the workbook has actuals, budget, forecast, quantity, rate, and timing fields, Copilot has something to work with. If it only has monthly totals and account names, ask it to label possible explanations as hypotheses, not conclusions. A variance bridge that sounds confident but hides a missing driver is worse than doing the pivot manually.

Prompt 3: monthly reporting package

Prompt: “Create a monthly reporting package from the tables in this workbook: executive summary, revenue and margin trends, expense variance by department, cash movement, and a list of items that need human review. Show the planned tables, charts, and formulas before adding them.”

This is where Copilot can save real assembly time if the workbook is already disciplined. Monthly reporting packages often involve the same transformations every cycle: refresh the period, update charts, summarize deltas, and flag outliers. Microsoft’s June 2026 finance update specifically includes monthly reporting packages among the Skill examples, and the Plan with Copilot review step gives finance teams a way to inspect planned workbook changes before accepting them. [1]

Do not use this prompt as a substitute for close controls. Use it to assemble the package faster, then review formulas, signs, period filters, subtotal logic, and any narrative explanation before distribution. Finance is the function where Copilot’s 2026 direction is most encouraging, but the handoff standard is still the board deck, not the chat response.

Marketing: strong for feedback, summaries, and quick visuals

Marketing gets value from Copilot when the job is interpretive but low-risk enough to review in batches: classify feedback, summarize campaign performance, and turn a ranked list into a chart. The danger is pretending sentiment analysis is customer truth. It is a fast labeling pass. Someone still needs to scan examples, collapse duplicate themes, and decide what the business will do with the categories.

Prompt 4: customer sentiment by theme

Prompt: “Analyse customer sentiment in the Feedback column and categorise by themes: product quality, pricing, service, packaging. Add sentiment labels, theme labels, and a short reason for each classification.”

Nexacu uses this sentiment-analysis pattern as a practical Copilot for Excel example and follows it with pivot table creation, which is the right sequence: classify the rows, then count and inspect the pattern. [3]

DataCamp also reported that Copilot correctly handled sentiment classification and pivot summaries in its Excel Copilot examples. That supports using this prompt for a first pass over survey comments, support notes, or post-purchase feedback, as long as the team samples the labels before treating the counts as campaign evidence. [4]

Prompt 5: campaign performance summary

Prompt: “Summarize campaign performance by channel. Compare spend, impressions, clicks, conversions, revenue, and conversion rate. Identify the channels with the strongest and weakest performance, and create a pivot table I can use for weekly reporting.”

This works best when the data already contains channel, campaign, date, spend, conversion, and revenue fields. Copilot can group and explain, but it should not invent attribution logic that is not in the file. If the workbook mixes paid search, affiliate, lifecycle email, and offline events with different attribution windows, keep the prompt closer to descriptive reporting: what rose, what fell, and what needs investigation.

Prompt 6: top products or campaigns as a chart

Prompt: “Show the top 5 products by amount as a bar chart, using product name for the axis and total amount for the values.”

GoSkills includes this pattern in its sample Copilot prompts for Excel 365, and it is one of the cleaner examples because the instruction has a clear grouping field, a clear measure, and a clear visual output. [5]

The same structure adapts well to “top campaigns by revenue,” “top landing pages by conversion,” or “top segments by average order value.” The review step is simple: check that Copilot summed the right amount column, did not count text rows as transactions, and did not chart a filtered subset by accident.

Operations: useful until the files split apart

Operations spreadsheets are where small messes become Monday morning delays: inconsistent vendor names, extra spaces, mixed capitalization, one column doing the work of three, and category labels that almost match. Copilot can help here because the task is visible. You can compare before and after columns and see whether the cleanup made the file more usable.

Prompt 7: clean names and formatting

Prompt: “Clean this data: remove extra spaces, standardise capitalization to proper case, and split the Name column into First Name and Last Name. Keep the original column and add new cleaned columns beside it.”

Nexacu uses this cleanup prompt as a tested Copilot example and cites operational time-saving use cases around repetitive spreadsheet cleanup. The important detail is the instruction to keep the original column. In an operations file, overwrite-free cleanup is easier to audit, filter, and reverse. [3]

Prompt 8: standardize categories for review

Prompt: “Standardize the Category column by grouping similar values into a smaller set of operational categories. Add a Proposed Category column and a Confidence or Review Needed column for uncertain rows.”

This is a better prompt than “fix the categories” because it creates a review queue. Copilot can group “shipping,” “freight,” and “delivery” if the surrounding data supports that grouping, but the ops owner should decide whether those labels are equivalent for the meeting, the system import, or the KPI definition.

Prompt 9: flag exceptions in inventory or fulfillment data

Prompt: “Review the inventory table and flag rows where stock on hand, reorder point, lead time, or open order quantity suggests a possible stockout or overstock. Add an Exception Type column and a short explanation.”

This is a reasonable Copilot use when the workbook has the needed fields in one table. It can create a first-pass exception list that an ops manager can sort before a supplier call or planning review. Keep the output as a flag, not an automated purchasing decision, unless the logic has been separately validated.

The common operations failure point is multi-file work. Microsoft’s own Copilot in Excel guidance describes working with Excel data in supported workbook contexts, and DataCamp notes that Copilot cannot merge or compare two separate workbooks. That is a hard practical limit for teams that keep supplier files, regional trackers, or site-level logs in separate spreadsheets. [4][6]

HR: fine for a clean table, weak for the real consolidation job

HR is not a poor fit because the questions are simple. It is a poor fit when the workflow is fragmented and sensitive. A headcount file may involve department submissions, job-level cleanup, manager changes, compensation-adjacent fields, and personal data. The available sources support basic single-table cleanup and summaries, but they do not document HR-specific privacy controls or PII handling that would make broad personnel analysis comfortable.

Prompt 10: clean a single HR roster

Prompt: “Clean this employee roster by standardizing department names, location names, employment status, and manager names. Add cleaned columns beside the original fields and flag rows where the correction is uncertain.”

This is the HR prompt most likely to be useful because it stays inside one table and preserves the source values. It is the same operational cleanup pattern, applied to people data. The review standard should be higher: a vendor-name correction may annoy procurement; a manager-name or status correction can affect access, reporting, or employee communication.

Prompt 11: headcount summary by department

Prompt: “Create a headcount summary by department, location, employment type, and status. Show totals, new hires, exits, and rows with missing or inconsistent required fields.”

For a single well-structured roster, this is a normal pivot-and-quality-check task. Copilot can help assemble the summary and identify blanks or inconsistent labels. The limit appears when HR wants to consolidate department spreadsheets first. Copilot cannot merge or compare two separate workbooks, a limitation confirmed by Microsoft Support’s workbook-scoped guidance and DataCamp’s review examples. [4][6]

Prompt 12: classify employee comments cautiously

Prompt: “For the anonymized Comment column, classify each response by sentiment and theme. Use only the themes listed in the Themes table. Add a Review Needed flag for ambiguous or sensitive comments.”

The wording matters: anonymized comments, fixed themes, and a review flag. Marketing-style sentiment analysis can be useful for HR only when the data governance is already handled outside the prompt. The research materials here do not document Copilot privacy controls specific to personnel data, so the safer conclusion is narrow: Copilot may help classify a prepared, anonymized, single-table dataset, but it should not be treated as an HR survey governance tool.

Scale is the second blocker. The COPILOT() function is reported with a cap of 100 calls per 10 minutes and 300 calls per hour, and DataStudios characterizes reliability as high around 200,000 cells but low at 4 million or more cells. Those limits make row-by-row AI classification a poor fit for large personnel datasets, even before considering privacy review. [7]

The limit that cuts across all four functions

Copilot is strongest when the workbook is structured, the task is bounded, and the human review step is designed into the prompt. Finance now has the best product momentum because Skills, connectors, and Plan with Copilot line up with how financial workbooks are reviewed. Marketing and operations get practical value from classification, summarization, charting, and cleanup. HR can use the same mechanics, but the real-world workflow runs into harder blockers sooner.

The two limits to check before spending time on prompt tuning are simple. First, if the task requires merging or comparing separate workbooks, Copilot in Excel is currently the wrong center of gravity. Second, if the task requires hundreds of COPILOT() calls across rows, the rate cap can become the constraint before the analysis is finished. [4][6][7]

Time-savings claims should also be read carefully. Nexacu reports Microsoft customer-story figures such as Toshiba saving 5.6 hours per month per employee and broader Microsoft customer stories averaging about 9 hours per month, but those are vendor-reported or vendor-adjacent figures rather than independent audits. They are useful as directional context, not as a guarantee for a messy workbook on a deadline. [3]

If your work matches the supported pattern, use the prompts now: one clean workbook, clear headers, bounded output, and a reviewer who knows what wrong looks like. If your blocker is multi-workbook consolidation, large-scale row processing, or sensitive HR data governance, compare Copilot against broader AI spreadsheet assistant options before rebuilding the workflow around a prompt.

References

1. Microsoft 365 Copilot in Excel Gains Finance Skills, Data Connectors, and Traceability, Windows Forum, June 25, 2026
2. Microsoft 365 Copilot review: Excel & Word, empower® Suite, 2024
3. Copilot for Excel (2026): Practical Prompts, Agent Mode & Time-Saving Examples, Nexacu, 2026
4. Excel Copilot: A Tutorial with Examples, DataCamp, 2025-2026
5. Sample Copilot Prompts for Excel 365, GoSkills
6. Get started with Copilot in Excel, Microsoft Support
7. Can Copilot Analyze Large Excel Spreadsheets? Performance Limits and Reliability, DataStudios, 2026