Skip to the content
Documentation
Help Start
Reading in:
  • German: 9,075 of 9,075 pages
About the help in other languages
All help pages

Write a plain-language summary

For editors - write the short summary at the top of a page or document (the In short, Intro or Summary field) so anyone understands what it is, who it is for and what to do, with a method, before-and-after shapes and a…

Download as PDF

Address: https://doc.exponential.earth/exphelp/viewer/help/government/tasks/publishing/write-a-plain-language-summary.md

On this page

Write a plain-language summary

This page is for editors who write the first lines of a page: the In short, Intro or Summary field. Most visitors read only these lines, and search results and link previews show them. Plain language guidance from government is collected at plainlanguage.gov; this page gives a short method.

Contents

  1. Before you start
  2. Steps
  3. Shapes that work
  4. Check the result
  5. Pitfalls

Before you start

  • Know who reads the page and what they want to do.
  • Have the full text or document at hand.

Steps

  1. Answer three questions, one sentence each:
    • What is this?
    • Who is it for?
    • What should the reader do, or what happens next?
  2. Use the words your readers use; put the official term in brackets once if it is needed.
  3. Put the most important fact first (a deadline, a change, a cost).
  4. Cut every sentence to one idea; aim for sentences under about 20 words.
  5. Use "you" and active verbs: "You can apply until 31 March" rather than "Applications may be submitted until ...".
  6. Read it aloud. If you stumble, rewrite.
  7. Put it in the summary field; Preview; Send for publishing.

Shapes that work

PageShape of the summary
A service"You can <do what> if <who>. It costs <cost>. Apply online or at <place>."
A report"This report shows <main finding>. It covers <scope and period>. The main recommendations are <two or three>."
A notice"<What> will <happen> at <place> from <date> to <date>. <What people should do>."
A consultation"We propose <what>. Tell us what you think by <date>. Your answers help decide <what>."

Check the result

  • To do: Someone outside your team understands the summary without reading further.
  • To do: Dates, amounts and places are exact.
  • To do: The summary makes sense in a search result, without the rest of the page.

Pitfalls

PitfallAvoid it
Repeating the titleadd information
Starting with the organization ("The Department of Example announces ...")start with what matters to the reader
Abbreviationswrite them out
"Please see the attached document"the summary must stand alone

Become an Exponential Partner

Partners share their information, provide funding, contribute back and develop the products with us, and that is how Exponential grows. A partner website and dashboard are planned for mid-2027: please become a partner today to speed up our growth rate and land new features faster.

Something wrong on this page? Report an error

Documentation license

This documentation is free documentation, licensed under the GNU Free Documentation License 1.3 or later.

Exponential Copyright © 1998-2026 Exponential Foundation and 7x