By ScoutMyTool Editorial Team · Last updated: 2026-05-27
Introduction
I have audited claim files that read like a well-built dossier and others that read like a glove-box of receipts. The difference is rarely effort — it is structure. The well-built file starts with a manifest, walks through the FNOL, the policyholder statement, the photo evidence with EXIF intact, the scope sheet, and ends with a diary appendix the carrier can read without logging into the claim system. The glove-box file has the same documents in the wrong order, no manifest, and photos compressed to the point where the dent on the rear bumper looks like a paint scratch. Here is the structure I use, the metadata I set, and the chain-of-custody steps that keep an adjuster's package above the line in QA.
Vocabulary, quickly
| Term | Meaning |
|---|---|
| Claim package | Single PDF combining claim form, statements, photos, and estimate |
| Chain of custody | Documented trail from photo capture to package submission |
| EXIF | Image metadata — timestamp, GPS, device — that supports a claim |
| First Notice of Loss (FNOL) | Initial claim filing with policyholder, date, and incident summary |
| Scope sheet | Itemized damage and estimated repair line items |
| Reservation of rights | Letter the carrier sends when coverage is uncertain |
| Diary entry | Adjuster's timestamped note in the claim file |
Step by step
- Establish chain of custody at intake. Note who took each photo, when, and where. The note is in the diary; the PDF carries an exported copy.
- Preserve EXIF on adjuster-captured photos. Place images in the PDF with EXIF intact; strip EXIF only for policyholder-submitted photos with unverifiable provenance.
- Build the package in a fixed section order. Manifest, FNOL, policyholder statement, photo evidence, scope sheet, third-party reports, diary appendix.
- Add a photo log to the manifest. Per-image timestamp, location, and one-line caption. The carrier scans this; missing photos get flagged immediately.
- Compress selectively. Full quality for evidence photos, 150 DPI for documents and reference images. Target 30-50 MB per package.
- Sign with a CA certificate. Tamper-evident signature on the final page; the certificate must come from a recognized CA, not self-signed.
- Hash and log. SHA-256 of the final PDF goes in the diary. Any later question about file integrity has a definitive answer.
- Submit via the carrier portal. Never email a claim package; email risks data exposure and breaks the audit trail. Use the portal upload and keep the upload confirmation.
Pre-submission checklist
- Manifest page ranges match the actual section boundaries — slipping a document in without updating the manifest is the most common QC failure.
- Photo log entries match the photos in the file; no orphan log entries, no unlogged photos.
- Evidence photos are full-quality and identifiable; reference photos are compressed.
- The signature certificate validates in Adobe Reader without warnings — warnings indicate an untrusted CA or expired certificate.
- Claim number appears in the file name, the manifest, the PDF metadata, and the portal upload form — four places, all consistent.
- Diary appendix matches the current diary entries in the claim system; an out-of-date appendix is worse than no appendix.
Related reading and tools
FAQ
- Should photos keep their EXIF or be stripped?
- Keep EXIF for adjuster-submitted photos — the timestamp and GPS support the loss event. Strip EXIF for any photo the policyholder sends that may contain unrelated location history (their home address embedded in a phone photo of a totaled car parked at the dealership). The rule: keep EXIF you can vouch for; strip EXIF you cannot.
- How do I prove the photo timestamp is real?
- Embed the photo in the PDF with EXIF preserved, sign the PDF with a tamper-evident certificate, and store the SHA-256 hash in the diary. The signature and hash freeze the timestamp claim; anyone can verify it later without trusting the file system date. For high-value claims, layer in a third-party trusted-timestamp service.
- My carrier rejects packages over 50 MB. How do I shrink without losing photo evidence?
- Compress images selectively — keep evidence photos at full quality, downsample reference photos and document scans to 150 DPI. Compress text-only pages with maximum efficiency. The package shrinks 60-80 percent without touching the evidence quality. Some carriers prefer split deliveries; respect the limit and split if needed.
- What goes on a manifest page for a claim package?
- Claim number, policyholder name, date of loss, file version, table of contents with page ranges, and a photo log listing each image's timestamp, location, and a one-line caption. The manifest is page 1; the carrier QA team scans it and routes the file. Missing manifest gets bounced before review.
- Can adjusters sign the package on a tablet in the field?
- Yes — a tablet PDF reader with a stylus and a tamper-evident certificate produces a legally enforceable signature. Capture the signature at the inspection if possible; that way the audit trail starts at the scene, not back at the desk. The certificate must come from a recognized CA — self-signed certificates cause downstream disputes.
- How do I handle diary entries — inside the PDF or in the claim system?
- Both. The claim system is the source of truth; the PDF carries an exported diary as a final-section appendix so the file is self-contained. Underwriters reviewing the file in a future audit may not have access to the claim system. The appendix prints from the claim system, no manual transcription.
Citations
- Wikipedia — “Claims adjuster — investigation and documentation.” en.wikipedia.org/wiki/Claims_adjuster
- Wikipedia — “Chain of custody — evidentiary integrity.” en.wikipedia.org/wiki/Chain_of_custody
- Wikipedia — “Exif — metadata fields that travel with photographs.” en.wikipedia.org/wiki/Exif
Assemble claim packages in your browser
Merge in section order, build the manifest and photo log, sign with a CA certificate, and compress for the portal — ScoutMyTool runs every step locally so claim data never crosses a third-party server.
Open the PDF toolkit →