AI workflow risk assessment template for a UK small business
A governance worksheet for defining purpose, information boundaries, possible harm, accountability and stop conditions before an AI pilot.
IF useful → CHECK boundary → HUMAN decision
Assess one defined use rather than AI in general
Checkpoint detail
Name the operational task, intended user, input category, output and decision that follows. ‘Use AI for customer service’ is too broad; ‘prepare a draft category for non-sensitive website enquiries before a person reads them’ can be examined. Record why assistance is being considered and whether a template, search rule or ordinary software could meet the need with less uncertainty. Assessment belongs to the specific purpose and configuration, not the product name alone. A provider can support both low-consequence drafting and unsuitable high-consequence decisions, so each use needs its own boundary and owner.
Describe error pathways and affected people
Checkpoint detail
Consider how an incorrect, invented, biased, incomplete or disclosed output could affect a customer, worker, supplier or the business. Distinguish a disposable internal draft from an output that changes eligibility, price, employment, health, safety, rights or access to a service. Identify who could notice each error and whether correction is realistic before harm occurs. High consequence, weak detectability or difficult reversal argues for manual handling or specialist review. Avoid converting ethical and operational questions into a comforting average score; preserve the individual red flags and the reason each matters.
Approve only a bounded and reversible pilot
Checkpoint detail
Use non-sensitive, representative material created for testing where possible. Specify success measures based on accuracy, reviewer effort, error types and operational fit rather than assumed savings. State a small volume, duration, authorised users, access settings and deletion plan. Stop immediately for prohibited information, repeated material errors, unexplained output, security concerns or reviewer overload. Record incidents and changes to provider terms or models. A completed template supports a manual, assist, bounded-pilot or stop decision; it is not legal advice, a data protection impact assessment determination or a security certification.
Classify information before selecting a provider
Checkpoint detail
List information categories, not real records: public business material, routine internal text, personal data, special category data, confidential commercial material, credentials or regulated records. Apply data minimisation and identify material that must never enter the proposed workflow. If personal data may be processed, determine the controller and processor roles, lawful basis, transparency needs, retention, access, international transfers and applicable provider terms with appropriate specialists. This template prompts those questions but does not decide legal compliance. Do not paste examples containing customer, employee or confidential information into an assessment worksheet.
Make human review a real control
Checkpoint detail
Name the reviewer, evidence available to them, time allowed and authority to reject or correct the output. A person clicking approve without source access or sufficient expertise is not meaningful oversight. Define which outputs require line-by-line checking, which may be sampled, and which are excluded entirely. Prevent automation bias by making uncertainty and source references visible where the tool supports them. Training, workload and escalation routes matter. The accountable owner should understand the workflow well enough to stop it; responsibility cannot be delegated to a model or hidden behind a vendor interface.
Practical control-register
AI use risk and control register
Complete one register for one purpose and retain red flags as separate decisions rather than averaging them away.