A Photo Index for Claim Report Drafts: Keep References Stable Through Revisions

A photo reference needs a stable destination

A reviewer reaches “see photo 4” in a draft, opens the attachment list, and finds a different image. Nothing about the inspection has changed. Someone added an overview photograph near the beginning, shifting the display order. The reference now points to the wrong place.

A claim photo index can prevent that particular drafting problem by connecting three things: a stable photo ID, the file a reviewer can open, and the passage that refers to it. The index proposed here is an original editorial worksheet for independent and field adjusters. It is a manual organization method, not an industry standard or a built-in StateClaimAI feature.

The existing claim photo documentation checklist addresses collection and visual context. This worksheet starts after photographs have been gathered, when the task is keeping references understandable through drafting, rearrangement, and review.

Separate identity from display order

Give each photograph used in the drafting packet a stable local ID, such as P-001. Keep that ID attached to the same source file throughout the packet's revisions. Record its original filename and a location the assigned reviewer can actually access. An ID that leads only to someone else's desktop is an incomplete reference.

Display order is a separate field. The same photograph might appear third in one draft and fifth in the next. Its stable ID stays P-001; the index records the current presentation number and draft version. Write “photo P-001” in working text where your team's format permits it. If the final format uses exhibit numbers, maintain an explicit mapping between those numbers and the stable IDs.

Do not build an ID around a conclusion. P-001 identifies a file; a name that asserts how a condition occurred adds an interpretation before review. Similarly, do not infer a capture date from a filename. Record where any date information came from, or leave the capture date unconfirmed.

Copy this photo-index worksheet

Create one packet header and repeat the photo record for each indexed item. A plain document is sufficient. Use your team's existing identifiers if they already provide a stable mapping.

Packet header

• Packet reference: A non-sensitive working reference, such as DEMO-A.
• Draft version: The particular narrative being checked, such as v2.
• Index version and prepared date: A version label and the date this index was prepared.
• Prepared by and review owner: The relevant team roles or internal identifiers.
• Photo location: The authorized folder or attachment bundle available to the reviewer.
• Scope: Which files this index covers; note any separate bundle outside its scope.

Repeating photo record

• Stable photo ID: One ID for one source photograph.
• Original filename: The filename as received, without silently replacing it.
• File locator: The folder, attachment name, or other usable route to that file.
• Provided by and receipt reference: Who supplied it and the note or message recording receipt.
• Capture date and basis: The stated date and its source, or “unconfirmed.”
• Location label and basis: The area shown and the note supporting that identification.
• Working caption: A short description limited to what the reviewer can see.
• Related note IDs: Any inspection or statement references that supply context.
• Draft references: Every section or paragraph currently referring to this image.
• Display mapping: The exhibit number or appendix position in this draft version.
• Related copies: Any crop, annotation, or other derivative included in the packet, labeled separately.
• Review status and open item: Whether the reference has been checked, by whom, and what still needs clarification.

The worksheet contains no field for deciding what a photograph means for an insurance outcome. Its purpose is navigation and attribution. A checked reference means that the reviewer found the intended file and compared the associated wording; it does not authenticate the image or resolve an underlying question.

Worked example: an added image changes the order

The following packet, files, dates, notes, and people are entirely fictional. No customer material is used. Imagine a small inspection packet for a storage room identified as “Room C” in the inspector's notes.

Packet DEMO-A, draft v1

• Header: Index I-01; prepared October 6, 2026; preparer Editor A; review owner Reviewer B; shared packet location DEMO-A/photos; scope three received images.
• P-001: Original IMG_3101.jpg; locator DEMO-A/photos/IMG_3101.jpg; provided by Inspector A, receipt note R-01; capture date October 5 per note N-01; room label Room C per N-01; caption “Room overview with two shelves and the entry door”; related note N-01; draft reference “Room C overview, paragraph 1”; display “Appendix image 1”; related copies none; status “reference checked by Reviewer B, no navigation issue.”
• P-002: Original IMG_3102.jpg; locator DEMO-A/photos/IMG_3102.jpg; provider and receipt Inspector A / R-01; capture date October 5 per N-02; location “Room C, lower shelf” per N-02; caption “Light-colored marks visible along the lower shelf edge”; related note N-02; draft reference “Shelf observations, paragraph 1”; display “Appendix image 2”; related copies none; status “file located; caption comparison pending.”
• P-003: Original image_7.jpg; locator DEMO-A/photos/image_7.jpg; provider Site Contact A, receipt R-02; capture date unconfirmed; location Room C reported in R-02; caption “Close view of a shelf corner”; related note R-02; draft references none; display “not included in v1”; related copies none; status “clarify which shelf before narrative use.”

The third record is intentionally incomplete. A plausible-looking image is not a reason to fill in its location by assumption. Keeping it visible in the index allows a reviewer to see the unresolved identification without treating it as support for a sentence.

Revision to draft v2

A fourth image arrives with a clearer room overview. Update the header to index I-02, draft v2, and a scope of four received images. Assign it P-004 and record its own filename, receipt reference, location basis, and review status. Place it first in the appendix if that suits the review packet. Update the display mappings: P-004 becomes image 1, P-001 becomes image 2, and P-002 becomes image 3.

The shelf sentence still refers to P-002. If the narrative must say “Appendix image 3,” record that mapping and check the rendered draft after the reorder. Do not recycle P-003 for the new image simply because the earlier file remains unused. Its unresolved record already has a meaning within the packet.

Check the index in both directions

Before handing over a draft, start in the narrative. Follow every photo reference to its index record and then to its actual file. Compare the caption, the area named, and the displayed image. If a crop is shown, confirm that its record names the source photograph and makes the relationship apparent.

Then start in the index. For each image marked as included, find its intended appearance or citation in the draft. Resolve missing references, repeated IDs assigned to different files, and display numbers left over from an earlier version. Record unused photographs as outside the current narrative rather than implying that every indexed file appears in the report.

Add a short handoff note: “Index I-02 checked against draft v2; P-003 location remains unresolved.” That note describes the documentation state without pretending that the whole report has been approved.

Move from an index to a reviewed draft

The property damage claim report template provides a broader outline for observations, source notes, and open items. Place your index alongside that structure and keep it available during human review.

This workflow follows the educational scope described in the editorial policy. It organizes references and does not supply claim decisions. A qualified professional must review the complete draft before use.

When the materials are ready for drafting, visit the StateClaimAI workspace. Keep the index as a working review aid, and check the resulting draft's actual references before sharing it.