Skip to content

Market research reporting: how to write a report leaders act on

Market research reporting is the work of turning survey and study data into outputs people use to decide: toplines, data tables, full reports, executive summaries and interactive reports. A good market research report leads with the answer, states each finding as what changed, why it matters and what to do, and shows bases and significance honestly.

Mark Langsfeld
Mark Langsfeld

Chief Executive Officer · Updated June 10, 2026

Part of the guide Automated reporting

The fieldwork is closed, the tables are back, and a brand lead wants to know what to do by Friday. Market research reporting is the step where good studies often lose their value: hundreds of tables go out, and nobody can say what changed or what to do about it. This guide shows how to choose a report format, structure a market research report, and write findings that leaders act on. It is part of our wider guide to automated reporting for market research.

Key takeaways

  • Pick the format by audience: toplines and data tables for analysts, executive summaries and full reports for decision makers.
  • Write a market research report answer-first: objectives, method and sample, key findings, implications, recommendations, then the appendix.
  • State every finding as what changed, why it matters and what to do next.
  • Show the base and the significance result next to every number a reader might act on.
  • Build the report as a template so the next wave takes hours, not weeks.

What does market research reporting cover?

Market research reporting covers every output that carries results from the data file to the people who use them. Most studies need more than one format, because an analyst checking a subgroup and a CMO deciding on budget want different things.

FormatMain audiencePurposeWhen to use it
ToplineResearch team, project sponsorFast first read of total-sample resultsDays after fieldwork closes, before full analysis
Data tablesAnalystsEvery question by every key subgroup, with bases and significanceAlways; they are the source for everything else
Full reportMarketing, product and insights teamsThe complete story: findings, evidence, implicationsMajor studies and annual or quarterly tracker readouts
Executive summarySenior leadersOne page of what changed, why it matters, what to doEvery study that feeds a decision
Interactive reportTeams who return to the dataFilter and explore results without a new data requestTrackers and studies many teams will query over time

Every format inherits errors from a messy data file, so cleaning, coding and weighting come first; see our guide to survey data processing.

How do you write a market research report?

To write a market research report, follow the order a busy reader needs, not the order you did the work. The answer comes first.

  1. Objectives. The business decision the study informs, in one or two sentences. “Decide which age group gets the trial budget next quarter” beats “understand consumer attitudes.”
  2. Method and sample. Who was asked, how many, when, and how the data was weighted, in a short paragraph.
  3. Key findings. Three to five findings, each a full sentence that states the result, with the chart that proves it.
  4. Implications. What the findings mean for the decision in the objectives.
  5. Recommendations. Specific actions, each tied to a finding. People decide; the report makes the case.
  6. Appendix. Questionnaire, full data tables with bases, definitions and the significance test used.

The test of a good structure: a reader who stops after the key findings should still know what to do.

How should you write each finding?

A finding is not a number. “46% of 18–34s would consider the brand” is a data point. A finding says what changed or stands out, why it matters for the objective, and what to do next.

Use the finding as the slide headline, in a full sentence, with the chart and base underneath. When we review tracker readouts, the most common fix is rewriting topic labels such as “Consideration by age” into sentences that still make sense if the chart fails to load.

How do you show bases and significance honestly?

The base is the number of respondents behind a percentage. Show it on every chart and table, as “n=300,” so readers can judge how much weight a number carries. Agree a minimum base rule before reporting; many teams flag subgroups under 50 as indicative only.

Significance testing tells you whether a gap between two groups is likely to be real rather than sampling noise. State the confidence level once (usually 95%), mark significant differences consistently with letters or arrows, and say plainly when a gap is not significant.

Which charts work best for survey data?

Choose the chart by the question type. Sorted horizontal bars suit single-choice and multi-choice questions, stacked bars suit agreement scales, and lines suit results across waves. Our guide to charting survey data goes through each case.

Cut 3D effects, heavy gridlines and colors that carry no meaning, and label bars directly. One message per chart, stated in the headline.

What does a worked example look like?

The numbers below are illustrative, not from a real study. A brand tracker asks 1,000 category buyers whether they would consider the brand next time they buy. The crosstab of consideration by age group comes back like this.

Would consider the brand18–3435–5455+Total
Base (n)3004003001,000
Respondents who would consider13815293383
Consideration46%38%31%38%

Total consideration is 383 ÷ 1,000 = 38%. Now test the gaps at 95% confidence:

  • 18–34 vs 55+: a 15-point gap. The standard error of the difference is the square root of (0.46 × 0.54 ÷ 300 + 0.31 × 0.69 ÷ 300), about 3.9 points. Times 1.96, the margin is about 7.7 points. 15 is larger, so the gap is significant.
  • 18–34 vs 35–54: an 8-point gap against a margin of about 7.4 points. Significant, but only just.
  • 35–54 vs 55+: a 7-point gap against a margin of about 7.1 points. Not significant; report it as directional.

The one-sentence finding: “Consideration is highest among 18–34s at 46%, a significant 15 points above buyers aged 55+ (31%; n=300 in each group).”

Why it matters: if the objective is to grow trial, the youngest group is the most open audience. The recommendation: “Focus next quarter’s trial activity on 18–34s, and before cutting spend on 55+, check whether their lower consideration comes from low awareness or poor fit.” The report claims no more than that: the 35–54 vs 55+ gap is not reliable, so it drives no separate decision.

How do you write an executive summary leaders read?

Keep it to one page. Open with the answer to the objective, then list three to five findings, each with its number, base and a one-line implication. Close with the recommendations and any decision you need from the reader. Cut method detail beyond one line, and any finding that does not change a decision.

If you produce these every wave, one-page updates on what changed, why it matters and what to do follow the same structure.

How do you make reports reusable across waves?

A tracker report should be a template, not a new project each wave. Fix the question wording, subgroup definitions, chart types and slide order, and compare each result with the previous wave, marking significant moves. Log anything that did change, such as a new question or sample source.

Separate the layer that changes from the layer that stays. Tables and charts should refresh from the new data file; the narrative is rewritten each wave. Our guide to automating tracker reporting shows how to set that up, and automated market research covers which other steps can run on a schedule.

What are the common mistakes?

  • The data dump. Sending every table in the deck, so readers pick their own three numbers.
  • No so-what. Topic headlines and charts with no finding or action attached.
  • Hidden bases. Percentages without n, or tiny subgroups presented with the same confidence as the total.
  • Chart junk. 3D bars, ten-slice pie charts and decorative color that compete with the message.
  • Calling noise a trend. Reporting a 3-point wave-on-wave move as a change when it sits inside the margin of error.

How do you put this into practice?

Start with the data tables, because every other format depends on them. Crosstabs and banner tables with weighting and significance testing give you subgroup results with bases and significance marked in one place. If your team rebuilds the same readout every wave, look at how to automate wave readouts and executive briefs, reviewed by your team before they go out.

For your next report, write the objective as a decision at the top of a blank page, then draft three finding sentences in the what changed, why it matters, what to do format before you build a single chart.

Frequently asked questions

How long should a market research report be?

As short as the decision allows. A one-page executive summary plus 10 to 20 slides of findings covers most single studies, with the full tables in an appendix. If a slide does not support a finding or a recommendation, move it to the appendix.

Should you report results that are not statistically significant?

Yes, when they answer a question someone asked, but label them clearly. Say the difference is directional or within the margin of error, and do not build a recommendation on it alone. Reporting a null result also stops people from acting on noise.

What should go in the appendix of a market research report?

The questionnaire, the full data tables with bases, the sample definition and quotas, the weighting approach, the significance test and confidence level used, and any definitions such as how top-two-box was calculated. Readers who want to check your work should find everything there.

Who should own the storyline of a market research report?

The researcher who ran the analysis should draft it, because they know where the data is thin. Review it with the stakeholder who owns the decision before it goes wide, so the recommendations match the choices that person can actually make.

See your recurring reporting in mTab.

Bring a tracker with a few waves. We'll show you the reports, the readouts Flows can draft, and the review step before anything goes out.

Book a demo