One-page decision
Proceed within the reviewed boundary, narrow the use, wait for evidence, or do not buy.
AI Pilot Acceptance Review
Did the pilot hold up beyond the demo?
For the COO or risk owner asked to approve one AI workflow. Keep every agreed test case, failed result and exclusion beside the proposed decision. Wait, narrow, or do not buy are valid answers.
Prepare notes on this device, then choose whether to email. Nothing is submitted.
The decision at the end.
Which uses have enough reviewed evidence to proceed, which need a narrower boundary, and which should wait? The file separates a provider result, a prepared record and the institution reviewer's acceptance.
What to bring.
- One defined workflow, unit of work, decision date and accountable owner.
- An agreed test-case register prepared independently of the results, including cases you expected but did not receive.
- Permitted source versions, instructions and result exports, with failures and repeated attempts retained.
- The current process and matched task observations, if an effort comparison is in scope.
- An institution reviewer who can judge answer quality and the proposed use boundary.
The file you keep.
Required cases and complete results
Every supplied result, failed case, repeated attempt, unresolved mapping and missing required case.
Acceptance and issue register
The human reviewer, their supplied decision, corrections, exclusions and the questions still open.
Matched effort comparison
When supported observations exist, preparation, operation, review, correction, re-entry and export effort under the same unit of work.
One workflow. Four steps.
Agree what should be tested
Name required cases, quality conditions, exclusions, the reviewer and allowed sources before reading the headline result.
Retain the supplied observations
Account for each result and keep provider statuses distinct from human review. A repeat is not silently a replacement.
Review failures and missing evidence
Keep missing cases, refused answers, corrections and open reviews out of an accepted-result claim.
Record the use decision
The institution decides what may proceed, what needs a narrower scope and what evidence is still required.
Timing, dependencies and ownership.
Plan two to four weeks once the workflow, permitted sources and reviewers are agreed. Missing exports, unrun cases and reviewer availability can change the schedule.
Your domain reviewer judges the answer, source adequacy and intended use. Technical and risk owners review the system outside this supplied-file method. A native result marked Pass does not accept an answer or approve deployment.
You keep the reviewed file and remaining cases. A changed source, model, instruction or use boundary needs the appropriate new tests; no continuing evaluation or hosted history is activated.
See the method.
Retain supplied evaluation results Compare matched task observations
The preparation method supports its specified CSV contract and runs no evaluation. It exports a pending comparison draft. Task effort stays unknown until supplied; response latency is not total task effort.
Who can act, on what, and until when?
Where an assistant's authority is relevant, separate internal tools, vendor features and customer-delegated assistants. Record the declared scope, expiry, owner and revocation question.
Discovery is not authority. A supplied identifier does not verify identity. Inspect the delegated-access simulation.
A file to inspect. A decision your institution owns.
Public tools run on supplied inputs and fictional examples. An engagement uses only sources you are allowed to share. We do not connect to a core, compile or execute institution code, take a financial action, certify compliance, give a legal opinion or claim achieved savings.
Bring the workflow and the approval date.
Bring the decision, deadline and accountable owner in general business terms. We agree the workflow, permitted sources, review responsibilities and exclusions before work begins.
Scope and fee are fixed in writing after one working session.
Prepare a scope request or email info@llmsquared.com. Do not attach confidential sources to an ordinary inquiry.
Choose the method route.
Run the bounded method in the browser, or in an approved assistant.