Skip to content

Responsible AI resourceMenuHomeModel policyDecisionsResearch & approachGet support

Leadership guide/Operations & assurance

Operations & assurance

Risk and approval

What exactly are we authorizing?

Download the guide↓Editable working records→

In this guidePurpose and responsibilityWhat to put in placeA campus exampleDecide locallyYour working recordPolicy and sourcesThe arrangement to establish.

Classify the use in its actual setting. The same tool can support routine drafting or a consequential decision. A vendor subscription is not approval for every possible use.

Responsible roles: Service owner with the responsible approval authority and specialist reviewers.

Leave with: A scoped approval with conditions, an owner and a review date.

What to put in place.

Describe the complete use

Record the purpose, people affected, tool and model, information sources, connected systems, intended outputs and any actions the system can take. Include AI already embedded in existing services.

Screen for consequences

Ask whether an error could affect admission, financial aid, employment, grades, health, safety, access to a service or a person's rights. Consider scale, vulnerable groups, sensitive information, difficulty of correction and the ability to act without a person.

Choose the review route

Routine assistance within an already approved tool, information class and use may follow ordinary staff or faculty authority. New institutional deployments, protected information or integrations need the appropriate operational review. Consequential uses and autonomous actions need the designated institutional authority plus relevant specialists before a live pilot.

Separate experimentation from live service

Use an isolated test environment and authorized test information. Use synthetic information where suitable and check that it does not reproduce personal records. Keep production credentials and actions disabled. A pilot with real people or records needs its own scoped approval.

Record the decision

Approve, approve a bounded pilot, request changes or decline. Name the conditions, prohibited actions, human reviewer, expiry or review date, stop authority and evidence needed for wider use. Legal or institutional prohibitions cannot be waived through a risk acceptance form.

Test it with a real situation.

Illustrative campus example

An admissions team may draft a public event invitation with an approved tool under ordinary rules. Ranking applicants changes the review route because it can affect opportunity. Connecting the system to send decisions or change records adds further authority that must be separately considered.

Make the arrangements yours.

Take a record into the work.

Use the editable companion to capture the decision in your institution’s own systems. These prompts are also available in the printable guide.

Purpose and scope

Identify the use, owner, people affected, systems, data and intended benefit.

Risk and review route

Record the consequential effects, action authority, review category and the reasons for it.

Conditions and evidence

List permitted and prohibited uses, specialist findings, unresolved issues and pilot limits.

Approval and renewal

Record the decision, authorized approver, stop authority, review date and change triggers.

Download the working records→

Connect policy to practice.

Model policy: Section 3 · Section 4 · Section 6 · Section 9.

HumanSkills implementation recommendations informed by the sources below. These voluntary resources are not legal requirements or a certification. Apply current institutional requirements and specialist review to the actual use.

Explore the other operating guides→