A PEO deal can look clean on paper until the first hard employee issue hits. A manager approves leave that conflicts with state rules. Payroll follows one cutoff, benefits enrollment follows another, and the handbook promises something neither the employer nor the PEO administers. By the time someone asks who owns the fix, HR is already cleaning up the gap.
That is why the handbook deserves attention early, not after implementation. It sets the rules employees read, gives managers a script they can follow, and documents where the employer keeps control inside a co-employment arrangement. I have seen handbook language settle disputes with a PEO before they turned into billing fights, and I have seen vague language create them.
This guide uses a 10-section checklist in priority order. It focuses on the policies that carry the most operational risk first, then adds the drafting details that matter in practice, including state-by-state friction points, enrollment timing, complaint channels, and remote work location issues. It also calls out places where handbook language gives employers room to negotiate service boundaries, approval workflows, and escalation paths with a PEO.
The highest-risk sections usually involve termination, pay, leave, benefits, and complaint procedures. If those are loosely drafted, the company invites inconsistent manager decisions, payroll errors, and preventable disputes over wrongful termination claims. A clear employee termination process and documentation workflow helps close one of the most common gaps between handbook promises and day-to-day practice.
Federal and state rules also change what a "basic" handbook needs to cover. Some policies become necessary once headcount reaches a legal threshold. Others need state-specific carveouts even for small employers. The goal is not a longer document. The goal is a handbook that matches how the company operates, reflects the PEO relationship accurately, and gives leadership fewer surprises when a real issue lands.
Table of Contents
- 1. At-Will Employment and Termination Procedures
- 2. Compensation, Pay Scales, and Salary Review Process
- 3. Paid Time Off and Leave Policies
- 4. Benefits Program Eligibility and Enrollment
- 5. Code of Conduct and Workplace Expectations
- 6. Health and Safety, Workplace Accommodations, and ADA Compliance
- 7. Anti-Discrimination, Harassment, and Complaint Resolution Procedures
- 8. Remote Work and Flexible Work Arrangements Policy
- 9. Conflict of Interest and Confidentiality Policy
- 10. Conflict Policy State-Specific Guidance and Sample Clauses
- 10-Item Employee Handbook Policy Comparison
- Next Steps Draft, Review, and Negotiate
1. At-Will Employment and Termination Procedures
A manager wants to terminate an employee on Friday. HR says the employee may have raised a leave issue two weeks earlier. The PEO says it will process the separation once the company confirms the decision. If the handbook is vague on who decides, what steps come first, and how final pay is handled by work state, that routine termination can turn into a dispute fast.
This section should do three things well. State that employment is at-will where permitted by law. Reserve the right to skip progressive discipline. Make clear that the company, not the PEO, decides hiring, discipline, and termination unless the service agreement says something different.
That last point causes more friction than many employers expect. In PEO deals, I look for two documents to match word-for-word on authority. The handbook should identify the employer as the decision-maker. The PEO agreement should say the PEO administers payroll, benefits, and notices after receiving approved instructions. If those documents conflict, managers hesitate, terminations get delayed, and the record gets messy.
A practical at-will and termination section usually covers resignation notice, discharge, layoffs, return of company property, final wage timing, benefit continuation notices, and whether unused PTO is paid out under company policy or state law. Keep the promises narrow. Final pay timing and payout rules vary by state, and overpromising in the handbook creates avoidable problems.
The drafting trade-off is simple. Employees need a fair explanation of process, but the company should not write itself into a rigid script. A sentence that says the company "will" use progressive discipline in every case is harder to defend than language stating the company may use coaching, warnings, suspension, or immediate termination based on the circumstances and applicable law.
What works in practice
Use the handbook to set expectations, not to recreate the internal termination checklist. Internally, the company should still require manager documentation, HR review, a check for protected activity or leave overlap, payroll instructions, and benefit notice coordination. The handbook only needs enough detail to stay consistent with the company's actual employee termination process and broader wage-and-hour compliance procedures.
A multistate employer might write that final wages will be paid within the timeframe required by the employee's work state, not the manager's office location. That single clarification prevents common errors in remote teams. A second useful sentence states that no supervisor can alter at-will status or promise severance except through a written agreement signed by an authorized company officer.
Practical rule: Name the termination decision-maker in the handbook, then make sure the PEO contract says the same thing.
Clear records matter. If a dispute later turns into allegations involving wrongful termination claims, inconsistent handbook language, undocumented exceptions, and loose manager emails make defense much harder.
2. Compensation, Pay Scales, and Salary Review Process
Pay language should be boring on purpose. The best sections define exempt and non-exempt classifications, pay frequency, overtime rules for eligible employees, bonus and commission timing, who approves compensation changes, and when reviews happen. Companies evaluating what should be included in an employee handbook often underrate this section, then find out too late that payroll processing and compensation authority were never clearly separated.
A manufacturing employer might spell out that production roles are non-exempt, paid hourly, and eligible for overtime under applicable wage-and-hour law. A SaaS business might explain that sales commissions are earned only under the written commission plan and paid after the triggering conditions in that plan are met. Both examples reduce the risk of managers making side promises.
What works in practice
The strongest handbook language ties review cycles to process, not to guaranteed outcomes. For example, annual salary reviews may occur in the first quarter, but increases remain discretionary and subject to company performance, market conditions, and individual results. That protects the company from a handbook sentence turning into an entitlement argument.
A second point matters in PEO arrangements. The employer should approve pay rates, promotions, bonuses, and commission plans. The PEO should process payroll based on authorized inputs. If that split isn't written down, finance teams end up chasing avoidable errors, especially when raises are submitted close to payroll cutoff.
- Define compensable time clearly: Training, required meetings, travel between job sites, and on-call time often create the biggest disputes.
- Separate policy from plan documents: Keep the handbook high level, then attach detailed commission plans or incentive memos outside the handbook.
- Tie approvals to roles: State that only designated leaders or HR may authorize wage or salary changes.
For teams using a co-employment model, this section should also line up with wage tracking and overtime administration. A mismatch between policy and payroll setup is one of the fastest ways to create avoidable wage and hour compliance problems.
3. Paid Time Off and Leave Policies
A leave policy usually looks fine until an employee in California asks about sick time carryover, a manager in Illinois approves unpaid time off outside policy, and payroll follows the PEO accrual report instead of the handbook. That is when weak drafting turns into a real operating problem.
This section should answer five questions without forcing employees to guess: what time off is available, how it accrues or whether it is frontloaded, who approves it, how it interacts with protected leave, and what happens at separation. If the PEO's HRIS is the system of record for balances, say that plainly. If HR keeps a manual tracker for a carve-out leave category, say that too. I have seen more disputes come from inconsistent tracking rules than from the accrual formula itself.
State law drives the hardest choices. A single PTO bank is easier to administer, but separate vacation and sick leave buckets can be the safer option in states where payout, carryover, use caps, or notice rules differ. Multi-state employers should keep the core policy in the handbook and use state addenda for sick leave, paid family and medical leave, school leave, voting leave, jury duty, and final pay treatment. That structure keeps the main handbook readable while giving HR room to update local rules without reopening the entire document.
For employers covered by the FMLA, the handbook needs a usable FMLA policy, not a vague summary. Include eligibility rules, the reasons leave may be taken, the company's 12-month measuring method, employee notice expectations, fitness-for-duty rules if used, benefits continuation, and how PTO runs concurrently with FMLA where the law permits. The policy should also tell employees who handles requests and certifications. In a PEO arrangement, that point matters because employees often assume the PEO approves leave when the employer still controls many leave decisions.
A practical policy might read like this in operation. A 200-person employer allows accrued PTO to run concurrently with approved FMLA leave, applies state paid sick leave first where required, and routes all medical certifications to HR, not to line managers. A smaller employer with a richer parental leave benefit may place that benefit in a separate policy so the handbook can state eligibility and coordination rules without turning a discretionary program into a permanent promise.
Clear instructions reduce manager error.
Spell out bereavement leave, jury duty, voting time, military leave, and any company parental or caregiver leave with enough detail to stop ad hoc exceptions. If approval authority sits with HR or a designated executive, name the role. If documentation may be required, say when and for which leave types. Managers should never be left to improvise.
PEO contracts affect this section more than many employers expect. The handbook should match the service model for leave intake, payroll coding, benefits continuation, and recordkeeping. Employers that use a co-employment model often pair leave administration with broader benefits support, and that setup should align with the PEO benefits administration model. If the PEO administers statutory leave tracking but the employer approves schedule changes and return-to-work arrangements, write that split down. It saves time during claims, audits, and employee complaints.
One more drafting point gets missed. Avoid blanket statements such as “unused PTO will be paid out upon termination” unless that is true in every state where you operate and in every separation scenario. I usually write payout language to track applicable state law and the employer's written policy by category of leave. That gives the company room to handle vacation payout rules correctly without accidentally extending payout rights to sick leave where none exist.
Retirement and health benefit coordination can also affect leave design, especially for longer absences and reinstatement rules. If you are reviewing handbook language alongside total rewards, it helps to find 401(k) plans for small businesses and compare how leave periods affect eligibility, employer contributions, and re-enrollment timing.
Employees do not need a long legal explanation. They need a policy they can follow on a stressful day, and a process your HR team, managers, payroll staff, and PEO can apply the same way every time.
4. Benefits Program Eligibility and Enrollment
Benefits language must match the plan setup the PEO administers. That sounds obvious, but often handbook promises and carrier rules diverge. The handbook should state who's eligible, any waiting period, the open enrollment window, the process for qualifying life events, and the employer contribution structure in plain terms.
A 180-person manufacturer might say full-time employees working the required weekly hours become eligible after a stated waiting period and may elect medical, dental, vision, life, and disability coverage through the enrollment portal. A retail company with seasonal staffing might use different eligibility language for variable-hour employees, but the rule must still match the PEO's benefit administration settings.
Where PEO friction usually appears
The enrollment process needs names and deadlines, not generalities. Employees should know when they'll receive the election notice, where they enroll, when coverage becomes effective, and what happens if they miss the deadline. If COBRA or state continuation obligations apply, the handbook should reference the formal notices without trying to restate every detail.
This is also a negotiation section, not just an HR section. Existing handbook content often misses the contract side of PEO administration. That gap matters because handbook policies should align with the PEO agreement's liability clauses, exit terms, and fee mechanics. Unclear contract language creates costly surprises for many buyers, as discussed in this handbook content gap analysis.
- Write the contribution method clearly: If the employer pays a fixed dollar amount, say that. If it pays a percentage, confirm how increases are handled.
- Define life event timing: Employees need to know how quickly marriage, birth, adoption, or loss of other coverage must be reported.
- Match the service agreement: If the PEO sponsors the plan, the handbook shouldn't imply the employer controls every enrollment exception.
Companies comparing co-employment options should also understand the practical meaning of PEO benefits before locking handbook language. For retirement planning language that sits alongside health benefits, it's also useful to review how employers find 401(k) plans for small businesses.
5. Code of Conduct and Workplace Expectations
The conduct section is where companies either create an enforceable standard or publish a culture statement with no operational value. The stronger approach is simple. Define attendance, professionalism, workplace behavior, use of company systems, social media limits, conflicts with safety rules, and the range of disciplinary responses. Then make sure managers can apply it consistently.
Objective rules work better than broad moral language. A distribution business might track unexcused absences in a rolling period and state what level of attendance issues triggers verbal or written discipline. A tech company might prohibit disclosure of confidential code, customer data, or internal product information on personal accounts. A corporate office might define respectful conduct and require cooperation in investigations.
Draft for consistency, not theatrics
The most important drafting choice is restraint. Policies that are too broad can interfere with protected activity, especially around wages, working conditions, or concerted complaints. Conduct language should target business risks without banning lawful discussion.
A conduct policy should tell a manager what to document on a bad Tuesday, not just what values belong on the careers page.
Good sections also include anti-retaliation wording and a short explanation of the investigation process. Employees should know where to report concerns, who may review them, and that discipline can range from coaching to termination based on severity and repeat behavior.
A final drafting note matters for distribution. If the handbook is delivered digitally, version control becomes part of enforcement. Digital handbook workflows with acknowledgment and training are often easier to defend than paper files, especially when managers need to prove employees received the current rule set, as outlined in this employee handbook best practices paper.
6. Health and Safety, Workplace Accommodations, and ADA Compliance
Safety language should be specific enough that supervisors know what to do after an incident. Report the injury. Get medical attention. Preserve the scene if needed. Notify HR or safety. Start the workers' compensation process. General statements about valuing safety don't help much when someone slips on a warehouse floor or reports a repetitive strain problem.
The accommodation piece needs equal attention. A handbook should tell employees how to request an accommodation, who handles the request, and that the company will engage in an interactive process. It should also explain that accommodations may involve schedule changes, equipment, reassignment of marginal duties, leave, or other adjustments depending on the situation.
The process matters more than the promise
A professional services firm might allow an employee or provider to request accommodation verbally or in writing through HR. A manufacturing employer might offer ergonomic review for employees with back, wrist, or workstation concerns. A warehouse employer might explain how light-duty review works after a work-related restriction.
What doesn't work is silence on ownership. In a PEO relationship, the employer usually controls the workplace and bears the practical burden of accommodation decisions, even if the PEO provides templates or guidance. The handbook should reflect that operational reality.
- Use one intake path: HR, not line managers alone, should receive and log accommodation requests.
- Document alternatives: If the requested option won't work, the file should show what was considered instead.
- Coordinate with safety reporting: Injury reporting, workers' comp, and accommodation review often overlap.
For employers that need a practical baseline, safety rules and reporting workflows should align with applicable OSHA requirements for employers. The best handbooks don't treat safety and accommodation as separate silos because, in actual operations, they rarely are.
7. Anti-Discrimination, Harassment, and Complaint Resolution Procedures
A complaint policy gets tested on the worst day, not the day the handbook is approved. An employee reports that a supervisor has been making comments about her pregnancy. The supervisor also approves schedules and time off. If the handbook tells her to report concerns only to her manager, the policy fails at the exact point it is supposed to work.
The handbook should prohibit discrimination, harassment, and retaliation in plain language, using protected categories that match the laws that apply to the workforce. Federal thresholds matter, but handbook drafting should not stop there. State and local law often cover smaller employers, add protected categories, or impose specific policy and training rules. In a PEO arrangement, this is one of the first places I check for gaps, because the PEO template may be legally serviceable at a high level while still missing state-specific wording your workforce needs.
Use a reporting structure that works in real operations
Employees need more than one way to report a concern. A standard approach is HR, a second management contact, and a third option such as a hotline, inbox, or named executive contact. That is not legal decoration. It solves a common failure point when the manager, local lead, or owner is the subject of the complaint.
Concrete examples help here. A tech company may list unwelcome touching, repeated requests for dates, sexual jokes, or displaying explicit material. A plant or warehouse may need examples tied to racial slurs, mocking an accent, exclusion based on national origin, or targeting a religious practice. A customer-facing business should also state that harassment by clients, vendors, or contractors must be reported and will be addressed.
The complaint procedure should say who receives reports, what happens after intake, and how confidentiality is handled. Do not promise absolute confidentiality. Promise that information will be shared only with those who need it to investigate and respond. Do not promise every matter will be closed within a fixed number of days either. A better commitment is prompt review, appropriate interim steps, a documented investigation, and follow-up when the review is complete.
Employees should never have only one person to tell.
This section is also a negotiation point with the PEO. Some PEOs offer investigator access, hotline support, or template workflows. Some push all intake back to the client. Get clear on that before the handbook is finalized. If the employer is expected to receive complaints first, the handbook should name the internal role that owns intake and escalation. If the PEO must be notified for certain categories, such as claims involving a manager, wage issues raised with discrimination allegations, or threats of litigation, build that escalation rule into the internal procedure rather than burying it in the service agreement.
A useful checklist for this section includes four parts: prohibited conduct, reporting paths, investigation process, and anti-retaliation protection. If any one of those is vague, employees lose confidence in the process and managers improvise. Improvisation is where risk usually starts.
For multi-state employers, this policy often needs a core rule plus state supplements. California, New York, Illinois, and other jurisdictions may require specific language, training references, or broader protected categories than federal law alone. The cleanest drafting approach is to keep the main handbook readable, then attach state-specific addenda where required. That structure also gives the employer more control in PEO negotiations, because it avoids rewriting the entire handbook every time one state rule changes.
8. Remote Work and Flexible Work Arrangements Policy
Remote work policies used to be a convenience section. For multi-state employers, they're now a compliance section. The handbook should state who may work remotely or on a hybrid schedule, who approves it, where the employee may work, what equipment is provided, how expenses are handled, and whether the arrangement can be changed or revoked.
A useful example is a company that approves remote work only in states where it has payroll and employment compliance support in place. Another is a hybrid policy that requires in-office attendance for onboarding, training, or client-facing work. The key is to tie flexibility to business needs and location controls, not vague manager discretion.
Remote work policy needs location logic
This becomes more important in PEO environments because state and local rules don't follow headquarters. They follow where employees work. In multi-state settings, handbook design often needs a modular structure that maps policies to employee location rather than a single static PDF. Thomson Reuters notes that multi-state employers should use a state-specific compliance matrix and modular access logic for local rules instead of relying on one uniform handbook, as described in this handbook drafting guidance.
A marketing agency, for example, might allow full remote work only for employees based in approved payroll states, while allowing limited remote days elsewhere pending review. A SaaS firm might reimburse approved home office equipment and require employees to maintain working internet, protect confidential information, and attend company meetings during stated core hours.
- Require relocation approval: Employees shouldn't move states first and notify payroll later.
- State equipment rules: Clarify who owns laptops, monitors, phones, and data plans.
- Address expense reimbursement: If the company reimburses internet or phone costs, say how and through what process.
The companies that manage remote work well track work location changes as carefully as compensation changes.
9. Conflict of Interest and Confidentiality Policy
Confidentiality language should protect real business interests without pretending every employee needs the same restrictions. A software company has different risks than a local service business. A senior sales leader handling strategic accounts presents different concerns than an entry-level coordinator. The handbook should reflect that.
A solid policy defines confidential information with examples such as customer lists, pricing, source code, product roadmaps, internal financial data, nonpublic processes, and vendor terms. It also requires return of company property and records at separation, and it tells employees when outside work, board service, family relationships, or vendor ties must be disclosed.
Protect information without overreaching
Broad, generic restrictions usually age badly, especially across states. Narrower drafting works better. A sales organization may prohibit use of account-specific pricing and active proposal data outside the company. A startup may focus on code repositories, architecture documents, and customer implementation materials. A professional services firm may require pre-approval for outside advisory work that overlaps with client relationships.
For employers using a PEO, this is another place where state law and contract setup matter. Some states sharply limit non-competes, so handbook language should lean on confidentiality, trade secret handling, and conflict disclosure rather than reflexively copying a broad restraint into every version.
Protect the asset, not the ego. Most companies need stronger confidentiality controls more than they need a sweeping non-compete.
Operationally, this section should also match the company's offboarding steps. Access shutoff, property return, and reminders about ongoing obligations should line up with whatever confidentiality at work procedures HR and IT use. For teams with cross-border exposure or international vendor relationships, it can also help to review broader UK trade secret protection essentials.
10. Conflict Policy State-Specific Guidance and Sample Clauses
A handbook usually breaks here first.
A company hires its first sales rep in California, promotes an engineering manager in Colorado, and expands customer success into Massachusetts. The conflict policy still uses one national clause copied from an old template. That is how employers end up with restrictions they cannot enforce, language that scares employees for no reason, and PEO partners pushing last-minute edits after rollout.
State-specific conflict terms belong in the drafting file, even when every clause does not appear in the employee-facing handbook. Multi-state employers need a core policy, then short state addenda or role-based supplements that match the employee's work state and actual access. A seller with direct account ownership may need a narrow customer non-solicit. A product leader may need stronger confidentiality and invention assignment terms. In some states, the right answer is no non-compete at all.
The practical goal is simple. Protect real business interests without writing a restriction your own counsel or PEO compliance team will cut apart later.
Use modular clauses by work state
Start with the employee's primary work state, not the company headquarters. For remote teams, that choice matters. California, Minnesota, North Dakota, and Oklahoma tend to limit non-compete enforceability sharply. Other states permit narrower restrictions if the scope, timing, and business interest are defensible. The handbook should not try to solve every post-employment issue in one paragraph. It should point employees to the rules that apply to their role and location, then pair those rules with separate agreements where needed.
Sample clauses work better when they are narrow and tied to a real risk:
- Customer non-solicit: Limit the restriction to customers or prospects the employee personally handled, and use a defined lookback period.
- Confidentiality clause: Protect trade secrets, pricing, product plans, source code, security practices, and other non-public information after employment ends.
- Outside activity disclosure: Require employees to report side work, board service, or family business ties that overlap with company vendors, clients, or competitors.
- Invention assignment: Use stronger language for engineering, product, and R&D roles, then confirm any state carve-outs that apply to employee-created inventions.
- Garden leave option: For senior employees, paid notice periods can reduce risk better than an aggressive restriction that will not hold up.
PEO arrangements add another layer. Some PEOs provide template restrictive covenant language that is written for broad national use. That saves time, but it can create negotiation points. Ask who owns updates when a state changes its rules, who pays for counsel review, and whether the PEO will support state-specific acknowledgments inside the HRIS. If they cannot, keep those clauses outside the handbook and manage them through offer letters or standalone agreements.
I usually push employers to decide three things before drafting. What information needs protection. Which roles create a measurable conflict or customer diversion risk. Which states require a different clause set. That discipline keeps the policy usable.
Sample drafting language
A disclosure clause can be plain:
Employees must promptly disclose any outside employment, consulting work, ownership interest, board service, or close personal relationship that could affect business decisions, vendor selection, customer dealings, or use of company information.
A narrow customer protection clause can stay focused:
For the period allowed under applicable state law, employees may not solicit business from customers they personally served or supervised on behalf of the company during the 12 months before separation, if the purpose is to divert that business from the company.
A state-sensitive savings clause also helps:
This policy will be interpreted and applied to the fullest extent permitted by the law of the employee's primary work state. If a provision is restricted or prohibited under that law, the company will apply only the enforceable portion.
Handbook governance matters as much as the clause text. Review this section at least annually, and revisit it any time the company adds a new state, changes its sales model, or gives employees broader access to customer or product data. Keep acknowledgment records by version and location. HRIS records should show which policy set each employee received. Payroll and legal should also confirm how any paid notice period or post-employment payment will be handled before the clause goes live.
10-Item Employee Handbook Policy Comparison
| Policy | Implementation complexity | Resource requirements | Expected outcomes | Ideal use cases | Key advantages |
|---|---|---|---|---|---|
| At-Will Employment and Termination Procedures | Medium–High, multi‑state rules and PEO coordination | State‑specific legal review, HR training, documentation/offboarding systems | Consistent terminations, reduced wrongful‑termination risk, clearer liability allocation | Multi‑state employers and companies using PEOs | Employer flexibility, consistent documentation, clarified PEO/employer roles |
| Compensation, Pay Scales, and Salary Review Process | High, FLSA classification and complex pay structures | Payroll system, market data, finance approval, PEO payroll coordination | Improved pay equity, wage‑hour compliance, defensible bonus/commission payouts | Organizations with varied roles, sales teams, multi‑state payrolls | Transparency, reduced wage claims, budget predictability |
| Paid Time Off (PTO) and Leave Policies | Medium, state accrual rules and FMLA integration | Leave‑tracking system (or PEO), HR admin, legal guidance | Predictable PTO liability, compliant leave handling, fewer payout disputes | Employers with significant PTO liabilities or multi‑state operations | Clear accrual/carryover rules, FMLA coordination, audit readiness |
| Benefits Program Eligibility and Enrollment | Medium–High, ERISA and plan design alignment with PEO | Benefits administration platform, PEO benefits support, budget for contributions | Accurate enrollments, predictable employer costs, ERISA compliance | Employers outsourcing benefits to PEOs or offering group plans | Simplified enrollment, aligned plan design, forecasting of benefit costs |
| Code of Conduct and Workplace Expectations | Medium, policy clarity and enforcement process needed | Manager training, HR investigation capacity, legal review | Consistent behavior standards, defensible discipline, safer workplace | All employers; especially regulated or safety‑sensitive workplaces | Reduces subjective enforcement, supports legal defensibility, promotes culture |
| Health & Safety, Workplace Accommodations, ADA Compliance | High, OSHA, workers' comp, interactive ADA process | Safety programs, accommodation forms, medical coordination, insurer/PEO support | Faster claims resolution, compliant accommodations, fewer OSHA violations | Physical worksites, employers with injury risk or accommodation needs | Demonstrates good‑faith ADA efforts, reduces citations, improves return‑to‑work outcomes |
| Anti‑Discrimination, Harassment, and Complaint Resolution Procedures | High, investigations and confidentiality requirements | Investigator resources, external hotline or third‑party, training, legal support | Early reporting, thorough investigations, reduced litigation exposure | Medium‑to‑large employers, public‑facing or multi‑location firms | Encourages reporting, anti‑retaliation protection, impartial investigation options |
| Remote Work and Flexible Work Arrangements Policy | Medium, multi‑state tax and equipment logistics | Nexus analysis, remote work agreements, IT support, stipends | Greater retention and hiring flexibility, managed compliance risks | Knowledge work, distributed teams, companies hiring across states | Expands talent pool, reduces office costs, sets clear remote expectations |
| Conflict of Interest and Confidentiality Policy | Medium, IP and post‑employment restrictions vary by state | State‑tailored legal drafting, signed agreements, IP assignment processes | Protection of trade secrets and client relationships, reduced poaching | Tech, professional services, companies with valuable IP or client lists | Protects IP and client data, enforces confidentiality, supports post‑employment controls |
| Conflict Policy: State‑Specific Guidance and Sample Clauses | Medium–High, ongoing jurisdictional maintenance | Regular legal updates, jurisdiction templates, HR administration, PEO coordination | Enforceable covenants by state, lower litigation risk, consistent implementation | Multi‑state employers seeking enforceable covenants | Tailors restrictions to law, offers practical alternatives, standardizes templates across locations |
Next Steps Draft, Review, and Negotiate
A handbook only works when it matches real operations. That means HR, finance, legal counsel, and the PEO all need to agree on the same answer to basic questions. Who approves compensation changes. Who owns leave tracking. Who handles investigations. Who sends enrollment notices. Who controls terminations. If the handbook says one thing and the service agreement says another, the service agreement usually drives the relationship, but the handbook still creates employee expectations and litigation risk.
The first move is to mark up the current handbook against the PEO contract. This review should focus on co-employment boundaries, benefits administration, payroll timing, leave handling, workers' compensation reporting, investigation support, and post-termination obligations. Existing handbook guides often focus on policy categories but skip the contract trade-offs that matter in a PEO relationship, especially around liability language, fee changes, and exit terms. That gap is one reason many buyers run into costly surprises when the contract gets tested in real operations, as noted earlier.
The second move is state alignment. A growing company with employees in several jurisdictions shouldn't rely on one static PDF and a hope that managers know the exceptions. State-specific addenda, modular clauses, and location-based distribution are far easier to maintain. Mental health and Employee Assistance Program access also deserve fresh review. Emerging 2025 to 2026 guidance has pushed these topics closer to compliance territory for some multi-state employers, and some commentary has flagged a lack of clear policy access as a meaningful retention issue, discussed in this 2025 handbook topics article. Even where the legal obligation is still evolving, clear access instructions belong in the handbook now.
Third, treat distribution and acknowledgment as part of the policy itself. A handbook no one can prove was delivered is weak evidence. Every employee should receive the current version through the company portal, email, or another reliable channel, and signed acknowledgments should be retained in the personnel record. The acknowledgment page should confirm receipt, review, and understanding while also reinforcing that the handbook is not a contract except where separate written agreements say otherwise.
Last, set a review schedule with names attached to it. Annual review is the baseline. New law, new state, new benefit design, or a PEO switch should trigger an interim update. A 30-day compliance audit after rollout is a practical way to catch broken links, missing state addenda, wrong enrollment language, outdated reporting contacts, and manager-side confusion before those mistakes turn into employee disputes. This is a key takeaway for anyone asking what should be included in an employee handbook. Include the sections employees need, the legal language counsel expects, and the operational detail the PEO relationship requires.
If a company is comparing PEO options, renewing an agreement, or trying to strengthen their position before signing, PEO Metrics helps buyers evaluate pricing, benefits, contract terms, service model, compliance support, and risk flags side by side so leadership can make a cleaner decision and negotiate from a stronger position.
