{"id":936,"date":"2016-10-03T21:24:51","date_gmt":"2016-10-04T01:24:51","guid":{"rendered":"http:\/\/techrhet.com\/3213\/?page_id=936"},"modified":"2016-10-03T21:24:51","modified_gmt":"2016-10-04T01:24:51","slug":"hats-a-design-procedure-for-routine-business-documents","status":"publish","type":"page","link":"https:\/\/techrhet.com\/3213\/hats-a-design-procedure-for-routine-business-documents\/","title":{"rendered":"HATS: A Design Procedure for Routine Business Documents"},"content":{"rendered":"<div class=\"stickmenu2\" style=\"font-size: 130%; padding-bottom: 4px;\"><a id=\"top\"><\/a>H.A.T.S.: <a href=\"#overview\">overview<\/a><a href=\"#intro\"><\/a> | <a href=\"#headings\">headings<\/a> | <a href=\"#access\">access<\/a> | <a href=\"#typography\">typography<\/a> | <a href=\"#space\">space<\/a> | <a href=\"#summary\">summary<\/a> | <a href=\"#final\">final<\/a><\/div>\n<p><span class=\"anchor\" id=\"overview\"><\/span><\/p>\n<div style=\"width:600px; text-align:center; margin:-10px auto 20px;\">Information based on and adapted from Baker, William H. &quot;HATS: A Design Procedure for Routine Business Documents.&quot; <em>Business Communication Quarterly <\/em>64.2 (2001): 65-76.<\/div>\n<div style=\"width:515; float:right; margin-left:15px; padding-top:25px;\"><img decoding=\"async\" loading=\"lazy\" src=\"https:\/\/techrhet.com\/3213\/wp-content\/uploads\/sites\/2\/2016\/10\/HATS-731px.png\" alt=\"\" width=\"500\" height=\"397\"\/><\/div>\n<h4>Overview<\/h4>\n<p>One of the most common mistaken notions novice professional writers hold is the idea that readers will approach their writing chronologically, reading the entire document from beginning to end. <\/p>\n<p> In professional arenas, audiences are comprised of different readers, different needs, and different approaches to reading. Upper management may read documents  for conclusions and recommendations, accountants may read documents for the budget sections, and lawyers  may read documents for the backgrounds and methods. Because professional contexts have various audiences with various needs and interests, professional writers must create documents that are easy to navigate, easy to understand, and serve the needs of all potential audiences. These documents are sometimes known as &ldquo;modular documents.&rdquo;<\/p>\n<p>Professional writers can use &quot;HATS&quot; to create modular documents that are easy to navigate, access, and understand. While we&#8217;re familiar with making documents <em>rhetorically<\/em> effective, HATS is a set of considerations for making documents <em>visually<\/em> effective. <\/p>\n<p><span class=\"anchor\" id=\"headings\"><\/span><\/p>\n<h4>Headings<\/h4>\n<p>Headings are navigation signposts that  guide readers through documents and preview  forthcoming information. Headings should be ADEQUATE in number\/frequency to serve as landmarks of current and forthcoming content. Headings should be organized HIERARCHICALLY, using typeface, size, style, and alignment to show different levels of importance, specificity, and relationships. <\/p>\n<p>For additional explanations and examples, check out the following links<\/p>\n<ul>\n<li style=\"padding-bottom:10px;\"><a href=\"http:\/\/typographyforlawyers.com\/hierarchical-headings.html\" target=\"_blank\">&#8220;Hierarchical Headings&#8221;<\/a> from <em>Typography for Lawyers; <\/em>provides a great explanation of why writers should use a tiered number system instead of traditional Roman numerals or numbered\/lettered hierarchies. <\/li>\n<li style=\"padding-bottom:10px;\"><a href=\"http:\/\/designsensory.com\/pws\/lesson6\/index.html\" target=\"_blank\">&#8220;Lesson 6: Using Parallel Form&#8221;<\/a> from<em> Professional Writing Style<\/em> by Dr. Russel Hirst, Associate Professor and Director of the Technical Communication Program at the University of Tennessee, Knoxville. <\/li>\n<li><a href=\"http:\/\/faculty.washington.edu\/farkas\/TC510-Fall2011\/Farkas-ManagingHeadings.pdf\" target=\"_blank\">&#8220;Managing Headings in Print and Online Documents&#8221;<\/a> from David K. Farkas from the Department of Technical Communication in the<br \/>\nCollege of Engineering at University of Washington. <\/li>\n<\/ul>\n<p><span class=\"anchor\" id=\"access\"><\/span><\/p>\n<h4>Access<\/h4>\n<div style=\"width:264px; float:right;\"><img decoding=\"async\" loading=\"lazy\" src=\"https:\/\/techrhet.com\/3213\/wp-content\/uploads\/sites\/2\/2016\/10\/charts-254.png\" alt=\"\" width=\"254\" height=\"648\" align=\"right\"\/><\/div>\n<p>When appropriate, visuals should accompany text to help convey complex ideas or data. This helps to make information understandable and accessible to audiences. <\/p>\n<p>In professional documents, writers may decide to use lists, graphic organizers, tables, visual aids, charts, illustrations, or photographs to convey information that might be difficult to read, understand, or use in paragraph format.<\/p>\n<div style=\"float:left; font-size:120%; font-weight:300;\">\n<table border=\"0\" align=\"left\" cellpadding=\"0\" cellspacing=\"10\">\n<col span=\"2\">\n<tr>\n<td style=\"text-align:right;\"><span style=\"font-family:'Roboto Slab'; font-size:130%; font-weight:400;\">Graphic<\/span><\/td>\n<td style=\"text-align:center;\"><span style=\"font-family:'Roboto Slab'; font-size:130%; font-weight:400;\">Information Type &amp; Uses<\/span><\/td>\n<\/tr>\n<tr>\n<td style=\"text-align:right; padding:10px;\">tables<\/td>\n<td style=\"padding:10px 10px 10px 30px;\">organized or systematic display of data<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align:right; padding:10px;\">maps<\/td>\n<td style=\"padding:10px 10px 10px 30px;\">geographic information; data by location<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align:right; padding:10px;\"> bulleted lists<\/td>\n<td style=\"padding:10px 10px 10px 30px;\">unordered or nonchronological  information<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align:right; padding:10px;\">numbered   list<\/td>\n<td style=\"padding:10px 10px 10px 30px;\">ordered, prioritized, or chronological information<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align:right; padding:10px;\">pie chart<\/td>\n<td style=\"padding:10px 10px 10px 30px;\"> relationships between  parts and the whole. <\/td>\n<\/tr>\n<tr>\n<td style=\"text-align:right; padding:10px;\">bar  graph<\/td>\n<td style=\"padding:10px 10px 10px 30px;\">simple comparisons; changes in quantity<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align:right; padding:10px;\">line graph<\/td>\n<td style=\"padding:10px 10px 10px 30px;\">trends or changes over time<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align:right; padding:10px;\">flowchart<\/td>\n<td style=\"padding:10px 10px 10px 30px;\">a process, often with  shapes to represent (types of) activities<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align:right; padding:10px;\">organization chart<\/td>\n<td style=\"padding:10px 10px 10px 30px;\">organizational hierarchy; how an organization is set up<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align:right; padding:10px;\">Gantt chart<\/td>\n<td style=\"padding:10px 10px 10px 30px;\">project schedule with concurrant, overlapping, and linear phases<\/td>\n<\/tr>\n<\/table>\n<\/div>\n<hr class=\"divider3\">\n<div class=\"pagefootnote\">fig 1: <a href=\"https:\/\/commons.wikimedia.org\/wiki\/File:Organizational_chart.svg\" target=\"_blank\">Organizational chart<\/a>, by TotoBaggins at the English language Wikipedia via Wikimedia Commons. Licensed under<a href=\"https:\/\/en.wikipedia.org\/wiki\/en:GNU_Free_Documentation_License\" target=\"_blank\"> GNU Free Documentation License<\/a> and Creative Commons Attribution-Share Alike 3.0 Unported <a href=\"http:\/\/creativecommons.org\/licenses\/by-sa\/3.0\/\" target=\"_blank\">(CC BY-SA 3.0)<\/a>.<\/div>\n<div class=\"pagefootnote\">fig 2: <a href=\"https:\/\/commons.wikimedia.org\/wiki\/File:Tornado_Frequency.svg\" target=\"_blank\">Tornado Frequency<\/a>, by 0Jak via [Wikimedia Commons. Licensed under Creative Commons Attribution-Share Alike 3.0 Unported <a href=\"http:\/\/creativecommons.org\/licenses\/by-sa\/3.0\/\" target=\"_blank\">(CC BY-SA 3.0)<\/a>.<\/div>\n<div class=\"pagefootnote\">fig 3: <a href=\"https:\/\/commons.wikimedia.org\/wiki\/File:Gantt-chart.png\" target=\"_blank\" data-rel=\"lightbox-image-0\" data-rl_title=\"\" data-rl_caption=\"\" title=\"\">Gantt chart<\/a>, by Mkoval via <em>Wikimedia Commons<\/em>. Licensed under<a href=\"https:\/\/en.wikipedia.org\/wiki\/en:GNU_Free_Documentation_License\" target=\"_blank\"> GNU Free Documentation License<\/a> and Creative Commons Attribution-Share Alike 3.0 Unported <a href=\"http:\/\/creativecommons.org\/licenses\/by-sa\/3.0\/\" target=\"_blank\">(CC BY-SA 3.0)<\/a>.<\/div>\n<p><span class=\"anchor\" id=\"typography\"><\/span><\/p>\n<div style=\"width:395px; padding-left:10px;float:right;\"><img decoding=\"async\" loading=\"lazy\" src=\"https:\/\/techrhet.com\/3213\/wp-content\/uploads\/sites\/2\/2016\/10\/typography-weights.png\" alt=\"\" width=\"385\" height=\"514\" align=\"right\"\/><\/div>\n<h4>Typography<\/h4>\n<h5>Type<\/h5>\n<p style=\"margin-bottom:0.5em;\">Typeface can convey professionalism, illustrate contrast, and show hierarchical organization of information. In general, make sure body text is readable by using a 10-12 point common serif font such as Times New Roman (for print documents). Select a contrasting font for headings and vary type size and style for subheadings.\n<\/p>\n<div style=\"padding-bottom:7px; padding-left:15px;\"><strong>typeface<\/strong> = font family such as Times New Roman, Arial, or Roboto<\/div>\n<div style=\"padding-bottom:7px; padding-left:15px;\"><strong>type size<\/strong> = size of font; in print documents, often measured in points; in online documents, often measured in pixels, em, or percent<\/div>\n<div style=\"padding-bottom:7px; padding-left:15px;\"><strong>type style<\/strong> = style of font such as italic, bold, or underlined<\/div>\n<p>Avoid using more than two typefaces in routine business documents. Use size, style, and font variants (such as all caps, small caps, etc.) to indicate hierarchy and contrast. Above all else, make sure the text is readable.<\/p>\n<h5>Alignment<\/h5>\n<div style=\"padding-bottom:7px; padding-top:7px;padding-left:15px;\"><strong>left-aligned<\/strong> = font family such as Times New Roman, Arial, or Roboto<\/div>\n<div style=\"padding-bottom:7px; padding-left:15px;\"><strong>right-aligned<\/strong> = size of font; in print documents, often measured in points; in online documents, often measured in pixels, em, or percent<\/div>\n<div style=\"padding-bottom:7px; padding-left:15px;\"><strong>centered<\/strong> = style of font such as italic, bold, or underlined\t<\/div>\n<div style=\"padding-bottom:7px; padding-left:15px;\"><strong>justified <\/strong>= style of font such as italic, bold, or underlined\t<\/div>\n<p>Except in rare circumstances, left-align (or left-justify) your body text. Left-aligned text should leave a &quot;ragged&quot; right margin. <\/p>\n<div style=\"width:841px; margin:20px auto;\"><img decoding=\"async\" loading=\"lazy\" src=\"https:\/\/techrhet.com\/3213\/wp-content\/uploads\/sites\/2\/2016\/10\/margins-all.png\" width=\"841\" height=\"466\" alt=\"\"\/><\/div>\n<p><span class=\"anchor\" id=\"space\"><\/span><\/p>\n<div style=\"width:410px; padding-top:20px; float:right;\"><img decoding=\"async\" loading=\"lazy\" src=\"https:\/\/techrhet.com\/3213\/wp-content\/uploads\/sites\/2\/2016\/10\/whitespace.png\" alt=\"\" width=\"400\" height=\"347\" align=\"right\"\/><\/div>\n<h4>Space<\/h4>\n<p>Allow adequate marginal space around the document &#8212; for routine business documents, 1 inch on all sides. Additionally, use white space around visuals instead of lines or frames and use space to visually link headings and text.<\/p>\n<p><span class=\"anchor\" id=\"summary\"><\/span><\/p>\n<h4>Summary<\/h4>\n<p>To recap, ask these questions when using HATS:<sup>*<\/sup><\/p>\n<ol>\n<li style=\"padding-bottom:10px;\"><strong>Headings:<\/strong> Are there enough headings? Do they reflect a clear hierarchy of organization?<\/li>\n<li style=\"padding-bottom:10px;\"><strong>Access:<\/strong> Is important information easy to find? Is the information easy to understand?  Does the method of presentation enhance readability and clarity?<\/li>\n<li style=\"padding-bottom:10px;\"><strong>Typography:<\/strong> Does the document use  appropriate typefaces, size, styles, and alignment for both body text and headings?<\/li>\n<li><strong>Space:<\/strong> Does the document have appropriate white space to make it inviting and easy to read?<\/li>\n<\/ol>\n<hr class=\"divider3\">\n<div class=\"pagefootnote\">* Recap questions adapted from the OWL at Purdue, <a href=\"https:\/\/owl.english.purdue.edu\/owl\/resource\/632\/1\/\" target=\"_blank\">&#8220;HATS: A Design Procedure for Routine Business Documents.&#8221; <\/a><\/div>\n<p><span class=\"anchor\" id=\"final\"><\/span><\/p>\n<h4>A Final Note:<\/h4>\n<div style=\"width:450px; margin:20px auto 3px;\"><img decoding=\"async\" loading=\"lazy\" src=\"https:\/\/techrhet.com\/3213\/wp-content\/uploads\/sites\/2\/2016\/10\/wall-of-text-2.png\" width=\"450\" height=\"465\" alt=\"\"\/><\/p>\n<div style=\"font-family:'Roboto Slab'; font-size:200%; color:#006064; text-align:center; margin:10px auto; width:400px;\">Nobody likes a wall of text.<\/div>\n<\/div>\n","protected":false},"excerpt":{"rendered":"<p>H.A.T.S.: overview | headings | access | typography | space | summary | final Information based on and adapted from Baker, William H. &quot;HATS: A Design Procedure for Routine Business Documents.&quot; Business Communication Quarterly 64.2 (2001): 65-76. Overview One of the most common mistaken notions novice professional writers hold is the idea that readers will <a href='https:\/\/techrhet.com\/3213\/hats-a-design-procedure-for-routine-business-documents\/' class='excerpt-more'>[&#8230;]<\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"no-sidebars.php","meta":[],"_links":{"self":[{"href":"https:\/\/techrhet.com\/3213\/wp-json\/wp\/v2\/pages\/936"}],"collection":[{"href":"https:\/\/techrhet.com\/3213\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/techrhet.com\/3213\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/techrhet.com\/3213\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/techrhet.com\/3213\/wp-json\/wp\/v2\/comments?post=936"}],"version-history":[{"count":0,"href":"https:\/\/techrhet.com\/3213\/wp-json\/wp\/v2\/pages\/936\/revisions"}],"wp:attachment":[{"href":"https:\/\/techrhet.com\/3213\/wp-json\/wp\/v2\/media?parent=936"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}