Design an Excel PivotTable for a business question

Author: AILesson6 min setupTested with:ChatGPTReviewed: 2026-08-28

Quick answer

Map a decision question to rows, columns, values, filters, and validation totals. Provide: Business question, Source table fields, Metric and filter rules. Expected result: A reproducible PivotTable layout with calculations, filters, and reconciliation checks.

1

Add your context

Your text stays in this browser. AILesson Prompts does not send it to a model or server.

2

Your prompt

Unfilled fields remain visible as placeholders, so you can still copy and edit the prompt

Design an Excel PivotTable for this business question.

Question:
[question]

Source table grain, fields, definitions, types, and units:
[schema]

Metric, period, filter, and missing-value rules:
[rules]

Confirm that one source row represents the intended unit before assigning fields. Return the exact Rows, Columns, Values, Filters, and Slicers layout; aggregation for every value; any calculated fields or formulas that must remain outside the PivotTable; sorting and display settings; and a validation plan. Do not average percentages or double-count repeated entities. Show source-to-Pivot totals and a small manual cross-check.
Try in Playground
Private by defaultPrompt assembly happens locally in your browser. Avoid placing confidential information into any AI service unless your organization allows it.

From input to outcome

A worked example

See how concrete context turns this recipe into a usable result

Actual input

Business question
Which product category and region combinations contributed most to Q2 net revenue, and which had high refund rates that need investigation?
Source table fields
Excel Table Sales; one row per order line. Fields OrderID, OrderDate, Region, ProductCategory, Quantity, GrossRevenueGBP, RefundAmountGBP. One order can have multiple lines.
Metric and filter rules
Q2 2026 only. NetRevenue=GrossRevenue−RefundAmount. Refund rate=RefundAmount/GrossRevenue. Show order-line count and distinct OrderID. Blank Region is Review, not a region. Rates must use summed amounts.

Example output

One source row is an order line, so ordinary Count of OrderID is a line count, not an order count. Add a source NetRevenue column and use the Data Model for Distinct Count of OrderID.

Layout: Rows = ProductCategory, then Region; Values = Sum of GrossRevenueGBP, Sum of RefundAmountGBP, Sum of NetRevenue, Sum of Quantity, Count of order lines, Distinct Count of OrderID; Filter = OrderDate grouped to Years and Quarters with 2026/Q2 selected; Slicer = Region and ProductCategory if interactive review is useful. Sort descending by Sum of NetRevenue. Show values as currency or whole counts, not mixed.

Calculate RefundRate outside the PivotTable from each row's summed refund divided by summed gross, or with a Data Model measure; never use Average of row refund rates. Route blank Region to a Review label in a helper column before refresh.

Validation: Q2 filtered source gross, refunds, net, quantity, and line count must equal Pivot grand totals; distinct OrderID must equal a UNIQUE/FILTER count. Manually choose one category-region pair, SUMIFS its gross/refund/net, and compare. A high refund rate is a diagnostic flag, not evidence that the category or region caused refunds.

Why this works

  1. 1

    Row-grain validation prevents a well-formatted PivotTable from double-counting entities.

  2. 2

    Explicit aggregations and reconciliation make the result reproducible rather than visual guesswork.

Check the result

  • Does each Value field use the correct sum, count, distinct count, or summary?

  • Are rates recomputed from totals rather than averaged?

  • Do PivotTable grand totals reconcile to the filtered source?

Use it with confidence

Frequently asked questions

Practical answers about when to use this recipe, what to provide, and where human review still matters

What should I prepare before using “Design an Excel PivotTable for a business question”?

For “Design an Excel PivotTable for a business question,” prepare Business question, Source table fields, and Metric and filter rules. Replace placeholders only with information you can verify. If a detail is unknown, preserve that uncertainty explicitly instead of asking the model to infer it.

When is the “Design an Excel PivotTable for a business question” result not ready to use?

The result is not ready if it does not yet deliver the stated outcome—A reproducible PivotTable layout with calculations, filters, and reconciliation checks—from the supplied evidence, or if it relies on unresolved assumptions, missing approvals, or invented details. Use the checks as release gates: revise the source inputs or assign a named, authorized reviewer instead of polishing an unsupported output.

Which AI tools have recorded tests for “Design an Excel PivotTable for a business question”?

The published test record for “Design an Excel PivotTable for a business question” lists ChatGPT as of 2026-08-28. This confirms recorded runs, not guaranteed compatibility or identical results in later product versions. For another tool or version, keep every constraint visible and repeat the result checks before use.

More ways to explore

Where this recipe fits

Keep the work moving