How to Mark Up Site Photos Without Altering the Original

A marked-up photo is often clearer than a paragraph. An arrow to the cracked weld, a box around the meter reading, the word “here” next to the water stain — annotation turns a photo the office has to interpret into one that explains itself. Crews should mark up photos, because it saves the back-and-forth of “which corner?” and “what am I looking at?”

But there is a catch that matters the instant a photo is evidence: if the markup is drawn onto the only copy, you have edited the record. The moment someone can say the image was altered after it was taken, its value as proof drops, arrow or no arrow. The trick is to get the clarity of markup without giving up the integrity of an untouched original — which is exactly what good field photo and data capture is supposed to protect.

Why editing the original is a problem

A photo used as documentation is making a claim: this is what the site looked like at this moment. Anything drawn on top of it is a second, later layer of interpretation. That is fine and useful, right up until the annotated file becomes the file of record and the pristine original is gone. Now the image in the claim, the report, or the dispute is a version that was demonstrably changed after capture, and the other side only has to point that out.

The failure is not the act of annotating. It is annotating in place, so that the marked copy overwrites or replaces the one nobody touched. A photo editor that saves over the original does exactly this, quietly, every time.

Keep the original, save the markup beside it

The clean solution is to treat an annotation as a new document, not an edit. When a crew marks up a photo in RoverDrop — arrows, boxes, text, freehand — the result is saved as a new file that is linked to the original. The original is never modified. It keeps its bytes, its checksum, and its place in the record; the annotated version sits next to it, plainly labeled as markup of that original.

This gives you both things at once. The office sees the annotated copy with the arrow pointing exactly where it needs to look, and anyone who needs the unaltered evidence can pull the original, provably the same file the camera produced. There is no forced choice between clarity and integrity, because the two live in separate files.

What “linked, not edited” buys you

• The original stays provable. Because it is never written to, the untouched photo keeps its checksum and can be shown byte-for-byte identical to what was captured.
• The markup is attributable. The annotated copy is recorded as its own event, so the trail shows who marked it up and when — the annotation has an author, not just an appearance.
• Both are in the packet.Original and markup travel together, so nobody has to hunt for the “real” one later or wonder which version is authoritative.

The original belongs in the archive, untouched

Keeping the original intact is not only about this week's report; it is about the copy that has to hold up years from now. When a packet is submitted, the original photo is sealed into the write-once archive, where it cannot be overwritten, and an annotation made afterward is simply another file added to the record, never a change to that sealed original. The evidence and the explanation coexist, and the evidence stays evidence. It is the same principle that runs through the whole chain of custody: the record is added to, never rewritten.

Annotate freely, once the original is safe

Once you know the original is preserved, annotation stops being risky and becomes purely useful. Circle the defect, label the reading, point at the thing you want the office to notice — mark up as much as helps, because none of it touches the file that proves what the site looked like. The rule is simple: never let the markup be the only copy. Keep the untouched original, save the annotation as its own linked file, and you get a photo that is both easy to read and hard to dispute. For the wider set of what a crew can capture in the field, see documenting photos with capture time and GPS.