Agree
Confirm the objective, authority, systems, criteria, access and exclusions. Establish how information will be shared and handled.
Govern / New Zealand
ISO 42001 AI governance
Aegentra helps New Zealand organisations develop an AI management system, connecting intended uses, responsibilities, risk decisions and evidence. The work starts with the AI systems you develop, provide or use and the people affected by them.
On this page
Start with the boundary
Define the work that is needed.
For organisations adopting AI, formalising oversight of existing use cases or preparing an AI management system for independent assessment.
- AI use inventory, scope and organisational roles
- AI risk and impact-assessment processes
- Governance, human oversight and supplier responsibilities
- Monitoring, change control and management review
Keep the responsibilities distinct
An AIMS is not proof that every AI output is accurate, safe or legally compliant. Model testing, privacy advice and sector-specific legal assessments may need separate specialist scopes.
What the engagement can produce
Useful outputs, agreed in advance.
- A scoped AIMS implementation plan
- Assigned accountability and AI decision records
- Prioritised governance and control workstreams
- Evidence and improvement actions for the agreed scope
Service pricing is provided by scoped quote, not the Academy’s per-learner course prices. The proposal identifies deliverables, assumptions, exclusions, responsibilities and commercial terms. No fixed price or completion date is promised before the scope is understood.
How we work
From evidence to a practical next step.
Examine
Gather the records and context required by the scope. Distinguish what evidence supports from what is still uncertain.
Act or report
Carry out the agreed consulting, audit, assessment or implementation task. Obtain approval before operational changes.
Verify and hand over
Document outcomes, limitations, owners and follow-up. Retesting or ongoing work is included only when expressly scoped.
We deliver online and arrange visits by appointment where agreed. Scope, assigned competence, timing, access requirements and any travel are confirmed before an engagement.
An illustrative starting point
What a useful first decision looks like.
Fictional example to explain the service, not a New Zealand client case study or a promised outcome.
A business introduces an AI assistant in several teams. The tool is the same, but the information it accesses and the decisions it supports differ. Governance needs to follow those actual uses rather than a single generic AI policy.
Questions for the first discussion
- Which AI systems and intended uses are involved?
- Do you develop, supply or use the systems?
- Who can approve deployment, changes and escalation?
Before you begin
Your questions, answered.
Do we need to build AI models to use ISO 42001?
No. ISO/IEC 42001 can be relevant to organisations using AI as well as developing or providing it. The appropriate scope and responsibilities depend on your role and systems. We clarify those before proposing an implementation plan.
What can be included in iso 42001 ai governance?
The agreed scope can include aI use inventory, scope and organisational roles; aI risk and impact-assessment processes; governance, human oversight and supplier responsibilities; monitoring, change control and management review. We confirm the exact deliverables and exclusions before work begins, rather than treating every organisation as the same project.
How much does this service cost?
Service pricing is provided by scoped quote, not the Academy’s per-learner course prices. The proposal identifies deliverables, assumptions, exclusions, responsibilities and commercial terms. No fixed price or completion date is promised before the scope is understood.
How do you deliver the work in New Zealand?
We deliver online and arrange visits by appointment where agreed. Scope, assigned competence, timing, access requirements and any travel are confirmed before an engagement.
What should we provide before a proposal?
Bring answers to these starting questions: Which AI systems and intended uses are involved? Do you develop, supply or use the systems? Who can approve deployment, changes and escalation? A short initial discussion should establish the boundary and next evidence needed. Do not email secrets or detailed personal records before secure handling has been agreed.
Reference points
Check the underlying guidance.
Page prepared and source references checked . References explain the relevant standard or technology; they are not endorsements of Aegentra.
Discuss your requirement
Start with your business.
Start with the requirement, the systems involved and the outcome you need. Please do not send passwords, sensitive records or unrestricted tenant access in an initial enquiry.