--- title: Add useful headings sidenav: guidelines redirect_from: - /howto/guidelines/headings.cfm - /howto/quickreference/pops/headers.cfm - /howto/guidelines/FederalPLGuidelines/orgHeadings.cfm sources: - author: 'Garner, Bryan A.' title: Legal Writing in Plain English date: 2001 publisher: 'University of Chicago Press, Chicago' page: p. 14-16 - author: 'Kimble, Joseph' title: Lifting the Fog of Legalese date: 2006 publisher: 'Carolina Academic Press, Durham, NC' page: p. 70 (C) - author: 'Murawski, Thomas A.' title: Writing Readable Regulations date: 1999 publisher: 'Carolina Academic Press Durham, NC' page: 'pp. 10-12, 27' - author: Office of the Federal Register title: Document Drafting Handbook link: 'http://www.archives.gov/federal-register/write/handbook/ddh.pdf' date: 1998 page: MMR-2 --- Well organized writing will still be difficult for users to follow if they can't see how it's organized. An effective way to reveal your document's organization is to use lots of useful headings. Headings are also critical for effective web pages (see [Writing for the web]({{ site.baseurl }}{% link _pages/guidelines/web/index.md %})). You should use headings liberally on the web to help your user accomplish top tasks. ## Types of headings There are three types of headings: - question headings - statement headings - topic headings ### Question headings Question headings are useful if you know what questions your audience will ask. Most people come to government documents with questions. If you know those questions, use them as headings. They will help the audience find the information they are looking for quickly. Using the question-and-answer format helps your audience scan the document and find specific information. Example: > Why do we use headings? ### Statement headings Statement headings are the next best choice because they are still very specific. Example: > Add useful headings ### Topic headings Topic headings are the most formal; many times management is more comfortable with them. But sometimes they're so vague that they just aren't helpful. Topic Headings such as "General," "Application," and "Scope" are so vague they may confuse the user. For example, "Application" might mean an application to your agency from someone reading your document. But it might as easily mean what the document applies to. Example: > Headings ## Add page-level structure It's often useful to start writing your document by developing the headings, structuring them to your audience's concerns. This approach can also reveal major groupings of information that you might want to identify with headings. In the following example, broad topic headings help organize the document, and specific topics add a second level of organization: