Although statements of policy appear in both handbooks and policies and procedures manuals, the topics covered in a policies and procedures manual are often more detailed and exhaustive. The subjects covered in an employee handbook are typically selective and the information provided is more general.
A handbook is sometimes referred to as a vade mecum (Latin, "go with me") or pocket reference. It may also be referred to as an enchiridion.
Certain policies are mandatory and must be included in your employee handbook. For example, California employers must have a written harassment, discrimination and retaliation prevention policy. Including these policies clarifies for employees their rights and obligations, and protects you from potential liability.
When creating an employee handbook, there are certain elements that must be included for it to be a legally binding contract between employer and employee. These include: Language stating that the agreement is mutually agreed upon by both parties. Clear definitions of expectations regarding job duties.
In short, employee handbooks are general and written for all employees. Policy manuals are more exhaustive and help supervisory employees understand and execute your organization's policies.
Starting with the basics, an employee handbook is a clear-cut document that outlines a company's policies and procedures. It also lays out any organizational expectations. It is not an employment agreement, so be sure to avoid using legal jargon.
How Is a Policy and Procedure Manual Different? Written policies and procedures are generally detailed step-by-step descriptions about how to perform company processes. The handbook, alternatively, should be simple and easy to read so that employees become familiar with your company.
Ten Policies Every Employer Should Have in its Handbook At-Will Employment. Must include “no contract” language. EEO/Anti-Harassment/Anti-Discrimination. Include. Time-Off. Jury Duty. FMLA. Eligibility Requirements. Attendance/Tardiness. Behavior/Conduct. Computer, Technology & Communication. Solicitations.
Policy Writing Guidance Keep it simple. Policies should be written in plain language – not legalese. Keep it general. Policies cannot contemplate all possible situations. Make it relevant. Check for accuracy and compliance. Ensure the policy can be enforced. Clearly state who does what. Less is more.