Separate actions from settings
A task list and a location list are not interchangeable. A collection can contain many settings while showing only one narrow action pattern. Define the actions first, then the relevant settings, objects, performers, and recording styles. Mark which combinations are essential and which are optional so the acquisition brief does not accidentally request every possible combination without a clear priority.
Count meaningful examples
Specify whether coverage is measured in completed sequences, attempts, source sessions, or accepted runtime. Several repeated takes can provide useful practice variation but may not represent independent performers or settings. Report these units separately. Long pauses and unrelated sections should not silently satisfy an activity quota whose purpose is to obtain examples of observable behavior with suitable context.
Include transitions and alternatives
Preparation, interruptions, retries, and alternative methods can matter as much as a clean successful action. Decide which should be included and how they are labeled. Avoid describing one preferred technique as the only valid action unless the task genuinely requires that constraint. A pilot should show where category boundaries become ambiguous so the coverage plan can be revised before scaling.
Use gaps to guide acquisition
Review coverage tables against actual sampled footage and annotate remaining gaps honestly. New collection may be useful for specific missing conditions, while an archive may offer broader exploratory material. Fiund can discuss these options with project-specific sample and source review. A coverage target is a procurement objective, not evidence that the requested footage is currently available or cleared for the proposed use.
Review checklist
- Define actions separately from settings.
- Choose sequence, session, and runtime counting units.
- Include relevant retries and transition behavior.
- Mark verified coverage and remaining targets separately.