Write a precise brief for a pivot-style summary

A grouped summary needs a measure, grouping dimensions and aggregation rule. Naming those three choices prevents a polished table with the wrong meaning.

Prepare the workbook

Keep an unchanged source copy and explain column meanings, units and date boundaries. Use a spreadsheet or data role with compatible local tools, or the prepared sandbox. Ask for a rejected-row report instead of silently deleting inconvenient records. OfficeCubs text previews do not recalculate formulas; open the final workbook in a spreadsheet application and check representative formulas and totals.

Inputs for this workflow: transactions.csv with region, product, quantity and revenue.

Work through the task

1. Choose the row and column dimensions.
2. Define sum versus count and the treatment of missing groups.

A brief you can adapt

Build an XLSX summary with regions as rows, product groups as columns and summed revenue as values. Include detail and totals sheets; label unassigned groups.

The filenames above are examples. Replace them with your actual inputs and destination before submitting the task.

Review the deliverable

Recalculate one cell from the source detail and verify both row and column totals.

Where this approach can fail

An average of precomputed averages is not automatically a valid overall average.

For the related desktop setup, see missing document tools.