Six IT policies staff can use in daily work
Define usable rules for sign-in, devices, applications, personal equipment, remote connections and public posts, with clear support and exception routes.

An IT policy should help a person decide what to do during ordinary work. A document saying only “use technology responsibly” leaves staff guessing about files, devices and unexpected requests.
Build the following six areas around the tools your business supports. Give each rule an owner, an example and a route for asking for an exception.
1. Sign-in and account recovery
Say where staff should store passwords, and cover unique credentials, multi-factor authentication and supported recovery methods. Explain how staff report an unexpected approval prompt or suspected compromise.
Use the Cyber Centre’s password guidance when setting requirements. It recommends passphrases of at least four words and 15 characters. Don’t copy an old template’s character-mix and scheduled-change rules without checking them against that guidance.
Give administrators a separate account for admin work, and keep a list of any shared accounts with an owner for each. Staff shouldn’t need to disclose a password to obtain routine support.
2. Acceptable use of devices and records
Explain where work records belong, how devices are secured and who applies updates. Cover shared workspaces, family access and reporting a lost device.
Write the policy to match available controls. A rule requiring encryption needs an owner who can verify encryption on the relevant devices.
3. Cloud services and applications
List the services staff can use and which information each may hold. Provide a review route for a new application, browser extension or AI tool.
Explain how a person can report a service they already use that isn’t on the list, along with the records it holds. Include a safe process for moving that information into one of the listed services.
4. Personal devices used for work
Define permitted devices, supported applications, expenses and the available company-device alternative. Explain management visibility, work-data removal and the process at departure.
The Privacy Commissioner’s workplace guidance explains that applicable obligations vary and that employee privacy continues at work. A signed policy doesn’t let you monitor or wipe personal information however you like.
Review the arrangement for your province, sector and employment context before using it.
5. Remote connections and public networks
Say how staff should connect to each service, including a business VPN where the system requires one. Include device updates, screen privacy and an alternative connection when a network looks suspicious.
Don’t tell staff a VPN makes a device, website or sign-in page safe. Explain what staff should do if they encounter a certificate warning or an unexpected login request.
6. Public posts and business social accounts
Identify who can speak for the business and who approves access to company accounts. Explain handling of customer information, photographs and confidential work visible in a background.
Keep incident reporting separate from public replies. A staff member needs a private route to report an account problem promptly.
Make the policies usable
Give staff brief instructions when a policy changes, and ask them to try the relevant task. Keep the current version easy to find.
Review support requests and exception records for rules people can’t follow with their current tools. IT consulting can help connect documented expectations with the systems and responsibilities needed to carry them out.


