Container Damage Documentation Best Practices for Container Depots
Structure your container damage claim documentation at the point of inspection — with validated container numbers, pre/post-repair photo records, and automated distribution to shipping lines. Trusted by container depots, shipping lines, and leasing companies across Europe.
No obligations — reply within 1 business day
What Is Container Damage Claim Documentation?
Container damage claim documentation is the structured process of capturing photographic evidence of container damage at inspection, linking each image to a validated container number, and maintaining retrievable pre-repair and post-repair records to support repair authorisation and shipping line cost recovery. It replaces unstructured methods — WhatsApp threads, email attachments, and shared folders — with a system where every photo is timestamped, GPS-tagged, and permanently associated with the correct container.
ConPDS implements this process through ConPDS Checker, a mobile application that reads container codes using AI-powered OCR — validated against ISO 6346 standards (owner code, serial number, and check digit validation) — and links every damage photo to the container record at the moment of capture. The full damage documentation set is stored centrally in the ConPDS dashboard, searchable by container number, and distributable to shipping lines and leasing companies via the guest portal or automated rule-based dispatch.
Photos captured in-app and linked to container numbers — no manual renaming or separate filing
Container codes validated against ISO 6346 standards at capture — not post-inspection
Pre-repair and post-repair conditions documented under the same container record
Spare part serial numbers captured and stored for warranty and claim traceability
Centralised archive searchable by container number — retrievable in seconds
Secure distribution to shipping lines via guest portal or automated photo dispatch
A depot processing 60 containers per day generates 360 or more damage inspection images daily. Without container-number linking enforced at capture, retrieval failure at the claims stage is not an edge case — it is a predictable operational outcome.
Without Structured Documentation
Photos manually renamed — errors under time pressure cause permanent retrieval failure
Images stored on personal devices — evidence lost when staff leave or change phones
No pre-repair record — post-repair claim is disputed as undocumented
Timestamp metadata stripped on WhatsApp transfer — evidence challenged in disputes
No spare part serial number record — warranty claim cannot be substantiated
With Structured Damage Documentation
Container number linked at capture by AI-powered OCR — zero manual renaming required
All photos stored in encrypted cloud archive — no dependency on any personal device
Pre-repair and post-repair records stored under the same container number chronologically
GPS location and capture timestamp preserved from field to archive without modification
Serial numbers photographed and linked per replaced component — traceable at every stage
Before/After Scenario: With manual methods, a shipping line raises a dispute three weeks after repair — the damage photos were taken but cannot be located because they were stored in a departing technician's WhatsApp folder. With structured container damage claim documentation, every photo is already indexed under the container number in the central archive, retrievable and distributable in under a minute.
How Container Damage Claim Documentation Works in Practice
01
Capture at Inspection
Photos taken in-app — not in the device camera roll
02
Validate Container Number
AI OCR reads code against ISO 6346 standards
03
Document Pre & Post Repair
Both states stored under one container record
04
Record Serial Numbers
Replaced parts photographed with serial numbers
05
Distribute & Archive
Automated dispatch to shipping lines — full audit trail
STEP 01–02
Capture & Validate at the Point of Inspection
Field technicians photograph damage using ConPDS Checker on their existing smartphone. The container code is read automatically by AI-powered OCR and verified against ISO 6346 standards before the photo is stored — no separate filing step, no risk of cross-container contamination.
STEP 03–04
Pre/Post-Repair Records and Serial Number Documentation
Damage is photographed before any repair work begins. Once repair is completed, post-repair photos are captured and stored under the same container record. Replaced spare parts — particularly for reefer units — are photographed with their serial numbers linked to the container, supporting warranty claims and dispute resolution.
STEP 05
Automated Distribution and Searchable Archive
Rule-based automated distribution dispatches the completed damage photo set to the defined shipping line or leasing company immediately after inspection. Every photo, container number, timestamp, and distribution event is stored in the central ConPDS dashboard — searchable and retrievable in seconds when a claim is raised.
Container Inspection Workflows That Require Structured Damage Documentation
Damage documentation requirements differ across depot operations. ConPDS is configured to meet the specific photo evidence requirements of each workflow listed below — all using the same structured platform.
Gate-In / Gate-Out
Arrival and Departure Damage Records
All six exterior sides photographed at gate-in, with damage close-ups captured and linked to the container record. Gate-out condition re-documented at departure — creating a clear before-and-after record for the full depot stay. The gate-in photo set is the foundation of every subsequent damage claim.
Repair Documentation
Pre-Repair and Post-Repair Evidence
Damage is photographed before work begins and again once repair is complete — both stored chronologically under the container number. This two-stage record provides the visual evidence required for repair estimate authorisation and post-repair billing disputes with shipping lines.
Reefer PTI
Spare Part and Component Documentation
Each replaced component is photographed individually with its serial number captured and linked to the reefer unit's container record. For reefer damage claims submitted via Maersk AEMS Container Maintenance & Repair APIs or other shipping line systems, this serial number record is the traceable evidence layer that supports cost recovery.
Lease Return
Condition at Return — Documented and Distributed
Lease return inspections require a complete photographic record of container condition at the moment of return — often disputed by leasing companies weeks or months later. Structured documentation ensures that the full condition record is timestamped, container-linked, and immediately distributable to the lessor through the guest portal or automated dispatch.
Operational and Claims Benefits of Structured Damage Documentation
search
Faster Claim Resolution
Every photo is already indexed under the container number — retrievable and distributable within seconds of a claim being raised, not hours of manual searching.
verified_user
Stronger Dispute Evidence
GPS location and capture timestamp are preserved from field to archive. A photo taken at inspection cannot be challenged as retroactive when its metadata is independently verifiable.
assignment
Complete Pre/Post-Repair Record
Both the damaged state and the repaired state are stored chronologically under one container record — the exact format shipping lines require for repair estimate authorisation.
link
No Documentation Living on Personal Devices
All photos upload to the encrypted central archive automatically — no inspection record is dependent on any individual's phone or WhatsApp account.
send
Automated Distribution to Shipping Lines
Rule-based dispatch sends the damage photo set to the relevant shipping line immediately after inspection — no manual export, no email attachment workflow required.
Audit Trail, Security, and Compliance for Container Damage Records
Every photo capture, distribution event, and access action within ConPDS is logged automatically — timestamped, locked against modification, and continuously available for audit or dispute review. Container damage records meet the evidence standards required by shipping lines, leasing companies, and insurance assessors.
GPS location and timestamp preserved from moment of capture
Complete distribution audit trail — recipient, channel, timestamp
GDPR compliant — configurable data retention periods
No documentation stored on personal devices or in unsecured chat threads
Audit trail continuous and unmodifiable — no manual logging required
Frequently Asked Questions
What is container damage claim documentation?
▼
Container damage claim documentation is the structured process of capturing photographic evidence of container damage at the point of inspection — with each image linked to a validated container number, timestamped, and stored as a retrievable record to support repair authorisation and shipping line cost recovery. It replaces informal methods such as WhatsApp threads, email attachments, and shared folders with a system where evidence is always findable and always verifiable.
Does container damage documentation software replace our existing DMS or Maintenance and Repair system?
▼
No. ConPDS integrates with existing Depot Management Systems and Maintenance & Repair platforms — including EOS, DepotMaster, Maersk AEMS Container Maintenance & Repair APIs, IMARS, MSC OVMR, Hapag FIS, and custom APIs. It provides the photo evidence layer those systems do not include, without replacing or disrupting the workflows already in place.
Does damage photo capture work without an internet connection?
▼
Yes. ConPDS Checker's AI-powered OCR and all core capture functions run fully offline — photos are stored securely on-device and sync to the central archive automatically when connectivity is restored. Field teams working in port yards, remote depot areas, or locations with intermittent signal are never blocked from capturing or validating damage documentation.
How is container damage photo data kept secure and GDPR compliant?
▼
Photos are encrypted on-device during capture and inaccessible to other applications. 256-bit HTTPS encryption is applied during upload to the central archive. The ConPDS dashboard enforces granular role-based access controls and configurable data retention periods. A continuous, unmodifiable audit trail covers every capture, access, and distribution event — GDPR compliant throughout.
Can shipping lines access container damage photos directly without a manual export process?
▼
Yes. The ConPDS guest portal gives shipping lines, leasing companies, and agents a secure, scoped login. They can search and view only the container records they have been granted access to — eliminating the manual export, formatting, and email attachment process entirely.
Does ConPDS capture spare part serial numbers for reefer damage and warranty claims?
▼
Yes. ConPDS Checker supports photographing replaced components individually, with serial numbers captured and linked to the container record. For reefer damage claims, this creates a traceable documentation trail — each replaced part is associated with the specific container number at the specific repair event, supporting both shipping line cost recovery and manufacturer warranty claims.
Related Resources
Container Repair Claim Documentation Software
How structured photo evidence supports repair estimate authorisation and dispute resolution with shipping lines.
Strengthen Your Container Damage Claim Documentation
Depots that apply structured container damage claim documentation resolve claims faster, reduce disputes, and maintain a complete inspection history — without adding workload to field teams. ConPDS provides the structured container documentation platform that makes this possible, starting on day one.
What Happens Without Structured Damage Documentation
✗ Claims rejected at the evidence stage — repair photos exist but cannot be located because they were stored in a personal device folder or named incorrectly under time pressure.
✗ No pre-repair record available — without a documented baseline, shipping lines dispute the existence of damage at the time of the repair estimate, not just its extent.
✗ Warranty claims unsupported — replaced reefer components without serial number records cannot be linked to the specific container and specific repair event a warranty claim requires.
✗ Distribution disputes unresolvable — when a shipping line claims it never received the inspection photos, there is no distribution log to demonstrate which photos were sent, via which channel, and when.
✗ Audit exposure at compliance reviews — without a continuous and unmodifiable record covering every capture and access event, damage documentation cannot meet the evidential standard required in insurance audits or legal disputes.
