No system fails overnight. It usually shrinks in usefulness gradually: first there's one exception handled "outside the system," then a parallel spreadsheet for whatever the system doesn't cover, and at some point HR stops being the team that runs processes and becomes the bottleneck everyone waits on to move forward.

These are concrete signs it's time to review your system, not just push through one more quarter.

There's a spreadsheet for "what the system doesn't do"

If your HR team keeps one or more parallel spreadsheets — to calculate overtime, to track which protective equipment was handed out, to note who's overdue for a performance review — that's a clear sign the system isn't covering processes you already have, even recent ones. Every parallel spreadsheet is a piece of data that can drift out of sync with the official system without anyone noticing until it matters.

Permissions are all-or-nothing

A system that's outgrown its usefulness usually has a generic permission scheme: admin, editor, viewer. Once a company grows and needs a manager to see their team's org chart but not everyone's personal data, or an HR staffer to manage payroll without being able to touch other people's permission settings, that simple scheme forces a choice between granting too much access or none at all. Granular permissions by module, level and scope aren't a large-company luxury — they're what lets you delegate without losing control.

Growing into multiple companies or brands breaks it

If your business opens a second legal entity, a subsidiary, or simply splits into separate brands, and the system can't keep each one's data isolated — its own headcount, its own documents, its own file storage — you end up either mixing data that should legally and operationally stay separate, or duplicating the entire system for the second company.

  • Are there "parallel" spreadsheets for whatever the system doesn't cover?
  • Are permissions all-or-nothing, or can they genuinely be tuned per module?
  • Could the system handle a second company with fully separated data?

There's a fourth signal, harder to measure but just as real: how long it takes HR to answer something that should be instant, like confirming someone's remaining vacation balance or fixing a data entry mistake. If the answer is "let me check the spreadsheet and get back to you" instead of pulling up a screen, the system has already stopped doing the job it's supposed to do. None of these signals show up on a single day — they build up over months, which is exactly why they're easy to normalize. Ask your team directly: is there a task you've quietly stopped trying to do in the system, because it's easier to work around it? The answer usually points straight at what needs to change. If more than one person gives the same answer, that's the signal.

If you answered yes to the first question and no to the other two, the system hasn't technically broken — it's simply stopped keeping pace with your company's actual size. That's the real signal, not a one-off glitch.