Employee Handbook Essentials for Startups: The 8 Policies You Need Before Your Fifth Hire

Why the Handbook Matters Before Employee #5

Texas presumes employment is at-will. Either party can terminate the relationship at any time, for any reason, and that default is one of the strongest employment-law protections Texas employers have. But it is a default, not a guarantee — and a badly written employee handbook is one of the fastest ways to waive it. In Federal Express Corp. v. Dutschmann, 846 S.W.2d 282 (Tex. 1993), the Texas Supreme Court held that a handbook disclaimer of any contractual relationship negates any implied limitation on the employer's termination right. The corollary is equally true: a handbook without that disclaimer, or one whose procedures create specific enforceable promises, can alter the relationship entirely.

The implied-contract exception is not theoretical. In Vida v. El Paso Employees' Federal Credit Union, 885 S.W.2d 177 (Tex. App. El Paso 1994, no writ), a provision stating no employee would be penalized for using the grievance procedure was enough to satisfy the specific, express limitation test — converting what the employer assumed was an at-will relationship into something that carried contractual weight. Founders who hand employees a handbook with detailed procedures and no disclaimer are handing plaintiffs an argument on a platter.

The other common misconception is that legal exposure tracks federal coverage thresholds. Title VII's anti-discrimination protections apply at 15 employees. FMLA leave obligations kick in at 50. A seven-person startup assumes it is below the threshold for most employment claims — and it is, for those statutes. But Texas common law wrongful termination claims carry no minimum-employee threshold. Neither does the Texas Payday Law. A three-person company can face a retaliation claim or a wage dispute the same day it makes its first hire. Building a handbook before the fifth employee is not bureaucratic overcaution; it is the point at which the gap between written policy and actual practice is still small enough to close without litigation pressure forcing the timeline.

Policy 1: The At-Will Statement and Disclaimer

The at-will disclaimer is the single most important sentence in any Texas employee handbook. Under Dutschmann, a handbook that contains an adequate disclaimer creates no implied contract even if it includes detailed procedures, guaranteed fair treatment language, and multi-step review processes. Without the disclaimer, each of those provisions becomes a potential express limitation on termination rights. The disclaimer does not need to be long — it needs to be unambiguous, prominent, and placed where no one can argue they missed it.

The language must cover three things. First, employment is at-will and either party may terminate the relationship at any time, with or without cause and with or without notice. Second, this handbook is not a contract of employment and does not create any contractual rights. Third, the company may revise, modify, or rescind any policy at any time without prior notice. Place this language at the front of the handbook — before the welcome message, before the mission statement, before anything else — and repeat it verbatim in the standalone acknowledgment form the employee signs.

The drafting trap that defeats otherwise valid disclaimers is progressive discipline. Courts applying the Vida specific-and-express test have found that a mandatory progressive discipline clause — one using language like "the company will follow these steps before termination" — overrides a general disclaimer because the specific procedural promise controls over the general disclaimer language. An employer who carefully places a disclaimer on page one and then writes a mandatory five-step discipline procedure on page twelve has created an internal contradiction that a court may resolve against the employer. The fix is permissive language: the company may use progressive discipline at its discretion, may skip any step, and reserves the right to terminate employment at any time regardless of whether prior steps were used. That language is consistent with at-will doctrine rather than a limitation on it.

Policies 2 and 3: Anti-Harassment, Non-Discrimination, and the Complaint Procedure

Your anti-harassment policy is not an ethics statement — it is an affirmative defense in litigation. Under the framework established by the U.S. Supreme Court in Faragher v. City of Boca Raton and Burlington Industries v. Ellerth (1998), an employer can avoid vicarious liability for supervisor harassment if it satisfies a two-prong test: the employer exercised reasonable care to prevent and promptly correct harassment, and the employee unreasonably failed to use the complaint procedure the employer provided. A policy that exists only on paper, that employees were never shown, or that lacks a functional complaint channel fails the first prong outright.

The EEOC's enforcement guidance on vicarious liability specifies six elements a policy must contain to support this defense: a clear explanation of prohibited conduct; an anti-retaliation assurance for employees who report; an accessible, multi-channel complaint process; a confidentiality assurance; a commitment to prompt, thorough, and impartial investigation; and an assurance of immediate and appropriate corrective action. Omitting any of these weakens the defense — courts examine the policy's actual content, not just its existence. At 15 or more employees, Title VII and Texas Labor Code Chapter 21 impose formal obligations; below that threshold, the defense is still worth building because it reflects sound workplace practice and reduces exposure under other theories.

The single most common failure in startup handbooks is the complaint channel. If the policy lists only the direct supervisor as the recipient of complaints, it fails on its face — because the supervisor may be the harasser. The EEOC requires procedures that include bypass options allowing employees to report to someone outside their direct chain of command. For a five-person company, that alternative might be a founding partner, an outside HR consultant, or an anonymous reporting email. The specific channel matters less than the structural independence from the accused. One practical approach: name two reporting channels in the policy, specify that employees may use whichever they choose, and confirm that retaliation for reporting — to either channel — will result in discipline up to and including termination.

Policies 4 and 5: Leave and PTO — What the Law Actually Requires

Texas does not require private employers to provide paid leave of any kind. Austin, San Antonio, and Dallas all passed paid sick leave ordinances, and all three were struck down — Austin's by the Texas Third Court of Appeals in 2018 on preemption grounds, with San Antonio's and Dallas's following the same reasoning. There is no state paid sick leave law, no city-level mandate that has survived judicial review, and no imminent legislative fix on the horizon. That means leave policy in Texas is almost entirely a contract question, not a compliance question — and contract questions are where drafting precision matters most.

The Texas Payday Law trap is the most expensive mistake founders make on this topic. Under Texas Workforce Commission guidance on accrued leave payouts, accrued PTO becomes legally protected wages — but only if a written policy promises payout. The TWC states it plainly: "Payouts of accrued leave are required under the Texas Payday Law only if such a payment is promised by the employer in a written policy or agreement." The payout obligation is controlled entirely by the policy's wording. A handbook that says employees "accrue" PTO without specifying a forfeiture or cap provision has, without intending to, created a wage liability that must be paid out at separation. The fix is straightforward: either use explicit accrual language with a stated cap and forfeiture clause, or adopt a flexible time off model with clear language that time off does not accrue and is not a wage. Note that the safe-harbor treatment of flexible PTO as a non-accruing benefit is a widely-used drafting strategy, but the TWC guidance does not directly address it — founders should treat it as risk mitigation language rather than a definitive safe harbor.

Federal leave mandates hit at different headcount milestones. The Uniformed Services Employment and Reemployment Rights Act (USERRA) applies to every employer regardless of size — there is no minimum employee count — making a military leave policy mandatory from employee one. The Pregnant Workers Fairness Act (PWFA), effective June 27, 2023, applies to employers with 15 or more employees and requires reasonable accommodation for limitations related to pregnancy, childbirth, or related medical conditions. That scope is broader than founders typically anticipate: it covers not just active pregnancy but miscarriage, postpartum depression, edema, lactation, and other related conditions. A narrow maternity leave policy does not satisfy PWFA — you need an accommodation request process. The Family and Medical Leave Act (FMLA) does not apply until 50 employees within 75 miles, meaning most early-stage startups are not covered, though the Americans with Disabilities Act (at 15 employees) may independently require leave as a reasonable accommodation for qualifying conditions.

Texas Labor Code § 122.001 also prohibits any employer from penalizing an employee for jury service — this applies at every size and should be reflected in your handbook regardless of how lean you are running.

Policies 6 and 7: Confidentiality, IP Assignment, and What Belongs in the Handbook vs. a Separate Agreement

A surprising number of tech founders assume that because an employee built it on company time, the company owns it. That assumption is only partially correct. Under 17 U.S.C. § 101, a work created by an employee within the scope of employment qualifies as a "work made for hire," vesting copyright automatically in the employer. Patents operate differently: patent rights vest initially in the inventor under federal law, not the employer, regardless of the employment relationship. Without a written assignment, a departing engineer takes patent rights with her — including rights to the code-adjacent inventions that drive your valuation. The fix is a standalone Confidential Information and Assignment of Inventions Agreement (CIAA), signed before the employee's first day. The handbook cross-references it; the CIAA does the heavy lifting.

The handbook does have real legal work to do on confidentiality. Under the Texas Uniform Trade Secrets Act (TUTSA), Tex. Civ. Prac. & Rem. Code § 134A.002(6), information qualifies as a trade secret only if it derives independent economic value from secrecy and its owner took reasonable measures to maintain that secrecy. A handbook confidentiality policy is documentary evidence of those reasonable measures. Texas courts will not protect information the owner took no steps to protect — absolute secrecy is not the standard, but specific, documented protective steps are. A handbook clause naming company systems, customer data, source code, and business plans as confidential contributes directly to that documented record.

The broader framework requires more than a handbook clause. Reasonable measures under TUTSA typically include requiring NDAs and CIAAs from employees and contractors, restricting access to sensitive information through password protection and encryption, and educating employees on confidentiality obligations and the consequences of misappropriation. The handbook confidentiality section is one layer of that multi-layered system, not a substitute for the others.

One more boundary to draw clearly: non-compete clauses do not belong in the handbook. Under Texas Business and Commerce Code § 15.50, a covenant not to compete is enforceable only if it is ancillary to an otherwise enforceable agreement at the time the agreement is made. A handbook is not that agreement — it is a unilaterally revisable policy document, not a bilateral contract. A non-compete buried in a handbook acknowledgment may be entirely unenforceable, and worse, it creates the appearance of protection where none exists. Non-competes belong in a separately negotiated and signed agreement — typically the offer letter or a standalone restrictive covenant agreement — with independent consideration.

What NOT to Include: Progressive Discipline and Arbitration Clauses

Progressive discipline policies — the verbal-warning, written-warning, PIP, termination sequence — feel responsible. They signal fairness. But drafting them with mandatory language is one of the most reliable ways to destroy an otherwise valid at-will disclaimer. Texas courts apply the same specific-and-express limitation test here that they use to find implied employment contracts generally: if the handbook says the company will follow these steps before terminating an employee, a court may read that as a specific express promise that controls over the general at-will disclaimer elsewhere in the document. The procedural commitment supersedes the general reservation of rights.

The fix is discretionary framing. A values-based conduct section can describe the range of responses to performance and behavioral issues, but the operative language should read something like: "The company may use progressive discipline, may skip any step at its sole discretion, and reserves the right to terminate employment at any time for any lawful reason regardless of whether prior steps have been taken." That phrasing preserves the at-will relationship and gives managers the flexibility to respond proportionately without creating a procedural promise the company will be held to in litigation.

Mandatory arbitration presents a different structural problem. A handbook arbitration policy and an enforceable arbitration agreement are not the same thing. Courts, including the Fifth Circuit, have refused to enforce handbook-embedded arbitration provisions when the employer reserved the right to modify the handbook at any time — a standard feature of most handbook acknowledgment forms. That modification-at-will language renders the arbitration clause illusory: the employer can change or eliminate the obligation unilaterally, so there is no mutuality of obligation. A clause without mutuality is not a contract.

Texas courts evaluate arbitration agreements for unconscionability on both procedural grounds (how the agreement was formed) and substantive grounds (cost allocation, confidentiality obligations, and whether the clause binds both parties equally). Post-Viking River Cruises v. Moriana, 596 U.S. 639 (2022), courts have continued to scrutinize whether employees gave knowing, bilateral assent to employment arbitration — a trend that makes the bilateral requirement and the standalone-agreement approach more important, not less. If arbitration is part of your employment strategy, draft it as a separate agreement, have every employee sign it individually at onboarding, and keep that executed agreement in the personnel file separate from the handbook acknowledgment.

Rolling Out the Handbook Without Creating Reliance

Writing the handbook is the easy part. The rollout is where founders create the reliance problems they were trying to avoid. Two steps determine whether your carefully drafted document functions as a policy manual or an accidental contract: the acknowledgment form and the supersession clause.

The acknowledgment form should be a standalone document — not a signature line on the last page of the handbook itself. It needs to accomplish three things above the signature line: confirm the employee received the handbook, state explicitly that the handbook is not a contract of employment, and confirm that the company may amend or revoke it at any time. All three elements track the disclaimer standard that Texas courts have applied since Federal Express Corp. v. Dutschmann — a disclaimer that says all three things gives you the protection; one that omits any of them introduces ambiguity.

Electronic signatures are fully valid. Under Texas Business and Commerce Code § 322.007, a record or signature cannot be denied legal effect solely because it is in electronic form. The federal E-SIGN Act (15 U.S.C. § 7001) applies to electronic signatures in commerce, including employment transactions. A DocuSign acknowledgment satisfies both statutes. There is no reason to delay rollout waiting for in-person wet signatures.

When you update the handbook — and you will — every amendment needs a new acknowledgment cycle. Posting a revised version to your intranet or Notion does not establish receipt. Send the revised handbook directly, collect fresh signatures, and include explicit supersession language in the document itself: this handbook replaces and supersedes all prior written policies, procedures, and handbooks. Without that language, employees who signed an earlier version may argue reliance on whichever prior policy was more favorable to them.