At 20 employees, most HR software looks like it is doing its job. Payroll runs. Onboarding paperwork gets filed. The handbook is current enough. Nobody is losing sleep over compliance.
At 75 employees, the same HR leader is often fielding manager questions they cannot answer confidently, discovering a policy gap during an employee relations issue, and wondering when exactly the company stopped being "small enough" to wing it. Nothing about the software changed. The company did.
This is the pattern behind one of the most common and least discussed HR technology failures: HR software and support that was genuinely adequate for a 20-person company is not automatically adequate for the same company at 75 people, because the legal obligations a company carries do not scale smoothly. They step up at specific headcounts, set by federal law, whether or not the HR function or the HR software was built to notice.
Compliance obligations do not grow gradually. They grow in steps.
Most growth planning treats HR capacity as a straight line: more employees means more onboarding, more payroll runs, more questions to field. That is true, but it understates the real risk. A handful of specific headcount thresholds change what a company is legally required to do, rather than just how much work there is to do.
Three of the most consequential are federal, well documented, and easy to cross without noticing:
50 employees within a 75-mile radius triggers FMLA
Under the Family and Medical Leave Act, an employer is generally covered once it has 50 or more employees, as defined in 29 CFR § 825.104. Whether a specific employee is eligible to take that leave is a separate test: it depends on whether the employer has 50 or more employees within 75 miles of that employee's worksite, per 29 CFR § 825.110 and explained by the U.S. Department of Labor. Below that line, a company can handle a serious employee medical situation or a new parent's leave request case by case, with whatever policy feels reasonable. Above it, the company has a legal obligation to provide job-protected leave, track eligibility correctly, and apply the rule consistently across managers and locations. A manager who improvises a leave decision after the company crosses this line is not being inconsistent. The company is exposed.
50 full-time-equivalent employees triggers the ACA employer mandate
The Affordable Care Act's employer shared responsibility provisions apply to Applicable Large Employers, generally defined as employers with 50 or more full-time-equivalent employees, per the IRS. Below that threshold, health coverage is a business decision. At and above it, offering coverage that meets minimum requirements, and reporting on it correctly, is a compliance obligation with real consequences for getting it wrong.
100 employees triggers EEO-1 reporting
Once an employer reaches 100 employees, it generally becomes subject to EEO-1 reporting, the annual workforce demographic data collection administered by the Equal Employment Opportunity Commission. A company that has never had to categorize its workforce this way now needs the data infrastructure to do it accurately and on schedule.
None of these thresholds care whether the HR team saw them coming. They apply the moment a company's headcount, or full-time-equivalent count, crosses the line, sometimes mid-quarter, sometimes because of a hiring push nobody flagged as legally significant. These figures are current as of 2026; confirm against the cited primary sources before relying on them, since thresholds can change.
Why this is a runway problem, not a workload problem
Here is where a lot of HR technology decisions go wrong. Leaders tend to evaluate HR software against current headcount and current workload. Does it handle 20 employees well today? Yes. Renewed. But the more useful question is whether the system gives an HR leader visibility into obligations that have not kicked in yet, so the team is not finding out about FMLA coverage the week an employee needs leave.
This is what a published Asure framework calls compliance runway: how far ahead a company's HR technology and support let it see the next obligation, versus how far the company can drift past a threshold before someone notices the gap. It is one of three evaluation dimensions covered in that framework, alongside service model archetype and payroll architecture, both explored in depth in the full pillar piece on evaluating HR and HCM software. This piece goes deep on compliance runway alone.
Short runway looks like this in practice: a spreadsheet-based system or a bare-bones payroll tool that tracks headcount as a number instead of a compliance signal. Nobody in the system is watching for 50 or 100. The HR leader finds out about a threshold the way most HR leaders find out about problems, after something already went wrong, a manager already made an inconsistent call, or an audit already flagged a gap. That is the exact fear HR leaders describe when they talk about falling behind on compliance updates: not that they do not care about compliance, but that the systems and staffing around them do not surface what changed until it is already a problem.
Long runway looks different. It means the HR technology itself reflects real headcount and location data continuously, so an approaching threshold is visible before it is crossed, and there is a way to get compliance expertise applied to that specific moment without having to build a full internal compliance function to do it.
What this looks like inside a growing company
Consider a 45-person professional services firm running lean HR software chosen when the company had 15 employees. The software processes payroll fine. It was never asked to track whether the company was approaching FMLA coverage, because at 15 employees that question did not exist. Six months and a hiring wave later, the company has 58 employees across two offices 40 miles apart. FMLA coverage applied the day it crossed 50, well before the day someone in HR ran the numbers and realized it.
That gap is not a software feature failure. It is a visibility failure. A connected system like AsureCentral, which keeps payroll, HR, and workforce data in one environment rather than scattered across spreadsheets and disconnected tools, gives an HR leader a current, accurate headcount and location picture as the company grows, instead of a snapshot frozen at the last time someone manually checked. That does not replace judgment about what a threshold requires. It closes the more basic gap: not knowing the number changed.
The second half of the gap is expertise, separate from the data itself. Knowing the company crossed 50 employees does not tell an HR leader everything FMLA now requires, how to build ACA-compliant offer documentation, or how to prepare EEO-1 data collection for the first time. This is the exact problem behind the pain HR leaders describe as needing to add compliance expertise without increasing headcount. Building an internal compliance function to cover FMLA, ACA, and EEO-1 readiness is a real cost that most companies in the 20-to-75-employee range are not ready to carry. Asure HR Compliance is built for this moment specifically: certified HR professionals who help a company recognize an approaching threshold and prepare for it, without the company hiring dedicated in-house compliance staff to do it.
Building runway into the HR technology decision
The mistake is evaluating HR software the way most best-of lists frame the decision, on current features for current headcount. A growth-stage company should instead ask what happens when it crosses 50 employees, 50 full-time-equivalents, or 100 employees, and whether its HR technology and support will surface that moment or let it pass quietly.
That question does not have a guaranteed answer, and no vendor can promise a compliance outcome. What a growing company can reasonably expect is a system that keeps accurate, current workforce data instead of static snapshots, paired with access to HR expertise that scales with the company rather than requiring a hire every time obligations expand. That combination, a connected system like AsureCentral and compliance support like Asure HR Compliance, is what compliance runway looks like in practice, not a feature checklist, but a way of staying ahead of the thresholds instead of discovering them after the fact.
For the two other dimensions that separate HR software choices that hold up at scale from ones that do not, service model archetype and payroll architecture, see the full evaluation framework.
If your company is approaching one of these thresholds, or has already crossed one without a system built to notice, that is the moment to evaluate whether AsureCentral and Asure HR Compliance can give your team the runway your current setup does not.
