Quarterly AI governance desk

The decision on your calendar.

A decision file ages when the vendor, source, model instruction or permission changes. Your team needs to know which declared tests and decisions need another review.

Bring the sources you are allowed to share.

• The retained decision baseline
• Approved source or feature updates
• Declared relationships to tests and decisions
• Customer reviewers and an agreed review cadence

The file your institution keeps.

• A supplied-change register
• Affected declared tests and decisions
• An assigned reviewer queue
• An updated file after customer review
• A retained review history and export

Four working steps.

1. Agree the questionOne workflow, permitted inputs, accountable owner and the decision due.
2. Prepare the sourcesKeep versions, missing records and assumptions visible.
3. Review the evidenceRetain failed cases. Your team reviews the proposed answer and open questions.
4. Leave the fileA one-page recommendation, supporting records and named next actions.

Your team owns review and acceptance.

This is a proposed managed service. Workload, cadence, permitted sources, customer review and fee require agreement. Connected retrieval, live monitoring and reminders are not operating features.

Timing depends on agreed inputs and customer review. Corrections within the agreed scope are recorded in the file; a new use or workflow requires a new scope.

Inspect the method.

Inspect the local refresh method. Browser methods work on supplied inputs or inspectable examples.

Scope and fee.

Scope and fee fixed in writing after one working session. The written scope names the sources, customer review responsibilities, deliverables and corrections included.