TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
RE: Readability statistics: is anyone expected to meet a particular Flesch score?
Subject:RE: Readability statistics: is anyone expected to meet a particular Flesch score? From:"James Barrow" <vrfour -at- verizon -dot- net> To:<techwr-l -at- lists -dot- techwr-l -dot- com> Date:Mon, 15 Jan 2007 09:00:27 -0800
>Geoffrey Marnell asked:
>
>A few years ago, on some forum or other, I read that some employers of
>technical writers expected their writers to always meet or better a
>particular Flesch readability score. (This score is based on the number of
>syllables per 100 words and the average number of words per sentence.
>Microsoft Word automatically computes this score, and displays it if you
>have set your Spelling & Grammar options accordingly.)
>
>Is anyone currently subject to such a demand (or has been in the recent
>past)? If so, what justification was given for it?
During a recent project, I worked for a consulting company who was tasked
with creating a large client-server app for the state. We (tech writers)
were told that the documentation could not be higher than a sixth grade
reading level. This presented a challenge since one really good sentence at
a twelfth grade level could translate to four good sentences at a sixth
grade level, thus increasing the volume of documentation, which was
specified in the SOW.
The justification for the sixth grade level Flesch score was this. As we
were developing the application and documentation, we were working the
people who would go back to train the users. We were training the trainers.
Since there was no support for the documentation once the app went live, we
had to make sure that what we wrote was as easy to understand as possible.
That is, state employees could call the consulting company with questions
(incidents) about the software, but not questions to clarify something in
the documentation.
WebWorks ePublisher Pro for Word features support for every major Help
format plus PDF, HTML and more. Flexible, precise, and efficient content
delivery. Try it today! http://www.webworks.com/techwr-l
Create HTML or Microsoft Word content and convert to Help file formats or
printed documentation. Features include single source authoring, team authoring,
Web-based technology, and PDF output. http://www.DocToHelp.com/TechwrlList
---
You are currently subscribed to TECHWR-L as archive -at- infoinfocus -dot- com -dot-