Systems and records
Freight claims evidence linkage: photos and the signed delivery record
By SourceX Editorial · Reviewed by Noah Loul ·
10 sections
Short answer
Freight claim photos link to the signed delivery record through four checks: the same PRO or bill of lading number, a capture time with its UTC offset inside the delivery window, damage that matches the written exception, and the claim file number tied to that receipt. Package each claim as a rights screened evidence packet that grades every link and keeps the carrier's decision with its date.
Document stack
Freight claims evidence
Key takeaways
- A claim photo is evidence only when its shipment number, capture time, place and visible damage line up with the signed delivery record.
- A damage notation on the receipt is not a claim; the receipt, the photos, the claim and the disposition are separate records that have to be linked.
- Convert every timestamp to UTC using the recorded offset before comparing photo and signature times.
- Keep the carrier's decision per item, with its date and reason, and flag outcomes that are not yet final.
- Screen every document for licensing rights, personal data and contract restrictions separately; holding a copy is not a right to license.
What evidence links freight claim photographs to the signed delivery record?
A photo is linked to the signed delivery record when four things agree: the same shipment identifier, such as the PRO or bill of lading number, appears on both or in the photo's capture record; the photo's capture time, with its time zone offset, falls inside the delivery window the signature records; what the photo shows matches the exception notation the consignee wrote; and the claim file number ties the claim back to that delivery receipt. Without those links a photo illustrates damage but does not show when or where it happened.
The regulations explain why the link matters. Under the FMCSA claim rules for motor carriers, a notation of damage on a delivery receipt does not by itself count as a claim, and a carrier that receives a claim opens a separate claim file and, unless it keeps an orderly internal procedure instead, notes the claim file number on the shipping order and the delivery receipt. The delivery record, the photos and the claim are separate documents that only become one case when someone links them.
For a company preparing its claim history as a dataset, those links are the value. Thousands of claim photos without keys teach a model what damaged pallets look like; the same photos linked to receipts, notations and outcomes teach it which evidence decided the claim.
Why the receipt notation and the claim are different records
The delivery receipt records the condition at handover; the claim is a later written demand. 49 CFR 370.3 sets the minimum for a claim: a written communication from the claimant, filed with a proper carrier within the time limits of the bill of lading or contract, identifying the shipment, asserting liability and asking for a specified or determinable amount. Bad order reports, inspection reports and notations on delivery receipts do not meet that minimum standing alone.
Time limits shape what a complete file contains. Under 49 U.S.C. 14706, a carrier may not set less than 9 months for filing a claim or less than 2 years for bringing a civil action, with the 2 years counted from the carrier's written notice disallowing the claim. The carrier side runs on its own clock: 370.5 requires acknowledgment within 30 days, and 370.9 requires the carrier to pay, decline or make a firm compromise offer within 120 days, or send written status updates at that point and every 60 days after.
A dataset that keeps only the claims system's status field loses this structure. Keep each document with its own date so a model can learn the sequence, not just the final label.
The starting state of one claim (illustrative)
The case below is invented to show how the evidence fits together; it describes no real shipper, carrier or claim. A building products distributor receives a less-than-truckload delivery of 12 pallets of floor tile at its warehouse. The driver uses a handheld to capture the consignee's electronic signature, and the receiving clerk types an exception before signing: two pallets with torn stretch wrap, one carton crushed on the top layer.
The driver's handheld takes three photos at the dock. The clerk takes six more on a warehouse phone after the pallets are broken down that afternoon. Nineteen days later the distributor's claims coordinator files a written claim with the carrier, attaching the bill of lading, the delivery receipt, the commercial invoice for the tile and all nine photos. The carrier acknowledges, sends an inspector, and later makes a compromise offer on the noted damage while declining a second group of cartons found broken a week after delivery.
The decision a model would learn from this file is not the status code. It is why one part was accepted and one declined, and that answer sits in the links between the photos, the notation and the inspection.
The link keys, field by field
Check each link separately and record the result as a field, not a judgment in a note. Field names below are examples to adapt to the systems you use, whether that is a TMS, a WMS, a carrier portal export or a claims mailbox.
| Link | On the delivery record | On the photo or its capture record | Match rule |
|---|---|---|---|
| Shipment identity | PRO and bill of lading number printed or stored with the POD | Number visible on the label in frame, or stored with the image by the capture app | Exact match after normalizing prefixes and leading zeros |
| Handover time | Signature timestamp with its time zone | Exif DateTimeOriginal plus OffsetTimeOriginal, or the app's upload time | Capture within the delivery window, both converted to UTC |
| Place | Consignee stop on the delivery record | Location stored by the capture app, if any, or the device's assigned site | Same site; unknown location is recorded as unknown, not assumed |
| Pieces | Handling unit and piece count on the receipt | Pallet or carton labels visible in frame | Photographed units are among those delivered |
| Condition | Exception notation text | Visible damage type and location on the load | Damage shown is the damage noted; extra damage is flagged as unnoted |
| Claim | Claim file number noted on the receipt or in the carrier's procedure | Photo listed as an attachment on that claim | Every attached photo resolves to the same claim file |
| Source | Who captured the signature: carrier driver, broker app, consignee system | Who took the photo: driver, consignee staff, inspector | Source recorded for each item, since it decides weight and rights |
What the timestamps can and cannot prove
A capture time is only comparable once you know its time zone. The 2019 edition of the Exif standard, maintained by the Camera and Imaging Products Association, defines OffsetTimeOriginal as the offset from UTC that goes with DateTimeOriginal, and later editions exist, so confirm the tag against the edition your devices write; many phones and handhelds write both, but some apps strip metadata on upload. Record which clock each time came from, and convert to UTC before comparing photo times with signature times.
Metadata is evidence, not proof. Device clocks drift, photos are re-saved, and messaging apps replace originals with compressed copies. Treat a match as strong when a shipment number is visible in frame and the time agrees, moderate when only the time agrees, and weak when neither is available, and carry that grade into the dataset.
Keep the original files where you can. A re-saved or forwarded copy may have lost its capture metadata, and a content hash of each original lets a reviewer detect the same photo attached to two different claims, which is a common error in busy claims mailboxes.
The rights screened claim evidence completeness packet
Use this packet as the unit of preparation for every claim. A claim is complete for licensing when each required item is present, linked to the claim file and has passed its rights screen. The last column shows the illustrative case above.
At a glance
The rights screened claim evidence completeness packet
| Item | Completeness test | Rights screen | Illustrative case status |
|---|---|---|---|
| Bill of lading | Shipment number, pieces and released value terms present | Shipper and consignee names replaced with stable tokens | Present, linked |
| Signed delivery receipt or electronic POD | Signature time, signer role and exception text captured | Signature image and signer name removed; role kept | Present, linked |
| Driver photos at delivery | Shipment number in frame or capture record, time within window | Faces, plates and other people's labels blurred | 3 of 3 linked, strong |
| Consignee photos after unloading | Time and place recorded; unit labels visible | Taken by the company's own staff; faces blurred | 6 of 6 linked, moderate |
| Inspection report | Inspector, date and findings per unit | Third-party or carrier document: confirm the company may license it, or exclude | Present; carrier inspector, held for review |
| Written claim | Meets the filing minimum: identifies shipment, asserts liability, states an amount | Amounts banded or removed if a confidentiality term applies | Present, filed day 19 |
| Carrier acknowledgment and status letters | Dates recorded against the 30 and 120 day clocks | Carrier staff names removed | Acknowledgment present |
| Disposition letter | Outcome per item and reason in the carrier's words | Settlement terms checked for confidentiality | Partial: noted damage accepted, later damage declined |
| Proof of value | Invoice line items for the claimed units | Prices banded or removed; customer identities tokenized | Present |
| Late-found damage photos | Linked to receipt? Usually not | As above | Unlinked, kept as a labeled counterexample |
Electronic signatures and what the signed record proves
An electronic POD is a real signature for most commercial purposes. The federal ESIGN Act provides that a signature or record relating to a transaction in interstate commerce may not be denied legal effect solely because it is in electronic form. That settles the format question, not the content question.
What the signed record proves is narrower than it looks. It shows that someone at the consignee accepted the pieces at a time and wrote, or did not write, an exception. It does not show that the pieces were undamaged when no exception was noted, and it does not show who caused damage that was noted. Keep the signer's role and the notation text; drop the signature image and the person's name, which add privacy risk without teaching a model anything about the claim.
Proving the decision and the eventual outcome
The outcome lives in the carrier's disposition letter and the payment or offer record, not in a closed status. Link the disposition to each claimed item so that a partial decision stays partial, and keep the carrier's stated reason in its own words, for example that damage found after delivery was not noted on the receipt.
Mark outcome maturity. A declined claim can still move: the 2-year period for a civil action runs from the carrier's written disallowance, so a claim declined recently is not settled history. Record the disposition date and whether further action followed, and leave immature cases out of training labels or flag them clearly.
Keep the counterexample. In the illustrative case, the cartons found broken a week later have photos, a time and a shipment number, but no notation on the receipt. They are exactly the cases where a model has to learn that strong photos do not overcome a missing link, so they belong in the dataset with their own label.
Whose evidence is it to license?
A shipper's claim file mixes documents the shipper created with documents created by carriers, inspectors and customers. Having a copy is access, not a right to license. Photos taken by your own staff and claim letters you wrote are usually yours; a carrier's inspection report or a broker's portal export may come with terms that restrict reuse. Under 49 CFR 371.3, each party to a brokered transaction has the right to review the broker's record of it, which is a right to see, not a right to redistribute.
Screen every item for three separate questions: does the company hold the rights to license it, does personal data in it need removing or consent, and does a contract such as a settlement agreement restrict disclosure. De-identification answers the second question only. Counsel should review the specific contracts and document sources before any file leaves the company.
Turning a claims history into a licensable dataset
Companies with years of linked claim files, from shippers and 3PLs to carriers, hold the kind of decision evidence AI developers rarely find in public data. A business that licenses claim histories through SourceX hands it the sourcing, rights review, contracting, preparation and delivery, while keeping every packet in-house until it has signed off on scope and terms.
Qualification starts with a few questions about the company, not with any claim photos; the packet above is a useful way to estimate how many of your claims are complete before that conversation.
Frequently asked questions
Is a damage notation on the delivery receipt a freight claim?
No. Under the FMCSA claim rules, notations of damage on delivery receipts, bad order reports and inspection reports do not by themselves meet the minimum requirements for filing a claim. A separate written claim that identifies the shipment, asserts liability and states an amount is still needed. The notation is important evidence for that claim.
What makes a claim photo strong evidence in a dataset?
A shipment number visible in frame or stored with the image, a capture time with its time zone that falls inside the delivery window, and damage that matches the written exception. Photos with only a matching time are weaker, and photos with neither are unlinked. Record the grade rather than discarding the weaker photos.
Should signature images be kept when preparing claim files?
Usually not. The signer's role, the signature time and the exception text carry the evidence a model needs. The signature image and the signer's name are personal data that add risk without adding information about the claim.
How long do carriers have to resolve a cargo claim?
Under 49 CFR 370.9, a motor carrier must pay, decline or make a firm compromise offer within 120 days of receiving the claim, or send written status updates at that point and every 60 days while it remains pending. Acknowledgment is due within 30 days under 370.5. Record these dates in the dataset so the sequence is preserved.
Can claim files that include carrier inspection reports be licensed?
Only after checking who created each document and under what terms. Reports written by a carrier or an independent inspector may not be the shipper's to license, even if the shipper holds a copy. Exclude them or obtain permission, and have counsel review the specific documents.
Sources
- Under 49 CFR 370.3, delivery receipt notations, bad order reports and inspection reports do not standing alone meet the minimum claim filing requirements, which call for a written claim identifying the shipment and asserting liability for a specified or determinable amount. Source
- Under 49 CFR 370.5, carriers acknowledge claims within 30 days, open a separate numbered claim file, and note the claim file number on the shipping order and delivery receipt unless an orderly internal procedure keeps records available. Source
- Under 49 CFR 370.9, carriers pay, decline or make a firm compromise offer in writing within 120 days, or advise the claimant of status then and every 60 days. Source
- 49 U.S.C. 14706(e) bars carriers from allowing less than 9 months to file a claim or less than 2 years to sue, counted from written notice of disallowance. Source
- 15 U.S.C. 7001 provides that a signature or record relating to a transaction in interstate commerce may not be denied legal effect solely because it is in electronic form. Source
- The Exif standard defines offset tags, including OffsetTimeOriginal, that record the UTC offset for the original capture date and time. Source
- 49 CFR 371.3 requires brokers to keep a record of each transaction for three years and gives each party to the transaction the right to review it. Source
See if your company qualifies
A short company assessment. No data uploads are needed.