Employee handbook development is the work of writing the rules your company actually follows, in language people will read, then keeping that book current. For a Kansas City employer, that usually means one workforce and two states. OPES Companies, in North Kansas City, Missouri, builds handbooks as a consulting project or keeps them current inside an ASO engagement. This is not legal advice, and it is not a template you can paste into a PDF and forget.
A handbook does two jobs. It tells employees what to expect. It gives managers one standard so the same situation does not get two answers. The common failure is a book that says one thing while the floor does another. That gap is worse than no policy when a decision gets questioned.
Start from the operation, not from a download
The first draft should describe how this company runs: how people clock in, who approves time off, what “call in” means, how a complaint gets to a person, and what a manager is supposed to write down. If the draft describes a company you do not have, throw it out.
Kansas and Missouri employers get into trouble with the same shortcut. Someone downloads a national handbook, changes the logo, and files it. The PTO section grants a benefit the company has never paid. The discipline ladder has four steps nobody uses. The attendance rule ignores how the shop actually covers a shift. Six months later a termination relies on a policy the employee never saw applied to anyone else.
Employee handbook development, done properly, is a set of decisions you are willing to live with, written down, then checked against current federal rules and against Missouri or Kansas rules for the people you employ. Local rules in the metro can add another layer. Counsel reviews legal risk. OPES drafts the practical book and can sit beside that attorney. OPES does not replace counsel.
If you employ people on both sides of the state line, say so in the scoping conversation. A Missouri-only book handed to a Kansas employee, or the reverse, is how “we have a handbook” stops being true.
What the book should cover
These are the sections a growing employer should be able to point to. They are categories, not a statute list. The exact wording has to match your practice and a current legal review.
Who employs them, and that the relationship is at-will where that is your intent. Employees should know the company name, who to go to with an HR question, and that a handbook is not an employment contract. Do not let a sloppy sentence accidentally promise a term of employment you did not mean to promise.
How to raise a problem. Equal-employment and harassment language is useless without a path: who receives a complaint, what happens next, and that retaliation for a good-faith report is not allowed. Managers need the same page. If the only instruction is “tell your supervisor,” and the supervisor is the problem, the policy fails in the moment you need it.
Time, attendance, and pay practices your payroll can follow. Payday, how hours are recorded, overtime expectations for nonexempt roles, and what happens when a timesheet is late. This has to match the system you actually use. A handbook that describes a paper timesheet while everyone clocks in on a phone will not help you in a wage dispute.
Time off you really grant. PTO, holidays, and any leave you offer beyond what the law requires. Write the rule you will apply on a Friday when three people ask at once. If Kansas employees and Missouri employees are treated differently, say that. Do not copy a coastal city’s paid-leave ordinance into a book for a shop that is not in that city.
Conduct and corrective action you will actually use. If you say every issue gets a verbal warning, a written warning, and a final warning, managers have to do that, or you have to say the company can skip steps when the conduct warrants it. Inconsistent discipline is where handbooks get used against the employer.
Safety and how to report an injury or a hazard. Who to tell, and that reporting is expected. This is especially plain in construction, manufacturing, and field work, which are common among OPES clients. The handbook is not your safety program. It is the instruction employees can find.
Benefits at the level of “where to look,” not a second plan document. Eligibility and plan design live in carrier documents and summary plan descriptions. The handbook should not invent deductibles or promise a benefit the plan does not provide. Point people to the real documents and to whoever administers enrollment.
Devices, confidentiality, and expectations that match the job. A professional-services firm and a field crew do not need the same paragraph. Write the one you will enforce.
An acknowledgment. Each employee gets the current version and signs that they received it. New hires do this in onboarding, not six weeks later when someone remembers. When you change the book, you reissue it. A signature on a 2019 version does not cover a 2026 rewrite.
Leave out policies you will not enforce. Leave out legal citations you do not understand. A short book that matches the floor beats a long book nobody can reconcile with last Tuesday.
Missouri and Kansas are not the same workplace
Plenty of Kansas City companies have a Missouri office, a Kansas shop, or people who live in one state and work in the other. Payroll registrations, wage rules, and leave rules do not automatically match just because the metro shares a highway.
Employee handbook development for that company has to answer:
- Which employees are covered by which version, or by which section
- Whether PTO, holidays, and call-in rules are the same on both sides of the line, or only look the same
- Who updates the book when a state or a city changes a rule that touches your headcount
- Whether managers in both locations have been told which page to follow
Do not treat “Kansas City” as a single employment-law jurisdiction. Headquarters is in North Kansas City, Missouri. That does not make every worker a Missouri employee. Ask which states you employ in before you approve a draft.
This is also not a reason, by itself, to move to a PEO. A bi-state handbook is a document problem. Co-employment is a tax and benefits structure. You can need the document and still keep your EIN. If the constraint is large-group benefits, that is a different conversation, covered in ASO vs PEO.
A project, or a book someone maintains
A one-time rewrite is HR consulting. You keep payroll. You get a draft built around your operation, checked against federal, Missouri, and Kansas requirements as they stand, and a version employees can acknowledge. Counsel still reviews legal risk if you want that review. Many employers need exactly this and nothing else.
Keeping the book true after that is a different job. Laws move. You add a shift, a state, or a benefit. Managers invent a practice the book does not mention. Administrative services outsourcing includes handbook development and updates on top of payroll and employee-relations support, and you remain the employer of record. Buy that when you want the book maintained, not when you only need this quarter’s rewrite.
Do not buy a year of administration to finish a document. Do not buy a PDF and assume it is still accurate in three years. The fuller picture of project versus ongoing help is in HR consulting for audits, handbooks, and investigations.
Whoever writes it should talk to the people who enforce it. A handbook drafted only from last year’s offer letters will miss the attendance rule the lead on the floor has been using. That conversation is part of development, not a nice-to-have.
What to ask before you approve a draft
- Did you write this from how we operate, or from a generic template?
- Which states and cities does this version cover, and where are we silent?
- Which sections describe a benefit or a discipline step we do not actually use?
- What will employees sign, and how do we reissue it when it changes?
- What is your role versus our attorney’s? (The consultant should not be giving legal advice.)
- Who updates this next year if we add people in the other state?
If the draft cannot survive those questions, it is not finished.
Frequently asked questions
What is employee handbook development?
Writing and updating the policies your company will actually follow, in plain language, checked against current employment rules, with a way for employees to acknowledge the version they received. It is not a logo slapped on a national template.
Does Missouri or Kansas require us to have a handbook?
This article is not legal advice, and a handbook is not universally mandated as a single document. Employers still need clear, consistent rules they can apply. A handbook is how most growing companies do that. Have counsel tell you what you must do in your locations. Have HR make the book match the operation.
Can one handbook cover Kansas and Missouri employees?
Often yes, if it says where rules differ and managers know which section applies. A single silent template that assumes one state’s practice is the failure mode, not the fact that you operate in both.
Is this a consulting project or part of ASO?
A rewrite with an end date is consulting. Ongoing updates plus payroll and employee-relations support is ASO. You can start with the project and add ASO later. You do not have to.
Will OPES act as our lawyer?
No. Attorneys assess legal risk. OPES handles the practical HR work and can work alongside counsel.
Write the book you will stand behind
The handbook employees will quote is the one managers already follow. Employee handbook development is the discipline of making those two things the same, for the states you actually employ in, and of giving people a current copy.
OPES Companies is at 214 E 18th Avenue in North Kansas City. If you want a draft built from your operation, not from a download, schedule a consultation. Call 816-994-9190.