📝 Lesson 7.1: Project — A Structured Report / Whitepaper with a TOC

Why Structure First (the Whole Project's Secret)

Think of a report the way a builder thinks of a house. Nobody sensible chooses the paint colors before the walls are framed. You lay the foundation, raise the frame, run the wiring — and only then decorate. A document works exactly the same way, and it's the single habit that separates a report that comes together in an hour from one that fights you for a whole afternoon.

Everything in this project rides on one idea you've been building since the start of the course: Content → Structure → Presentation. Today you'll feel why that order matters, because the report's most impressive features are not things you draw by hand — they're things Docs generates for you from the structure you've already put in place:

• The table of contents is built automatically from your Heading 1 and Heading 2 styles (the same styles you met back in Lesson 2.3).
• The document outline in the left margin — your navigation for a long document — comes from those same headings.
• A consistent, professional look falls out of applying styles once, instead of hand-formatting forty headings one at a time.

So the order of the build is deliberate. We'll plan the headings, apply the styles, and only then generate the table of contents and polish the presentation. If you ever find yourself bolding a heading by hand today, stop — that's the old typewriter instinct, and it quietly breaks the automatic features we're relying on.

Step 1 — Plan & Outline the Report

Before we open Docs, we plan on paper (or in a scratch note). A report is really an argument with sections, and the sections are your Heading 1s. Sub-points within a section become Heading 2s. Get this skeleton right and the rest of the build is almost mechanical.

A classic report or whitepaper structure looks like this — feel free to adapt it to your real topic:

Write this list of headings first — just the headings, no body text yet. It should take five minutes, and it forces you to decide what the report actually says before you get lost in wording. Aim for four to six Heading 1 sections; you can always add more once the frame is up.

Step 2 — Heading Styles & the Cover Page

Now we open a new document at docs.google.com and give the skeleton real structure. This is the load-bearing step: the styles you apply here are what the table of contents, the outline, and your polished look will all be built from.

Apply the heading styles

Using the styles habit from Lesson 2.3: click into a section title, then apply a style from the styles dropdown on the left of the toolbar (it usually reads Normal text), or use the keyboard shortcuts, which are faster once they're in your fingers:

• Ctrl+Alt+1 (Mac: Cmd+Option+1) — Heading 1, for your main section titles
• Ctrl+Alt+2 (Mac: Cmd+Option+2) — Heading 2, for sub-sections
• Ctrl+Alt+0 (Mac: Cmd+Option+0) — back to Normal text, for body paragraphs

Apply Heading 1 to each main section, Heading 2 to each sub-section, and leave your body paragraphs as Normal text. Do not reach for the bold button and a bigger font size — that only looks like a heading; it doesn't become one, and the automatic TOC will ignore it entirely. This is the exact distinction we drew back in Lesson 2.3, and today is where it earns its keep.

Build the cover page

A cover page gives a report instant credibility. Put your cursor at the very top of the document, above your first heading, and create a title block. You can style the title with the Title and Subtitle styles (they sit in the same styles dropdown as your headings) so the look stays consistent and — importantly — a "Title" is not treated as a section in the TOC.

Your cover typically holds the report title, a subtitle or one-line description, your name, and the date. To push the rest of the report onto its own page, insert a page break right after the cover material: Insert > Break > Page break, or Ctrl+Enter. Now your cover stands alone, and the report body starts fresh on page two.

That diagram is the whole lesson in one line: the outline feeds the styled headings, the styled headings feed the automatic TOC, and the polished report is the payoff. Everything flows left to right from structure.

Step 3 — Automatic TOC, Footnotes & Page Numbers

Here's the reward for structuring first. Because your headings are real styles, three professional features drop into place almost for free.

Insert the automatic table of contents

Put your cursor where the TOC belongs — usually on its own page just after the cover, before the Introduction. Then use Insert > Table of contents and pick a style. Docs reads your Heading 1 and Heading 2 styles and lists them, often with page numbers or clickable links. This is the same automatic TOC we introduced in Lesson 3.2; the difference now is that it's serving a real, multi-page report.

⚠️ Important Note: The table of contents does not update itself as you keep writing. When you add or rename a heading, or the page numbers shift, click the TOC and press the update (circular arrow) button that appears, or right-click it and choose to update. We'll do a final update in Step 5 — but get used to refreshing it any time the structure changes.

Add footnotes for citations

A whitepaper cites its sources, and footnotes are the clean way to do it. Click at the end of the sentence or claim you want to support, then use Insert > Footnote (or Ctrl+Alt+F). Docs drops a small superscript number and jumps your cursor to the bottom of the page, where you type the source. Add a couple of footnotes to your Findings section so the report reads as evidence-based rather than opinion. The numbering renumbers itself automatically if you add or remove one later — another job the software handles so you don't have to.

Turn on page numbers

Multi-page documents need page numbers so the TOC's numbers mean something and readers can find their place. Use Insert > Page numbers and choose a position (top or bottom, and whether to show a number on the first page — usually you'll skip it on the cover). Docs places them in the header or footer area and keeps them accurate as the document grows.

Step 4 — A Figure with Caption & Alt Text

Reports are more persuasive with something to look at. Your figure can be an image (a chart, a photo, a diagram) or a table of data — both count. This reuses the object skills from Module 4; here we add the finishing touches that make a figure feel professional and accessible.

Insert the figure

In your Findings section, insert an image with Insert > Image (upload one, or use Insert > Image > Search the web for a licensed picture), or insert a data table with Insert > Table. Keep it modestly sized so it sits comfortably within the text column and doesn't overwhelm the page.

Add a caption

A caption tells the reader what they're looking at. The simplest, most portable approach is a short line of centered text directly beneath the figure, such as "Figure 1: Quarterly response times, 2024." Numbering your figures ("Figure 1", "Figure 2") lets you refer to them from your body text — a hallmark of a real report.

Add alt text for accessibility

Alt text is a short written description of an image that screen readers announce to people who can't see it — and it's genuinely important, not an optional extra. Right-click the image and choose Alt text (or find it in the image options), then write a plain-language description of what the figure shows, not just its title. A good alt text for a chart describes the trend ("Response times fell steadily from January to December"), not just "a chart."

Step 5 — Polish, Header/Footer & Final Review

The report is built; now we make it feel finished. Polish is mostly about consistency — the quiet quality that readers feel without being able to name it.

Add a header and footer

A header or footer that repeats on every page adds polish and context. Use Insert > Headers and footers (or double-click the top or bottom margin of a page). A common, tasteful choice: the report title in the header, and your page number plus perhaps a date in the footer. Most reports also turn on the option to skip the header/footer on the first page so the cover stays clean — look for that checkbox in the header/footer options.

Make the styling consistent

Skim the whole document with fresh eyes and check that:

• Every main section uses Heading 1 and every sub-section uses Heading 2 — nothing hand-bolded.
• Body paragraphs are all Normal text, with consistent spacing (adjust once via Format > Line & paragraph spacing if needed).
• Your figure caption style is the same everywhere.

If you want to nudge the look of all your headings at once — say, a different color or font — change one heading to taste, then update the style to match it (the "update Heading 1 to match" option in the styles menu). That's the styles-over-hand-formatting payoff: one change, applied everywhere, in seconds. Compare that to re-formatting every heading by hand, and you'll never go back.

Update the TOC and do a final read-through

Because you added headings, a figure, and footnotes after inserting the TOC, the page numbers have shifted. Click the table of contents and press its update button so it reflects the finished document. Then read the report once, top to bottom, checking that the TOC links land on the right sections, footnotes point to real sources, and page numbers are sensible. A two-minute final pass catches almost every embarrassing mistake.

🎯 Project: Build Your Report End-to-End

This is the real thing. You'll produce a complete 3–5 page structured report from a blank page, assembling every skill above in order. Pick a topic you actually care about — a proposal for your team, a research summary for a class, a whitepaper for a side project, or even a well-organized version of the document you've been planning since Lesson 1.1. A genuine topic makes the hour fly by.

[Report Title]              <- style as Title
[One-line subtitle]         <- style as Subtitle
Your Name  ·  Date
--- page break here (Ctrl+Enter) ---

Table of Contents           <- Insert > Table of contents on the next line

Executive Summary           <- Heading 1
Introduction                <- Heading 1
   Background                <- Heading 2
   Scope                     <- Heading 2
Findings                     <- Heading 1
   Finding 1                 <- Heading 2  (put your figure + footnotes here)
   Finding 2                 <- Heading 2
Recommendations             <- Heading 1
Conclusion                  <- Heading 1

Best Practices for Structured Reports

✅ Do's

• Outline before you write. Deciding your headings first is the fastest route to a coherent report — and it hands you the TOC for free.
• Let structure generate the extras. TOC, outline, and consistent styling all flow from headings. Set the structure and the polish nearly builds itself.
• Update the TOC last. Make it the final step, after every heading and page has settled, so its numbers are accurate.
• Write real alt text. Describe what a figure shows, not just that it exists — it's the accessible, professional choice.

❌ Don'ts

• Don't hand-format headings. Bold-and-bigger looks like a heading but isn't one; it breaks the TOC and outline.
• Don't decorate before the structure is done. Fiddling with fonts on page one while the skeleton is half-built wastes the effort the moment you restructure.
• Don't forget the cover's page break. Without a page break, your body creeps onto the cover as you add text.

📓 Learning Journal

📝 Lesson Summary

🎉 What You've Accomplished

You built a complete, multi-page structured report from a blank page — cover to conclusion, with an automatic TOC, footnotes, page numbers, a header/footer, and a captioned figure. More importantly, you did it the professional way: structure first, presentation last, letting the software generate the hard parts. This is the exact workflow behind real whitepapers, research reports, and proposals. You're no longer using features one at a time — you're building finished documents.

❓ Common Questions at This Stage

🔭 Looking Ahead

Next up — Lesson 7.2: Project — A Résumé & a Newsletter (Designed Documents) — we shift from structure to design. You'll build two smaller, layout-focused documents: a clean one-page résumé and a two-column newsletter, practicing columns, tables for alignment, image text wrapping, and the design principles that make a page look intentional.

✅ Before the Next Lesson

• Finish your report and run through the completion checklist
• Try exporting it once as a PDF (File > Download > PDF Document) to see how it locks the layout
• Write your Learning Journal entry for this lesson

📚 Additional Resources

• docs.google.com — open the app
• Google Docs Help Center (Google Support)
• Add and edit a table of contents (Google Support)