Skip to main content
CONPDS CHECKER

How to Maintain an Audit Trail for Container Inspections

Without a structured audit trail, inspection records live in personal inboxes, WhatsApp threads, and file servers — unverifiable, untraceable, and useless during claims or audits.

Trusted by container depots, shipping lines, and leasing companies across Europe

What Is a Container Inspection Audit Trail?

An inspection evidence trail is a chronological log of every inspection photo, event, and user action tied to a container — each entry timestamped, ISO 6346-linked, and stored centrally as continuous audit documentation.

This allows container depots to trace who captured what, when, where it went, and who accessed it — creating a complete inspection chain of custody system for audits, disputes, and compliance checks.
ConPDS maintains this audit trail automatically at every stage of the inspection lifecycle. Every photo captured by ConPDS Checker is timestamped during field capture, linked to a validated container number, and synced to an encrypted central archive — with every subsequent access, distribution, and modification event logged against a named user. Photos captured in the mobile app cannot be tampered with in flight; once in the system, edits are logged and originals retained for restore. The result is a continuous documentation chain that covers the full journey from field capture to external recipient.
Inspection timestamp recorded at moment of photo capture — not on upload
Container number validated and linked automatically
User activity logged — access, modification, and distribution events against named users
Secure cloud storage with configurable retention periods and role-based access controls
Full retrieval — any container's complete photo history and audit log accessible instantly by container number

Why Unstructured Container Inspection Records Create Serious Audit Trail Gaps

Documentation Failures

Normal chat or email forwarding does not reliably preserve original capture metadata or enforce a container-number link
Manual file naming creates association errors — a single transposed character makes a photo permanently unfindable
Photos stored on personal devices disappear entirely when an employee leaves or a device is replaced

Compliance & Dispute Risk

In a GDPR review or insurance audit, there is no way to demonstrate what was documented, when, or by whom — absence of records is itself an exposure
Damage dispute counterparties routinely challenge photo timestamps not locked during the inspection itself
No visibility over who accessed or shared inspection records — access events are entirely unlogged
Operational scale, structural risk: A depot processing 100 containers per day generates 600+ inspection images daily. Without structured container-number linking and timestamping, that volume increases the risk of missing or mislinked records and makes later reconstruction harder.
With manual methods: a shipping line disputes gate-in condition weeks after handover. The photos existed only in a chat thread that has since been cleared. Normal chat or email forwarding does not reliably preserve original capture metadata, and there is no container-linked system record to retrieve.

With a structured chain-of-custody record: Checker links the photos to the container number and retains the capture timestamp. Device-recorded location can be included when enabled and available as context, not independent proof of presence. Access and configured distribution attempts are logged for later review.

How a Structured Inspection Audit Log Works in Practice

01
Capture
Timestamped at source
02
Validate
OCR code link
03
Log
User activity trail
04
Store
Encrypted archive
05
Retrieve
Instant by container
STEP 01

Timestamping at the Moment of Capture — Not on Upload

ConPDS Checker records the precise timestamp and device-recorded geographic capture location when available at the moment each photo is taken — not when it is uploaded to the server. This distinction is operationally critical: if timestamp data is only applied on upload, the record can be challenged as retrospective. Photos captured in the mobile app cannot be tampered with in flight; capture-time metadata survives transfer to the central platform. Device GPS is not independently verifiable proof of presence — it is the location the device recorded when configured and available.

STEP 02

Container-Number Validation via AI-Powered Container Number OCR

Checker reads container numbers on-device with ISO 6346 check-digit verification. Wrong recognition is flagged so the user can retake or enter the number manually, reducing manual association errors before the record is stored.

STEP 03

User Activity Logging Across the Entire Documentation Lifecycle

Every action in the ConPDS platform is logged against a named user: who captured each photo, who accessed which container record, who approved or modified documentation, who triggered a distribution event, and which external party viewed records through the guest portal. For example, when a shipping line accesses an inspection report through the guest portal, that event — including timestamp, user identity, and container ID — is automatically logged. The audit trail covers the complete chain of custody — from the technician in the yard to the shipping line reviewing compliance-ready photo evidence online.

STEP 04

Encrypted Cloud Storage with Configurable Retention

Photos use encrypted on-device storage until upload. HTTPS transport protects the transfer to the EU-hosted central archive, where role-based access controls and configured retention apply. Temporary on-device local-copy behaviour after upload is stated once in the security FAQ below.

STEP 05

Instant Retrieval and Structured Distribution on Demand

Records can be retrieved by container number and exported or shared through the scoped guest portal. When a tenant distribution rule is configured, Checker can dispatch via email, FTP, SFTP, or API immediately or after a configured delay, with every attempt logged. The tenant audit log reference shows what is recorded.

Container Inspection Workflows That Require a Structured Audit Trail

LEASE RETURN INSPECTION

End-of-Lease Condition Documentation

A structured lease return record can support review of pre-existing versus new damage. When a tenant distribution rule is configured, the record can be sent immediately or after a configured delay, with the attempt logged.

DAMAGE & REPAIR CLAIM

Pre- and Post-Repair Photo Evidence

Repair documentation requires before-and-after photo evidence to support a repair claim. The audit trail records not only the photos but the repair event sequence — damage identified, estimate raised, repair completed, photos taken — with every action timestamped and user-logged to create audit-traceable container photos as defensible claim evidence.

GATE-IN / GATE-OUT

EIR and Condition Capture

Every gate-in event generates a timestamped, container-linked photo set covering all six exterior sides. The audit trail records when the EIR was created, which technician performed the inspection, and confirms the gate-in condition at a verifiable point in time — the baseline record for any future damage claim or lease dispute.

EXTERNAL DISTRIBUTION

Shipping Line and Leasing Company Access Logging

Every photo set or inspection report dispatched to a shipping line or leasing company — whether via email, FTP, API, or guest portal login — is recorded automatically with the recipient identity, dispatch timestamp, and container reference. The depot always has a verifiable record of what was shared, when, and with whom.

WASH STATION

Pre- and Post-Wash Condition Record

Wash station operations require documentation of container condition on arrival and post-wash to support cleaning certificates. The audit trail records the full wash event — arrival condition, wash completed, post-wash photos — as a continuous sequence of timestamped actions rather than isolated images with no connective record.

REEFER PTI

Spare Part and Post-Repair Traceability

Reefer PTI documentation includes replaced spare parts photographed with serial numbers captured for warranty purposes. The audit trail links each spare part record to the specific container and PTI event — creating a component-level chain of custody that shipping lines and leasing companies can verify directly through the guest portal. Learn how audit-traceable records support reefer PTI claims with part-level documentation →

What a Structured Inspection Audit Log Delivers

Resolve Disputes in Minutes, Not Days

Any container's full history — photos, timestamps, access log — retrievable in seconds, not days of manual searching.

Compliance Confidence

A complete, structured audit log means GDPR reviews, insurance audits, and contractual compliance checks draw on verifiable records — not reconstructed approximations.

Audit-Logged Chain of Custody — From Yard to Claim

Capture, access, distribution, edits, tags, notes, and later changes are logged; when a photo is edited, the original upload is retained for recovery.

Automated Distribution with Full Logging

When a tenant rule is configured, Checker can dispatch inspection records immediately or after a configured delay, with every attempt logged as a success or failure.

No Documentation Lost to Personnel Changes

The central archive remains authoritative regardless of staff turnover — records stay retrievable by container number after device or personnel changes.

Works Fully Offline

ConPDS Checker captures and timestamps inspection photos in port yards and remote depot areas without connectivity — audit trail data syncs automatically on reconnection.

Compliance and Security Architecture

Privacy-by-design Full Audit Trail End-to-End Traceability 256-bit Encrypted Storage Role-Based Access Control Code Validated Configurable Retention Periods
Photos encrypted on-device and inaccessible to other applications — audit trail integrity begins during field capture, not on upload
256-bit HTTPS encryption during transfer, with role-based access controls applied at individual user level across the entire organisation
Guest portal access is scoped strictly to records the external party has been explicitly granted permission to view — every guest login and container access event is logged in the audit trail
Integrates with existing depot management systems and maintenance & repair platforms without replacing them — ConPDS adds the structured photo evidence and audit layer your current stack is missing. See how the ConPDS depot inspection compliance platform fits alongside your existing systems.

Frequently Asked Questions

What is a container inspection audit trail?
An inspection evidence trail is a structured, chronological record of inspection actions, photos, access events, and documentation updates linked to a container. Checker logs capture, access, distribution, edits, tags, notes, and later changes.
Does ConPDS replace an existing depot management system?
No. ConPDS integrates with existing depot management systems and maintenance & repair platforms — including EOS, DepotMaster, Maersk AEMS, CMA-CGM, IMARS, MSC OVMR, Hapag FIS, Seaco, Triton, and custom APIs — adding the structured photo documentation and audit trail layer those systems cannot provide without disrupting existing workflows. If your system is not yet supported, we will add the integration on request.
Does ConPDS work offline in port yards and remote depot areas?
Yes. ConPDS Checker operates fully offline — including on-device OCR with ISO 6346 check-digit verification and automatic timestamping. Wrong recognition is flagged for retake or manual entry. All core functionality is available without an internet connection. Photos and audit trail data sync automatically to the central platform once connectivity is restored, with no manual action required from the field technician.
Is the audit trail data privacy-by-design and secure?
Yes. Photos are stored encrypted on the device until upload, and a local copy is retained for about seven days after successful upload. HTTPS encrypted transport, role-based access controls, configurable retention, and audit logging support privacy-by-design workflows.
Can audit trail records be exported and shared with shipping lines or leasing companies?
Yes. Records can be exported from the dashboard. When a tenant distribution rule is configured, Checker can send them via email, FTP, SFTP, or API immediately or after a configured delay, and every attempt is logged with success or failure. External parties can also receive scoped guest-portal access, with each access event logged. Learn how container depots structure gate-in and lease return documentation for shipping line distribution.
Does ConPDS log all user access and modification events?
Yes. Every inbound photo, distribution event, guest portal login, container record access, and modification action is logged with the responsible user identity, timestamp, and container reference. The audit trail covers the complete documentation lifecycle with no gaps — from the field technician capturing the photo through to the external recipient viewing it through the guest portal.
Does ConPDS integrate with shipping line systems for automated audit trail distribution?
Yes. ConPDS integrates with Maersk AEMS, MSC OVMR, Hapag FIS, IMARS, Triton, Seaco, CMA-CGM, and other supported systems. When a tenant rule is configured, distribution can run immediately or after a configured delay, and every attempt is logged with success or failure.

Ready to Build a Complete Audit Trail for Every Container Inspection?

ConPDS maintains a continuous audit trail automatically — from the first photo taken in the yard through every distribution event and later edit logged against a named user, with originals retained for restore when photos are edited.

What Happens Without a Structured Inspection Audit Log
Weak damage-dispute record: photos remain in a chat thread or shared folder without an enforced container link. Normal chat or email forwarding does not reliably preserve original capture metadata.
Audit failure by absence: in a GDPR review or insurance audit, the organisation cannot demonstrate what was documented, when, or by whom — the absence of structured records is itself a compliance exposure.
Evidence lost to personnel changes: inspection histories held on personal devices or in individual inboxes vanish permanently when an employee leaves — no recovery is possible after the fact.
No visibility over external access: there is no record of which shipping line representative accessed which container documentation, when, and what they viewed — distribution is entirely unlogged.
Claim costs absorbed without recourse: repairs the depot performed and damage that was pre-existing cannot be proven, so the cost is carried rather than recovered through a supported claim.

With ConPDS, every inspection event — from gate-in through to reefer PTI, wash station documentation, and lease return — builds into a searchable, exportable audit trail that turns scattered field data into defensible records.

ConPDS replaces scattered records with a continuous, logged inspection history — retrievable instantly, exportable in seconds, and trusted by leading shipping lines.

No obligations — reply within 1 business day