Essential cookies only, Cookie Policy.

Policy

Writing a Password Policy for a Small Business

Writing a Password Policy for a Small Business | Work Password, key points at a glance
Writing a Password Policy for a Small Business | Work Password, key points at a glance
📅 30 Apr 2026·⏱ 8 min·✍ Rachel Morris

A password policy is a documented statement of your organisation's requirements for credential management. For most SMEs it is a one-to-two-page document that belongs in the staff handbook, the security policy, or both. Writing one is neither difficult nor time-consuming, but skipping it creates gaps in Cyber Essentials compliance, complicates insurance claims after incidents, and leaves staff without clear expectations.

What to Include

A complete SME password policy covers six areas:

  1. Scope: Which accounts and systems this policy applies to (all company accounts, cloud services, shared systems)
  2. Password requirements: Generated by the company password manager; minimum length; no personal information; unique per system
  3. Password manager: Which tool is designated, that all staff must use it for work credentials, how to get access
  4. MFA requirements: Which accounts require MFA and the accepted methods
  5. Change requirements: When passwords must be changed (on security concern, on a service breach notification, not on a fixed schedule)
  6. Prohibited actions: Sharing credentials, writing in plaintext, reusing personal passwords, emailing credentials

Drafting It in an Afternoon

A password policy does not need to be a lengthy document. For most small businesses, a clear, one-page set of rules is far more useful than a sprawling framework that nobody reads. You can get a working draft together in a single sitting by following a straightforward sequence.

Once you have a draft, circulate it to staff with a brief explanation of why the policy exists. Understanding the reasoning makes people far more likely to follow it.

Enforcing It Without Friction

A policy that frustrates staff will quietly be ignored. The aim is to set rules that are firm but practical, and to build enforcement into normal working habits rather than treating it as a separate discipline.

Set a review cycle and stick to it. Reviewing the policy once a year is usually sufficient for a small business, unless you take on new software, experience a security incident, or significantly change how your team works. Put a recurring reminder in your calendar so the review actually happens.

Be clear about what happens when the policy is breached. Staff need to know what is expected of them if they share a password, reuse credentials across accounts, or lose a device. The response does not need to be punitive, but it should be consistent and documented.

Keep the policy current. Remove references to systems you no longer use, and add guidance whenever you introduce new tools. An outdated policy creates confusion about what actually applies. Treat it as a living document rather than something filed away after first publication.

Finally, make the policy easy to find. Staff cannot follow rules they have to hunt for. Keep a copy somewhere accessible, such as your company intranet or a shared drive folder that everyone can reach.

What to Avoid

Use the Policy Builder: The Work Password Policy Builder generates a ready-to-copy policy paragraph based on your chosen settings, including Cyber Essentials compliance status for each configuration.
password policy SME documentation Cyber Essentials HR
For informational purposes only. Consult a qualified IT security professional for advice specific to your organisation.
Affiliate disclosure: This page contains affiliate links. If you purchase through these links, we earn a commission at no extra cost to you.

⚡ Try NordPass, Get NordPass at 56% off + 3 months extra and experience enterprise-grade password security at an affordable price. Features include zero-knowledge encryption, cross-platform sync, and breach monitoring.