Skip to main content

    Executive tool

    AI compliance checklist: the questions an AI review must answer

    Use this checklist to organise a selected AI workflow for review. It helps identify evidence and responsibility. It does not determine which laws apply or certify compliance.

    Define the review boundary

    Record the entity, purpose, workflow, system version, affected people and included information. Name the business owner and specialist reviewers.

    List exclusions and unknowns. Without a defined population, 'review complete' has no clear meaning.

    Working checklist

    AreaQuestion to resolveEvidence to consider
    ApplicabilityWhich legal, contractual and internal requirements apply?Scoped specialist assessment and basis
    PurposeWhy is the use needed and what may it do?Limits set on the use and its approved purpose
    InformationWhat is collected, used, generated, shared and retained?Information-flow map and product-specific terms
    Affected decisionsHow does the program influence outcomes about people?Workflow, inputs, outputs and the human role in practice
    Fairness and qualityWhat material errors or unequal outcomes need assessment?Representative evaluation and specialist analysis
    SecurityWhat can the system access or change?Implemented permissions, testing and response arrangements
    Claims and communicationsWhat is said to users and customers?Reviewed wording and substantiation
    Intellectual propertyWhat rights support inputs and intended outputs?Licences, permissions and relevant legal review
    VendorsWhich dependencies and processing arrangements matter?Contracts, what each service covers and evidence of how you would leave each vendor
    OperationWho monitors, changes, interrupts and retires the use?Named owners and tested operating procedures

    Not every row establishes a mandatory legal obligation for every use. The reviewer must distinguish law, guidance, contract and internal practice.

    Add an evidence status

    Give each row one of these statuses:

    • supported within scope
    • action required
    • not assessed
    • not applicable with reason.

    Record who made the judgement and on what basis.

    Do not convert 'not assessed' into 'compliant'. Do not call an uncertainty a breach without assessment.

    Assign the next action

    For each unresolved question, name the evidence needed, owner and review date. Identify decisions that cannot proceed until a material issue is resolved.

    Changes in purpose, information, model, tools or permissions can require a new assessment. Completion is not permanent approval for every future configuration.

    Copy the checklist, assign an owner to each area and set review dates. Bring the rows you cannot resolve.

    Resolve a business problem