Spreadsheets vs compliance software: when does an agency actually need to switch?

A spreadsheet tracking candidate compliance, AWR dates and right to work renewals works fine for a small agency, and it's worth saying plainly that switching to dedicated software isn't automatically the right call just because a vendor would like it to be. The genuinely useful question isn't whether a spreadsheet is good enough in the abstract — it's whether it's still good enough for how your agency actually operates today.

Why a spreadsheet works, for a while

A spreadsheet with a start date and a formula for the 12-week AWR threshold is genuinely fine when one person owns it, updates it consistently, and the number of active placements is small enough to hold in view. The formula isn't the problem. The problem shows up later, and it shows up quietly.

The specific signs it's time to look elsewhere

• –More than one person needs to update the same file, and there's no reliable way to know whether the version being looked at is current.
• –Nobody can say with confidence, on any given day, who's actually responsible for checking it that week.
• –A near-miss has already happened — a threshold or renewal date that was almost missed, caught late rather than with real lead time.
• –The file has grown complex enough that a formula error would be genuinely hard to spot, because nobody fully understands every tab anymore.
• –Branches or consultants have started keeping their own separate versions, because the shared one stopped being trustworthy.

What a spreadsheet structurally can't do

The deeper issue isn't file size — it's that a spreadsheet doesn't flag its own staleness. A dashboard that's meant to show who's approaching an AWR threshold or whose right to work needs renewing is only useful if it's actually being updated, and a spreadsheet has no way of surfacing that it hasn't been touched in three weeks. Software built for this specifically closes that gap by generating the alert from the underlying data automatically, rather than depending on someone remembering to look.

Switching isn't free, and that's worth being honest about

Moving off a spreadsheet has real costs — migrating existing records, retraining consultants on a new workflow, and a period where things feel slower before they feel faster. What actually matters in the software you switch to is worth working out properly before committing to the migration effort, rather than switching reactively the week after a near-miss and picking whichever tool is fastest to set up.

A reasonable way to make the call

A useful exercise is asking, honestly, what would have to go wrong for the current spreadsheet-based process to actually fail — and then asking how likely that specific failure is given how the agency is actually run today, not how it was run when the spreadsheet was first built. An agency that's grown from two consultants to eight, or added several new hirers with different reporting needs, is answering a different question than it was a year or two ago, even if nobody's formally decided the spreadsheet has stopped working.

What the actual cost comparison should include

When weighing software cost against sticking with a spreadsheet, the honest comparison isn't the software's price against zero — a spreadsheet has a real cost too, in the consultant time spent maintaining it and the risk cost of the thing it's meant to catch slipping through. That risk cost is harder to put a number on, but it's not zero, and it tends to grow, not shrink, as an agency adds branches and consultants.

The cost paid somewhere other than the licence line

Spreadsheets look free because their cost sits in other people's time and in occasional expensive surprises: the hours assembling a client compliance report by hand, the expiry that passed in an unopened column, the placement queried months later where the evidence could not be produced.

The comparison that matters is not a licence fee against zero. It is a licence fee against a quantity of administrative time plus a tolerance for the occasional loss — and in a compliance context, the absence of any audit trail is its own exposure.

Common mistakes

• –Comparing a licence cost against zero rather than the time it replaces
• –No audit trail, so an error cannot be traced or dated
• –Multiple copies circulating with no agreed master
• –Waiting for visible failure when the failure mode is quiet inaccuracy
• –Migrating every historic row rather than what is currently live
• –Underestimating how much of the sheet's meaning lives in one person's head