What an AI governance charter is and why it differs from a standing policy
A general institutional AI policy is typically issued unilaterally by university administration and can be revised without negotiation. An AI governance charter embedded in a faculty union collective bargaining agreement works differently. It is negotiated between the institution and the bargaining unit, and its terms carry the enforceability of the labor contract itself. Once ratified, charter provisions are not guidance faculty can choose to follow; they are contractual commitments both parties are obligated to honor for the term of the agreement.
In practice, a charter of this kind typically addresses four areas: notification requirements when AI tools are introduced or changed, limits on how faculty and student data may be used, appeal rights for decisions influenced by AI, and a mechanism for joint oversight, usually a labor-management committee with representation from both the union and the administration.
Charter versus general institutional policy. Unilateral policies can be rewritten by administration alone. Charter language is bargained, ratified, and enforceable through the grievance and arbitration pathways of the collective bargaining agreement for the life of the contract.
Core elements of an AI governance charter
Most faculty-union charters converge on a small set of commitments. Each commitment is contractual text first; technical systems become relevant only when the institution must demonstrate ongoing compliance.
-
Notification terms
Faculty must be informed when an AI tool is introduced or changed.
-
Data use limits
Restrictions on using faculty or student data for training or analysis.
-
Appeal rights
A process for contesting decisions influenced by AI in grading or assessment.
-
Joint oversight
A labor-management committee responsible for administering the charter.
-
Enforcement mapping
Translation of negotiated terms into access controls and audit logging.
Joint oversight committees and their practical limits
Charters commonly reference a joint committee, composed of union and administration representatives, as the body responsible for administering the agreement's AI provisions. The committee's authority and composition vary by institution and are defined in the specific contract language rather than by any universal template.
A recurring operational question is whether this committee has direct technical visibility into system logs and access records, or whether it depends on periodic manual reporting from IT or academic administration. A committee limited to manual reporting can only review what it is given. A committee with log or dashboard access can independently verify compliance. This distinction affects whether the charter's enforceability rests on institutional self-reporting or on direct evidence, and it is a negotiated and architectural decision rather than a purely technical one.
Common gaps when implementing a charter
Contract language alone does not close these gaps. They appear when negotiated obligations have no corresponding process or system control:
- Notification obligations exist in contract language but no communication mechanism reaches bargaining unit members when tools change.
- Data use restrictions are written but not enforced by access controls or data classification at the system level.
- Audit logs lack sufficient granularity, such as user, timestamp, and model version, to support an appeal filed months later.
- Log retention periods are not defined, so records may not exist by the time an appeal is filed.
- No single unit owns both the negotiated text and the technical controls, since labor relations, IT, and academic administration each hold part of the responsibility.
Mapping charter commitments to technical controls
Enforcement depends on linking each negotiated provision to a concrete control. The mapping below is a practical inventory model for labor relations, IT, and academic administration working from a ratified charter.
Practical next steps for implementation teams
Translating a ratified charter into operational practice typically requires collaboration across labor relations or HR, IT and security, and academic administration, since no single group owns both the negotiated language and the systems that must enforce it. A practical starting point is to inventory each charter provision and identify the specific control, if any, that currently supports it: an access permission, a logging pipeline, a retention policy, or a manual process.
Where a provision has no corresponding control, that gap should be documented and assigned to a responsible party before the next bargaining cycle, since unresolved gaps tend to resurface as disputes during renegotiation. Institutions evaluating tools to support this work should look for role-based access controls that reflect the boundaries defined in the charter, audit logging detailed enough to support appeals, and a runtime policy enforcement layer that applies data use restrictions automatically rather than relying on manual compliance by individual instructors or departments.