CATEGORY DEFINITION

Container Operational Evidence: Definition and Workflow

Q: How is this different from a photo documentation app?

A photo documentation app captures files. An operational evidence system captures records with validated container numbers, retention rules, metadata, access history, distribution logging, and on-demand retrieval. The difference matters when evidence must survive a repair dispute, lessor audit, off-hire claim, or compliance review.

Container operational evidence is the defensible, container-linked record of every inspection, repair, lease return, gate event, PTI, and wash that has happened to a container — captured during the operation, retained under operator-controlled policies, and produced on demand for the disputed charge, the lessor audit, the M&R dispute, and the compliance review. The platform that produces it is the evidence infrastructure underneath the depot, the workshop, the wash bay, and the gate. People still type "container operational evidence" into Google when looking for it — that is the popular phrase for the same category, just framed at the wrong altitude.

No obligations — reply within 1 business day

What Is Container Operational Evidence?

Container operational evidence is the defensible record of what has happened to a container — every inspection, every repair, every lease return, every PTI, every wash, every gate event — captured during the operation and tied to the ISO 6346-validated container number. The category is defined by four properties together: container-linked at capture (not after the fact), retained under business-controlled rules, audit-logged end to end (capture, access, distribution), and producible on demand for the disputed charge, the lessor audit, and the maintenance and repair claim. Take any of the four away and you do not have evidence — you have photos.

The evidence infrastructure is the platform that produces this evidence — purpose-built for container depots, terminals, repair workshops, wash stations, gate operations, and compliance teams. It replaces informal methods (ad-hoc messaging, mail attachments, shared drives) with a defensible record built into the workflow, not bolted onto it. ConPDS is the structured implementation of this category: container-linked records flow from Checker in the field, Tracker at the camera, and Autogate at the gate into a single audit-logged chain.

Captures container records via mobile — Android and iOS, on the devices the team already carries, no specialist hardware required

Validates the ISO 6346 container number at the point of capture using on-device OCR with check-digit verification — wrong recognition flagged for retake or manual entry

Retains photo, video, and audio chronologically per container under role-based access and configurable retention rules

Produces evidence on demand for shipping lines, leasing companies, agents, and auditors via email, FTP, API, or guest portal — every distribution event logged

Integrates with existing Depot Management Systems (DMS) and Maintenance & Repair systems — adds the evidence layer DMS platforms do not provide, without replacing existing workflows

Maintains a continuous audit trail of every capture, access, distribution, and later edit (original retained) — including tags and notes

Why Informal Documentation Becomes Operational Risk

Many depots, workshops, and gates handling dozens of containers daily rely on informal methods for inspection records. A depot processing 100 containers per day generates 600+ images daily; without container-linked capture and an audit-logged chain, that volume increases the risk of missing or mislinked records during later review.

The Informal Methods

WhatsApp threads as the primary record — original camera metadata not reliably available after a normal chat send; records lost when threads are cleared or devices replaced

Email attachments with inconsistent naming — a single transposed character makes a file permanently unfindable

Shared folders without enforced structure — photos manually renamed under time pressure, associated to the wrong container number

Records on personal devices — months of documentation lost in a single personnel change, and no audit log of who saw or shared what

The Operational Consequences

Repair claims disputed or rejected — evidence cannot be found, or is attached to the wrong container unit

Shipping lines and lessors challenge whether photos were taken at inspection or retroactively — missing capture timestamp or device-recorded GPS when available

Audits and compliance reviews where the operation cannot demonstrate what was inspected, when, by whom, or with what result

Separate cropping, compressing, renaming, associating, and uploading tasks — each a potential point of failure under high-volume conditions

How the Operational Evidence Layer Works in Practice

Capture

Mobile, offline-capable

Validate

ISO 6346 OCR at capture

Retain

On terms you control

Produce

On demand, audit-logged

STEP 01

How Is Container Operational Evidence Captured in the Field?

Field technicians use the ConPDS Checker mobile application to capture container records directly at the depot, terminal, port, workshop, or wash bay. Checker reads ISO 6346 container numbers via on-device OCR with check-digit verification — wrong recognition flagged for retake or manual entry — links every photo, video, and audio note to the correct container record, and syncs to the central platform — fully offline-capable. Technicians can capture up to 30 seconds of video or spoken audio commentary per container, providing context that static photos alone cannot convey — critical for reefer compressor checks, repair findings, and damage walk-throughs.

STEP 02

How Is Each Record Validated Against the Container Number Standard?

Container number validation occurs at the moment of capture — not during manual upload or filing. Checker verifies the ISO 6346 check digit; wrong recognition is flagged for retake or manual entry. Mobile capture retains the timestamp and can include device-recorded location when enabled and available; location is context for review, not independent proof of presence. The workflow reduces separate renaming, reformatting, resizing, and uploading tasks.

STEP 03

How Is the Evidence Retained on Terms the Operation Controls?

All validated records are retained in a cloud-based dashboard accessible from any browser, hosted on EU infrastructure with privacy-by-design. Office staff search by container number, depot, date range, or inspection type. Every container builds a chronological evidence record — photos, video, and audio together — under granular role-based access controls and configurable retention periods. Capture, access, distribution, and later edits (original retained) are logged in a continuous audit trail.

STEP 04

How Is Evidence Produced on Demand for Customers, Lessors, and Auditors?

When a tenant distribution rule is configured, Checker can dispatch container-linked evidence via email, FTP, SFTP, or API immediately or after a configured delay. Every attempt is logged with success or failure. External parties can also access permitted records through the scoped guest portal. The platform integrates with EOS, DepotMaster, Maersk AEMS, CMA-CGM, IMARS, MSC OVMR, Hapag FIS, Seaco, Triton, and custom APIs; further integrations can be offered on request.

Where the Evidence Layer Is Used

The evidence layer supports every stage of the container lifecycle — from gate-in inspection through repair and PTI to lease return, M&R claim defence, and the lessor audit. These are the most common operational contexts where defensible, container-linked records replace informal methods.

Depot & Gate Operations

Gate-in inspection — full six-side record linked to the container number and Equipment Interchange Receipt (EIR) at arrival

Gate-out documentation — container condition re-documented at departure, creating a clear before-and-after evidence record for the full depot stay

EIR processing — evidence matched to the Equipment Interchange Receipt at every handover point

Lease return inspection — timestamped condition record protecting the depot from pre-existing damage liability under lessor audit

Claims, Audit & Compliance

Container damage documentation — close-up records of damage location, type, and extent linked to the container number

M&R claim defence — pre- and post-repair evidence attached to the repair estimate for shipping line submission and dispute defence

Damage claim evidence — container-linked record with booking reference for cargo and equipment dispute resolution

Audit posture — complete, retrievable inspection and gate history available for every container on request, every audit, every depot

Informal Methods vs. the Operational Evidence Layer

Informal Method	Operational Evidence Layer
WhatsApp threads — original camera metadata not reliably available after a normal chat send; records lost when devices change; no audit log	Container-linked records with capture timestamp retained and device-recorded location when enabled and available as context
Manual file renaming — one typo makes a photo permanently unfindable	Automatic ISO 6346 container number validation at capture — on-device OCR with check-digit verification; retake or manual entry when needed
Shared folders without structure — no enforced naming or organisation	Searchable container archive — find any container's full evidence history in seconds
Email distribution — no record of receipt, no delivery confirmation, no audit chain	Rule-based automated dispatch with full distribution audit trail per container event
Personal devices — months of records lost in a single personnel change, no central retention	Central cloud archive under business-controlled retention — every record retained regardless of staff changes

What the Operational Evidence Layer Delivers

Evidence Producible in Seconds

Find any container's full evidence history in seconds — by container number, date, or depot — without searching email threads, chat archives, or shared folders.

Operational Within Days of Onboarding

The team begins capturing container-linked records within days of onboarding. No lengthy implementation, no training programme, no IT project required before deployment.

AI-Powered ISO 6346 Recognition

On-device OCR built specifically for the container number standard — reads and verifies the ISO 6346 check digit at capture; wrong recognition is flagged for retake or manual entry.

Fully Offline-Capable

All core functions — OCR, capture, container linking — run without internet. Records sync automatically on reconnection. No cloud dependency for field operations.

Integrates with Existing DMS and M&R Systems

Adds the container-linked evidence layer the current stack is missing — without replacing or disrupting the workflows already in place.

No Capital Outlay

Subscription-based pricing. Setup, configuration, onboarding, and ongoing operational support are all included — no separate implementation charges, no hidden fees.

Security, Compliance, and Audit Trail

Privacy-by-design Continuous Audit Trail Device-recorded GPS when available + Timestamp at Capture 256-bit HTTPS Encryption Role-Based Access Control Configurable Retention Periods

Every capture, distribution event, access action, and later edit (original retained) is timestamped and logged automatically — a continuous audit trail that requires no manual logging at any stage

Capture timestamp retained; device-recorded location included when enabled and available as context for review, not independent proof of presence

A complete distribution audit trail records who received which records, via which channel, and when — resolving disputes about whether evidence was shared in seconds rather than days

Guest portal access is fully logged — every external login, container search, and download recorded against the guest account, confirming receipt and engagement with the evidence

For Shipping Lines & Leasing Companies ISO 6346-validated container evidence can reduce claim cycle time and improve dispute review accuracy by providing a retrievable condition history across multiple depots. When a shipping line or leasing company requests evidence of container condition at any point in its history, the full timestamped record can be retrieved and shared in seconds — not assembled from email threads over several days.

Frequently Asked Questions

How should operators define container evidence? ▲

Container operational evidence is the defensible record of every inspection, repair, lease return, gate event, PTI, and wash that has happened to a container — captured during the operation, linked to the ISO 6346-validated container number, retained under operator-controlled policies, and produced on demand for the disputed charge, the lessor audit, the M&R dispute, and the compliance review. The platform that produces it is the evidence infrastructure underneath the depot, the workshop, the wash bay, and the gate.

How is this different from a photo documentation app? ▲

A photo documentation app captures files. ConPDS captures records with validated container numbers, retention rules, metadata, access history, distribution logging, and on-demand retrieval. The difference matters when evidence must survive a repair dispute, lessor audit, off-hire claim, or compliance review.

Does the evidence infrastructure replace a depot management system? ▲

No. It integrates with existing Depot Management Systems (DMS) and Maintenance & Repair systems — adding the container-linked evidence layer DMS platforms do not provide, without replacing or disrupting workflows already in place.

Does the evidence workflow work offline? ▲

Yes. ConPDS Checker runs on-device OCR with ISO 6346 check-digit verification and all core capture functions fully offline. Wrong recognition is flagged for retake or manual entry. Records are stored securely on-device and sync automatically when connectivity is restored — making it operational in ports, terminal yards, and remote depot areas with intermittent signal.

How is this evidence kept secure and defensible? ▲

Records are encrypted on-device and inaccessible to other applications. 256-bit HTTPS encryption is applied in transit. The central dashboard enforces granular role-based access, configurable data retention, and a continuous audit trail of every capture, access, edit (original retained), and distribution event. Storage is privacy-by-design in EU infrastructure. Edits and later changes are logged — defensibility comes from the continuous audit trail, not from claiming an immutable log.

What is the difference between a depot management system and evidence infrastructure? ▲

A depot management system (DMS) manages container inventory, bookings, and operational data — it tells the depot what should be happening. ConPDS captures, retains, and produces the defensible record of what did happen — the container-linked proof behind every charge, claim, audit, and dispute. The DMS is the system of record for operations; the evidence archive is the system of record for what those operations produced. Both are needed; neither replaces the other.

Can ConPDS integrate with Maersk, MSC, Hapag, and DMS systems? ▲

Yes. ConPDS integrates with Maersk AEMS, CMA-CGM, MSC OVMR, Hapag FIS, IMARS, Seaco, Triton, EOS, DepotMaster, and custom APIs via REST, FTP, SFTP, and email. When a tenant rule is configured, records can be distributed immediately or after a configured delay, and every attempt is logged with success or failure. Further integrations can be offered on request.

See the Evidence Layer in Practice

A shipping line disputes a container damage claim four months after gate-out. With informal methods, the depot searches email threads and shared folders — and cannot locate the gate-in record. With ConPDS, the full container history is retrieved in seconds and the dispute is resolved before it escalates. A disputed repair without defensible evidence becomes a direct operational cost; a defensible record turns it back into a closed file.

What Happens Without Defensible Evidence

✗ Unresolvable damage disputes. When a claim is raised months after inspection, the depot cannot produce a timestamped, container-linked record — and carries the cost of damage it cannot prove was pre-existing.

✗ Failed compliance audits. Without a continuous audit trail of capture, access, distribution, and later edits, the depot cannot demonstrate to a shipping line, leasing company, or regulator what was inspected, when, or by whom.

✗ Rejected M&R claim submissions. Repair claims submitted without container-linked, before-and-after evidence are routinely challenged by shipping lines — increasing claim cycle time and reducing recovery rates.

✗ Unrecoverable EIR gaps. Gate-in and gate-out records held in informal systems cannot be reliably matched to Equipment Interchange Receipts — leaving handover condition disputes with no defensible resolution.

✗ Operational exposure at scale. Every container processed without defensible evidence is a liability — the risk compounds with volume, and a single high-value dispute can exceed the annual cost of the evidence layer.

If the operation handles container inspection daily, a container-linked evidence layer reduces retrieval failures, eliminates manual filing errors, and creates defensible records for every claim, every audit, and every shipping-line review.