{"id":178,"date":"2025-09-13T21:10:55","date_gmt":"2025-09-13T21:10:55","guid":{"rendered":"https:\/\/libraryresources.nse.org.ng\/professionalandtechnicalcommunication\/chapter\/7-1-structure-of-routine-messages\/"},"modified":"2026-03-16T14:19:34","modified_gmt":"2026-03-16T14:19:34","slug":"7-1-structure-of-routine-messages","status":"publish","type":"chapter","link":"https:\/\/libraryresources.nse.org.ng\/professionalandtechnicalcommunication\/chapter\/7-1-structure-of-routine-messages\/","title":{"raw":"7.1 Structure of Routine Messages","rendered":"7.1 Structure of Routine Messages"},"content":{"raw":"<div class=\"7.1-structure-of-routine-messages\">\n<p class=\"import-Normal\">Perhaps the simplest and most common routine message type is where the sender offers up information that helps the receiver. These may not be official memos, but they follow the same structure: opening, body, and closing.<\/p>\n<p class=\"import-Normal\">Managers, clients, and coworkers alike send and receive requests for information and action all day. Because these provide the recipient with direction on what to do, the information that comes back or action that results from such requests can only be as good as the instructions given. Such messages must therefore be well organized and clear about expectations, opening directly with a clearly stated general request unless you anticipate resistance to the request and proceeding with background and more detailed instruction, if necessary (see example below for parts of routine messages).<\/p>\n\n<h2>Opening<\/h2>\nDescribe the reason for the message. Main point should be included from the beginning of the message.\n<div class=\"textbox textbox--examples\"><header class=\"textbox__header\">\n<h3 class=\"textbox__title\"><em>Example<\/em><\/h3>\n<\/header>\n<div class=\"textbox__content\">\n\nHello Mohammed: I hope you are having a wonderful week. Could you help update the website by adding the new hires to the Personnel page?\n\n<\/div>\n<\/div>\n<h2>Body<\/h2>\nInclude the details of the message in an organized matter.\n<div class=\"textbox textbox--examples\"><header class=\"textbox__header\">\n<h3 class=\"textbox__title\"><em>Example<\/em><\/h3>\n<\/header>\n<div class=\"textbox__content\">\n\nWe have hired three new associates in the past few weeks. With the content of the attached folder that contains their bios and hi-res pics, please do the following\n<ul>\n \t<li>Proof of bios using Track Changes and send them to me.<\/li>\n \t<li>Post the proofed bios on the site. I would like to quickly read them and suggest further edits over the phone, if necessary, since time is of the essence here.<\/li>\n \t<li>Downsize the pics to 72dpi and crop them so that they are the same dimensions as the other portraits on that page before posting them along with the bios.<\/li>\n<\/ul>\n<\/div>\n<\/div>\n<h2>Close<\/h2>\nProvide action and next steps related to the content.\n<div class=\"textbox textbox--examples\"><header class=\"textbox__header\">\n<h3 class=\"textbox__title\"><em>Example<\/em><\/h3>\n<\/header>\n<div class=\"textbox__content\">\n\nCould we have this update all wrapped up by Monday January 23rd, 2026? We\u2019re meeting with some investors early next week and we\u2019d like the site to be fully up to date by then. Much appreciate your time\n\n<\/div>\n<\/div>\n<\/div>\n&nbsp;\n<div class=\"7.1-structure-of-routine-messages\">\n<p class=\"import-Normal\">This section is adapted from <a class=\"rId7\" href=\"https:\/\/pressbooks.senecapolytechnic.ca\/buscomm\/chapter\/8-1-information-shares-action-requests-and-replies\/\"><span class=\"import-Hyperlink\">Information Shares, Action Requests, and Replies<\/span><\/a> in <a href=\"https:\/\/pressbooks.senecapolytechnic.ca\/buscomm\/\">Communication@Work<\/a> Copyright \u00a9 2019 by Jordan Smith\u00a0licensed under a\u00a0<a class=\"rId9\" href=\"https:\/\/creativecommons.org\/licenses\/by\/4.0\/\"><span class=\"import-Hyperlink\">Creative Commons Attribution 4.0 International License<\/span><\/a>, except where otherwise noted.<\/p>\n\n<\/div>","rendered":"<div class=\"7.1-structure-of-routine-messages\">\n<p class=\"import-Normal\">Perhaps the simplest and most common routine message type is where the sender offers up information that helps the receiver. These may not be official memos, but they follow the same structure: opening, body, and closing.<\/p>\n<p class=\"import-Normal\">Managers, clients, and coworkers alike send and receive requests for information and action all day. Because these provide the recipient with direction on what to do, the information that comes back or action that results from such requests can only be as good as the instructions given. Such messages must therefore be well organized and clear about expectations, opening directly with a clearly stated general request unless you anticipate resistance to the request and proceeding with background and more detailed instruction, if necessary (see example below for parts of routine messages).<\/p>\n<h2>Opening<\/h2>\n<p>Describe the reason for the message. Main point should be included from the beginning of the message.<\/p>\n<div class=\"textbox textbox--examples\">\n<header class=\"textbox__header\">\n<h3 class=\"textbox__title\"><em>Example<\/em><\/h3>\n<\/header>\n<div class=\"textbox__content\">\n<p>Hello Mohammed: I hope you are having a wonderful week. Could you help update the website by adding the new hires to the Personnel page?<\/p>\n<\/div>\n<\/div>\n<h2>Body<\/h2>\n<p>Include the details of the message in an organized matter.<\/p>\n<div class=\"textbox textbox--examples\">\n<header class=\"textbox__header\">\n<h3 class=\"textbox__title\"><em>Example<\/em><\/h3>\n<\/header>\n<div class=\"textbox__content\">\n<p>We have hired three new associates in the past few weeks. With the content of the attached folder that contains their bios and hi-res pics, please do the following<\/p>\n<ul>\n<li>Proof of bios using Track Changes and send them to me.<\/li>\n<li>Post the proofed bios on the site. I would like to quickly read them and suggest further edits over the phone, if necessary, since time is of the essence here.<\/li>\n<li>Downsize the pics to 72dpi and crop them so that they are the same dimensions as the other portraits on that page before posting them along with the bios.<\/li>\n<\/ul>\n<\/div>\n<\/div>\n<h2>Close<\/h2>\n<p>Provide action and next steps related to the content.<\/p>\n<div class=\"textbox textbox--examples\">\n<header class=\"textbox__header\">\n<h3 class=\"textbox__title\"><em>Example<\/em><\/h3>\n<\/header>\n<div class=\"textbox__content\">\n<p>Could we have this update all wrapped up by Monday January 23rd, 2026? We\u2019re meeting with some investors early next week and we\u2019d like the site to be fully up to date by then. Much appreciate your time<\/p>\n<\/div>\n<\/div>\n<\/div>\n<p>&nbsp;<\/p>\n<div class=\"7.1-structure-of-routine-messages\">\n<p class=\"import-Normal\">This section is adapted from <a class=\"rId7\" href=\"https:\/\/pressbooks.senecapolytechnic.ca\/buscomm\/chapter\/8-1-information-shares-action-requests-and-replies\/\"><span class=\"import-Hyperlink\">Information Shares, Action Requests, and Replies<\/span><\/a> in <a href=\"https:\/\/pressbooks.senecapolytechnic.ca\/buscomm\/\">Communication@Work<\/a> Copyright \u00a9 2019 by Jordan Smith\u00a0licensed under a\u00a0<a class=\"rId9\" href=\"https:\/\/creativecommons.org\/licenses\/by\/4.0\/\"><span class=\"import-Hyperlink\">Creative Commons Attribution 4.0 International License<\/span><\/a>, except where otherwise noted.<\/p>\n<\/div>\n","protected":false},"author":1,"menu_order":9,"template":"","meta":{"pb_show_title":"","pb_short_title":"","pb_subtitle":"","pb_authors":[],"pb_section_license":""},"chapter-type":[],"contributor":[],"license":[],"class_list":["post-178","chapter","type-chapter","status-publish","hentry"],"part":177,"_links":{"self":[{"href":"https:\/\/libraryresources.nse.org.ng\/professionalandtechnicalcommunication\/wp-json\/pressbooks\/v2\/chapters\/178","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/libraryresources.nse.org.ng\/professionalandtechnicalcommunication\/wp-json\/pressbooks\/v2\/chapters"}],"about":[{"href":"https:\/\/libraryresources.nse.org.ng\/professionalandtechnicalcommunication\/wp-json\/wp\/v2\/types\/chapter"}],"author":[{"embeddable":true,"href":"https:\/\/libraryresources.nse.org.ng\/professionalandtechnicalcommunication\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":1,"href":"https:\/\/libraryresources.nse.org.ng\/professionalandtechnicalcommunication\/wp-json\/pressbooks\/v2\/chapters\/178\/revisions"}],"predecessor-version":[{"id":179,"href":"https:\/\/libraryresources.nse.org.ng\/professionalandtechnicalcommunication\/wp-json\/pressbooks\/v2\/chapters\/178\/revisions\/179"}],"part":[{"href":"https:\/\/libraryresources.nse.org.ng\/professionalandtechnicalcommunication\/wp-json\/pressbooks\/v2\/parts\/177"}],"metadata":[{"href":"https:\/\/libraryresources.nse.org.ng\/professionalandtechnicalcommunication\/wp-json\/pressbooks\/v2\/chapters\/178\/metadata\/"}],"wp:attachment":[{"href":"https:\/\/libraryresources.nse.org.ng\/professionalandtechnicalcommunication\/wp-json\/wp\/v2\/media?parent=178"}],"wp:term":[{"taxonomy":"chapter-type","embeddable":true,"href":"https:\/\/libraryresources.nse.org.ng\/professionalandtechnicalcommunication\/wp-json\/pressbooks\/v2\/chapter-type?post=178"},{"taxonomy":"contributor","embeddable":true,"href":"https:\/\/libraryresources.nse.org.ng\/professionalandtechnicalcommunication\/wp-json\/wp\/v2\/contributor?post=178"},{"taxonomy":"license","embeddable":true,"href":"https:\/\/libraryresources.nse.org.ng\/professionalandtechnicalcommunication\/wp-json\/wp\/v2\/license?post=178"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}