Describe the object and the distinction
An inspection request often begins with a broad instruction such as “check the surface” or “confirm the assembly.” The first task is to identify what needs to be distinguished. Is the question about presence, position, appearance, a particular mark, or a change from a reference?
The definition should identify the object and the region of interest in plain language. It should also explain which differences matter to the business and which are acceptable variation. A useful inspection definition does not ask the future system to infer an unstated quality standard from a few attractive examples.
Include the difficult boundary cases
Clear positive and negative examples help explain the task, but uncertain cases often reveal the real requirements. A faint mark, a partially obscured component, or an unusual but acceptable finish can force the team to decide where an automatic observation should stop and a human review should begin.
The scope can organize those cases and identify who is qualified to resolve them. Where no reliable reference judgment exists, the issue should be recorded as an open requirement. Treating disagreement as a labeling inconvenience can create an evaluation that looks precise while testing the wrong distinction.
Connect the observation to an action
The output of an inspection needs a recipient and an intended response. A flag may prompt a closer look, a repeat capture, or a separate operational decision. Those responses need different information. A simple indication may be enough for one task, while another needs an image, a location, and a reason for uncertainty.
Define what happens when the view is inadequate or the result is ambiguous. The research should not assume that every item must be forced into an acceptable or unacceptable category. The client’s process should determine how unresolved observations are handled.
A definition the next specialist can use
The deliverable can combine the inspection purpose, relevant features, example categories, boundary cases, capture constraints, and expected response. It should make clear which requirements are agreed and which need confirmation before implementation.
This definition provides a basis for a capture study and an evaluation plan. It does not specify a complete camera installation or establish that an image-based method is suitable. If the target feature cannot be represented reliably under the available conditions, the appropriate next step may be to revise the task or investigate another approach.