Skip to main content
Boermans Digital
Main menu

WorksheetAutomation

Prepare an AI or automation pilot: the checklist

Start an AI or automation pilot with one specific question: which task do you want to improve, what should the trial demonstrate and who will review the result? Use this checklist to define scope, test data, checks and open agreements.

Checklist to prepare an AI or automation trial.

Continue with a saved file

Choose a saved pilot, trial log or handoff JSON file. The helper checks its type on this device and opens the matching existing preview. Nothing is uploaded or applied automatically.

You can also use the separate Open buttons: Pilot · Trial log · Handoff note. Without JavaScript, use the text downloads at those sections.

Is the trial boundary clear?

Identify the question, the start and finish, and excluded cases. State whether the trial only prepares suggestions or also changes records. Expanding the scope requires another assessment of risk, tests and authority.

What should an AI trial test?

Suppose a team member uses AI to draft an answer to a product question. Define which questions and sources are in scope. Use permitted examples, fictional where appropriate, and agree in advance what a good answer must contain.

  • Normal question: the draft must agree with the chosen, up-to-date source.
  • Missing information: the draft must not present an invented detail as fact. The reviewer must be able to identify what is still needed.
  • Conflicting sources or an out-of-scope question: a person investigates the difference or takes over the task.

Compare the work before and during the trial, including source checks and corrections. Agree which errors mean stopping and who decides whether to continue testing. A completed worksheet does not prove that AI is suitable or that the application is ready for use.

Explore an AI trial with human review or discuss the preparation needed for your AI question.

Are data and access arrangements agreed?

Check who may use test data and where it may be processed. Use appropriate, permitted samples and restrict permissions to the necessary actions. A shared account without an owner obscures responsibility. Decide who removes access when the trial ends.

Are expected outcomes defined?

Choose ordinary cases and recognisable exceptions. Include repeated requests, missing information and interruptions where relevant. Have a process owner define the correct handling in advance. Otherwise you may only test whether the technology performs an action.

Who decides, using which evidence?

Agree acceptable quality and remaining human effort. A single error percentage without considering consequences is insufficient. Identify conditions that require an immediate pause and who must authorise resumption.

Can the process be stopped in a controlled way?

Describe how to locate work in progress and how people can continue. Falling back is not always a matter of restarting the old task: changes may already have occurred. Establish the current state before taking action and prevent duplicate effects.

Do unresolved items have owners?

Assign an owner and follow-up action to each open agreement. Include cover during absence and an evaluation point. Unknown is a useful status when someone is responsible for investigating it. Use the checklist to support a substantive decision, not to grant permission automatically once boxes are ticked.

Use a saved process canvas as a starting point

Open a saved canvas or a proposed pilot file with Open saved worksheet below. Review which information will be used. By default only blank fields are filled; your existing texts and rows marked described/recorded stay unchanged. Replace everything is a separate choice.

Canvas context is a starting point, not permission, acceptance criteria or approval. Transferred canvas items are always open for discussion. Access, stopping, recovery and operations still need separate agreements.

Boermans Digital / WorksheetPilot checklist
[ ]

Question, scope and excluded cases

Owner / open action:

[ ]

Owner and reviewers

Owner / open action:

[ ]

Test data, permission and processing location

Owner / open action:

[ ]

Accounts, least privilege and access removal

Owner / open action:

[ ]

Ordinary cases, exceptions and expected outcomes

Owner / open action:

[ ]

Acceptance criteria, measurements and decision owner

Owner / open action:

[ ]

Stop conditions, resumption and authorised owner

Owner / open action:

[ ]

Fallback, duplicate effects and work in progress

Owner / open action:

[ ]

Maintenance, absence cover and evaluation

Owner / open action:

Record only necessary process information. Leave out personal data, passwords and confidential customer details.

What would you like to clarify?

Back to the workflow overview

Describe the process step or open question. We can explore a practical next step together.

Discuss your process

Explore your process with the Automation Scan

Trial log and proposed evaluation

Back to the workflow overview

For the MFT chain, use K-01 and six fictional cases. Record receipt, validation and processing separately. An unknown processing state requires investigation before any resend; the evaluation does not authorise recovery. Download K-01 · MFT route

For AI draft replies, choose the AI draft trial and use the fictional source TEST-H1. Prepare drafts in an approved application or with a template; this worksheet generates no replies and sends nothing. A reviewer checks the source, missing information and commitments before any sending outside the trial. Download TEST-H1 and instruction

Prepare cases from the pilot above, agree expected outcomes and record observations separately. Choose a proposed evaluation only after reviewing evidence. No result or financial saving is inferred from completed fields.

Use references and role names. Keep customer details, personal data and credentials out of the log. Everything stays in this tab unless you download a file.

Evaluation: assess the trial evidence

Back to the workflow overview

First prepare or open a trial log above and confirm its preview. Without JavaScript, use the blank text evaluation.

Prepare or open a trial log · Blank evaluation (text)

From trial findings to a follow-up question

Back to the workflow overview

Prepare a compact handoff note. Choose what matters; the full log, reviewer names and pilot agreements are not included automatically. Review and edit the proposal before sharing. Nothing is sent.

Start by preparing a trial log above. You can also reopen a saved handoff independently. Changes to the trial do not change an existing note.

A v4.20 note opens with its existing text preserved and an empty follow-up block. Saving uses file version 2; reopen it in v4.21 or later. Replacing a note with a new proposal also replaces its follow-up response.

Follow-up: response and remaining questions

Back to the workflow overview

First prepare or open a handoff note and confirm its preview. Without JavaScript, use the text note with follow-up block.

Prepare or open a handoff note · Blank handoff with follow-up (text)

Download blank handoff note (text). You can use this without JavaScript. Save JSON to reopen the interactive note; text is a readable export. There is no automatic storage, upload or contact-form transfer.

Prefer a file or paper? Use the blank logs and evaluation note. Order log · Invoice log · Blank evaluation note (text)

Boermans Digital / privacy

Your cookie preferences

You decide whether Google Analytics may load. The website, scans and calculator also work without Analytics.

Completed fields, scan answers and calculator results are not sent to Analytics.

Which data and retention periods?

We remember your choice on this device for up to 180 days, including a refusal. The _ga and _ga_* Analytics cookies are configured for up to 180 days. Retention at Google is configured separately in the Analytics account.

Storage for website functionsFunctional

The website remembers your privacy choice. Only when you choose to switch language can scans, the guide and calculator temporarily carry answers within the same tab. Contact details are not stored in that transfer.

Contact form protectionAt request review

Google reCAPTCHA loads when you open the review of your completed request. Google then processes technical data and may use security cookies. This is separate from your Analytics choice. Contact by email remains available.

Analytics is off.