Comparison must identify room and physical item while keeping each visit's observations without automatically assigning responsibility.
Index
Comparing entire galleries makes changes hard to explain when an item receives different names on arrival and departure.
The rule that changes the scope
Comparison must identify room and physical item while keeping each visit's observations without automatically assigning responsibility.
An inspection app may cover forms; a custom extension organizes item matching and evidence comparison.
Not every item will have comparable photographs, and the interface must show that limitation. Lighting, framing or description differences require human review rather than automatic conclusions. Include a room subdivided between visits: history should show the structural change and help locate the earlier element. Scope the comparison report as support for analysis without promising fault attribution or legal validity merely because photographs are organized side by side.
Specify operational deliverables
- Connect each record to property, room and inspected item using stable identification.
- Show observations and photos side by side with each visit's date.
- Record items not found or inaccessible instead of treating them as accepted.
Test the exception before acceptance
In a hypothetical scenario, a door description changes between visits; review must confirm it is the same item before comparing its condition.
Reference for assessing scope
NN/g: writing task scenarios for usability testing
Prepare your project with Quantum9
Bring two inspections of the same property and an item difficult to match across records.