| Usually, the policies and procedures are separated in | | | | thus they must never include information that can |
| the policy manual template as well as in the manual | | | | easily be out of date. Acronyms should also be |
| itself. Policies should be written in clear and simple | | | | avoided and step-by-step instructions for procedures |
| language, and they should directly state the rule. | | | | must be present. Highly technical words should also |
| They should express who the authority is and they | | | | be avoided so as not to mislead the new employees. |
| must be consistent and logical. | | | | For the design and layout, the document should have |
| Procedures, on the other hand, are developed with | | | | a white background for greater visibility. Presentation |
| the customers in mind. They should benefit the | | | | must also be highly structured so a user can |
| customers of the company. They should be | | | | immediately locate the sections he would want to |
| understandable, and must be followed through easily | | | | read. Here comes the use of your outlines so it can |
| by readers. They should also offer options rather | | | | easily be modified. Use labels and headings also to |
| than restrictions. | | | | introduce your key points, and even the margins |
| When you write a policy manual template and the | | | | should be consistent throughout the document. If |
| manual itself, make sure that it is concise. If you can | | | | you want certain styles to be applied on your |
| express the rules and procedures in fewer words, | | | | document, use formal templates that are found in |
| the better. They must also be realistic and factual, | | | | M.S. Word or Mac. |