Sample the uncertain conditions
A pilot should test the parts of the brief most likely to fail: work below the camera, reflective objects, interruptions, or movement between areas. Include ordinary examples too, so the review has context. Choose complete sequences from the planned conditions rather than requesting only the most polished moments from an otherwise unexamined recording session.
Review against explicit questions
Can the required interaction be seen? Are task boundaries understandable? Do labels reference the delivered timeline? Write the question and the evidence used to answer it. A simple pass label without explanation makes it hard to resolve disagreement or know whether a later capture change addresses the actual problem.
Classify issues by cause
Separate mount setup, task instructions, source restrictions, annotation ambiguity, and file integrity. Each requires a different response. A camera adjustment cannot solve an unclear success definition, while rewriting a label cannot recover an action that was never visible. Keep examples of each issue and identify whether it is fixable in processing or requires another recording. Assign each unresolved issue to the relevant capture or review decision.
Agree on the next version
Record approved changes, unresolved questions, and the precise pilot files reviewed. If configuration changes materially, review examples from the updated setup before assuming earlier conclusions still apply. Pilot acceptance establishes agreement about those examples and conditions; it should not be presented as a guarantee that every future session will satisfy the same requirements automatically.
Review checklist
- Include difficult planned conditions
- Ask evidence-based review questions
- Identify the cause of each issue
- Version decisions and revised examples