
Start a retention discussion with the questions the records must answer. Storing everything indefinitely is not a substitute for knowing which images matter, how they are identified and who can retrieve them.
List the review use cases
Ask quality staff what they need for a defect investigation, repeatability review or customer enquiry. Distinguish an image from its associated result and setup context. Identify requirements imposed by applicable agreements or procedures instead of inventing a universal retention period.
Estimate from the proposed workflow
Use expected inspection activity and confirmed file characteristics to assess storage needs. Keep assumptions visible and review them with the system owner. A brochure statement about data collection does not establish storage capacity or retention behaviour for your configuration.
Define access and recovery
Agree who can view, export or administer the records and how access is approved. Establish a backup and recovery approach appropriate to the environment, then have authorised staff verify it. Do not assume a copied folder proves a complete restoration.
Test a retrieval request
Locate an agreed example and verify that the image, result and identity remain connected. Our AOI data planning guide explains how retention fits into the complete information flow.
Frequently asked questions
Is there one correct retention period for all inspection images?
No. Use the relevant customer, quality and operational requirements and confirm the decision with the responsible owners.
What should accompany a retained defect image?
Preserve the identity and result context needed for its intended review, including the relevant setup reference where required.
How can a team check whether retrieval works?
Use a realistic record request and verify that the correct image and associated information can be found and interpreted.