SUPERWISE services · Step 5 of 7

AI governance and controls

Give every AI use an owner, an approval path, and controls people can actually run.
$20,000 to $50,0004 to 8 weeks

What you walk away with

  • AI acceptable-use policy
  • AI use-case inventory
  • Risk and controls register
  • Approval and change workflow

Where this fits

Step 5 on the services path

Each step answers the question the last one raised. Start wherever the assessment points you.

  1. Govern and run

    AI governance and controls

Why it matters

What changes for your team

As AI use grows, your people work to one clear set of rules, every use has a named owner, and leaders get evidence they can review.

People know what is allowed

Staff can tell which AI uses are approved, what data they may use and when to stop and ask, so nobody has to guess.

Every decision has an owner

Business, technology, legal and compliance share one approval path, so decisions get made instead of passed between teams.

Leadership can see the risk

Executives and the board get a regular view of active use cases, exceptions, control status and the decisions that need them.

How it works

Three stages, with your team in the room

4 to 8 weeks

Week 1

Know which AI uses and obligations are in scope, who decides and how approvals work today.

Weeks 2–4

Get the rules in writing: the policy, the controls, the risk records and who owns what.

Weeks 5–8

Prove the process on a real use case, train its owners and give leaders board-ready reporting.

The details

Everything you need to decide

Price, fit, your team’s time, how data is handled, and what you keep.

Price and scope

Draft pricing for review: we confirm a fixed scope and price after a scoping call.

TierPrice rangeDurationIncluded
Service$20,000 to $50,0004 to 8 weeksAI policy and approval workflow

Not included

  • Certification, attestation or a guarantee that the organization complies with a law or framework
  • Legal advice or a ruling on which legal requirements apply
  • External audit, certification-body or regulator fees
  • Software and product subscriptions
  • Running approvals, controls, registers or reporting after handover
  • More than five use cases, or more business units, unless they are added to the scope
Is this the right starting point?

Good fit if

  • For teams that need policies, ownership, controls, and reporting that people can actually operate.
  • Teams of 50 to 500 people putting AI into regular use
  • You want a defined handover your team keeps.
What you keep

AI acceptable-use policy

A plain-language policy on approved uses, prohibited data, human review, exceptions and staff responsibilities. It gives staff one answer, and you update it as tools, risks and business needs change.

AI use-case inventory

A working register of the AI uses in scope, with their purpose, owners, data, users and approval state. Use it to see what is running, find unowned uses and choose what to review first.

Risk and controls register

For up to five use cases, a record linking each risk to its preventive, runtime and follow-up controls and their evidence. Use it to check that controls work and to show why a use case was approved, restricted or stopped.

Approval and change workflow

An intake, review, exception and change process with decision criteria and required records. Requests reach a documented decision without a new process for every tool or project.

RACI and escalation path

A map of who recommends, approves, operates, reviews and receives escalations. Routine decisions and urgent issues go straight to the right person.

Leadership reporting pack

A board and executive template for use-case status, material risks, exceptions, control performance and decisions due. Use it to run consistent oversight meetings and keep a record of leadership review.

Governance operating guide

The review calendar, meeting inputs, evidence checklist, document owners and instructions for keeping the framework current. It keeps the program running after handover, so the policy is not a one-time document.
What your team gives

Plan for about 6 to 10 hours across the client team in a typical week, with more time during workflow testing and final approval.

Executive sponsor

Sets the business objective, settles ownership questions and approves the final operating model.About 1 hour per week

Governance or compliance owner

Coordinates documents, workshops, reviews and the people who will run the process.About 3 to 5 hours per week

Business and technical owners

Explain the selected use cases, data, systems, risks and current controls, then test the workflow.About 1 to 2 hours per owner during relevant weeks

Legal adviser

Decides which laws, duties and contract terms apply, and reviews policy wording where needed.About 1 hour during policy and framework reviews
Data, security, and ownership
  • We agree the systems, documents, and use cases in scope before access is provided, and use client-controlled access wherever possible.
  • We ask for the minimum access needed and do not need production credentials when documents, interviews, or a limited environment answer the question.
  • The governance design states what activity and decision evidence must be retained; the client decides its legal retention requirements with its advisers.
  • Sentinel applies configured policies and records metadata for the supported AI tools listed on its page. Prompt and response content stays private.

SUPERWISE signs a Business Associate Agreement with healthcare customers, and the scope is confirmed during scoping. See the trust center.

You own the policy set, inventory, registers, workflows, templates, decisions and operating guide. If you stop working with us, they stay yours, and your named owners can keep the process running without a SUPERWISE services contract.

The engagement closes with a handover and the review calendar in your operating guide. Teams that need to test readiness against a named framework usually move to AI compliance readiness. Teams that want ongoing control operation and reporting can scope Managed AI operations under a separate service agreement.

Examples and how we measure success

These are examples of suitable work, not claims about past client engagements.

Staff already use ChatGPT or Claude

Set acceptable-use rules for public AI tools, name the data that is off limits and give staff a clear way to request an exception.

A client asks for your AI policy

An approved policy, ownership model and current control register give your team a ready answer.

The board wants AI oversight

A reporting pack shows the use-case inventory, material risks, exceptions, control status and decisions due.

A regulated workflow is moving beyond a pilot

Map its risks and controls, name the approvers, set the evidence to keep, and test the change and escalation process.

Departments buy AI tools separately

One intake and approval workflow reviews every new tool against the same risk questions before anyone uses it.

Measures we agree at kickoff

  • Every in-scope use case has a named business owner and an approval state.
  • The team runs a real use case through intake, approval, exception and escalation.
  • Each in-scope risk links to an owner, a control and the evidence used to review it.
  • Staff can find the approved-use and prohibited-data rules without relying on an informal answer.
  • Leadership can run a review from the reporting pack and see the decisions due.
Who delivers the work

No case study of this exact governance engagement is published yet. The nearest published example is Renova Health, where SUPERWISE supports managed AI operations; the services team also runs managed AI operations for Boca Raton Regional Hospital. Both are ongoing operations work, and neither organization is presented as a buyer of this governance package.

AI governance and controls questions

What to expect before you start

Talk to us

Talk to our team

Tell us about your team and we will scope ai governance and controls with you.

Tools in scope (required)