How Container Depots Should Structure Inspection Photo Workflows
A container depot inspection photo programme that relies on WhatsApp threads, email attachments, or shared folders fails the moment a claim, audit, or shipping line dispute demands evidence. This guide sets out the four operational steps — capture, validate, store, distribute — that make depot documentation retrievable, auditable, and defensible from gate-in to lease return.
Trusted by container depots, shipping lines, and leasing companies across Europe — from single-depot operators to large-scale terminal operators processing tens of thousands of photos monthly.
A depot inspection photo workflow is a structured process for capturing, validating, storing, and distributing container inspection photos at every stage of a depot operation — gate-in, gate-out, Equipment Interchange Receipt (EIR) processing, damage recording, and lease return inspections. Checker mobile capture links each photo to a validated container number and retains its capture timestamp; device-recorded location can be included when enabled and available as context, not independent proof of presence. Normal chat or email forwarding does not reliably preserve original capture metadata.
Where ConPDS Fits
ConPDS Checker is the mobile application field technicians use to capture inspection photos in the yard, following this exact sequence — reading and validating the container number, linking the image to the correct record, and syncing to a central archive with optional rule-based distribution. For the full platform view — capture, archive, distribution, and depot-system integration — see the container depot photo management platform overview.
Photos linked to validated container numbers at capture — OCR reads and verifies the container number, with retake or manual entry available if recognition fails
Capture timestamp retained; device-recorded location included when enabled and available as context for later review
All records searchable by container number, date, depot, or inspection type — retrievable in seconds by office staff or supervisors from any browser
Where a distribution rule is configured, documentation can be dispatched to shipping lines, leasing companies, and agents immediately or after a delay, with every attempt logged
Integrates with existing Depot Management Systems (DMS) and Maintenance & Repair systems — adds the photo evidence layer without replacing or disrupting workflows already in place
Most depots processing containers daily use informal methods to manage inspection photos. Each method creates a specific, documented failure pattern — with direct consequences for damage claims, lease return disputes, and compliance reviews that arise weeks or months after the original inspection.
Depot photo volume compounds this fast — see the container depot photo management overview for an operational sense of how many images a single shift's inspections generate. Without structured container-number linking at capture, a single transposed digit in a filename or a WhatsApp thread that gets cleared makes those records permanently unrecoverable.
The Manual Methods — and Their Failure Points
Photos stored in personal device galleries — not linked to container numbers, permanently lost when staff leave or devices are replaced
Ad hoc messaging, mail attachments, and shared drives — organised around people and threads rather than validated container numbers, with no audit trail, no access control, and no searchability
Manual renaming required to meet customer naming conventions — under time pressure, filenames are transposed, abbreviated, or inconsistently formatted
Photos manually associated to container records post-capture — at daily operating volume, this is a routine source of error, not an exceptional one
The Operational Consequences
Damage claims disputed or rejected — photo evidence is linked to the wrong unit, or cannot be located at all when the claim is raised
Normal chat or email forwarding does not reliably preserve original capture metadata, making later review harder
Entire inspection histories lost in a single personnel change — no secondary copy, no system record, no recoverable audit trail
Separate cropping, compressing, renaming, associating, and uploading tasks — each a potential point of failure at daily operating volume
With manual methods: a gate-in photo is forwarded through chat, manually renamed, and filed in a shared folder. Normal chat or email forwarding does not reliably preserve original capture metadata, and a transposed container number can make later retrieval difficult.
With a structured container inspection photo programme: Checker links the photo to the validated container number and retains its capture timestamp. Device-recorded location can be included when enabled and available as context, not independent proof of presence. When a tenant distribution rule is configured, delivery can be immediate or delayed, and every attempt is logged with success or failure.
How a Structured Container Photo Programme Operates in Practice
01
Capture
Mobile, offline-capable
02
Validate
Code validation · AI OCR
03
Store
Searchable archive
04
Distribute
Rule-based · logged
STEP 01
How Are Depot Inspection Photos Captured in the Yard?
Field technicians use ConPDS Checker, the mobile application, to photograph containers at the point of inspection — gate-in and gate-out moves, damage recording, lease return, or any other workflow event. OCR reads the container number on the device, including offline, and verifies the ISO 6346 check digit at the moment of capture; wrong recognition is flagged, and if a number is not recognized, the technician can retake the photo or type it in manually. The application operates fully offline — so technicians working in port yards, remote depot areas, and locations with intermittent signal never lose capability, with photos syncing automatically when connectivity is restored.
STEP 02
How Does the System Link Every Photo to the Correct Container Record?
Checker verifies the ISO 6346 check digit at capture. Wrong recognition is flagged; if the number is not recognized, the user can retake the photo or enter the number manually. Mobile capture retains the timestamp and can include device-recorded location when enabled and available as context. Photos from gate-in, damage inspection, repair, and gate-out can then be retrieved under the same container record.
STEP 03
Where Are Depot Inspection Records Stored and How Are They Retrieved?
All validated photos sync to the ConPDS web dashboard, accessible from any browser by authorised users. Office staff and supervisors search by container number, date range, inspection type, or depot — retrieving the full photo history for any container in seconds. Every container builds its own permanent, chronological visual record — photos, video, and audio stored together, with granular role-based access controls determining who can view, manage, or share documentation at every level of the organisation. For depots that need a full audit log of access and distribution events, learn more about how container inspection audit trail software supports compliance reviews.
STEP 04
How Does Documentation Reach Shipping Lines and Equipment Lessors Without Manual Forwarding?
Where a distribution rule is configured, ConPDS dispatches inspection photos to defined recipients — shipping lines, leasing companies, or agents — via email, FTP, SFTP, or API, either immediately or after a configured delay. Rules are configured once per container ownership or depot workflow, and every distribution attempt is logged with success or failure — channel, recipient, and timestamp. External parties access records through the ConPDS guest portal: a secure, simplified login scoped only to the container records they have been granted permission to view. ConPDS integrates with existing Depot Management Systems (DMS) and Maintenance & Repair systems including EOS, DepotMaster, Maersk AEMS, CMA-CGM, IMARS, MSC OVMR, Hapag FIS, Seaco, Triton, and custom APIs. New integrations are added on request.
The Same Sequence Applies at Every Stage of a Container's Depot Stay
Gate-in, damage recording, pre- and post-repair checks, and lease return all follow the same capture → validate → store → distribute sequence described above — only the photo set and the recipients change. Routing any of these events through ad hoc chats, mail attachments, or shared drives instead reintroduces the same retrieval and dispute risk this guide is written to avoid.
For the full breakdown of how each inspection type — gate-in/gate-out, damage and repair, lease return, and controlled external access — is documented and distributed, see the container depot photo management platform overview.
What a Structured Inspection Photo Programme Delivers Operationally
flash_on
Any Container's Full Photo History in Seconds
Gate-in, damage recording, pre-repair, post-repair, gate-out — all linked to one container record, retrievable by container number regardless of when the inspection occurred.
assignment
Consistent Standards Across Every Inspector and Shift
Structured capture enforces the same documentation process across all inspectors, devices, and lighting conditions — removing the variability that undermines damage claims and shipping line reviews.
link
No Manual Forwarding to Shipping Lines
Where a distribution rule is configured, photos are dispatched automatically instead of forwarded by hand. When a shipping line claims photos were not sent, the distribution log — success or failure, per attempt — resolves the dispute.
Operational Within Days of Onboarding — No New Hardware Required
ConPDS Checker runs on the iOS and Android smartphones already carried by depot technicians. No specialist devices, no IT project, no hardware procurement required before deployment.
sync
Fully Offline-Capable with Automatic Sync
AI-powered OCR and all core functions run without internet. Photos queue on-device and sync automatically on reconnection — no data loss, no delayed uploads in areas with poor signal.
How a Structured Depot Workflow Supports Documentation Compliance and Audit
Every photo capture, distribution event, and access action is timestamped and logged automatically — including photo edits (with the original retained for recovery), tags, notes, and later changes to those fields
Capture timestamp retained; device-recorded location included when enabled and available as context, not independent proof of presence
The ConPDS guest portal gives shipping lines and leasing companies a secure, simplified login scoped strictly to the container records they have been granted permission to view — every login, search, and download logged against the external account
Photos stored encrypted on the device until upload, and encrypted in transit over HTTPS — retention can be set globally across terminals with per-terminal override, and privacy-by-design applies throughout
Frequently Asked Questions
What is a depot inspection photo workflow? ▼
It is a structured process for capturing, validating, storing, and distributing container inspection photos at every stage of a depot operation — gate-in, gate-out, EIR processing, damage recording, and lease return inspections. It replaces informal methods such as WhatsApp threads, email attachments, and shared folders with a retrievable, auditable system where every photo is linked to a validated container number at the moment of capture using ISO 6346 standards.
Does it replace an existing DMS or M&R system? ▼
No. ConPDS integrates with existing Depot Management Systems (DMS) and Maintenance & Repair systems — including EOS, DepotMaster, Maersk AEMS, CMA-CGM, IMARS, MSC OVMR, Hapag FIS, Seaco, Triton, and custom APIs. If your system is not yet supported, we will add the integration on request. It adds the structured photo evidence layer those systems do not provide, without replacing or disrupting the workflows already in place.
Does depot inspection photo documentation work without an internet connection? ▼
Yes. ConPDS Checker runs its AI-powered OCR and all core capture functions fully offline. Photos are stored securely on-device and sync automatically when connectivity is restored — making the workflow fully operational in port yards, remote depot areas, and locations with intermittent signal.
How is depot inspection photo data kept secure and privacy-by-design? ▼
Photos are stored encrypted on the device until upload, and inaccessible to other applications during field capture. HTTPS encryption is applied during upload. The central dashboard enforces role-based access controls, retention that can be set globally across terminals with per-terminal override, and a continuous audit trail of every capture, access, and distribution event. The platform is privacy-by-design throughout.
How does automated distribution work in this workflow? ▼
Where a distribution rule is configured, ConPDS dispatches photos automatically to defined recipients via email, FTP, SFTP, or API — immediately or after a configured delay. Rules are configured once per container ownership or depot workflow, and every distribution attempt is logged with success or failure — resolving shipping-line receipt disputes without manual investigation.
Related Resources
Checker Email Dropbox
Bring external contractor photos into your Checker archive — email intake with container number in the subject, no app for senders.
Week 1 pillar article — the full platform overview covering capture, validation, storage, and distribution across all container depot and vertical workflows.
Structure Your Container Inspection Photo Programme
ConPDS gives container depots a structured, audit-ready documentation workflow — from mobile capture in the yard to automated distribution and DMS integration. No new hardware. No disruption to existing systems. Operational within days of onboarding.
What Happens Without a Structured Depot Inspection Workflow
✗
Damage claim rejected — photo evidence exists but is attached to the wrong container number. No recoverable record from the correct unit.
✗
Leasing company disputes the baseline — gate-in photos were forwarded through an informal channel with no captured timestamp or location on file. The condition at arrival cannot be verified.
✗
Capture context is unclear — normal chat or email forwarding does not reliably preserve original capture metadata, so later review depends on other records.
✗
File cannot be retrieved — the technician who ran the gate-in inspection left three months ago. The photos were on their personal device. No central record exists.
✗
Manual search consumes hours — a shipping line requests the full gate-in set for 14 containers. Staff spend three hours across email threads, shared folders, and messaging apps. Some photos are missing. The rest arrive late.
With this workflow in place, any inspection record is retrievable in seconds — and the next claim, audit, or shipping line dispute is resolved with evidence, not explanations.
