<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>style guide | CalmIT</title>
	<atom:link href="https://calmit.org/tag/style-guide/feed/" rel="self" type="application/rss+xml" />
	<link>https://calmit.org</link>
	<description>Remote Support</description>
	<lastBuildDate>Fri, 18 Sep 2026 07:24:04 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.1.4</generator>

<image>
	<url>https://calmit.org/wp-content/uploads/Circle_blue-1.png</url>
	<title>style guide | CalmIT</title>
	<link>https://calmit.org</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Writing Plainly</title>
		<link>https://calmit.org/plain-language/</link>
		
		<dc:creator><![CDATA[]]></dc:creator>
		<pubDate>Tue, 07 Jan 2014 17:41:52 +0000</pubDate>
				<category><![CDATA[Writing for the Web]]></category>
		<category><![CDATA[content]]></category>
		<category><![CDATA[How to]]></category>
		<category><![CDATA[style guide]]></category>
		<category><![CDATA[writing]]></category>
		<guid isPermaLink="false">https://zenpages.org/?page_id=2396</guid>

					<description><![CDATA[PDF version Hard writing makes easy reading. ~An old adage. Plain language writing is reader-focused writing. But what makes something plain language? The Center for Plain Language defines “plain” in terms of people’s behaviour. Can the audience for the material quickly and easily: find what they need understand what they find act appropriately on that [&#8230;]]]></description>
										<content:encoded><![CDATA[<p><a style="line-height: 1.5em;" href="https://calmit.org/wp-content/uploads/PlainLanguage.pdf" target="_blank" rel="noopener">PDF version</a></p>
<div id="attachment_2514" style="width: 275px" class="wp-caption alignright"><img decoding="async" aria-describedby="caption-attachment-2514" class="wp-image-2514 size-full" src="https://calmit.org/wp-content/uploads/pen_writing.jpg" alt="pen_writing" width="265" height="178" /><p id="caption-attachment-2514" class="wp-caption-text">Writing in plain language is key to helping readers understand and use your information.</p></div>
<p><strong><em>Hard writing makes easy reading.</em></strong></p>
<p>~An old adage.</p>
<p>Plain language writing is <strong>reader-focused</strong> writing. But what makes something plain language?</p>
<p>The Center for Plain Language defines “plain” in terms of people’s <strong><em>behaviour.</em></strong> Can the audience for the material quickly and easily:</p>
<ul>
<li>find what they need</li>
<li>understand what they find</li>
<li>act appropriately on that understanding? (<a href="#ref1">1</a>)</li>
</ul>
<p>In 1998, President Clinton made plain language a major government initiative. He wrote:</p>
<p><em>By using plain language, we send a clear message about what the government is doing, what it requires, and what services it offers…. Plain language documents have logical organization; common, everyday words, except for necessary technical terms; ‘you’ and other pronouns; the active voice; and short sentences.</em> (<a href="#ref2">2</a>)</p>
<p>Today, all of us who write can find immediate guidance on the principles of plain language at the government’s website <a href="http://www.plainlanguage.gov/" target="_blank" rel="noopener">plainlanguage.gov</a>. The info in this tip sheet comes directly from its how-to’s, tools, checklists, and examples, sometimes even verbatim.</p>
<p>Of course, we’ve only tapped the surface of what you can find with a visit to plainlanguage.gov. You’ll also find info and guidance on writing in plain language for the sake of your readers by visiting the <a href="#resources">resources</a> we’ve listed at the end of this page. Enjoy!</p>
<p><a href="#top">Back to top</a></p>
<h4>10 Tips for Writing in Plain Language</h4>
<p><strong>#1 | Write for the average reader.</strong></p>
<p>Know the expertise and interest of your average reader, and write to that person. Don’t write to the experts, the lawyers, or doctoral candidates, unless they’re your intended audience. (<a href="#ref3">3</a>)</p>
<p>To communicate with the average reader, we need to write at the 6th to the 8th grade reading level. (<a href="#ref4">4</a>)</p>
<p><strong>#2 | Organize to serve the reader’s needs.</strong></p>
<p>The two most useful principles:</p>
<ul>
<li>Put the most important material first and the exceptions last</li>
<li>Organize material chronologically</li>
</ul>
<p><strong>#3 | Use helpful headings.</strong></p>
<p>Headings help the reader find their way. Use more headings on the web, with less info under each. People skim and scan.<br />
(Read more about <a href="/webwriting/headings">crafting your headings and subheadings</a>.)</p>
<p><a href="#top">Back to top</a></p>
<p><strong>#4 | Use “you” to speak to your reader.</strong></p>
<p>Using pronouns pulls the reader in. Use “you” for the reader, “we” for your agency.</p>
<p><strong>#5 | Use active voice.</strong></p>
<p>Active voice makes it clear <em>who</em> is doing <em>what</em>. It is shorter and clearer.</p>
<p><em><strong>Examples</strong></em><br />
<em>Passive:</em> The tray of food was dropped by the waiter.<br />
<em>Active:</em> The waiter dropped the tray of food.</p>
<p><em>Passive:</em> Your request for funding has been denied by the review committee.<br />
<em>Active:</em> The review committee denied your request for funding. (<a href="#ref5">5</a>)</p>
<p><em>Occasions to use passive voice:</em></p>
<ul>
<li>when you don’t know the actor (“John was murdered.”)</li>
<li>when the actor is unimportant (“The senator was re-elected.”)</li>
<li>when the emphasis is on the acted-upon (“The little girl was rescued.”) (<a href="#ref6">6</a>)</li>
</ul>
<p><a href="#top">Back to top</a></p>
<p><strong>#6 | Use short sentences and short sections.</strong></p>
<p>Short sentences, paragraphs, and sections help readers get through material. Chunking adds white space.</p>
<p><em>Example</em><br />
<strong>Before:</strong> Long, dense paragraph…<br />
<strong>After:</strong> Do at least 30 minutes of exercise, like brisk walking, most days of the week.</p>
<p><a href="#top">Back to top</a></p>
<p><strong>#7 | Use concrete, familiar words.</strong></p>
<p>Avoid jargon, foreign terms, legal terms. Replace complex words with simple ones.</p>
<p><em>Examples</em><br />
Instead of: <em>a and/or b</em> → <strong>a or b or both</strong><br />
Instead of: <em>accomplish</em> → <strong>do</strong><br />
Instead of: <em>accorded</em> → <strong>given</strong></p>
<p><strong><em>Want the full list?</em></strong><br />
<a href="https://www.plainlanguage.gov/resources/checklists/" target="_blank" rel="noopener">plainlanguage.gov</a></p>
<p><a href="#top">Back to top</a></p>
<p><strong>#8 | Omit excess words.</strong></p>
<p>Challenge every word. Remove unnecessary modifiers.</p>
<p><em>Examples</em><br />
Instead of: <em>as a means of</em> → <strong>to</strong><br />
Instead of: <em>at the present time</em> → <strong>now</strong></p>
<p><strong>Before:</strong> Long bureaucratic sentence…<br />
<strong>After:</strong> If you make a hole while freeing a stuck vehicle, you must fill it before you drive away.</p>
<p><a href="#top">Back to top</a></p>
<p><strong>#9 | Place words carefully.</strong></p>
<p>Keep subject, verb, and object close. Put exceptions at the end. Place modifiers correctly.</p>
<p><strong>#10 | Use no more than 2 or 3 subordinate levels.</strong></p>
<p>More than 3 levels confuses readers. Subdivide instead.</p>
<p><span id="resources"></span><br />
<a href="#top">Back to top</a></p>
<h4>Resources of More Information</h4>
<p>plainlanguage.gov is not the only source. Here are others:</p>
<p>NIH Plain Language Online Training<br />
<a href="http://plainlanguage.nih.gov/CBTs/PlainLanguage/login.asp" target="_blank" rel="noopener">plainlanguage.nih.gov</a></p>
<p>Plain Language Wizardry<br />
<a href="http://plainlanguage.com/" target="_blank" rel="noopener">plainlanguage.com</a></p>
<p>Plain English Campaign<br />
<a href="http://www.plainenglishtraining.com/" target="_blank" rel="noopener">plainenglishtraining.com</a></p>
<p>Plain Language Association International<br />
<a href="http://www.plainlanguagenetwork.org/" target="_blank" rel="noopener">plainlanguagenetwork.org</a></p>
<p>Center for Plain Language<br />
<a href="http://www.centerforplainlanguage.org/" target="_blank" rel="noopener">centerforplainlanguage.org</a></p>
<p>Readability Formulas<br />
<a href="http://www.readabilityformulas.com/" target="_blank" rel="noopener">readabilityformulas.com</a></p>
<p>Style Writer’s Readability Calculations<br />
<a href="http://www.stylewriter-usa.com/readabilitycalc.html" target="_blank" rel="noopener">stylewriter-usa.com</a></p>
<p><a href="#top">Back to top</a></p>
<p><strong>Want to read another section of Writing for the Web?</strong></p>
<ul>
<li><a href="/webwriting/reading">How people read on the web</a></li>
<li><a href="/webwriting/scanning">Helping readers skim and scan</a></li>
<li><a href="https://zenpages.org/essential-message-first/">Putting your essential message first</a></li>
<li><a href="/webwriting/chunking">Chunking your information</a></li>
<li><a href="/webwriting/headings">Using headings and subheadings</a></li>
<li>Writing in plain language (you’re here)</li>
</ul>
<p><span id="ref1"></span><a href="#top">Back to top</a></p>
<h4>References</h4>
<p><em>The National Dissemination Center thanks <a href="http://www.plainlanguage.gov/" target="_blank" rel="noopener">plainlanguage.gov</a> for its excellent materials, freely used here unless noted below.</em></p>
<p>1 | Center for Plain Language. (n.d.). <em>About plain language</em>. <a href="http://centerforplainlanguage.org/about-plain-language/" target="_blank" rel="noopener">centerforplainlanguage.org</a></p>
<p><span id="ref2"></span><br />
2 | Locke, J. (2004). <em>A history of plain language in the United States government</em>. <a href="http://www.plainlanguage.gov/whatisPL/history/locke.cfm" target="_blank" rel="noopener">plainlanguage.gov</a></p>
<p><span id="ref3"></span><br />
3 | plainlanguage.gov. (n.d.). <em>Document checklist for plain language</em>. <a href="http://www.plainlanguage.gov/howto/quickreference/checklist.cfm" target="_blank" rel="noopener">plainlanguage.gov</a></p>
<p><span id="ref4"></span><br />
4 | The Informatics Review. (n.d.). <em>Comprehension and reading level</em>. <a href="http://web.archive.org/web/20111018045029/http://www.informatics-review.com/FAQ/reading.html" target="_blank" rel="noopener">informatics-review.com</a></p>
<p>As an alternative: DuBay, W.H. (2004). <em>The principles of readability</em>. <a href="http://www.impact-information.com/impactinfo/readability02.pdf" target="_blank" rel="noopener">impact-information.com</a></p>
<p><span id="ref5"></span><br />
5 | The Quality Writing Center. (n.d.). <em>Choosing between active and passive voice</em>. <a href="http://www.uark.edu/campus-resources/qwrtcntr/resources/handouts/activepassive.htm" target="_blank" rel="noopener">uark.edu</a></p>
<p><span id="ref6"></span><br />
6 | Bailey, E.P. (1996). <em>Plain English at work</em>. Oxford.</p>
<p><a href="#top">Back to top</a></p>
]]></content:encoded>
					
		
		
			</item>
	</channel>
</rss>
