🎉 Konveio recognized in the prestigious 2024 GovTech 100 list!
How-tos

Solving the Challenges of Writing in Plain Language

July 19, 2021
4
minute read

Konveio’s Document Engagement Platform transforms static PDF documents into digital experiences, rivaling that of a custom HTML website. But the writing used on a PDF or website must follow several best practices, not the least of which is to write in plain language.

SIMPLE, BUT NOT EASY

After studying the official website for the Plain Language Act of 2010, we wanted to highlight how our latest interactive glossary feature solves a conundrum that all planning professionals invariably face while writing complex documents and trying to follow best practices to make the document understandable.

Below are three quotes from the official website for the Plain Language Act that highlight the disconnect between best practices and the reality that planners face. After we’re on the same page, we’ll share our remedy.

BEST PRACTICE #1:

  • “When you have no way to express an idea except to use technical language, make sure to define your terms.”
  • Source (FPLG - Minimize Jargon)

BEST PRACTICE #2:

BEST PRACTICE #3:

  • “...readers are likely to forget that you’d assigned some common word a new meaning, and when they come upon the word later in your document they assign the common meaning, rather than your specialized one.” -  Morris Cohen (from Reason and Law)
  • Source: FPLG - Minimize Definitions

At Konveio, we know that this is easier said than done. It’s unrealistic to expect that by word choice alone, a technical/legal document can avoid the use of jargon and acronyms entirely. Therefore some definitions will be necessary.

Even with definitions kept to a minimum, most readers of a zoning code will skip ahead to a specific section that may be dozens of pages into a document. To have definitions readily available for clarity wherever the reader starts within the document, there would likely need to be definitions of special terms for every page or section which is downright unrealistic.

While appendices are welcome and encouraged, the default impulse for most readers is to ask Google to define an unfamiliar term, which may not provide the same definition or meaning that the writer intended.

So how can we add clarity and ensure mutual understanding without turning a 600-page document into an 800-page document?

Solution

Konveio allows you to upload a customized table of definitions that are relevant to your document and provide the assumed knowledge required for the average stakeholder to interpret each page without adding clutter or length to a document. It can be added to or adjusted at any time and reused across multiple documents.

In summary, we believe that writers ought to follow the advice of the plain language guidelines. And when they cannot, they should be empathetic and use technology to solve the problem.

Similar posts

With over 2,400 apps available in the Slack App Directory.

Explore a live example

Experience our platform as if you were a participant.
Explore Konveio
Don't be shy!
Check it out for yourself.
🎉 Konveio recognized in the prestigious 2024 GovTech 100 list!
https://www.konveio.com/blog/plain-language-act-of-2010
www.konveio.com
CC-MAIN-2024-33
37132
application/http; msgtype=response
sha1:JCFQ4KIG6AQACTXQHXWTXJLI4G3DPZZO
<urn:uuid:1dd24786-8f68-4258-988b-aaae00ce188f>
2024-08-13T18:26:22Z
52.206.163.162
text/html
sha1:E2AMY4B7UPFCUSIAQOWU3EQMES44E2ZK
<urn:uuid:2e515c0d-35a5-4f11-807d-aeca5431bff0>
https://www.konveio.com/blog/plain-language-act-of-2010
response
<urn:uuid:2824c0c0-2b2f-4915-936f-f2843f5f9d30>
isPartOf: CC-MAIN-2024-33
publisher: Common Crawl
description: Wide crawl of the web for August 2024
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-67-67-90
software: Apache Nutch 1.20 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.5-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: https://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/