Software security for HR and leave data: a plain-English guide for small businesses without an HR team
By the Redstone HR team · Published
Subscribe to our newsletter
Read about our privacy policy.
For a small business, software security for HR and leave data comes down to two questions: how safe is your staff data where it lives today, and how can you check a supplier's answers before you move it? In many small businesses the bigger risk is not new software at all. It is a holiday spreadsheet, a chain of emails and a tray of paper forms that nobody fully controls.
This guide is for the office manager, operations lead or founder who looks after annual leave alongside everything else. It explains where the real risks sit, what to ask any leave or HR software supplier, and which responsibilities stay with you whatever tool you use.
What does software security mean when you're choosing HR or leave software?
When you are buying HR or leave software, software security means how well a supplier protects your staff's personal data, and how well you can prove that it does. Staff names, holiday entitlement, sickness absence and family leave are all personal data. In many small businesses that data is scattered across files and inboxes with no clear owner.
Most of what you find when you search for software security is written for developers building software: secure coding, threat modelling and testing frameworks. That material is useful to suppliers, but it does not help a practice manager deciding where to keep the team's holiday requests.
A more useful way to frame the question for a small business is:
- How safe is our staff data where it lives today?
- If we move it into a tool, what would we ask the supplier, and how would we check the answers?
- Which parts of keeping that data safe and lawful stay with us?
Why is a holiday spreadsheet often the bigger security risk?
A holiday spreadsheet is often the bigger security risk because it gets copied, emailed and edited by several people, so there is no single trusted record and no reliable history of changes. In most small organisations, leave is handled by someone with a full job already, and it ends up spread across a spreadsheet, email threads and paper forms that drift apart.
The weak points of a spreadsheet-and-email setup are familiar to anyone who has managed one:
- Copies multiply. The file is emailed to a manager, saved to a desktop, attached to a payroll email. Each copy is another place staff data sits, and you rarely know who still has one.
- Versions disagree. Two people update different copies, and nobody is sure which balance is right.
- There is no clear history. If someone changes a balance, there is usually no record of who did it, when or why.
- Paper sits in trays. Holiday request forms and sick notes wait on desks or in folders that anyone passing can read.
The hidden cost is accuracy as well as security. When the spreadsheet, the emails and the forms no longer agree, balances are wrong, payroll gets corrected after the fact and staff dispute what they are owed. That is an accuracy problem and a trust problem at the same time.
This is not only a UK concern. According to Kazee, writing on 5 November 2026 about employers in Kenya, spreadsheets often fail over time, with hidden leave, lost history and disputes when staff leave or ask about their balances. The legal detail differs by country, but the pattern is the same for any small business keeping leave in a spreadsheet.
What kinds of staff data does leave software hold, and why is some of it sensitive?
Leave software holds a mix of everyday and sensitive staff data, so the first security decision is who needs to see which parts of it. The main categories are:
- Names and contact details for every employee.
- Holiday entitlement and balances, including carryover.
- Holiday request history: what was requested, approved or declined, and by whom.
- Sickness absence records, which can relate to someone's health.
- Absence scores such as the Bradford Factor, which weight frequent short absences.
- Family leave records, such as maternity, paternity or adoption leave.
Sickness and family leave records deserve the most care because they can reveal personal circumstances. Family leave rules also vary widely by country, as this guide to how paid maternity leave differs between countries shows, so records may carry details that differ for staff in different places.
Before you choose any tool, write down who actually needs to see each type of data. A common starting point is that each employee sees their own balance and requests, each manager sees their own team, and only one or two people see sickness details for everyone. Then check whether a tool can match that, rather than accepting whatever its defaults are.
Is cloud HR software safe for a small business?
Cloud HR software is not automatically safer or riskier than a spreadsheet; what matters is encryption, access control, where records are kept and whether the supplier can evidence its answers. The useful comparison is what each approach controls for you and what it leaves to you.
Approach What it controls for you What it leaves to you Local spreadsheet Very little: it is a file on one computer Backups, access, version control, change history, getting copies back Shared drive spreadsheet One location and basic file permissions Who edits what, change history, stopping copies being downloaded and emailed Full HR suite Access roles, records and audit trails across many HR tasks Setting it up correctly, paying for features a 1–50 person team may not need, often priced per user Focused cloud leave software One record for requests, approvals and balances, with access by role Configuring rules correctly, checking the supplier's security answers, managing who has logins
For most small businesses, the security gain from moving off a spreadsheet comes from having one record rather than many copies, and from people logging in to see what they need instead of being sent a file. For a wider look at the trade-offs, see the benefits and considerations of cloud HR software.
Which security features should you ask about: encryption, two-factor authentication and single sign-on?
The three security features worth asking every supplier about are encryption, two-factor authentication and single sign-on, because together they cover how data is protected and how people log in.
Encryption at rest and in transit
Encryption scrambles data so it cannot be read without a key. "In transit" means data is encrypted as it travels between someone's browser and the supplier's servers, so it cannot be read if intercepted. "At rest" means data is encrypted where it is stored, so a stolen disk or backup is not readable. Ask for both.
Two-factor authentication
Two-factor authentication (2FA) asks for a second check, such as a code on a phone, as well as a password. It matters for HR systems because managers approve holiday requests from wherever they are, and a reused or guessed password should not be enough to open the team's records. Here is more on what two-factor authentication means for HR systems.
Single sign-on
Single sign-on (SSO) lets staff log in with an account you already manage, such as Google Workspace or a Microsoft account. When someone leaves, switching off that one account removes their access everywhere, which is easier than remembering every system they used. See how single sign-on works for HR systems.
Ask each supplier directly whether it offers 2FA and SSO today, and on which plans. Do not assume either is included.
What about GDPR, and who is responsible for compliance if you use leave software?
The employer remains responsible for compliance, whatever software you use. Leave software applies the rules you configure, so you still need to check those rules match your contracts and the law, including holiday entitlement and bank holidays.
That applies to data protection too. Choosing a supplier that follows GDPR requirements helps, but you still decide what data you collect, who can see it and how long you keep it.
When you speak to a supplier, ask:
- Do you follow GDPR requirements?
- Is data encrypted at rest and in transit?
- Can you provide security documentation or a security review?
- On which plans is that documentation available?
As an example of the kind of answer to expect, Redstone HR states that it uses encryption at rest and in transit, follows GDPR requirements, and can provide a security review for Enterprise customers. Answers that specific are easy to check and compare. Vague answers such as "bank-level security" are not.
Do AI features in HR software change the security picture?
AI features change the security picture only in that they raise fair questions about what data the assistant can see and where its answers come from. An AI assistant that answers staff questions about annual leave, or one that summarises documents, is handling information about your people and your policies.
Useful questions to ask a supplier:
- What data can the assistant see: just the policy, or individual employee records too?
- Do its answers come from the leave policy you have configured, or from general information?
- Can an employee only get answers about their own balance, not a colleague's?
- Is the AI included in your plan, or an extra?
If you want background first, this article on how AI-powered HR tools work in practice covers the main uses.
How do you check a vendor's security answers without a formal RFP?
You can check a vendor's security answers without a formal request for proposal by sending every supplier the same one-page list of questions and asking them to mark each answer "live today" or "planned". A formal RFP is usually overkill for a 1–50 person team, and the one-page list gives you most of the benefit in a fraction of the time.
A one-page security list for leave software might include:
- Is data encrypted at rest and in transit?
- Do you follow GDPR requirements?
- Do you offer two-factor authentication or single sign-on, and on which plans?
- Can we control who sees what: employees, managers and administrators?
- Is there a history of changes to balances and approvals?
- How do we export our data, and in what formats?
- Is there a minimum contract, and how do we leave?
- Is a security review or security documentation available?
The "live today" or "planned" label matters because suppliers often describe roadmap features in the same breath as working ones. Redstone HR, for instance, states that direct payroll integrations are planned, and that what is available now is payroll-ready exports in CSV, Excel or PDF. It also states there are no long-term contracts. That is the level of plainness to expect from any supplier on your shortlist.
Does your sector face stricter expectations on security and records?
Some sectors face stricter expectations because clients, regulators, funders or auditors ask to see accurate absence records and a clear trail of who approved what. Healthcare, financial services and security services are common examples.
In these sectors, two things help most:
- Audit-ready central records. One record of every request, approval and balance, instead of figures pieced together from three sources.
- Exportable absence history. Being able to produce leave and absence figures, including Bradford Factor scores where relevant, as a CSV, Excel or PDF file when someone asks.
If you run a guarding or security firm, see leave management for security services firms for how these needs play out with shift-based teams.
Self-assessment: how secure is the way you manage leave today?
A short self-assessment shows whether your risk sits in the process or the tool. Answer yes or no to each question:
- Is there one record of leave that everyone trusts?
- Do you know everyone who can open the holiday spreadsheet, and everyone who has a copy?
- Is there a history of who changed a balance, and when?
- Are sick notes and holiday request forms kept somewhere other than paper trays and email inboxes?
- Can staff check their own balance without someone sending them a file?
- Could you produce accurate leave figures for payroll in minutes?
- If someone left tomorrow, would their leave history and final balance be clear?
- Do your configured leave rules, including holiday entitlement and bank holidays, match your contracts?
If you answered "no" to several of these, the risk is in the process, not just the tool. Tidying the spreadsheet or adding another reconciliation step moves the same checking and correcting onto someone who already has a full job.
The better approach is one trusted record in which the checks happen as part of each decision. Managers see who else is off before approving, balances update automatically, and staff look up their own holiday entitlement, so data is not copied between files and the person in charge only handles genuine exceptions.
Next step: work through your own setup
Start with the self-assessment above and run it against your current holiday spreadsheet, emails and forms. Then use the one-page vendor list with every supplier on your shortlist, including Redstone HR, and compare the "live today" answers side by side.
If you would like to talk through how your small business handles leave data, you can get in touch through the Redstone HR website.
Frequently asked questions
Is a holiday spreadsheet less secure than leave software?
Often, yes, because a holiday spreadsheet gets copied and emailed, has no reliable history of changes and leaves no single trusted record. Leave software is only better if the supplier can show encryption, access control by role and a clear change history.
Who is responsible for compliance if a small business uses leave software?
The employer remains responsible for compliance. Leave software applies the rules you configure, so you still need to check that holiday entitlement, bank holidays and data handling match your contracts and the law.
What security questions should I ask a leave software supplier?
Ask whether data is encrypted at rest and in transit, whether the supplier follows GDPR requirements, whether it offers two-factor authentication or single sign-on, who can see what, how you export your data and whether a security review is available. Ask the supplier to mark each answer 'live today' or 'planned'.
Does a small business need a formal RFP to choose HR software?
A formal request for proposal is usually overkill for a 1–50 person team. Sending every supplier the same one-page list of questions, marked 'live today' or 'planned', gives you most of the benefit.
Is sickness absence data more sensitive than holiday data?
Yes, sickness absence and family leave records can reveal someone's health or personal circumstances, so fewer people should see them. Decide who needs access to each type of data before choosing a tool.
Keep reading
What is a Form 16? A plain-English guide for small businesses, including how Part A and Part B are generated
What is a Form 16? A plain-English guide to what it certifies, how Parts A and B are generated, and why accurate leave records keep the figures right.
What are software vendors? The questions a small business should ask HR software vendors before buying leave software
What are software vendors, and what should a small business ask before buying leave software? The questions that expose cost, cover and set-up gaps.
Sandwich Leave Policy: How to Handle Holiday Requests Around Weekends and Bank Holidays Without Leaving Your Small Business Short-Staffed
How a sandwich leave policy treats weekends and bank holidays, and how a small business can stop holiday requests leaving it short-staffed.
Leave Management Case Study: How a Small Business Stops Overlapping Annual Leave Leaving It Short-Staffed
A leave management case study for small businesses: why overlapping annual leave leaves you short-staffed, why spreadsheets fail, and what fixes it.
Free tools: Holiday entitlement calculator · Bradford Factor calculator · Free leave templates · Leave law guides · HR glossary
