Why annotate photos instead of using captions only?
Captions describe; annotations point. On cluttered site photos, a text note saying crack on wall is ambiguous. Arrows and circles remove interpretation error for contractors pricing fixes and clients approving handover. The problem with captions alone is that a real inspection photo often shows a whole room or a busy plant-room panel, and a written description leaves the reader guessing which of several features the inspector meant. A mark drawn directly on the image removes that guesswork entirely, which cuts the email back-and-forth between office and site and, in a dispute, makes it obvious exactly what was flagged rather than leaving room for two readings of the same picture.
Can annotations include measurements?
Many field apps support scale lines or numeric notes for crack width and clearance gaps. Confirm tooling meets your engineering or QA standards for dimensional records. Measurement annotations are useful where a defect is judged by size, such as a crack that is acceptable below a certain width or a clearance gap that must meet a code, because a photo alone does not convey scale. It is worth checking how the tool records those figures and whether that method is accepted by your engineers or QA standard, since a hand-noted dimension supports triage and reporting but may not replace a calibrated instrument reading where the standard demands a formally measured value.
Do annotations work offline?
Markup should save locally with the photo before sync. Inspectly360 supports offline annotation so tower walks and plant rooms are not delayed for connectivity. This keeps the inspector working at the pace of the walk rather than the pace of the network, which matters on a handover of a new tower where connectivity is often absent and there may be dozens of defects to mark per floor. Because the annotated image is stored on the device with its checklist item, the inspector circles a stain, labels the location, and moves on, and the finished markup uploads exactly as drawn once the phone reaches signal, with no need to redo anything back at the office.
How do annotations export to client PDFs?
Reports embed annotated images at full resolution or in appendix linked to checklist rows. Clients see the same marks the inspector drew on site. The important guarantee is that the version the client receives is identical to what the inspector produced in the field, so the arrow and label on the report match the defect exactly as it was flagged. Linking each annotated image back to its checklist item also keeps a busy report readable when one unit has many findings, because the reader can see which mark belongs to which line rather than scrolling through a disconnected gallery of photos trying to reconstruct the inspector's intent.
Can AI and manual annotation coexist?
Yes. AI may suggest defect regions; inspectors refine with manual arrows and labels before submission. Human markup confirms what the official record shows. The two work well together because AI is good at drawing attention to a likely defect region quickly, while the inspector brings the judgement about what it actually is and how serious it is. A sensible workflow lets the model propose the area, then has the inspector accept, adjust, or add their own arrows and labels before the photo is saved, so the final annotated image reflects a human decision. That keeps accountability with the qualified inspector while still getting the speed benefit of the AI suggestion.
