Spreadsheets vs dedicated licence tracking: when to actually switch

Nobody sets out to run compliance on a spreadsheet forever. It is the obvious first tool — free, familiar, fast to set up — and for a small operation it genuinely works. The question worth asking periodically is not whether the sheet still exists, but whether it still describes reality. See tracking licence expiry without a spreadsheet for the specific ways it drifts.

Signals worth paying attention to

There is no fixed headcount at which a spreadsheet stops working — it depends on how many people touch it and how often things change. A handful of recurring signals are more reliable than a number.

• –More than one person needs to update it, and versions have started to disagree with each other
• –Cover decisions get made by people who do not have the sheet open
• –An assessment or audit took longer than it should have because information had to be assembled from several places
• –A near-miss happened — an officer nearly rostered with an expired licence — and it was caught by luck, not by the system
• –Onboarding a new site or contract means rebuilding structure the sheet was never designed to hold

Any one of these on its own is manageable. Two or three together usually means the sheet has outgrown what a spreadsheet can be trusted to do reliably, regardless of how carefully it is maintained.

What actually changes when you switch

The value of dedicated tracking is not that it is more accurate than a well-kept spreadsheet — a well-kept spreadsheet can be perfectly accurate. It is that the information sits where the decision gets made, rather than in a separate file someone has to remember to open. See what to look for in security management software for what that should look like in practice.

The cost of switching too late

Switching late tends to mean switching under pressure — after an assessment finding, or after a near-miss makes the exposure obvious. Migrating licence records, screening files and training history is straightforward when done calmly, and considerably less so when it is done in response to a problem that has already happened.

The specific weakness in this use case

Spreadsheets handle many compliance tasks adequately. Licence tracking is a poor fit for a particular reason: the record has to be right at the moment a rostering decision is made, by someone who is not the person maintaining the sheet, often outside office hours. A file that is accurate when opened is not the same as a check that happens at the point of decision.

The second weakness is the absence of an audit trail. A cell can be changed by anyone with access, leaving no record of what it said before or who changed it — which is a different order of problem when the record concerns whether someone was lawfully working.

Common mistakes

• –A record that is accurate when opened but not checked at the point of rostering
• –No audit trail, so a change cannot be traced or dated
• –Multiple copies with no agreed master
• –No notification, so the sheet only works if somebody opens it
• –Leavers and joiners handled inconsistently
• –One person maintaining it with no cover

What separates a record you can rely on

Three things a spreadsheet structurally cannot provide: a check at the moment a rostering decision is made, a notification that reaches someone without the file being opened, and an audit trail showing what the record said and when it changed.

For many compliance tasks the absence of those is tolerable. For a record concerning whether someone was lawfully working a shift, each one is the difference between evidence and assertion.

One practical test: change a cell and look for the trace

Open your licence tracker, change an expiry date, and then try to find out what it said before and who changed it.

You cannot, which is fine for most operational data and is a different order of problem for a record concerning whether somebody was lawfully working. That single test is usually what settles the argument in this sector, more than any feature comparison.

• –Look for an audit trail before comparing features
• –Check whether the record is consulted at the point of rostering
• –Count how many copies are actually in circulation
• –Hold notifications, not just dates
• –Test what happens when the person who maintains it is away