Everything that goes into your AI governance framework

A breakdown of what's inside the Core AI Policy Framework, and what each add-on actually includes.

Inside the Core AI Policy Framework

This is the foundation document every engagement is built around, structured so your team can actually follow it day to day.

Acceptable use policy

What AI tools are approved, what tasks they can be used for, and what's explicitly off-limits, written in plain language rather than legal boilerplate.

Data classification and handling

A simple classification of what counts as sensitive, confidential, or public data, and rules for what can and can't be shared with an AI tool at each level.

Third-party AI tool approval process

A defined workflow for how a new AI tool gets reviewed and approved (or rejected), including who owns the decision and how long it should take.

Model and output risk guidance

Practical guidance on checking AI-generated output for accuracy, bias, and appropriateness before it's used in a client-facing or decision-making context.

Incident response procedure

A clear, short procedure for what happens if an AI tool mishandles or exposes data, including who is notified and what the immediate steps are.

Roles and ownership

Who in your company owns AI governance day to day, what decisions they can make alone, and when something needs to be escalated.

Training and awareness plan

A lightweight plan for making sure the team actually knows the policy exists and understands the parts relevant to their role.

Review and audit cadence

A schedule for revisiting the framework as your AI stack, team, and the regulatory environment change, so it doesn't quietly go out of date.

How the rest of the engagement works

Customisation

The framework mapped specifically to your business rather than left generic, so it reflects how your company actually operates.

  • Mapped to your specific product and data flows
  • Aligned to your existing compliance stack (SOC 2, ISO 27001)
  • Referenced against DPDP and, where relevant, RBI expectations
  • Written in your company's tone and terminology

Team workshop

A live working session with your team to walk through the framework, answer real questions, and build genuine buy-in before rollout.

  • A structured session, typically 60 to 90 minutes
  • Walkthrough of the framework section by section
  • Open floor for team questions and edge cases
  • A short summary sent afterwards for anyone who missed it

Ongoing retainer

Regular check-ins so the framework keeps up with your company instead of sitting unused in a drawer after month one.

  • Quarterly review of the framework against your current AI stack
  • Updates as regulation or guidance changes
  • Review of any new AI tools before they're approved
  • Priority access for questions between reviews

See how this comes together for you

Most engagements start with a short call to understand your AI stack before anything is drafted.