Design an Excel PivotTable for a business question

Autor: AILesson6 Min. EinrichtungszeitGetestet mit:ChatGPTGeprüft am: 2026-08-28

Schnelle Antwort

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

1

Kontext hinzufügen

Dein Text bleibt in diesem Browser. AILesson Prompts sendet ihn nicht an ein Modell oder einen Server.

2

Dein Prompt

Nicht ausgefüllte Felder bleiben als Platzhalter sichtbar, sodass du den Prompt weiterhin kopieren und bearbeiten kannst.

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.
Im Playground ausprobieren
Standardmäßig privatDer Prompt wird lokal in deinem Browser zusammengestellt. Gib keine vertraulichen Informationen in einen KI-Dienst ein, es sei denn, deine Organisation erlaubt dies.

Von der Eingabe zum Ergebnis

Ein ausgearbeitetes Beispiel

Sieh dir an, wie konkreter Kontext dieses Rezept in ein nutzbares Ergebnis verwandelt.

Tatsächliche Eingabe

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.

Beispielausgabe

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.

Warum das funktioniert

  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.

Ergebnis prüfen

  • 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?

Sicher nutzen

Häufig gestellte Fragen

Praktische Antworten dazu, wann du dieses Rezept verwenden solltest, was du bereitstellen solltest und wo menschliche Prüfung weiterhin wichtig ist.

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.

Weitere Möglichkeiten zum Entdecken

Wo dieses Rezept hineinpasst

Bring die Arbeit voran