FirstHR

Company Policy: 8 Essential Policies Every Small Business Needs

What is a company policy and which does your small business need? 8 essential policies, the HR policy development process, and how to deliver them.

Nick Anisimov

Nick Anisimov

FirstHR Founder

Core HR•
•
22 min

Company Policy

8 essential policies every small business needs

My first employee dispute was about PTO. An employee took a Friday off, assumed it was paid, and was surprised when their paycheck was short. I assumed unpaid time off was the default since I had never said otherwise. We were both operating on assumptions because I had never written a PTO policy. It was a $200 problem that took three hours to resolve and damaged trust that took months to rebuild.

That was at 6 employees. By 12, I had a similar issue with every topic I had not documented: what counts as a sick day, whether personal devices can access company email, what happens if someone is consistently late. Each time, the answer was "we do not have a policy on that," followed by an awkward improvised decision that felt unfair to someone.

Company policies are not bureaucracy. They are answers to questions your employees will definitely ask, written down before the question creates a conflict. This guide covers what a company policy actually is, the 8 policies every small business needs, how to write them without a legal team, how to make sure employees actually read them, and the delivery-and-signature loop that turns a document into a defensible business practice. That loop (write the policy, deliver it during onboarding, collect an e-signature, store it in the employee's file, make it accessible in a portal) is exactly how FirstHR handles policy management for small and growing teams.

TL;DR
A company policy is a documented guideline that sets expectations for employee behavior and company procedures. Small businesses need 8: EEO, anti-harassment, attendance and PTO, at-will employment, technology use, health and safety, code of conduct, and social media. They protect you only once employees have read and signed them, so deliver them during onboarding and collect e-signatures.

What Is a Company Policy?

A company policy is a written document that defines a rule, standard, or expectation for how employees and the organization operate. It answers the question "what is our position on X?" where X is anything from time off to harassment to social media use.

Definition
Company Policy
A company policy is a formal, documented statement that establishes guidelines, rules, or standards governing employee behavior, organizational practices, or operational procedures. Policies serve three purposes: they set consistent expectations for all employees, they protect the company legally by documenting standards and signed acknowledgments, and they provide a reference for decision-making when situations arise. A policy differs from a procedure: the policy states the rule, the procedure explains how to follow it.

The practical distinction between a policy you need and one you do not: if two reasonable people could interpret a situation differently and reach different conclusions, you need a policy. "Can I work from home on Fridays?" is a policy question. "Is theft allowed?" is not (that is already covered by law). Policies fill the gaps between common sense and the specific expectations of your company.

The Policy-Onboarding Connection
Only 12% of employees strongly agree their organization does a great job of onboarding new hires (Gallup). A major contributor: new hires who do not receive clear policies during their first week, leading to confusion about expectations, inconsistent treatment, and preventable conflicts.

Why Company Policies Matter for Small Businesses

ReasonWithout PoliciesWith Policies
ConsistencyEach situation handled differently based on founder's mood or memorySame rules apply to everyone; decisions are predictable and defensible
Legal protectionNo documentation that standards were communicatedSigned acknowledgments prove the employee was informed of expectations
Onboarding clarityNew hires guess the rules through trial and errorNew hires read and sign policies on Day 1; expectations are explicit
Dispute resolutionFounder makes ad hoc decisions that feel arbitraryWritten policy provides the basis for fair, consistent resolution
ComplianceNo evidence that federally or state-required standards are metDocumented policies with acknowledgments satisfy audit requirements

For small businesses specifically, policies matter more per employee because there is no HR department to mediate disputes. When a conflict arises at a small company, the founder resolves it. A written policy gives the founder a defensible basis for the decision ("our PTO policy states that requests require 5 business days notice") instead of an improvised judgment that may seem unfair.

The cost of getting this wrong lands early. According to SHRM, up to 20% of employee turnover happens within the first 45 days on the job, which is exactly the window where a new hire is still guessing at rules nobody wrote down.

What worked for me
The policy that saved me the most grief was the simplest one: attendance. Before writing it, I had three different informal expectations for three different employees based on when I hired them and what I said in their interview (which I could not remember). After writing a clear attendance policy with defined working hours, a process for requesting time off, and what constitutes an unexcused absence, disputes about attendance dropped to zero. Not because people stopped having attendance issues, but because everyone knew the rule and I could enforce it consistently.
Still Using Spreadsheets for Onboarding?
Automate documents, training assignments, task management, and track onboarding progress in real time.
See How It Works

8 Essential Company Policies for Small Businesses

You do not need 40 policies at a small business. You need 8 that cover the situations most likely to create conflict, legal exposure, or confusion. These 8 policies address the gaps where assumptions diverge and disputes emerge.

Equal Employment OpportunityStates that you do not discriminate in hiring, promotion, or termination based on protected characteristics. The Equal Pay Act reaches you from the first employee; Title VII, the ADA, and GINA start at 15.
Anti-Harassment and Anti-DiscriminationDefines prohibited conduct, reporting procedures, and investigation process. New York and Illinois reach every employer regardless of company size.
Attendance and PTODefines work hours, time-off accrual, request procedures, and unexcused absence handling. Prevents the disputes that come from three employees holding three different understandings.
At-Will EmploymentClarifies that employment can be terminated by either party at any time (in at-will states). Protects against implied contract claims.
Acceptable Use (Technology)Covers use of company devices, email, internet, and software. Sets expectations for personal use, monitoring, and data security.
Health and SafetyOutlines workplace safety procedures, reporting requirements, and emergency protocols. The OSH Act general duty clause binds every employer regardless of size.
Code of ConductDefines expected behavior, ethical standards, and consequences for violations. Sets the tone for workplace culture from Day 1.
Social MediaAddresses employee conduct on social media regarding the company. Protects the brand while respecting employee rights under NLRA.

1. Equal Employment Opportunity (EEO)

States that the company does not discriminate based on race, color, religion, sex, national origin, age, disability, or genetic information. Title VII, the ADA, and GINA reach an employer with 15 or more employees for each working day in each of 20 or more calendar weeks in the current or preceding year, and the ADEA starts at 20.

Do not read those thresholds as permission to wait. The federal Equal Pay Act has no headcount floor at all, so equal pay for equal work applies from your first employee, and a written EEO policy is the cheapest evidence that the standard was in place all along.

2. Anti-Harassment and Anti-Discrimination

Defines what constitutes harassment (including sexual harassment), how to report it, and how reports are investigated. Even where no state mandates it, the policy is what demonstrates that the standard was communicated and a reporting route existed before anything went wrong.

State mandates land at very different sizes. California requires a written policy and interactive training at five or more employees, Connecticut at three, Maine at 15, and Delaware at 50 for training, while New York and Illinois reach every employer at any size.

3. Attendance and PTO

Covers expected working hours, how PTO is earned and used, how to request time off, and what constitutes an unexcused absence. This is the single most common source of employee disputes at small businesses because expectations vary wildly without documentation. Include your PTO accrual rate, the request process, blackout periods (if any), and what happens to unused PTO at termination (varies by state).

4. At-Will Employment

Clarifies that employment is at-will: either party can end the relationship at any time, for any legal reason, with or without notice. This policy is essential in at-will states (49 of 50, Montana being the exception after probationary period) because it prevents implied contract claims. Include it in the offer letter, the employee handbook, and as a standalone signed acknowledgment.

5. Acceptable Use (Technology)

Defines how company devices, email, internet, and software should be used. Covers whether personal use is permitted, whether the company monitors activity, data security expectations, and what happens to access when someone leaves. This policy becomes critical the moment an employee uses a personal device for work or accesses company data from home. Before you write the monitoring section, check the employee monitoring laws in your state, because notice and consent rules vary.

6. Health and Safety

Outlines workplace safety standards, hazard reporting, emergency procedures, and your commitment to OSHA compliance. The general duty clause at Section 5(a)(1) of the OSH Act requires every employer to furnish a place of employment free from recognized hazards that are causing or are likely to cause death or serious physical harm, with no headcount threshold anywhere in it.

Scope follows your operation. For an office-based small business the policy covers ergonomics, fire evacuation, where the first aid kit lives, and how to report an incident. For a business with physical operations it gets longer and more specific to the hazards of the trade.

7. Code of Conduct

Defines expected behavior, ethical standards, and professional conduct. Covers honesty, respect, confidentiality, conflicts of interest, and the consequences of violating the code. This policy sets the cultural baseline: "this is how we behave here." It is broader than specific operational policies and serves as the umbrella under which other policies sit.

8. Social Media

Addresses employee conduct on social media regarding the company, its products, its customers, and its employees. This is the policy most likely to be drafted too broadly and then be unenforceable.

The constraint is federal labor law. Section 7 of the NLRA protects concerted activities for collective bargaining or other mutual aid or protection, with no headcount floor and whether or not a union is involved, so a blanket ban on company-related posts will not hold. What the policy can do is set guidelines for representing the company, protecting confidential information, and separating personal opinion from official position.

Which Policies at Which Company Size

HeadcountEssential PoliciesAdd When Ready
1-5 employeesAt-will statement (in offer letter), anti-harassment (required in some states), basic code of conductWait on formal policies until you reach 5-8 employees unless state law requires earlier
5-15 employeesAll 8 essential policies above. California requires harassment prevention at 5+.Remote work policy if applicable, expense reimbursement, confidentiality/NDA
15-25 employeesAll essential + Title VII and ADA now apply. Review EEO policy with an attorney.Drug and alcohol policy, performance management policy, progressive discipline
25-50 employeesAll above + formalized handbook with annual review cycleData privacy, AI usage, whistleblower, leave policies beyond PTO (bereavement, jury duty)
50+ employeesFMLA now applies. ACA applies. Full policy manual with legal review.COBRA administration, mandatory benefit disclosures, workplace violence prevention

The employee count thresholds are not arbitrary. Federal and state laws activate at specific headcounts: 15 employees triggers Title VII, the ADA, and GINA; 20 triggers COBRA and the ADEA; 50 triggers FMLA and the ACA applicable large employer rules. Each threshold adds compliance obligations that your policies must address.

Crossing 50 changes your handbook directly rather than just your obligations. Under 29 CFR 825.300(a)(3), a covered employer with eligible employees must include the FMLA general notice in its employee handbook or other written guidance on benefits and leave rights, where such written materials exist, or hand a copy to each new employee at hiring.

The HR Policy Development Process

Knowing which policies you need is one thing; building them is another. HR policy development is the process of going from no documented rules to a working set of policies that people have actually read and that hold up when tested. Most small businesses skip straight to drafting, which is why they end up with policies copied from a company ten times their size, never reviewed by anyone, and unsigned by half the team. The seven phases below are the sequence that avoids that.

1. Needs assessmentOwner or whoever handles HR
Identify the gaps before writing anything. List the questions employees have actually asked, the situations you improvised an answer for, and the legal thresholds your headcount has crossed. Each gap is a candidate policy. Most small businesses discover they need 6-8, not 40.
2. Prioritize by riskOwner
Rank candidates by legal exposure and how often the situation comes up. Legally required policies (anti-harassment, EEO, safety) come first regardless of frequency. High-frequency operational policies (attendance, PTO, technology use) come next. Everything else waits.
3. Draft in plain languageOwner or HR
Write each policy on one page: purpose, scope, the rule, the procedure, the consequences. Use existing templates as a starting structure, but rewrite the specifics for how your company actually operates. A copied enterprise policy describes a company you do not run.
4. Gather inputManagers and affected employees
Have the people who will live under the policy read the draft. They catch the practical problems (a PTO notice period that breaks during busy season, a device policy that ignores how the team actually works) before the policy is live and hard to walk back.
5. Legal review where it countsEmployment attorney
Not every policy needs a lawyer. Compliance-driven ones do: anti-harassment, EEO, at-will language, leave, and anything state-specific. Operational policies like expense reimbursement can wait for your next scheduled legal check-in.
6. Communicate and collect signaturesOwner or HR
Roll the policy out through onboarding and a company-wide announcement, then collect a signed acknowledgment from every employee. An unsigned policy is a document, not a protection. This is the step most small businesses skip.
7. Review on a scheduleOwner or HR
Set an annual review date and stick to it, plus triggered reviews when laws change, headcount crosses a threshold, or an incident exposes a gap. Policy development is a cycle, not a one-time project.

Two phases carry most of the weight. The needs assessment determines whether you end up with the 8 policies your business actually needs or a 40-policy manual nobody reads; the honest version of this step is simply listing every question an employee has asked that you had to improvise an answer to. And communication with signed acknowledgments is what converts a document into protection, since an unsigned policy proves nothing about what the employee was told. Everything between those two is craft; those two are the difference between a policy program that works and one that exists.

The whole process is a cycle, not a project with an end date. A policy set built once and never revisited drifts out of alignment with the law and with how your company actually operates, usually within two years. Set the annual review date when you finish the first round, and treat headcount thresholds and law changes as triggers that pull the review forward.

The worksheet below is the needs assessment written down: the log of questions you had to improvise an answer to, the headcount thresholds you have crossed, the candidate policies ranked by exposure, and the ones you are deliberately not writing this round.

Policy Needs Assessment and Priority List
POLICY NEEDS ASSESSMENT AND PRIORITY LIST

[Company Name]
Completed by: Date:
Headcount today:
States we employ people in:
Section 1 is a log, not a memory test. Keep it open for a week or two before
ranking anything, and write the questions down as they arrive.
1. QUESTIONS WE HAD TO IMPROVISE AN ANSWER TO

Date Who asked The question What we said Written down
2. THRESHOLDS OUR HEADCOUNT HAS CROSSED

15 employees: [ ] Not yet [ ] Crossed on
Policies to review at this point:
20 employees: [ ] Not yet [ ] Crossed on
Policies to review at this point:
50 employees: [ ] Not yet [ ] Crossed on
Policies to review at this point:
State or local rules that reach us at a lower count:
3. CANDIDATE POLICIES

One line per candidate. Rank by exposure and by how often the situation comes
up, not by how easy the policy is to write.
Policy Why it is on the list Required Risk Owner Draft by
Risk key: H for legal exposure or money at stake, M for a recurring dispute,
L for housekeeping.
4. NOT NOW

Writing this down matters as much as the list above, because it stops the same
suggestion coming back every month.
Policy: Deferred because:
Revisit at:
Policy: Deferred because:
Revisit at:
Policy: Deferred because:
Revisit at:
5. WHAT WE ARE WRITING THIS ROUND

Number of policies to write now:
Who drafts them:
Which ones a lawyer sees before release:
Who reads the drafts before they go live:
All drafts done by:
Every employee signed by:
Annual review date set for:
Approved by: Date:
Note: general information, not legal advice. Confirm which policies your state
and local law requires at your headcount.

How to Write a Company Policy

1
Define the purpose
State the problem the policy solves in one sentence. 'This policy establishes guidelines for requesting and using paid time off.' If you cannot state the purpose in one sentence, the policy is too broad.
2
Set the scope
Who does this policy apply to? All employees, only full-time, only specific departments, or including contractors? Be explicit. 'This policy applies to all full-time and part-time employees. Independent contractors are not covered.'
3
Write the policy statement
State the actual rule in plain language. Avoid legal jargon that employees will not read. 'Full-time employees earn 15 days of PTO per year, accruing at 1.25 days per month' is better than a paragraph of legalese.
4
Describe the procedure
Explain how to comply: how to submit a request, who approves it, what the timeline is. 'Submit PTO requests through the employee portal at least 5 business days in advance. Your manager will respond within 2 business days.'
5
Define consequences
What happens if someone violates the policy? Be proportionate and specific. 'Violations may result in disciplinary action, up to and including termination, depending on severity.' For compliance-related policies, state that violations may also result in legal consequences.

Keep each policy to one page. Two pages maximum. The longer the policy, the less likely employees are to read it. If a topic requires more than two pages, split it into a policy (the rule) and a separate procedure document (the detailed steps).

Policies and Procedures: Where They Split

A company policy states the rule and the procedure states the steps, and a small business needs both written down only where the steps are not obvious. The attendance policy says the day starts at nine. The procedure says how to request a late start, who approves it, and how much notice counts.

At 15 people, most of ours lived in one document with the procedure at the bottom, and that is usually the right shape at this size. Split them apart when the steps change more often than the rule does, or when a manager runs the steps and everyone else only needs to know the rule.

The Plain Language Test
After writing a policy, read it to someone who was not involved in drafting it and ask them to explain what the policy requires. If they cannot summarize it accurately in 30 seconds, rewrite it. Policies written in clear, simple language get read. Policies written in legal jargon get skipped, signed unread, and ignored until a dispute arises.
Companies Using FirstHR Onboard 3x Faster
Join hundreds of small businesses who transformed their new hire experience.
See It in Action

Making Sure Employees Actually Read Your Policies

A policy that sits in a Google Drive folder nobody opens does not protect your business. The policy only matters when employees have received it, read it, and signed an acknowledgment confirming they understood it. That acknowledgment is the document you produce when a dispute arises: "The employee was informed of this policy on their start date and signed an acknowledgment. Here is the signed copy."

StepWhat HappensWhat It Protects
1. Include in onboardingNew hires receive all policies as a required onboarding task on Day 1 or during preboardingEnsures every employee receives policies from the start, not months later
2. Collect e-signaturesEach employee signs an electronic acknowledgment for every policyCreates a defensible record that the employee received and read the policy
3. Store in employee fileSigned acknowledgments are stored in the employee's personnel recordProvides retrieval-ready documentation for audits, disputes, or legal proceedings
4. Make accessible via portalAll current policies are available in an employee self-service portalEmployees can reference policies anytime without asking the founder
5. Re-sign on updatesWhen a policy changes, re-distribute and collect new signaturesEnsures employees are always acknowledged on the current version

Running that loop means knowing, at any moment, which version of which policy each person has signed. The workbook below keeps the register of policies and versions on one tab and the per-employee acknowledgments on another, so the answer to that question is a filter rather than a search through email.

Policy Register and Acknowledgment Tracker
ABCDEFGHIJK
1PolicyVersionEffective DateOwnerApplies ToLast ReviewedNext Review DueLawyer Review NeededLawyer Reviewed OnWhere Employees Find ItStatus
2Equal employment opportunity1.001/12/2026N. OwnerAll employees01/12/202601/11/2027Yes01/08/2026Handbook and portalCurrent
3Attendance and time off2.103/02/2026N. OwnerAll employees03/02/202603/01/2027NoHandbook and portalCurrent, re-signatures in progress
4Acceptable use of technology1.001/12/2026N. OwnerEmployees and contractors01/12/202601/11/2027NoPortalCurrent
5
6
7
8

This five-step loop (deliver, sign, store, access, re-sign) is the difference between policies that protect your business and policies that exist on paper but carry no legal weight. It also puts the manager in the loop, which matters: according to Gallup, employees are 3.4 times as likely to call their onboarding successful when the manager takes an active role in it.

What worked for me
Before building the delivery loop into our onboarding process, I had no idea which policies each employee had actually signed. When a dispute arose about our PTO policy, I could not prove the employee had received it. After implementing onboarding-delivered policies with e-signatures stored in each employee's file, I never faced that problem again. The 10 minutes it takes to set up policy delivery in onboarding saves hours of uncertainty during the one dispute that inevitably happens.

Updating Company Policies

Policies are not static documents. Laws change, your company grows, and new situations arise that existing policies do not cover. A structured update process prevents your policies from becoming outdated and legally insufficient.

When to UpdateWhat Triggers ItWhat to Do
Annual reviewCalendar reminder (January is common)Read every policy. Confirm it still reflects current law and practice. Update dates and version numbers.
Headcount thresholdCrossing 15, 20, or 50 employeesReview which federal and state laws now apply and update or add policies accordingly.
Law changeFederal or state employment law updateUpdate affected policies within 30 days. Re-distribute and collect new signatures.
IncidentA situation arises that no current policy coversDraft a new policy addressing the gap. Do not retroactively apply it to the incident that prompted it.
State expansionHiring in a new stateReview that state's employment law requirements and add or modify policies as needed.

When you update a policy, the update is meaningless until employees acknowledge the new version. Re-distribute the updated policy, collect new e-signatures, and store the new acknowledgments alongside the original versions. Version history matters: you need to know which version each employee signed and when.

Headcount is the trigger people forget, because it moves without anyone filing paperwork. The EEOC publishes a small business page that walks through which of the laws it enforces apply at which size, and it is worth rereading the January you notice the team has grown.

Common Company Policy Mistakes

MistakeWhy It HappensThe Fix
No written policies at allSeems unnecessary at 5-10 employeesWrite the 8 essential policies when you reach 5-8 employees. One afternoon prevents years of disputes.
Copying enterprise policy manualsFound a 50-page template online and adopted it wholesaleWrite policies for your actual company. A small business needs 8 policies, not 40.
Policies exist but nobody has signed themDelivered verbally or shared as 'optional reading'Collect an e-signature for every policy from every employee. No signature = no legal protection.
Policies are inaccessible after onboardingShared once during orientation, then never referenced againStore in a self-service portal where employees can access them anytime.
Never updating policiesSet-it-and-forget-it mentalityReview annually. Update when laws change or headcount thresholds are crossed.
Overly complex languageWritten by or for lawyers, not employeesWrite at a 7th-grade reading level. If employees do not understand it, the policy does not work.
Inconsistent enforcementPolicy exists but founder ignores it for some employeesEnforce every policy consistently. Selective enforcement creates legal liability and destroys trust.

The most damaging mistake is inconsistent enforcement. If your attendance policy says unexcused absences result in a written warning, but you only enforce it for some employees, you have created evidence of discriminatory treatment. Every policy you write must be enforced the same way for everyone. If a policy is too strict to enforce consistently, rewrite it to a standard you can actually maintain.

Key Takeaways
A company policy is a written guideline that sets expectations for employee behavior and company procedures. It protects the business only if employees have signed an acknowledgment.
Small businesses need 8 essential policies: EEO, anti-harassment, attendance/PTO, at-will employment, technology use, health and safety, code of conduct, and social media.
Keep each policy to one page, written in plain language. If employees cannot summarize it in 30 seconds, rewrite it.
Deliver all policies during onboarding, collect e-signatures, store signed copies in each employee's file, and make current versions accessible via a self-service portal.
Review all policies annually. Update immediately when laws change, headcount thresholds are crossed, or incidents reveal gaps.
Enforce every policy consistently for every employee. Selective enforcement creates legal liability and destroys team trust.

Frequently Asked Questions

What is the HR policy development process?

HR policy development is the process of identifying, drafting, approving, and maintaining the policies a company operates under. It runs in seven phases: (1) needs assessment, listing the gaps where employees have asked questions you had to improvise answers to, plus any legal thresholds your headcount has crossed; (2) prioritization by risk, putting legally required policies like anti-harassment and EEO first and high-frequency operational ones like attendance and PTO next; (3) drafting each policy in plain language on a single page covering purpose, scope, rule, procedure, and consequences; (4) gathering input from the managers and employees who will live under the policy, since they catch practical problems before it goes live; (5) legal review for compliance-driven policies specifically, not for every operational one; (6) communicating the policy through onboarding and collecting signed acknowledgments from every employee, which is what turns a document into legal protection; and (7) reviewing on an annual schedule with triggered reviews when laws change or headcount crosses a threshold. The process is a cycle rather than a one-time project.

What is a company policy?

A company policy is a documented set of guidelines that defines expected behavior, procedures, or standards for employees and the organization. Policies cover topics like attendance, harassment, technology use, PTO, and workplace safety. They establish consistent rules that apply to everyone, protect the company legally, and set clear expectations for employees from Day 1.

What company policies are required by law?

Federal law mandates no single list of written policies, but several rules push you toward one. The OSH Act general duty clause obliges every employer, at any size, to furnish a workplace free from recognized hazards. Title VII, the ADA and GINA attach at 15 or more employees, the ADEA at 20, and a written EEO policy is the practical way to show the standard was communicated. At 50 or more employees, an FMLA-covered employer with eligible staff must carry the FMLA general notice inside its handbook or other written benefits guidance, where such materials exist. States add more: California requires a written harassment prevention policy and training at five or more employees, and 18 states plus the District of Columbia required paid sick leave from covered private employers as of December 2024.

How many policies does a small business need?

Eight covers most small businesses: equal employment opportunity, anti-harassment, attendance and PTO, at-will employment, acceptable technology use, health and safety, code of conduct, and social media. Add data privacy, remote work, and expense reimbursement as the business grows into needing them. Past roughly 15 policies the set stops working, because the volume itself is what stops people reading any of it. The right test is not how many policies you have but how many questions your team keeps asking that none of them answer.

What is the difference between a policy and a procedure?

A policy states what the company expects or requires. A procedure explains how to fulfill that expectation. For example, the PTO policy says employees earn 15 days per year. The PTO procedure says to submit a request through the employee portal at least 5 business days in advance. Policies set the rule. Procedures explain the steps to follow the rule. Small businesses often combine both in one document for simplicity.

How do you write a company policy?

Follow five steps: define the purpose (what problem does this policy solve), state the scope (who does it apply to), write the policy statement (the actual rule, in plain language), describe the procedure (how to comply), and define consequences (what happens if violated). Keep it under one page. Use simple language. Have an employment attorney review any policy that involves legal compliance. Share the policy during onboarding and collect a signed acknowledgment.

How do you make sure employees read company policies?

Three practices: deliver policies during onboarding as a required task (not optional reading), collect signed acknowledgments for every policy (electronic signatures count), and make policies accessible in a self-service portal so employees can reference them anytime. The signed acknowledgment is the critical step: it creates documentation that the employee received and read the policy, which protects the company if a dispute arises.

How often should company policies be updated?

Review all policies annually, even where nothing has changed. Update immediately when a state or federal law changes, when headcount crosses a statutory threshold, or when an incident exposes a gap. The thresholds worth watching are 15, where Title VII, the ADA and GINA attach, 20, where COBRA and the ADEA attach, and 50, where FMLA and the ACA applicable large employer rules attach. After any update, re-distribute the policy and collect fresh signed acknowledgments rather than relying on the old ones. Keep version history, because the question that matters in a dispute is which version that specific employee signed and on what date.

Do I need a lawyer to write company policies?

You do not need a lawyer to draft every policy, but you should have an employment attorney review policies that involve legal compliance: anti-harassment, anti-discrimination, at-will employment, FMLA leave, and any state-specific requirements. For operational policies like PTO, attendance, technology use, and social media, you can write them yourself using established templates and have them reviewed during your next legal consultation.

Ready to transform your onboarding?

7-day free trial No credit card required
Start Your Free Trial