An IT policy template is a fill-in document that sets the rules for how staff use company technology, and who owns, approves, and reviews those rules. The one below covers seven starter policies, with sample wording you can copy or download.
It comes from the team behind SherpaDesk, a helpdesk and professional services automation (PSA) tool a small IT team can run alone. Have a lawyer review the set before you adopt it, especially if you handle health, payment, or student data.
Key takeaways
An IT policy is a written set of rules for how people at your company use its accounts, devices, and data. NIST defines a policy as "a statement of objectives, rules, practices or regulations governing the activities of people within a certain context."
A policy says what must happen; a procedure says how. "Accounts are disabled when an employee leaves" is policy. The clicks that disable them belong in a procedure, which our guide to helpdesk SOPs covers.
CISA puts ownership in writing: "All roles and responsibilities involving cybersecurity should be documented in an organization's cybersecurity policy."
Some IT leads start from nothing. As one r/ITManagers member put it after stepping into a new IT role: "Coming into this position we had no formal policies, procedures, SOPs etc."
Start with seven areas, each tied to a familiar bad day: a shared password, a lost laptop, an account nobody disabled.
| Policy | What it settles | Primary source behind it | Usual owner |
|---|---|---|---|
| 1. Acceptable use | What company accounts, devices, and data may be used for | NIST asks whether you have acceptable use policies for business and employee-owned devices | IT lead, with HR |
| 2. Passwords and MFA | Length, storage, and where MFA is required | NIST SP 800-63B-4; CISA CPG 3.B and 3.F | IT lead |
| 3. Devices and BYOD | Encryption, screen locks, lost devices, personal phones | NIST: full-disk encryption on laptops | IT lead |
| 4. Access | Who gets which systems on joining, changing roles, and leaving | CISA CPG 3.D and 3.H | IT lead, with managers |
| 5. Data backup | What is backed up, where copies live, how restores are tested | CISA CPG 3.O | IT lead or MSP |
| 6. Incident reporting | What staff report, how, and how fast | CISA CPG 3.J; NIST Respond function | IT lead, with leadership |
| 7. Software requests | How a new app or AI tool gets approved | CISA CPG 3.P | IT lead, with finance |
Add remote-work, vendor-access, or data-retention rules now if your operations, data, or contracts call for them, and ask counsel which apply. A set of seven that people sign beats twenty that sit in a shared drive.
Section 0 of the template settles who is responsible before any rule appears.
Owner. One named person keeps the policies current and the exception log up to date. With one IT person, that's usually them.
Approver. The CEO, owner, or managing partner signs each version. Approval gives the rules weight, but it can turn into a queue. One solo IT manager described the bottleneck: "I'm having a hard time because she has to approve everything." Approve versions, not sentences.
Review. CISA's goal is that policies are "reviewed at least annually," then updated, communicated, and enforced as requirements, risks, threats, and technology change.
Acknowledgment. CISA says new employees should receive initial cybersecurity training "prior to accessing computer systems." The signature on the last page fits that moment.
Exceptions. Someone will need to break a rule for a good reason. Write it down. CISA's wording for passwords shows the pattern: where a minimum length isn't feasible, "compensating controls are applied and recorded."
Copy the block or download the TXT. Brackets mark what you fill in; bracketed numbers are starting values.
IT policy template · plain textSTARTER IT POLICIES FOR A SMALL BUSINESS
Draft to adapt, then review with your lawyer before adoption
Company: [legal name]
Applies to: employees, contractors, and interns who use
company accounts, devices, or data
Version: [1.0] Effective: [date]
Next review: [date, no more than 12 months away]
0. HOW THIS POLICY SET IS RUN
Policy owner: [name, role]. Keeps the policies current,
answers questions, and keeps the exception log.
Approver: [name; CEO, owner, or managing partner].
Signs each version before it takes effect.
Signature: ________________ Approval date: __________
Revision history and past versions: [location]
Review: at least once a year, and after a security
incident, a new core system, or a change in a law or
contract that affects us.
Acknowledgment: every user reads and signs this set
before getting access (existing staff by [date]), and
again after each new version.
Training: security training before first access and at
least once a year, assigned by the policy owner.
Exceptions: ask the policy owner in writing. Only
[the approver or the policy owner] may approve one.
Each gets the record below and an end date no more
than [90] days out. It ends then unless renewed.
Exception record: User or asset: ____ Rule: ____
Reason: ____ Safeguard: ____ Approver: ____
Granted: ____ Ends: ____
Violations: [reported to the user's manager and handled
under the employee handbook, section __].
1. ACCEPTABLE USE
1.1 Company accounts, devices, and data are for work.
Limited personal use is fine if it breaks no rule.
1.2 Never share your individually assigned work
accounts or passwords, not even with coworkers
or IT. Shared system accounts exist only where IT
lists them in the password manager.
1.3 Use only approved software, browser extensions,
and online services, AI tools included (section 7).
1.4 Keep [confidential data, e.g. client files, payroll,
health or student records] out of personal email,
personal cloud storage, and unapproved AI tools.
1.5 Verify each recipient first. Share confidential
data only with authorized recipients, through
[approved sharing tools], and encrypted where
[a contract, a law, or IT] requires.
1.6 Do not plug unknown USB drives or other media into
company devices.
1.7 The company may [monitor or log] use of its systems
as described in [handbook section]. [Counsel to
confirm this clause for every state we employ in.]
2. PASSWORDS AND MULTI-FACTOR AUTHENTICATION (MFA)
2.1 Passwords are at least [16] characters. Passphrases
are welcome. No other complexity rules apply.
2.2 Use a different password for every account, kept
in the approved password manager: [name].
2.3 Passwords change when there is a sign of compromise,
not on a schedule.
2.4 MFA is required on email, [accounting, payroll,
banking, remote access], every admin account, and
every other system that offers it.
2.5 MFA methods, strongest first: phishing-resistant
(security key or passkey); otherwise an
authenticator app, preferably push with number
matching; SMS or voice codes only when nothing
else is offered.
2.6 Default passwords are changed on every new device
or system before it goes into use.
3. DEVICES AND PERSONAL DEVICES (BYOD)
3.1 Company laptops have full-disk encryption, a screen
lock after [5] minutes, and automatic updates on.
3.2 Personal phones and computers may reach [email,
chat, calendar] only with a screen lock, current
updates, and [the app or browser rules IT names].
3.3 Personal devices do not store [confidential data]
outside approved apps.
3.4 Report a lost or stolen device holding company
data to [IT contact] at once.
3.5 By your end date, return company devices and remove
company accounts and data from personal devices
[with IT present, or IT removes them remotely].
4. ACCESS: JOINING, CHANGING ROLES, LEAVING
4.1 Access starts with a request from the user's manager
and covers only the systems the job needs.
4.2 Admin rights go to named people only, on a separate
admin account that is not used for email or browsing.
4.3 After a role change, access the user no longer needs
is removed within [5 business days].
4.4 When someone leaves, their accounts are disabled
at the end date and time agreed with [HR or the
manager], and shared system passwords they knew
are changed.
4.5 Accounts unused for [30] days are disabled.
4.6 Every quarter the policy owner reviews who can reach
[key systems] and records the result.
5. DATA BACKUP
5.1 Backed up: [file shares, accounting, Microsoft 365
or Google Workspace, line-of-business app].
5.2 Backups run at least [daily] and are kept for
[30] days.
5.3 At least one copy is offsite and offline, out of
reach of everyday admin accounts.
5.4 Restores are tested and the result is recorded:
[one file every quarter, one full system every
year]. Never less than once a year.
5.5 Backup owner: [name or provider].
6. INCIDENT REPORTING
6.1 Report at once, even if you are not sure: a link
you clicked in a strange email, a lost device, or
data sent to the wrong person.
6.2 How to report: [helpdesk email, portal, or phone].
After hours: [phone number].
6.3 Do not delete the email, wipe the device, or try a
fix yourself unless IT asks you to.
6.4 No one faces retaliation for a good-faith report,
including a report of their own mistake. The
underlying violation is still handled under the
employee handbook.
6.5 The policy owner decides who else must be told
under the security incident response plan at
[location].
7. SOFTWARE AND SERVICE REQUESTS
7.1 The approved list of software and online services
is kept at [location].
7.2 For anything else, free tools and AI services
included, send a request to [helpdesk email or
portal]: what it is, who needs it, what data it
will touch, and what it costs.
7.3 IT checks security, licensing, and data handling
and answers within [5 business days].
7.4 Approved tools join the list. A declined request
gets a reason and, where one exists, an approved
alternative.
ACKNOWLEDGMENT
I have read version [1.0] of these policies and agree to
follow them.
Name: ________________ Signature: ________________
Date: ________________
Name a person, not a team, as owner. Decide who may approve exceptions: the owner for small gaps, or the approver for anything that touches confidential data. Keep the exception log beside the policies.
In clause 1.4, name your confidential data in plain words. In 1.5, name the tools staff use to send it, such as an encrypted file-sharing link. Clause 1.7 on monitoring is the one to leave for your lawyer.
NIST, CISA, and the FTC set different minimums for different cases. NIST's digital identity guidelines set 15 characters for a password used alone and 8 when it's part of MFA. CISA's goal is 16 or more characters "when technically feasible."
The FTC tells small businesses "a strong password is at least 12 characters." The template starts at 16, which meets all three length recommendations. If a system can't take 16, record it as an exception.
NIST rules out composition rules and mandatory periodic password changes, and requires a change when there is evidence of compromise. Clauses 2.1 and 2.3 follow that.
Clause 2.5 follows CISA's order. Phishing-resistant MFA comes first. Otherwise, use an authenticator app, "preferably push notification with number matching." SMS or voice is used only "when no other options are possible."
For personal phones, list only the apps they may reach in 3.2. If IT will wipe company data remotely under 3.5, ask your lawyer about that clause.
CISA wants "a defined and enforced administrative process to off board staff," inactive accounts disabled after a set period, such as 30 days, and quarterly access reviews. In 4.4, agree the end date and time with HR, so a dismissal or a contract end is covered too. The steps live in our IT onboarding and offboarding checklist.
CISA's goal is to "securely store backups offsite and offline" and to test recovery on a schedule. Its small-business page is blunter: "It's critical to regularly test partial and full restores." If an MSP runs your backups, name it in 5.5 and ask for restore results in writing.
NIST asks you to list "what/when/how to report" as required by laws, regulations, contracts, or policies. Clause 6.4 protects anyone who reports in good faith, without excusing the violation itself. Restoring service after a report follows your incident management process. A suspected breach follows your security incident response plan.
CISA calls for review, testing, and approval before new software is installed, plus "a list of approved hardware, firmware, and software." Make the request easy. One r/ITManagers member said they made tool requests go through review "so people had a real path to yes."
A set of seven that people sign beats twenty that sit in a shared drive.
Example: Ridgeline Landscape Design has 40 staff, one IT lead, and an MSP that runs backups. Here's part of its filled-in set.
| Field | Filled in |
|---|---|
| Applies to | 38 employees, 2 contractors, summer interns |
| Version and dates | 1.0, effective January 5, 2027; existing staff sign by January 19, 2027; next review December 1, 2027 |
| Owner | Dana Ortiz, IT lead |
| Approved by | Sam Patel, managing partner; signed December 15, 2026; past versions in the policies folder |
| 2.1 Password length | 16 characters |
| 2.4 MFA required on | Email, QuickBooks Online, payroll, bank portal, VPN, all admin accounts |
| 5.4 Restore tests | One project folder every quarter; the full file server each June, done by the MSP |
| Exception record | User: Lee Wong, marketing. Rule: 1.3. Reason: a client requires its own proofing app for one campaign; that one app only. Safeguard: proofs only, no client contracts uploaded; MFA on. Granted: January 5, 2027. Approver: Sam Patel (touches client data). Ends: March 31, 2027 |
Subscribe to the SherpaDesk Blog.
Get Tips for Running IT With a Small Team.
Loading form…
The form couldn’t load. Please try again.
Or start your free trial →SHERPADESK · FREE TRIAL
Resolve tickets.
Turn time into revenue.
Bring support tickets, billable time, and invoicing into one place. Built for small IT teams and MSPs.
After your trial, keep your first agent free forever.
SHERPADESK · LIVE DEMO
See tickets, time,
and billing work together.
Walk through ticketing, time tracking, and billing with a product specialist. See how SherpaDesk fits the way your team works.
A live walkthrough tailored to your team.
Leave a bracket open rather than guess, then close it before approval. Walk two staff members through the draft and ask what is unclear or unworkable.
Common mistake: copying every rule from a 30-policy enterprise pack. Keep what you can enforce today.
Flag the monitoring clause, remote wipe, discipline, and any regulated data you hold.
Before signing, check four things. Every bracket is filled, and the handbook and response plan it cites exist.
The sign-by date for existing staff is set, and training is assigned. Set the review date at the same meeting.
One link, one current version.
Existing staff sign by the recorded date; new hires sign before access. CISA also asks for "at least annual cybersecurity training for all organizational users."
Give every exception an end date.
Common mistake: rules with no consequence. As one IT manager on r/ITManagers wrote, shadow IT can grow "when IT has governance, AUPs, processes, etc," if "there's no actual consequence for ignoring all of that."
If several people share IT work, our IT department structure guide gives each area one owner and a backup. MSPs writing these policies for clients can start with our MSP cybersecurity guide on scope.
How this works in SherpaDesk
You can use SherpaDesk as an internal ticketing system for your own staff. Publish each policy as a knowledgebase article at one of five publish levels. Each article keeps Logs, a dated change history.
You can attach public articles to a ticket reply; private ones don't appear in that search. The two public levels need no login, so keep sensitive policy text private.
Record requests and exceptions as tickets: forward your support address to SherpaDesk, and incoming emails become tickets. Link custom fields to a class, such as software requests, so the form shows only those fields. Routing rules can send that class to a specific technician, such as your IT policy owner.
A helpdesk and PSA a small IT team can run alone. No contract. No implementation project. No dedicated admin.
Base Camp is $45 per agent per month ($40 billed annually). The first agent is free, forever. You get 14 days free with no card.
Knowledge Base In SherpaDesk →
Who this isn't for
Companies that need a counsel-reviewed policy set for HIPAA, PCI DSS, or a SOC 2 audit. Start from that framework with your lawyer or auditor. A helpdesk keeps a policy findable; it doesn't make you compliant.
A policy states the rule and who owns it. A procedure gives the steps a technician follows to carry it out. Policies change rarely and need approval. Procedures change whenever a tool changes, so keep them in a separate document the IT team can edit.
NIST's CSF 2.0 Small Business Quick-Start Guide lists the governance actions and questions to answer. For templates, the Center for Internet Security offers 13 policy templates aligned to the CIS Controls, written for Implementation Group 1. SANS lists 36 free policy templates.
Written rules let you train and enforce without relying on memory. NIST's small-business guide asks whether you have acceptable use policies for business and employee-owned devices, and whether employees have been educated on them. A signed set also gives a new hire one clear document before first access.
Start from a short template, fill it in with the person who will own it, and cut any rule you can't enforce yet. Then get a lawyer's review and the approver's signature, publish one version, and collect signed acknowledgments. Close every bracket before the approver signs.
Mostly. A cybersecurity policy covers protection of systems and data, which is most of this set. Acceptable use and software requests also cover everyday work and spending. What matters is that each rule has an owner and a review date.
No. An IT policy is an internal rule set for staff. A website privacy policy is a public notice about the personal data you collect. Write it with your lawyer, and keep it consistent with the data rules in your IT policies.
Patrick co-founded SherpaDesk and has led it as CEO since 2013. He has worked with IT service providers since 1998, first on network projects for schools and government offices, then on the helpdesk software their technicians use every day.