
AI governance and responsible-use policy
Your staff are already using generative AI. Governance decides which tools are allowed, what data can go into them, who approves new uses and how leadership keeps oversight. We build that framework in documents your leadership can actually sign.
Reviewed by the ITRS security team · Last updated
This page is general information, not legal advice. For advice on your obligations, speak with your lawyer.
AI governance is the set of rules that decides which AI tools staff may use, what data may go into them, who approves new uses and how leadership keeps oversight. IT Rapid Support writes that framework, from discovery of the tools already in use to policies leadership can sign.
Why AI needs governance now
Canada's federal, provincial and territorial privacy commissioners have published nine principles covering the development, provision and use of generative AI: legal authority and consent, appropriate purposes, necessity and proportionality, openness, accountability, individual access, limiting collection, accuracy and safeguards. They also point to privacy impact assessments. An AI governance policy turns those principles into rules staff can follow.
Generative AI arrived in most workplaces without a project plan. It is built into Microsoft 365, Google Workspace, meeting tools, CRMs and browsers, and free consumer tools are a click away. That creates real exposure: client or patient information pasted into a public chatbot, AI-generated text sent to clients without review, meeting transcripts stored where nobody expected, and automated decisions about people that no one can explain.
Canadian regulators have signalled their expectations. In December 2023 the federal, provincial and territorial privacy commissioners published Principles for responsible, trustworthy and privacy-protective generative AI technologies, which apply existing privacy principles such as legal authority and consent, appropriate purposes, necessity and proportionality, openness, accountability and safeguards to organizations that develop and use generative AI. Quebec's private-sector law already requires organizations to inform people when a decision about them is based exclusively on automated processing. Governance is how you show you have thought about these issues before something goes wrong.
Inventory: which AI tools are already in use
We start by finding out what is really happening. That means reviewing sign-in and app-consent records in Microsoft Entra ID or Google Workspace, web and network logs where available, browser extensions, and the AI features switched on inside the software you already license, then confirming it with a short staff survey. The result is a register of AI tools and uses, each with an owner, the data involved and the business purpose.
Risk tiers and approval workflow
Not every use needs a committee. We set up tiers so low-risk uses move quickly and high-risk ones get proper review:
| Tier | Typical uses | Approval |
|---|---|---|
Low | Drafting internal text, summarizing public material, with no personal or confidential data | Allowed with approved tools under the policy |
Medium | Using internal confidential data inside an enterprise tool with contractual data protections | Business owner plus IT sign-off |
High | Personal or sensitive information, client deliverables, anything that affects decisions about people | Formal AI risk assessment and leadership approval |
Prohibited | Uses the policy rules out, such as entering client data into consumer tools | Not permitted |
Policy: acceptable use, data rules and human review
The acceptable-use policy is the document every employee reads. We keep it short and specific: approved tools, the categories of data that may never be entered, when output must be reviewed by a qualified person before use, labelling of AI-assisted work where clients or regulators expect it, and how to request a new tool. Behind it sits a governance standard for leadership that covers roles, the approval process, record-keeping and incident handling.
Oversight, logging and review cadence
Governance only works if someone checks. We align oversight with the four functions of the NIST AI Risk Management Framework (Govern, Map, Measure, Manage), released in January 2023, scaled to the size of your organization. In practice that means: an accountable executive; an AI register reviewed on a set schedule; audit logging switched on for enterprise AI tools where the platform supports it; retention settings for AI interactions that match your records policy; and a simple route for staff to report AI errors or misuse. Where you want to go further, ISO/IEC 42001 provides a certifiable management-system structure, and Canada's voluntary code of conduct for advanced generative AI systems describes expectations for developers and managers of those systems.
Deliverables
AI governance work is scoped in writing before work starts. Fees are quoted per engagement. The technical rollout of Microsoft Copilot is a separate engagement, covered on our Copilot readiness page.
- AI tool and use register, with owners and data categories
- Risk-tier model and approval workflow
- Staff acceptable-use policy (plain language, two to four pages)
- Leadership governance standard with roles and review cadence
- Configuration notes for logging, retention and access settings in your AI tools
- A one-page briefing for the board or partners
Frequently asked questions
Governance scales down. For a small organization the whole framework can be a two-page staff policy, a one-page register and a named person who approves new tools. The point is that decisions are made deliberately and written down, not that you build a bureaucracy.
Blocking everything usually pushes staff to personal phones and accounts, where you have no visibility at all. A better pattern is to approve one or two enterprise tools with proper data protections, block or restrict the consumer tools that create the most risk, and make the approved route easy to use.
Whatever the status of dedicated AI legislation, existing privacy laws, sector rules and professional obligations already apply to how you use AI, and Quebec's private-sector law has specific rules on decisions based exclusively on automated processing. Ask counsel which rules apply to your sector today.
It depends on the number of tools in use and how many people need to be consulted. We scope the work in writing after an initial conversation, so you know the deliverables and the estimate before anything starts.
Related work.
- Case studyFrom Breach Forensics to a Company-Wide Identity PlanFrom reconstructing a 2018 mailbox compromise minute by minute to scoping centralized Entra ID and Intune management for a 40 to 50 person pharma firm.
- Case studyEmail Authentication for a Vaughan Smart-Home IntegratorHow IT Rapid Support audited a Vaughan smart-home integrator's email authentication and implemented DKIM and DMARC to shut down domain spoofing.
Related.
- PracticePrivacy, Data Governance & AIPIPEDA and Quebec Law 25 readiness, data mapping, breach notification and AI governance.
- ServiceVendor privacy and security reviewsYour vendors hold your data, connect to your systems and can be the way an attacker gets in.
- ServiceAI tool risk assessmentsBefore a new AI tool touches client, patient or employee data, someone should check where that data goes, whether it trains the vendor's models, how long it is kept and…
- ServiceMicrosoft Copilot readiness and secure AI deploymentsMicrosoft 365 Copilot can find anything a user has permission to open. In most tenants, that is far more than anyone intends.
- GuideAI acceptable use policy: what to includeStaff are already using generative AI tools. A short, clear acceptable use policy tells them which tools are approved, what information must never go in, who is…
Not sure what your obligations require of your systems?
Speak with our privacy practice. We are staffed 24/7. Active incident? Call (289) 582-9930, 24/7.
