Records must retain location, issue and follow-up stage; a later photograph should supplement previous evidence rather than replace it.
Index
A gallery of filenames cannot track a defect when staff photograph the same location on different days.
The rule that changes the scope
Records must retain location, issue and follow-up stage; a later photograph should supplement previous evidence rather than replace it.
Shared storage covers files; a custom application connects images to inspected items and issue revisions.
Field capture must allow context to be recorded before the image is submitted. If association happens later, the interface should keep unlinked photographs in an explicit queue rather than mix them with closed issues. A detail photographed from another angle still belongs to the same issue. Define who may correct that relationship and how comparison displays the sequence without claiming a picture alone proves a technical solution.
Specify operational deliverables
- Locate each photograph at an inspection point using the team's existing identification.
- Separate the initial image, intervention evidence and closure review.
- Record a caption and owner without relying solely on information embedded in the file.
Test the exception before acceptance
In a hypothetical scenario, a later photograph is uploaded against the wrong location; correction must preserve the previous association and record the adjustment.
Reference for assessing scope
NN/g: writing task scenarios for usability testing
Prepare your project with Quantum9
Bring a sequence of issue photographs and the map used to locate inspection points.