Run AI pilot with safe test data: Approve input boundary: use invented examples or cleared material only; Rehearse route to result: save every step, including retries and reviewer decisions; Report findings: compare outcomes against acceptance rules and current processes
Image: AI Tool Review Desk

Pilot Programs

Part of AI procurement and pilot programmes

Running an AI tool pilot with non-sensitive test data

Set an input boundary, rehearse the full workflow and report what a non-sensitive AI pilot can establish.

Run a non-sensitive AI pilot as a controlled rehearsal of the proposed work. Approve the inputs and account, keep every attempt, and check whether staff can reach an acceptable result through the planned review and handover. The exercise can expose workflow problems without sending customer or confidential records to an unapproved service.

Approve the input boundary

Record the account, feature, users and permitted inputs. Use invented examples or material specifically cleared for this exercise. Inspect the complete prompt, attachment, screenshot and connected source before submission.

Removing a name may leave details that identify a person. Do not connect a live drive or inbox merely to make the pilot easier.

A business account may have different terms and settings. Check the actual route before using cleared business material; fictional content alone does not make an account suitable for every later use.

Rehearse the route to an approved result

Choose a task with a person able to judge the output. For a fictional supplier enquiry, provide an approved information sheet and invented enquiries, including a routine request, a missing detail and an exception. Define what a reviewer may accept, correct or send to a person before running them.

For each case, save the input version, product, account, feature, settings, date, first response, retries, reviewer decision and repair work. Follow the result to the destination ordinary work would use. Count copying, checking and re-entry. If the tool can propose an external action, keep that action behind an approved review point during the exercise.

Observation / Record

Result
Accepted, corrected, rejected or unresolved, with the reason
Human work
Preparation, checking, correction and handover
Exception
Missing information, refusal, error or unsupported claim
Process fit
Whether the right person could finish the item

Report what the exercise establishes

Compare the completed cases with the preset acceptance rule and a comparable current process. Keep awkward and failed cases. Note whether a problem came from the tool, source material, account limit or handover design, since each calls for a different response.

State the finding for the cases and conditions used. Invented examples may reveal whether instructions, review and handover work together. They may miss features of live work and do not authorise use of personal or confidential records. If the next stage requires those records, assess the intended account, agreement and data flow, and obtain the relevant internal approvals before expanding the pilot.

More from Pilot Programs