A charter before the first decision
AI Council and Steering Committee Setup
Establish an AI management forum with a clear mandate, membership, delegation, quorum and conflict rules, using a practical charter structure.
An AI council becomes useful when people know which decisions it can make and why it exists. A committee created only to “oversee AI” can overlap with investment, technology, risk and executive forums while leaving important questions unresolved. Setup should begin with a mandate and delegation, then membership and working arrangements.
This guide is for the executive sponsor establishing an AI management council or steering committee. It provides a charter structure and a worked authority example. Once the forum exists, its recurring intake, agenda and decision records belong in the separate AI steering committee operating model.
Decide whether a new forum is necessary
List the decisions that currently lack a reliable home: priorities across business units, shared specialist capacity, release exceptions, service ownership or unresolved trade-offs. Check whether an existing executive or technology forum already has the authority and competence to decide them. Expanding an existing mandate may be simpler than creating another committee.
A council and a steering committee can be different bodies, but their names alone do not establish different purposes. If both exist, specify their distinct outputs and the direction of delegation. For a modest portfolio, one management forum with clear boundaries may be sufficient.
The NIST AI RMF Govern guidance calls for clear documented responsibilities and communication lines. The charter below is an original way to implement that management discipline, not a legal requirement to form a particular committee.
Secure a mandate from the appropriate authority
The committee cannot grant itself powers that belong to the board, an executive or another delegated body. Identify who establishes it and the existing delegation under which it acts. Record the relationship with risk, audit, finance and technology governance.
Keep management decisions separate from matters reserved for the board. The forum may prepare recommendations and evidence for directors without becoming the board's substitute. A committee vote cannot override an applicable legal requirement or another function's defined authority.
State the forum's purpose as an outcome. For example: “Coordinate the AI portfolio within approved strategy, funding and risk boundaries, assign accountable service ownership, and resolve cross-functional decisions within delegated authority.” This is more precise than a mandate to promote AI everywhere.
Build the charter around explicit clauses
| Clause | Decision to document |
|---|---|
| Purpose and scope | Portfolio, entities, lifecycle stages and decisions covered |
| Authority source | Establishing authority, delegation reference and limits |
| Reserved and delegated matters | What the committee decides, recommends, escalates or leaves to service owners |
| Membership | Chair, standing members, specialist participants, deputies and secretary |
| Decision conditions | Required participation, evidence, quorum and handling of disagreement |
| Conflicts and confidentiality | Disclosure, recusal, access to papers and handling of sensitive evidence |
| Reporting and records | Recipient of decisions, record owner and escalation obligations |
| Review and closure | Mandate review triggers and conditions for changing or ending the forum |
Complete the clauses with the organisation's actual roles and authority. Avoid signing a template whose budget limits, escalation routes or decision rights remain unresolved. If a clause depends on another policy, identify the current reference and owner instead of copying text that will become inconsistent.
Select members for decisions, not representation alone
The chair should have enough authority to resolve cross-functional priorities and enough attention to prepare for decisions. This could be a COO, CIO, transformation leader or another authorised executive. Choose the role from the mandate rather than assuming that AI must always sit under one title.
Standing membership should cover business outcomes, technology and data, resources and risk. Invite specialists when the decision requires their expertise. For example, a privacy question needs the relevant privacy owner; a workforce change needs the responsible people leader. Every interested department does not need a permanent vote.
Assign a secretary who maintains the charter, records decisions and checks that submissions reach the correct authority. This is substantive coordination work and needs capacity. Name deputies and state whether they carry the member's full decision authority or attend only to provide information.
Define decision rights in plain language
Use a decision schedule rather than relying on a broad responsibility matrix. It should identify the decision, proposer, required contributors, final authority and escalation condition. The AI operating model provides the surrounding service and platform responsibilities.
| Decision | Committee role | Boundary |
|---|---|---|
| Sequence approved initiatives competing for specialists | Decide within delegated portfolio authority | Do not exceed approved funding or override reserved commitments |
| Expand a service's action authority | Review or recommend according to delegation | Require affected owners and relevant control evidence |
| Accept a material residual risk | Decide only where expressly authorised | Escalate beyond tolerance or delegated authority |
| Change enterprise risk appetite | Recommend to the appropriate authority | No self-issued expansion of the committee's mandate |
| Perform a routine approved source update | Receive reporting only when needed | Leave operational execution with the service owner |
Document any specialist consent required by the organisation's rules. A majority vote does not resolve a missing privacy determination or security acceptance where another owner holds that decision. Conversely, an advisory comment should not become an informal veto unless the authority has been assigned.
Set quorum and conflict rules that protect the decision
A headcount-only quorum can allow a technically valid meeting to make an uninformed decision. Define required roles for the decision type. An illustrative rule might require the chair or authorised deputy, the affected business owner and the relevant risk or control owner for a release exception. This is a design example, not a universal minimum.
Specify how dissent is recorded and escalated. The chair should distinguish disagreement about evidence from disagreement about priorities. Missing evidence may require deferral; a legitimate trade-off within authority may require a decision with recorded reasons.
Suppliers and advisers can provide evidence but should disclose interests in the outcome. For a procurement recommendation, define whether an interested adviser leaves the decision discussion or acts only as a technical contributor. Procurement evidence should follow the vendor due diligence process, with selection responsibility retained by the buyer.
Test the charter with a fictional decision
Suppose a Saudi group has two approved initiatives competing for one evaluation specialist. The commercial director wants a quotation assistant first; operations wants a service-triage assistant. The committee's mandate permits sequencing within an approved portfolio but does not permit additional funding.
The forum can decide the order after examining business urgency, readiness and dependencies. It cannot promise a second specialist without the required resource approval. If the commercial proposal also seeks a higher action limit, that is a separate decision with different contributors and evidence. Combining both requests under “approve the project” would obscure the authority boundary.
Run this rehearsal before the first formal meeting. Ask whether the charter identifies who proposes, who advises, who decides and who receives the outcome. If participants give different answers, revise the charter before relying on it.
Launch with a limited initial remit and a review point
Adopt the charter through the appropriate authority, appoint members, brief them on the evidence they will receive and explain the route to service owners. Connect material risk decisions to the risk register and the broader AI governance process.
After the first operating cycle, review whether the forum resolved decisions or duplicated other bodies. Adjust membership, delegation or scope where evidence supports a change. The aim is a durable decision mechanism that the organisation can explain, rather than a permanent meeting whose original purpose has been forgotten.
Open for AI's agentic AI consulting can help map authority and prioritised use cases. Bring your existing delegation, committee map and two unresolved decisions to discuss an AI council charter with clear authority.
FAQ
Your questions, answered.
Do we need both an AI council and an AI steering committee?
Only if they have distinct decisions and outputs. Define the direction of delegation and the boundary between strategy, portfolio coordination and operational decisions. For a smaller portfolio, one existing or newly mandated forum may be sufficient. Two names do not justify two approval layers over the same work.
Who should chair an AI management committee?
Choose the executive role with authority over the decisions in its mandate and capacity to prepare and follow through. That may be a business, technology or transformation leader. The chair should resolve cross-functional trade-offs without claiming powers reserved for the board or other authorised owners.
Should every department have a permanent seat?
Not necessarily. Keep standing membership aligned with recurring decisions and invite specialists for relevant matters. Define who must participate for each decision type. Permanent attendance without a decision role can make the forum slow, while missing a necessary control owner can make its conclusions unreliable.
Can the committee approve any AI risk by majority vote?
No. Its authority comes from the organisation's delegation and applicable requirements. Identify reserved matters and specialist decisions that cannot be replaced by a general vote. Record dissent and escalate issues outside the mandate. A charter should make these boundaries clear before a contentious case reaches the meeting.
How should advisers with delivery interests participate?
Require disclosure of the relevant interest and define their role for the decision. They may provide technical evidence while the buyer retains selection and acceptance authority. For sensitive procurement decisions, use appropriate recusal or separate challenge. Record the arrangement so participants and later reviewers understand the potential conflict.
What should be agreed before the first committee meeting?
Approve the mandate, delegation, membership, decision conditions, conflict rules and reporting route. Test the charter on realistic decisions to expose ambiguity. A first meeting should use an agreed authority structure, rather than attempting to decide its own powers while simultaneously approving a consequential project.