HR: Where “We’ve Always Done It This Way” Gets Expensive

Written by James Sanders

Oops Files, Part 3

Employment issues rarely begin with a dramatic event. More often, they build gradually: a worker is labeled an independent contractor because it is convenient, pay practices are handled informally, performance concerns are discussed but never documented, or policies exist only in someone’s memory.

Those shortcuts can become expensive when an employee leaves, a wage claim is filed, a discrimination or retaliation allegation is raised, or a government agency asks questions. In those moments, the issue is no longer simply whether management acted reasonably; it is also whether the company can show what it did, why it did it, and that it treated comparable situations consistently.

A few recurring trouble spots deserve regular attention:

• Worker classification. Calling someone a contractor, paying them on a 1099, or allowing flexible hours does not alone establish independent-contractor status. Classification should reflect the actual working relationship, including the degree of control, the worker’s independence, and the economic realities of the arrangement.
• Wage-and-hour discipline. Pay practices should be reviewed for overtime eligibility, timekeeping, off-the-clock work, deductions, commissions, bonuses, and final-pay obligations. A salaried title does not automatically make a position exempt from overtime rules.
• Documentation. Managers should document material performance discussions, coaching, discipline, leave-related issues, and the legitimate business reasons supporting significant employment decisions. Documentation should be timely, factual, and professional—not a post-dispute reconstruction.
• Policies that match practice. Employee handbooks and policies should be current, understandable, and actually followed. Inconsistent enforcement—especially involving attendance, leave, workplace conduct, or discipline—can create unnecessary risk even where the written policy is sound.
• Hiring and separation. Job descriptions, offer letters, confidentiality and restrictive-covenant agreements, onboarding materials, exit procedures, and return-of-property protocols all help define expectations and preserve the company’s position when a relationship ends.

Consider a common example: a growing company engages a “contractor” who works full-time, uses company systems, reports to a supervisor, performs core business functions, and has no meaningful independent customer base. If the relationship is later challenged, the company may face more than a classification correction; it may also confront unpaid-wage exposure, payroll-tax issues, benefit claims, penalties, and attorneys’ fees.

The practical takeaway is straightforward: employment compliance is not merely an HR function. It is an operating-system issue. Owners and management teams should periodically audit their classifications, payroll practices, core policies, and personnel files before a dispute supplies the motivation—and the deadline—to do so.