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

What We're Building & Why This Order

A report or whitepaper is the document that most rewards the structured way of working. It's long enough that hand-formatting drifts and falls apart, and formal enough that a table of contents, page numbers, and proper citations actually matter. This is the perfect place to see why we spent Modules 2 and 3 on Styles and structure: the payoff is a document that practically assembles itself.

Here's the finished shape you're aiming for — a professional report with all the standard parts in place:

• A cover page (title, subtitle, author, date) with no page number and no running header
• An automatic Table of Contents on its own page, built from your headings
• The body: an introduction, several sections and subsections using Heading 1/2/3, and a conclusion
• A figure (chart, diagram, or image) with a numbered caption and a cross-reference to it in the text
• Footnotes for asides and citations for sources, plus a short reference list
• Headers and footers with page numbers on the body pages only
• One theme — a coordinated set of fonts and colors — applied across the whole thing

The single most important decision is the order you build in. Beginners fight the layout while they're still deciding what to say, and the document turns into a mess of manual tweaks. Do it in three passes instead — the through-line of this whole course:

Write the words first with no fuss about looks. Then give them a structure of Heading styles, sections, and a table of contents. Only then apply presentation — a theme, a captioned figure, footnotes, and final polish. Because presentation flows from structure, you can restyle the entire report at the end by changing its theme or Styles, without hunting through pages. That dotted arrow is the whole reason this order works.

Content First — the Outline & the Words

Open a blank document at microsoft365.com (Word for the web is perfectly capable of everything in this project except a couple of clearly flagged extras) or the desktop app, and do nothing but write. Resist every urge to bold, resize, or center. You're only producing content in this pass.

Start from a skeleton outline so you never face a truly blank page. A solid, general-purpose report outline looks like this — adapt the topic to whatever you genuinely need to write:

[Report Title]
[One-line subtitle]

Executive Summary
    (3-5 sentences: the point of the whole report)

Introduction
    Background
    Purpose and scope

Findings
    Finding one
    Finding two
    Finding three

Discussion
    What it means
    Limitations

Recommendations

Conclusion

References

Type each of those as a plain line and write a paragraph or two of real text under each. Keep it honest and short — three to six pages is plenty for this project. The goal is a complete draft where every section has actual words in it, because the structure pass and the table of contents only mean something when there's real content to hang on them.

One thing to notice already: as you type, Word may be silently applying the Normal style to every paragraph. That's fine for body text. In the next pass we'll take those outline lines that are really headings and tell Word so — which is the moment the document stops being flat text and becomes a structured thing.

Structure — Heading Styles & the Navigation Pane

This is the pass that makes the report a report. Go through your draft and apply real heading Styles to the lines that are headings — never bold-and-resize by hand. The rule of thumb for a report:

To apply a style, click anywhere in the heading line (you don't need to select the whole line) and pick the style from the Styles gallery on Home > Styles. Keyboard shortcuts are faster once you trust them: Ctrl+Alt+1 for Heading 1, Ctrl+Alt+2 for Heading 2, Ctrl+Alt+3 for Heading 3, and Ctrl+Shift+N to return a line to Normal (on a Mac: ⌘+Option+1/2/3 and ⌘+Shift+N). Work top to bottom until every heading has the right level and nothing is hand-bolded.

Now open the Navigation pane — View > Navigation Pane (a checkbox on the desktop app, a toggle on the web — the same route as in Lesson 3.1). This is your map. It lists every heading in order and lets you jump to any section, and — crucially — drag headings to reorder whole sections, moving all their text with them. If a heading doesn't appear in the pane, it isn't a real heading yet; it's hand-formatted text pretending to be one. Fix it now, because the table of contents you'll build next reads from exactly this outline.

The Cover Page, Sections, Headers & Footers

A report needs a cover page that carries no page number and no running header, and body pages that do. The trick that makes this clean is the section break — a divider that lets different parts of one document have different headers, footers, and page numbering.

Add the cover page

The easiest route is Insert > Cover Page, which drops in a designed cover with placeholder fields for title, subtitle, author, and date — fill them in and it inherits your theme automatically. (At the time of writing, Cover Page is a desktop feature; on the web, build a simple cover by putting your Title-styled title, a subtitle, and your name on the first page and following it with a page break.) However you make it, the cover should be its own page, before the table of contents.

Separate the cover from the body with a section break

Put your cursor at the very end of the cover page (or the TOC page) and insert a Next Page section break via Layout > Breaks > Section Breaks > Next Page. A section break — unlike a plain page break — starts a new "section" that can have its own header, footer, and page numbering. That's what lets the cover stay clean while the body gets numbers.

Add headers, footers, and page numbers to the body only

Double-click into the footer of the first body page to open the Header & Footer tools. The key step: turn off Link to Previous so this section's footer is independent of the cover's. Then insert a page number via Insert > Page Number > Bottom of Page. Set it to start at 1 in Page Number > Format Page Numbers > Start at so your body begins on page 1 even though the cover and TOC came first. Add a header if you like — the report title on the left, or a short running title — again with Link to Previous off so it doesn't bleed onto the cover.

The Automatic Table of Contents

Here's the reward for all that Heading-styling: a table of contents that builds itself and updates on command. Put your cursor on the page you set aside for it (between the cover and the body), then go to References > Table of Contents and pick an automatic style. Word reads your Heading 1/2/3 structure and generates a clickable, page-numbered contents list in seconds.

The thing to internalize: a Word TOC is a field, not typed text. It's a live reflection of your headings. When you add, rename, or reorder sections, or the page numbers shift, you don't retype anything — you update the field. Click the TOC and choose Update Table (or right-click it and pick Update Field), then choose Update entire table to catch both text changes and page shifts, or Update page numbers only if headings didn't change.

To rebuild your TOC after edits:
1. Click anywhere inside the Table of Contents.
2. Choose "Update Table" (References tab) or right-click > "Update Field".
3. Pick "Update entire table" to catch renamed/added/moved headings.
4. Confirm — page numbers and titles now match the document exactly.

If your TOC comes out empty or is missing sections, the cause is almost always the one from the last section: those headings aren't real Heading styles. Go back to the Navigation pane, confirm every section shows there, fix any hand-formatted "headings," and update the field again.

Figures, Cross-references, Footnotes & Citations

A report usually has at least one figure — a chart, a diagram, a photo — and the professional way to handle it is with a caption and a cross-reference, not by typing "see the picture above."

Insert the figure and caption it

Place your figure with Insert > Pictures (or a chart via Insert > Chart), then right under it add a caption: References > Insert Caption, with the label set to Figure. Word numbers it automatically — Figure 1, Figure 2, and so on — and renumbers if you add figures earlier. Type a short description after the number: "Figure 1. Adoption over the first six months." Set the picture's text wrapping (from Lesson 4.1) to Top and Bottom or In Line with Text so the caption stays attached beneath it.

Cross-reference it from the text

In the paragraph that discusses the figure, add a cross-reference instead of a hand-typed number: References > Cross-reference, choose reference type Figure, and insert "Only label and number." Now your sentence reads "as shown in Figure 1," and if figures renumber, the reference updates when you update fields — no stale "Figure 3" that's now Figure 2. (Insert Caption and Cross-reference are fullest in the desktop app; on the web you can caption manually, but the automatic numbering and live cross-reference are a desktop strength worth knowing.)

Footnotes and citations

For an aside or a source note at the bottom of the page, use References > Insert Footnote (Ctrl+Alt+F; ⌘+Option+F on a Mac). Word places a superscript number in the text and a matching note at the foot of the page, and renumbers everything automatically as you add or remove notes. For proper source citations, the desktop app's References > Insert Citation lets you add sources and a chosen style (APA, MLA, Chicago) and then generate a Bibliography. On the web, keep a simple manually written References section at the end — the Heading 1 "References" you already created — listing your sources in a consistent format.

Presentation — One Consistent Theme

With content and structure done, presentation is the fast, satisfying finish. Because you formatted by meaning, you can restyle the entire report from one place. On the desktop app that's Design > Themes and the Design gallery of coordinated style sets and color/font combinations; on the web you'll adjust the document's Styles and colors from the Styles and formatting options. Pick one theme and let it flow everywhere — headings, body, TOC, captions, and cover all update together because they're all driven by Styles.

Restraint is what makes a report look professional. A few reliable rules:

• Two fonts, at most — one for headings, one for body. The theme picks a coordinated pair for you.
• One accent color used consistently for headings and figure captions — not a rainbow.
• Generous white space. Let paragraph spacing (not blank lines) breathe; don't cram.
• Consistency over cleverness. The same thing should look the same everywhere — that's the whole benefit of Styles.

Do a final pass: update all fields (TOC, cross-references, page numbers), skim in the Navigation pane to confirm the outline reads well, check the cover has no page number, and read it once top to bottom. Then export a shareable copy with File > Save As / Download > PDF (or File > Export > PDF) — the format most people will open, with your layout locked in.

⚠️ Important Note: If a change to a heading, a moved section, or a new figure isn't reflected in the TOC or a cross-reference, you almost certainly just need to update the fields. Make a habit of updating all fields right before you export — it's the one step that separates a polished report from one with a "Figure 4" that no longer exists.

🎯 Project: Build the Structured Report

Now you build the whole thing, in order. This is a guided, end-to-end project — the goal is a real 3–6 page report or whitepaper with every professional part in place. Follow the passes exactly; the order is what makes it feel easy.

[Title style]      The State of [Your Topic]
[subtitle line]    A short structured report
[author / date]    Your Name — [today's date]

--- section break: Table of Contents page here ---

--- section break: body begins, page number starts at 1 ---

[Heading 1]  Executive Summary
[Normal]     Three to five sentences summarizing the whole report.

[Heading 1]  Introduction
[Heading 2]    Background
[Normal]       Why this topic matters; what led here.
[Heading 2]    Purpose and Scope
[Normal]       What this report covers and does not cover.

[Heading 1]  Findings
[Heading 2]    Finding One
[Normal]       Evidence. Insert Figure 1 here and cross-reference it.
[Heading 2]    Finding Two
[Heading 2]    Finding Three

[Heading 1]  Discussion
[Heading 2]    What It Means
[Heading 2]    Limitations              (add a footnote here)

[Heading 1]  Recommendations
[Normal]     Two or three concrete recommendations.

[Heading 1]  Conclusion

[Heading 1]  References
[Normal]     Source 1. Source 2.        (or an Insert Citation bibliography)

Best Practices for Long, Structured Documents

✅ Do's

• Build in three passes. Content, then structure, then presentation — never all at once.
• Trust the Navigation pane as your source of truth. If the outline reads well there, the TOC will too.
• Update all fields before exporting. Select all (Ctrl+A) and refresh so the TOC, captions, and cross-references are current.
• Use section breaks for anything that must look different — cover, TOC, landscape pages, changed numbering.

❌ Don'ts

• Don't type a table of contents by hand. It goes stale the moment the document changes; let the field build it.
• Don't type figure numbers or "see above." Caption and cross-reference so numbering stays correct.
• Don't add blank lines or a page break where you need a section break. Only a section break gives independent headers and numbering.
• Don't over-decorate. Two fonts, one accent color, and consistency beat a busy design every time.

📓 Learning Journal

📝 Lesson Summary

🎉 What You've Accomplished

You just built a complete, professional, multi-page document from a blank page — cover, self-building table of contents, headers and page numbers, a captioned and cross-referenced figure, footnotes and citations, and one coordinated theme. More importantly, you proved to yourself that the structured way is faster and cleaner than hand-formatting. Everything you touched in Modules 1–4 came together in one real deliverable you could send today.

❓ Common Questions at This Stage

🔭 Looking Ahead

In the next lesson — Lesson 7.2: Project — A Résumé & a Newsletter (Designed Documents) — we switch from long-and-formal to short-and-designed. You'll build two shorter pieces where layout and restraint take center stage: a clean one-page résumé aligned with Styles and tables (never spaces), and a newsletter with columns, a masthead, wrapped images, and pull quotes. Same core habits, a very different look.

✅ Before the Next Lesson

• Finish and export your report so you have a real, complete document to be proud of
• Try one experiment: change the theme and watch the whole report restyle in a click
• Write your Learning Journal entry for this lesson

📚 Additional Resources

• Microsoft Word Help & Learning (Microsoft Support)
• Insert a table of contents (Microsoft Support)
• Word report and document templates (create.microsoft.com)