Building a Data Analysis Report in R

A data analysis report in R is a self-contained document that interleaves narrative text, R code, and its output — plots, tables, and inline computed values — so the reader sees exactly how each conclusion was produced rather than trusting a static slide export from an analysis nobody can re-run. R Markdown (and its successor Quarto) is the standard tool for this: you write plain Markdown for prose and fenced code chunks for R, and knitting the document executes every chunk fresh and weaves the results directly into the final HTML, PDF, or Word output.

An .Rmd or .qmd file begins with a YAML header specifying the title, author, date, and output format (html_document, pdf_document, word_document, or a Quarto equivalent), followed by the document body where prose is written in plain Markdown and R code lives in fenced chunks. Each chunk accepts options — echo = FALSE to hide code and show only output, fig.width and fig.height to control plot sizing, message = FALSE and warning = FALSE to suppress package startup noise — that give fine-grained control over what the final reader actually sees.

A well-structured analysis report follows a consistent narrative arc: an early chunk imports raw data with readr::read_csv() or similar and immediately checks its shape and types with glimpse() or str(), a cleaning section handles missing values, type coercion, and outlier flags explicitly rather than silently, and an exploratory section computes summary statistics and early visualizations before any modeling begins. Keeping these phases as distinct, labeled sections — not one giant undifferentiated chunk — means a reader (including future you) can jump straight to "where did this filtering happen?" without re-reading the entire script.

For narrative reports, ggplot2 remains the standard for figures because its layered syntax makes it easy to add clear titles, axis labels, and annotations that a plot needs when it's read by someone who wasn't in the room for the analysis, while packages like gt, kableExtra, or DT turn a plain data frame into a formatted, publication-ready table with sortable columns, conditional cell coloring, or captions. The most common mistake in report tables is dumping a raw print(df) into the document — a reader parsing 40 unlabeled columns of a base R print output learns far less than they would from three clearly labeled summary tables built with gt::gt().

Beyond a single static report, R Markdown and Quarto support parameters — declared in the YAML header as params: region: "West" — that let the same .Rmd template generate a different report per region, per month, or per client by passing different parameter values to rmarkdown::render() or quarto::quarto_render(), which is how many organizations automate dozens of near-identical reports from one source file instead of copy-pasting a script 20 times. For sharing, knitting to html_document with self_contained: true embeds all images and CSS into a single portable HTML file, while pdf_document (via LaTeX/tinytex) produces a fixed, print-ready document better suited for formal or archival distribution.