AI governance: common problems
What are the most common AI governance problems?
The most common AI governance problem is that staff are already using AI tools before any policy exists. Client data gets pasted into public chatbots, and nobody owns the output. The second is confusing AI governance with data or cyber governance: they overlap, but they answer different questions.
ISO/IEC 27001:2022 and ISO/IEC 42001:2023 certified (as at 12 May 2026). Founded in Christchurch in 2005.
Or call 0800 242 206
How an AI governance engagement runs
Four steps, and nothing is proposed before step three is done.
- A 15 minute founder call to check fit.
- A 45 minute discovery call on what data you hold and where staff already use AI tools, sanctioned or not.
- A Cyber Risk Assessment to find the gaps that exist, not the ones a template assumes.
- A proposal built on what was found. The common path is the AI 90 Day Governance Project, which ends with one AI use case live and documented.
We do not build the AI tool or model itself. That is separate work, and we say so at the proposal stage. Cost depends on the size and complexity of the organisation, and sits on the AI governance cost page.
Staff already using AI tools before any policy exists
Someone in accounts pastes numbers into ChatGPT to draft a report. A manager uses Copilot to summarise meeting notes. Nobody asked permission, because nobody realised they needed to. It is rarely recklessness: free tools are one click away, so a client name or a customer’s personal details end up in a public tool without anyone deciding that should happen. The assessment looks at four things first:
- Which tools staff already use, including free consumer versions
- What kind of data gets typed or pasted into them
- Whether Microsoft 365 or Copilot access is licensed but ungoverned
- Where a written policy is missing, and where one exists but nobody follows it
Locking everything down overnight pushes staff onto personal devices, which is worse for oversight. The aim is rules staff can follow. Our AI governance page walks through the structure.
AI governance versus data and cyber governance
Cyber governance protects the systems and data you already have. It sits under ISO/IEC 27001:2022 and the SMB1001 framework, and answers one question: is your data and network protected?
AI governance sits under ISO/IEC 42001:2023 and answers a different one: can you show, in writing, how a specific AI use case was assessed, approved and put into use? A business can have solid firewalls and multi-factor authentication and still have no record of which teams feed client data into a chatbot.
If no cyber security foundation work has been done, get that assessed first. Governance documentation on top of an unpatched network or shared logins does not hold up under a client audit, an insurer or an SMB1001 review. The order matters, and we will say so rather than sell the AI project on its own.
What you walk away with
A lot of AI governance talk stays abstract, all frameworks and no output. Ours ends with a documented, live AI use case, not a slide deck in a shared drive.
- Documentation and a decision process for one AI use case, taken live within the 90 day project
- A risk review showing where AI tools touch customer data, who has access, and what happens if a model gets something wrong in front of a client
- A record that stands up to a client audit, an insurer or an SMB1001 certification review
Related reading: what a cyber security audit tests, SMB1001 certification and our licensing, insurance and credentials.
Frequently asked questions
Do we need AI governance if only a couple of staff use AI tools casually?
Usually, yes. Casual use is where gaps start, like someone pasting client details into a public AI tool without a rule against it.
Is a written AI policy the same thing as AI governance?
No. A policy is a document. AI governance is the process behind it: the risk review and documentation that show how a use case was assessed and approved, audit ready under ISO/IEC 42001:2023.
Does a smaller business need the same 90 day project as a larger one?
The timeline is the same, but the size and complexity of the organisation decides how much work it covers. More approval layers means more groundwork.
Will this slow down our team?
No. The goal is one use case live with proper documentation, not extra layers of approval on everyday work. We do not build, replace or switch off your AI tools.
Talk to a founder about AI governance
Fifteen minutes with a founder, not a sales rep. We will ask what your staff are already using and tell you plainly whether governance work is the right next step.
Or call 0800 242 206