What are your staff actually allowed to do on their work devices? For plenty of businesses in Basildon, that question might not have a clear and obvious answer.
In those businesses, people make reasonable guesses. It could be someone signing up for a free tool using their work email and usual password or forwarding a client list to their personal inbox to finish at home. There’s no ill intention behind these decisions; they’re just getting on with their job.
Then one of those everyday choices goes wrong, and everyone asks the same question: what were they actually allowed to do? Usually, nobody ever wrote it down, because there was never an acceptable use policy to agree to in the first place.
Rules for Everything Except the Tech
Most businesses have a staff handbook for things like dress code, booking time off, and what counts as misconduct. Somewhere in an induction pack, every new starter is handed the rules for how the place works.
What they rarely get is the equivalent for technology: the laptop, the email account, the phone, the logins. These are the tools they’ll use every hour of every working day. The rules for those tend to go unwritten, passed on by assumption, or never spelt out at all.
The government’s own research bears this out. Just over a third of UK businesses (36%) have formal cyber security policies in place. An acceptable use policy is only one slice of that. A handbook sets the standard for how people behave at work; an acceptable use policy does the same job for how they use the technology.
What Does an Acceptable Use Policy Cover?
A good acceptable use policy is a clear list of what’s expected, covering the handful of areas where a wrong guess does the most damage.
- Devices and data: Which devices people can use for work, what they’re allowed to install, whether data can be copied onto a USB stick or taken home, and how company information should be handled day to day.
- Email and messaging: How to spot a dodgy message, what should never be sent to an external or personal address, and why work accounts shouldn’t be used to sign up for random services. This is the big one: phishing is still the most common attack on UK businesses, reaching 38% of them in the past year, and the inbox is where most of it starts.
- Passwords and access: No sharing logins, no reusing the same password everywhere, and turning on multi-factor authentication wherever it’s offered. Simple rules that quietly prevent a lot of problems.
- Personal use and personal devices: Where reasonable personal use ends, and what happens when someone uses their own phone or laptop for work. If staff do use their own kit, this is where a BYOD policy sets the ground rules, so a personal device doesn’t become an unlocked back door into the business.
- Leavers: Removing access, returning equipment, and closing down accounts, ideally before someone’s last day rather than weeks after it.
Together, these make up the acceptable use side of your wider IT security policy: the part that deals with how people, as well as software, can keep the business safe.
Good People Still Have to Guess
When this comes up, the honest objection is usually some version of “we trust our people”. And that’s fair enough. Most teams are made up of sensible, careful people who’d never knowingly put the business at risk.
But trust isn’t really the question in this case. An acceptable use policy doesn’t exist because you think someone might act maliciously. It exists because, without one, everyone is left to guess, and even careful people guess differently.
There are two ways a team ends up getting technology right.
- One is that every person independently lands on the same sensible answer every time, with nobody having ever spelt it out.
- The other is that it’s written down, so no one has to guess in the first place.
One of those is far more dependable than the other.
Putting the rules in writing isn’t a sign you don’t trust your team; it’s how you give them a fair shot at getting it right.
What Does a Good Acceptable Use Policy Look Like?
A good acceptable use policy is short. If it runs too long, nobody reads it. And if nobody reads a rule, is it really a rule in the first place? One or two pages of plain English do more than a dense document ever will.
It’s specific to how you work, too. A template pulled off the internet is a starting point, not a finished policy. The useful version reflects your real tools and the things that would genuinely cause you a problem.
Then there’s the part most businesses skip: making sure people have actually read it and agreed to it. A policy sitting unopened in a shared drive isn’t in force; it’s just a file. The fix is a quick sign-off when someone joins and again whenever it changes, so there’s a record of who agreed to what. That admin is easy to let slide, which is why our Virtual IT Department handles policy distribution and sign-off for the businesses we look after, so it actually happens.
And it’s reviewed. The tools people use change fast, and a policy written three years ago won’t mention half of them, from new apps to AI tools. A yearly once-over keeps it honest.
Not Sure What Your Staff Have Actually Agreed To?
If you can’t quite answer that, you’re in good company; plenty of businesses can’t. The good news is that finding out where you stand is quick, and there’s nothing to commit to. We’ll look at what you’ve already got, point out any gaps, and help you put something simple in writing if it’s worth doing. Get in touch with us and we’ll gladly take a look.
FAQs
What’s the difference between an acceptable use policy and an IT security policy?
The IT security policy is the bigger document, covering how the business protects its systems and data overall. An acceptable use policy is the people-facing part of it: the plain-English rules for what staff can and can’t do on company devices, email and accounts. It’s the bit your team actually signs.
Do small businesses really need an acceptable use policy?
Yes, often more than larger ones. Bigger firms have IT staff and processes to catch a risky decision; smaller businesses rarely do, so the written rules take on that job. A page or two that everyone has read and agreed to covers most of the risk.
What should a BYOD policy cover?
BYOD means “bring your own device”: staff using their own phones or laptops for work. The essentials are a screen lock and up-to-date software on anything that touches company data, work kept separate from personal use, and a way to remove company access if the device is lost or the person leaves.
How often should you review your IT policies?
At least once a year, and whenever something significant changes, like a new system or the arrival of AI tools. Policies written a couple of years ago often miss the tools people now use daily. A short annual review keeps them worth following.