Decision tool · experimental

Is this pilot worth paying for?

Record the one uncertainty that could change your purchase decision, the least costly safe way to learn it, and the result your decision owner would act on.

Working record

Make the decision test explicit

Do not buy a pilot just to gather activity. First decide whether its result can change a named next step.

0 of 15 fields recorded. Open fields remain unresolved.

Decision to makeFor example, request a costed proposal, run wider validation, revise or stop.Current processThe baseline work and period you would continue without this option.Configured robot optionName the task, configuration and operating boundary.Other plausible optionA process change or another way to do the work.Decision-sensitive unknownWhich uncertain input could reverse the option ranking?Current evidence or rangeState the source and date, or say that no reliable range exists.Buyer-set switch conditionWhat observed result would change the decision? Include conditions and exceptions.Least-cost adequate learning methodCan documents, a survey, sample test or simulation answer this before a site pilot?Pilot cost ceilingBuyer-approved maximum or 'not agreed'; do not invent a number.Installed-cost unknownsInterfaces, tooling, site works, commissioning or other unpriced items.Recurring-cost unknownsSupport, supervision, recovery, software or other unpriced items.Safety and site entry conditionsName the accountable owner and prerequisites; these are not tradeable performance benefits.Measurement and exception planBaseline period, logs, denominator, failures, interventions and review owner.Observed result or inconclusive reasonLeave blank before testing; distinguish measurement from estimate.Decision owner and dateWho can choose proceed, revise, gather more evidence or stop?

Not ready for a funding decision: record the pivotal unknown, switch condition, learning method and decision owner.

Decision disposition

Entries stay in this browser tab. Download before leaving if you want to keep them.

Acceptance handoff

Keep exceptions outside the release boundary visible

Record each failed, untested or deviated case separately. Exclusion is a decision to document, never a test pass.

6 missing exception references. Completeness does not approve release.

Exception 1

Requirement and test caseReference the agreed requirement, case and configured system.Exception and retained evidenceState failed, untested or deviated conditions; retain the raw result reference.Affected release boundaryWhich task, variant, interface or condition remains outside the proposed release?Interim restriction and accountable ownerWho owns the restriction and what is withheld while this remains open?Closure evidence and next reviewName the retest or other evidence, responsible role and review date; do not invent a deadline.Decision reference and authorityRecord the actual decision, owner, date and evidence; a filled field does not approve release.

Exception 1 disposition

Entries remain in this tab. Download before leaving. No operational files are uploaded or checked.