Skip to main content
GOVERNANCE · RETENTION · ACCESS · EVIDENCE CHAIN

Container Inspection Audit, Compliance & Evidence-Chain Software

Used by container depots, terminals, reefer service facilities, wash stations, and shipping-line operations across Europe, Africa, Australia and the Middle East — including operators with active CSC, ACC, lessor, shipping-line, and GDPR audit obligations.
ConPDS Checker is the audit, compliance, and evidence-chain layer for container operations. It captures inspection photos in a continuous, container-indexed audit trail under tenant-controlled retention, role-based access, and logged capture, access, edit, and distribution events — so every CSC inspection, lease return, repair stage, and wash record is defensible the moment an auditor, lessor, shipping-line counterparty, or DPO asks for it.

Built for the operations leaders, quality managers, and compliance officers who carry the audit posture of multi-site container operations — and who need one governance layer behind every audit cycle, not one improvisation per audit. Replace ad-hoc photo libraries and shared folders with structured inspection records that survive CSC periodic inspections, ACC cleaning audits, lessor and shipping-line audits of repair history, and internal GDPR data-handling reviews under one retrieval mechanism.

No obligations — reply within 1 business day · Privacy-by-design · EU-hosted infrastructure · standard DPA on request.
Capture timestamp & device-recorded GPS when available — continuous audit trail
Configurable retention per tenant and inspection type
Role-based access control (RBAC) with end-to-end audit log

Why most inspection records collapse the moment an audit lands

Container inspection records become audit evidence only when four governance properties hold: continuous audit capture, validated container indexing, controlled retention, and a logged access chain. Photos in a shared drive, a chat thread, or a depot manager's phone meet none of those tests — and an auditor, lessor, shipping-line counterparty, or DPO disputes the inspection by default when the record cannot be reconstructed quickly under those four headings. The exposure does not sit with the field worker; it sits with the leadership team that signs off the audit posture.

In many operations, inspection records are still

Stored in shared folders without container-number linkage
Subject to silent rename, replace, or back-date with no audit trail
Stripped of GPS and timestamp metadata by chat-app compression
Retained for "as long as it takes to fill the disk" — not by policy
Accessible to anyone with the network share — no role separation

The result when an audit arrives

CSC / ACC inspection records cannot be produced under the audit deadline
Lessor audits of repair history return incomplete or unverifiable evidence
GDPR access requests cannot be answered without ad-hoc folder searches
No access log — no record of who viewed or distributed the inspection evidence
Audit defensibility is built into the inspection workflow at capture, not negotiated when the auditor arrives. For the underlying mechanics, see how container inspection audit trail software works and digital documentation standards in modern container depots.

A Continuous Audit Inspection Workflow — From Capture to Audit Production

ConPDS Checker structures container inspection documentation around the four disciplines an auditor actually checks: continuous audit capture, validated container linkage, controlled retention, and on-demand production.

01
Capture
02
Link
03
Retain
04
Produce
Step 01 — Capture

Logged Photo and Metadata Capture

Field staff capture inspection photos on standard smartphones; the app retains timestamp, device-recorded geographic location when available, and device identity at the moment of capture. Photos captured in the mobile app cannot be tampered with in flight; once in the system, users can edit and annotate, and when a photo is edited Checker keeps the original upload for restore.

Step 02 — Link

ISO 6346 Validation Linked to the Inspection Record

On-device OCR with ISO 6346 check-digit verification reads and validates the container number (owner code, serial number, and check digit). Wrong recognition is flagged so the user can retake or enter the number manually — linking every photo to the active inspection record at capture and reducing misattribution between containers, inspection types, or counterparties.

Step 03 — Retain

Configurable Retention and Role-Based Access

Retention windows are configurable per tenant and per inspection type — CSC inspections on the periodic cycle, lease returns on the contractual claim window, wash records on the customer audit horizon. RBAC scopes who can view, export, or distribute each record, and every access event is logged.

Step 04 — Produce

One-Click Audit Production

Container number, work-order reference, date range, depot, or inspection type returns the matching record in seconds. Full structured exports — photos plus metadata under a single ISO 6346-validated reference — are a one-click action when an auditor, lessor, or counterparty asks.

What Audit-Defensible Documentation Actually Requires

Six properties separate audit-grade inspection documentation from a folder of phone photos. ConPDS Checker bakes all six into the record at capture — not after the auditor arrives.

Continuous Audit Capture
Timestamp, device-recorded GPS when available, and device identity retained at capture — mobile captures cannot be tampered with in flight; edits keep the original for restore.
ISO 6346 Validated Link
Every photo linked via on-device OCR with ISO 6346 check-digit verification — wrong recognition flagged for retake or manual entry.
Configurable Retention
Retention windows scoped per tenant and per inspection type — CSC, lease return, wash, repair each on the correct audit horizon.
Role-Based Access Control
Field capture, office review, audit-only access, guest portal viewing — each scoped to the user's actual function.
End-to-End Access Log
Every capture, view, export, and distribution event logged — the access log is itself part of the audit record. The audit log documentation lists every event type recorded.
Privacy-by-design & EU-hosted
Encryption at rest and in transit, EU-hosted infrastructure, standard DPA, support for subject access and deletion requests — built for GDPR-governed workflows.

Ad-hoc inspection records vs the audit-grade evidence chain

An auditor's first question is "show me the inspection record for this container on this date — and the access log for who has seen it." The operator with the evidence-chain layer produces it in seconds and passes the audit. The operator without it reconstructs from chat threads and shared folders, fails the request, and inherits a finding. The difference is built into the workflow at capture, not negotiated afterward.

✗ Ad-Hoc Inspection Records
Photos in shared folders or chat threads — not container-indexed
GPS / timestamp metadata stripped or modifiable
Retention by accident — until the disk fills or the staff member leaves
Anyone with the network share can view, edit, or delete
No audit log — no record of who viewed or distributed what
✓ Audit-Grade Documentation with ConPDS
Photos linked to ISO 6346-validated container records at capture
Timestamp / device-recorded GPS when available / device identity retained — in-flight captures protected; edits keep original for restore
Retention enforced automatically per tenant and inspection type
RBAC — field, office, audit-only, guest each scoped
Continuous audit trail — every capture, view, export, distribution, and edit logged

Frequently Asked Questions — Audit & Compliance Documentation

What is container inspection audit and compliance documentation software?
Container inspection audit and compliance documentation software captures container inspection photos and the surrounding metadata in a continuous, container-indexed audit trail — with configurable retention, role-based access control, and automatic logging of every capture, view, edit, and distribution event. It is the evidence layer that survives a CSC inspection audit, an ACC cleaning audit, a lessor or shipping line audit of repair history, and an internal GDPR-governed data-handling review, with a single retrieval mechanism behind every audit type.
What audit standards and inspection regimes does the platform support?
ConPDS Checker provides the structured photographic evidence layer required by CSC periodic inspections, ACC (Acceptable Container Condition, the ITCO tank inspection guideline) compliance, ACEP and PES inspection regimes, IICL-6 and UCIRC inspection standards, and lessor / shipping line audit requirements. The platform does not certify the inspection itself — that remains the inspector's responsibility — but it captures, links, and retains the photo evidence the certifying body requires.
How does Checker protect and log inspection records?
Photos captured in the mobile app cannot be tampered with in flight; once in the system, users can edit and annotate, and when a photo is edited Checker keeps the original upload for restore. Capture retains timestamp, device-recorded geographic location when available, and device context. Checker keeps a continuous audit trail of capture, access, distribution, guest access, exports, and integration delivery — including photo edits, tags, notes, and later changes — tied to the user account that performed each action.
How are retention periods configured for different audit windows?
Retention is configurable per tenant and can be scoped by inspection type, container class, or counterparty — so a CSC inspection retained on the periodic-inspection cycle, a lease return retained for the contractual claim window, and a wash record retained for the customer's audit horizon all run on independent schedules.
Is the platform privacy-by-design and where is data stored?
Yes. All data is stored on EU-hosted infrastructure with encryption at rest and in transit. Each customer operates in its own secure tenant — inspection records are visible only to the customer and to parties the customer explicitly grants guest portal access to. ConPDS provides the standard data processing agreement and supports data subject access and deletion requests within the legal retention period.
How is access controlled — and how is it logged?
Access is role-based and scoped to the function the user actually needs — field capture, office review, integration administration, audit-only review, or guest portal viewing. Every access event is logged: who viewed which container record, from which device, at what time, and what they did with it. The access log itself is part of the audit record.
How quickly can a full inspection history be produced for an auditor?
Container number, work-order reference, date range, depot, or inspection type — any of these returns the matching inspection history in seconds from the web dashboard. A full structured export (photos plus metadata in a single package) is a one-click action.
Trusted by container operations across Europe, Africa, Australia and the Middle East
Alisan Den Hartogh Aktas APM Terminals Autamarocchi CCIS Contrepair Cut Coal Eimskip Eurobox Gruppospinelli HRS Isotank Central James Group International Medlog Namops Logistics Porpet QTerminals Kramer Rotterdam Rhespa Europe SDT Marine & Cargo Washmed Werra Kombi Terminal Zuidnatie Zwennis Containers

Pass the audit on the first request — every audit, every cycle

See how ConPDS Checker turns container inspection documentation into a governance layer the leadership team can rely on across audit cycles — continuous audit capture, configurable retention per inspection type, role-based access, logged edits with originals retained for restore, privacy-by-design on EU-hosted infrastructure with standard DPA on request.