# Workflow automation pilot scope: a buyer acceptance checklist

> Write an automation pilot as one process, with exclusions, exception tests and handover evidence. A demo is not acceptance and not a rollout.

Source: https://www.fyadvisers.com/blog/workflow-automation-pilot-scope-acceptance-checklist/  
Author: Fiona Wang, FYAdvisers  
Published: 2026-11-08  
Last updated: 2026-11-08

A useful pilot shows that one process works, including the exceptions you already know about. It names where the work starts, where it ends, which records it may change and when a person takes over. A polished demonstration is not evidence for a wider rollout.

Choosing whether to build, buy or skip is the [AI readiness assessment](/services/ai-readiness-assessment/). This page assumes you have picked a process and you need a statement of work. Pricing the result is the [quote worksheet](/blog/workflow-automation-cost-singapore/). Keeping it running is [maintenance](/blog/workflow-automation-maintenance-failed-runs/).

## Write the process as something you can point at

Reject a scope that says “automate admin”. Replace it with:

- the trigger, and the system that emits it;
- the inputs, including the fields that are often blank;
- the system that is authoritative for each fact;
- the outputs, and which of them are drafts;
- the owner of the queue;
- the escalation when the owner is away.

If you cannot name those, you are not ready to pilot. You are ready to sit with the people who do the work and watch five real cases.

## Bound it until a result would matter

Pick a process with sample data you are allowed to use and an owner who will attend the tests. Note what happens to the business if the result is wrong. That impact decides how much human review you keep.

Rules are enough when the branch is predictable. A model is in scope only with a defined input, a defined output and a person or a check in front of any customer, payment or access change. “Add AI” is not a pilot scope.

Illustrative boundary, not a client engagement: the pilot automates supplier-invoice intake and approval for one legal entity and one approval band. Multi-currency, historical migration and payment execution are written as exclusions. They can be a later project if the pilot shows where they belong. They are not quietly included because the demo data was simple.

## In scope, out of scope, and your dependencies

State the applications, the fields, the volume assumption, the approval stages, the environment (sandbox or a slice of production) and the exclusions. Then list what the supplier cannot finish without you:

- a licence or a premium connector, checked against [Microsoft’s licensing description](https://learn.microsoft.com/en-us/power-platform/admin/power-automate-licensing/deep-dive-on-specific-license) if that is the platform, or against the equivalent page for the tool you chose;
- an API enabled on your plan;
- a sample of real exceptions with personal data removed;
- a decision on the authority matrix;
- a credential owner who will still be employed at go-live.

Personal data in samples is still personal data. The PDPC’s [Key Concepts guidelines](https://www.pdpc.gov.sg/-/media/Files/PDPC/PDF-Files/Advisory-Guidelines/AG-on-Key-Concepts/Advisory-Guidelines-on-Key-Concepts-in-the-PDPA-17-May-2022.pdf) expect reasonable protection. Use redacted copies. Do not paste a live NRIC into a test flow because it was convenient.

## The test pack

Witness at least:

| Case | Pass looks like |
|---|---|
| Ordinary item | The right record, the right status, a person still does the step you reserved for them |
| Missing field | An exception queue, not a guessed value |
| Duplicate | One business record |
| Permission denied | An alert, no endless retry |
| Downstream unavailable | No partial claim of success. See the [failed-run tests](/blog/workflow-automation-maintenance-failed-runs/) |
| Change after approval | The old decision does not apply to the new version |

Write what “pass” means and which cases are allowed to finish in the manual queue. A manual finish of an in-scope ordinary item is a fail. A manual finish of an excluded case is success.

## Baseline without a fantasy saving

If you want a before-and-after, measure it yourselves: cycle time on a sample you define, number of times a person touches the item, and how often the result is corrected. Any return-on-investment sketch must show its assumptions and must subtract review time, exception handling and maintenance. This guide does not promise a labour saving. A pilot that only speeds up the happy path and hides a longer queue has not been measured.

## Acceptance is a handover

Final acceptance includes the definition, the test record, the runbook, training of the named operator, company-owned accounts, an export, and a demonstrated pause and revert. The operator, not the supplier, resolves one failed item from the runbook while you watch. A larger rollout is a new decision after that evidence. It is not an automatic extension.

Illustrative scenario, not a client engagement: the pilot’s last session uses a redacted duplicate invoice, a missing purchase-order number and a timeout after the accounting system has already stored the bill. The company’s operator follows the runbook and does not create a second bill. Access to the tenant is already in the company’s admin. Only then is the pilot called accepted.

A model trial has its own tests: [AI pilot and PoC acceptance](/blog/ai-pilot-poc-acceptance-checklist-singapore/).

To turn “automate admin” into one process and a test pack, use the contact form or WhatsApp +65 9071 3976 ([chat](https://wa.me/6590713976)).

## Frequently asked questions

### What has to work before the final pilot payment?

The pass rules in the statement of work: the in-scope path, each named exception, the runbook used by your operator, and the export and access transfer. A workshop and a slide are not those rules.

### Which dependencies can stop the pilot even if the supplier is ready?

Your licences, an API that is not on your plan, a sandbox you have not opened, data you have not cleaned, and an approver who has not signed the matrix. List them as customer dependencies with a date, or the delay will be argued later.

### What evidence is handed over?

The workflow definition, the field list, the test results, the runbook, the place where business state is stored, admin access, and a way to pause and revert. Credentials stay in company-owned stores.

### How is this different from an AI readiness assessment?

A readiness assessment helps you choose what is worth doing. This checklist is the statement of work and the acceptance pack for one process you have already chosen.
