12.01Report Design and CompilationAvailable

Research Report Architecture

Decide the shape of a report before you write it: chapters, order, method placement, appendix boundary, and how much space each section gets.

Free. Works on Claude, ChatGPT, Gemini or any assistant that accepts a skill file.

What this skill does

The method, encoded.

Most weak research reports are not badly written. They are badly shaped, and better writing was never going to rescue them. The report follows the questionnaire, so it ends on demographics and never on the answer. The largest chapter is the one with the most cross-tabs behind it rather than the one that bears on the decision. Every chapter is a topic, so no chapter reaches a conclusion. And the structure is usually last project's structure, applied without anyone asking whether this project has the same shape.

This skill makes the structural decision explicit and makes it early, when changing it costs ten minutes rather than two days. It gives the conventional reference structure as a starting point to argue with, then supplies the decision rules that actually determine shape: the decision at stake, how the audience will read, whether the study is one argument or several parallel findings, whether the objectives map to chapters or cut across them, and whether the reader needs the method before the findings or after.

It also fixes the two sizing failures that quietly ruin good reports: sections sized by evidence volume rather than importance, and material sent to the appendix by exhaustion rather than by rule.

You get a one to two page architecture document, agreed before compilation begins, that several writers can work to without producing sections that will not join.

Best used for

  • Studies about to be written up where the chapter set has not been agreed
  • Projects whose objectives cut across each other rather than mapping to chapters
  • Reports serving two audiences with different reading behaviour
  • Tracking waves inheriting a structure nobody has re-examined
  • Studies producing far more material than the report can hold
  • Multi-writer reports needing a shared plan before drafting

Typical inputs

What you give it.

The decision the report informs, its owner and its timing, Agreed research objectives in final form, Top ten to twenty findings with bases and confidence, Audience description and expected reading behaviour, Format ceiling, page or slide limit, and any fixed sections, Agreed narrative or storyline, Previous wave or predecessor report in the same series, Questionnaire or discussion guide as fielded, Known stakeholder positions and prior beliefs

Typical outputs

What you get back.

Agreed architecture document, one to two pages, Chapter table with title, one-job statement, altitude, reader belief, budget and objectives answered, Objective-to-evidence mapping with a clean, cross-cutting or uneven verdict, Stated argument shape, ordering principle and methodology placement with reasons, Page or slide budget per chapter, set by decision weight, Main-document versus appendix boundary rule and appendix contents list, Record of material cut entirely, with reasons, Structural review points for researcher judgement

Method coverage

What the skill works through.

  1. Why report structure is usually decided by default
  2. The conventional reference structure, and why it is a starting point rather than a template
  3. Fixing the decision, the audience and how the report will be read
  4. Testing whether objectives map to chapters or cut across them
  5. One argument or several parallel findings, and why the answer changes the structure
  6. Choosing an ordering principle: decision-led, journey, segment or thematic
  7. Where methodology goes for different audiences
  8. Giving every chapter one job
  9. Sizing sections against importance rather than evidence volume
  10. Setting the main-document and appendix boundary by rule
  11. Writing the architecture down and agreeing it before compilation
  12. Stress-testing a structure before anyone writes to it
  13. When not to design a structure, and what to use instead

Download

Free skill. One file.

Enter your email once. Every skill you download after that takes a single click.

How to install

Add the skill file and the five kernel protocols to a Claude Project, a ChatGPT Project, a Gemini Gem, or paste them at the top of any assistant conversation. Then give it your real research material, not a description of it.

Download skill

Questions

Common questions.

How should I structure a research report?

Start from the decision it informs and how the audience will read, not from a template. Then answer four questions in order: do the objectives map to chapters or cut across each other, is this one argument or several parallel findings, what ordering principle follows from that, and what job does each chapter do. The conventional structure (summary, context, objectives, method, findings, implications, recommendations, appendix) is a reasonable first guess and a poor final answer. If your last four reports had the same sections, at least three of them were the wrong shape.

Should the report follow the order of the questionnaire?

Almost never by choice. Instrument order is the default only because it requires no decision, and it reliably produces chapters that end without conclusions and a report that finishes on demographics. Order from the argument the reader has to travel. The legitimate exceptions are a prescribed tender or regulatory format, a tracking template read side by side across waves, a data book or appendix, and the case where the instrument already followed a natural sequence.

Should each objective get its own chapter?

Test it rather than assume it. Lay your top findings against the objective list and see which objective each answers. If each objective is answered by a distinct body of evidence, the objectives can be the chapters. If the same evidence answers two or three objectives, a chapter per objective will present that evidence three times, and the chapters should instead be built around the evidence bodies with a coverage table showing where each objective is answered.

Where should the methodology section go?

It depends on the audience and there are three defensible answers. Before the findings, in full, where the reader must judge the evidence before accepting the conclusions: academic, regulatory, technical or contested work. A short statement early with the detail appended, for most commercial reporting. After the findings, for a senior audience reading for a decision. Whatever you choose, material limitations still travel with the findings they qualify: a base of 44 is disclosed where the number appears, not only in the method section.

How long should each section of a report be?

Set the budget by how much the section bears on the decision, then check it against the evidence volume. Left alone, sections grow to fit the analysis behind them, which is exactly how the largest chapter in a report ends up being the least important one. A study that ran forty questions on usage and eight on the thing being decided will produce a usage chapter five times too big unless someone sizes deliberately. Surplus evidence goes to the appendix and the budget holds.

What should go in the appendix of a research report?

Decide by a rule, before you are tired. A workable one: the main document carries what the reader needs to follow and check the argument, and the appendix carries everything else that was analysed. So full tables, the instrument as fielded, the complete method, and secondary findings go back. Three things never go to the appendix for convenience: contradicting evidence, material caveats, and anything moved there because it complicates the story.

Is a research report one argument or a set of findings?

Try stating it in three sentences. If the sentences want "because" and "therefore", it is one argument and the structure should be linear, with chapters that depend on each other. If they want "and", the findings are parallel and the structure should be modular, ordered by importance, with chapters that stand alone. If you write "and therefore", you have the common mixed case: build the linear argument as a spine and place the independent findings after it as visibly separate sections rather than interleaving them.

When should I decide the structure of a report?

After you know roughly what the study found, and before any prose exists. Too early and you are structuring the questionnaire. Too late and the report has already been written into the wrong shape, and changing it costs days and loses source references. The practical test is whether you can state the top five findings. If you cannot, structure the analysis first.

How do I write one report for two different audiences?

Build for the audience holding the decision, and make the other audience's chapters extractable: self-contained, with their own bases and context, so a chapter lifted into their meeting still stands alone. A structure that tries to serve two audiences equally usually serves neither. Where the two genuinely need different conclusions emphasised, the honest answer is one report plus a separate short executive artefact, not one compromised structure.

Should a tracking report keep the same structure every wave?

Separate two things. Conventions (base definitions, segment names, terminology, comparison rules) should be carried forward deliberately, because they are what makes waves comparable. Structure should be re-examined every wave, because the story changes even when the questionnaire does not. A tracking report with the same chapter order for six waves is usually reporting the instrument rather than the market.

Research where people already are.
Analyse it where you already work.

Yazi helps researchers conduct surveys, AI interviews and longitudinal research directly through WhatsApp.

New Report on SA Gambling Impact
Check It Out