How to Structure Professional Documents in Word: Reports, Proposals, Policies and Manuals

The Tutoring Club now writes documents that decide things: an annual report for the community center board, a grant proposal to a local foundation, a safety policy every site must follow, and a volunteer manual people use in the middle of a busy session. Each one has a different reader asking a different question. A document that answers the wrong question, or hides the answer on page 11, fails even if every sentence is correct.

In this tutorial you will match structure to genre, write an executive summary, turn headings into statements, plan front matter, and use Word's structure features so the document stays organized when you move whole sections. Then you will review the result with a rubric. The practice file is a messy annual report for you to restructure.

Match structure to the genre

Before you write, ask two questions: who will read this, and what do I need them to do afterwards? Approve money, follow a rule, finish a task, make a decision. The genre is the standard answer to those questions, and readers expect its structure. Use it.

• Reports are read by busy people who may read only page 1. Put the conclusions there and the evidence after.
• Proposals are scored. If the funder gives headings or a scoring sheet, use their headings, in their order, with their words. Reviewers look for each item where they expect it.
• Policies are looked up, not read. Number every rule so people can point to "rule 3.2", define words that could be argued about, and say who owns the policy and when it will be reviewed.
• Manuals and SOPs (standard operating procedures) are used mid-task. Organize by task, not by topic: Sign a student out, not Pickup procedures. One action per numbered step.

Write an executive summary that answers first

An executive summary is the whole document in one page, for the reader who will read nothing else. It is not an introduction, which tells readers what is coming. It tells them what you found and what you want.

1. The answer. One or two sentences: the main finding and the main recommendation.
2. The ask. What you need from the reader, and by when.
3. Key findings. Three to five bullets, each with a number.
4. Where to find more. Cross-references to the sections with the details.

Write it last, when you know what the document says, and put it first, right after the title page and table of contents. Keep it to one page. If it doesn't fit, you haven't decided what matters most yet. Test it: someone who reads only the summary should be able to make the decision.

Headings as statements, and the front matter

In reports and proposals, turn label headings into statement headings that carry the message. Then the Navigation pane (View› then Show› then Navigation Pane) reads like a summary of the whole document, and a reader who skims only the headings still gets the story.

Not every heading should be a statement. Keep labels for reference parts readers look for by name, such as Definitions, Budget in a funder's template, or Appendix A. Attendance data. In manuals, use task headings that start with a verb: Sign a student out.

Front matter is what comes before the main text. For any document longer than a few pages, plan three parts:

• Title page. Title, subtitle, organization, date and version. Use Insert› then Pages› then Cover Page or your template kit's own cover. Insert the title with Insert› then Text› then Quick Parts› then Document Property› then Title so the cover always matches the Title property from the previous tutorial. Turn on Different First Page in the header and footer options so the cover has no page number.
• Table of contents. References› then Table of Contents, built from the heading styles, as in Intermediate Tutorial 2. Statement headings make the TOC itself worth reading.
• Revision history. A small table that shows which version this is and what changed, so nobody acts on an old copy.

Word features that hold the structure together

A professional document gets reorganized many times before it is final. Built with Word's structure features, a section can move and every number, reference and contents entry follows. Built by hand, every move breaks something.

You learned these tools one at a time in Advanced Tutorial 1 and Advanced Tutorial 4. What is new at this level is using them as a system: decide the genre, build the outline with heading styles in View› then Views› then Outline, then write. In Outline view or the Navigation pane you can drag a heading to move a whole section with everything under it.

Write in plain language

Plain language is not simple thinking. It is writing your reader can understand the first time they read it. For high-stakes documents it matters more, not less: a board member reading on a phone, a parent reading in a second language, or a volunteer reading during a busy session all need the point fast.

• Short sentences. Aim for an average of 15 to 20 words. One idea per sentence, one topic per paragraph.
• Active voice and real people. Say who does what: The site coordinator updates the pickup list.
• Common words. Use, not utilize. Before, not prior to.
• Define each term once and then use the same word every time. Don't switch between site, location and branch.
• Lists for steps and choices, tables for comparisons, prose for reasons.
• In policies, choose words on purpose: must for requirements, should for recommendations, may for permissions. Say what each means in the definitions.

Word can help you spot long sentences and wordy phrases. Run Review› then Proofing› then Editor and look at the refinement suggestions for clarity and conciseness. In many versions you can also turn on Show readability statistics in File› then Options› then Proofing; Word then shows average sentence length and a readability score after a spelling and grammar check. Treat the numbers as a hint, not a grade.

Review high-stakes documents with a rubric

A rubric turns "looks good to me" into specific checks that two reviewers can agree on. Score each row 0 (not yet), 1 (needs work) or 2 (ready). Send the document on only with no zeros and at least 12 of 14 points. Use it at the review stage of the workflow from Tutorial 3 of this level, and add the accessibility record from the previous tutorial.

Common mistakes

Practice