Start a vision prototype acceptance plan by listing device and software scope, inputs, outputs and site responsibilities. List function, decision quality, latency and recovery separately. For each item, agree on environment, samples, expected results and required evidence. Keep an item pending until its required inputs are available.
Retain the version used for each acceptance run
Record device and camera configuration, software, models or rules, parameters, reference images and dependencies. Use stable sample identifiers to link images, expected decisions and actual results. Save file checksums to avoid mixing changed files with earlier acceptance results.
Execute the agreed procedure and save exceptions
Run samples in the agreed environment, keeping individual outputs, logs and evidence images. Check invalid inputs, process restart, result transfer failure and recovery behavior. Record why equipment or materials prevented completion. A demonstration screenshot cannot replace the corresponding check.
Close issues with retest records
Record the issue, revised version and affected scope. Retest the original failing samples and check related functions. Deliver old and new results, unresolved issues and limitations. Complete later production samples, continuous operation and acceptance of interfaces at the production site under their own plans. Do not mark them as passed in advance.
For verification record design, see NIST data collection guidance.