STANDARDS EXPLAINER

Digital Documentation Standards in Modern Container Depots

Inspection criteria tell you what to check. Digital documentation controls tell you whether the resulting photo evidence is linked, retrievable, and logged — they do not invent the external requirements.

For multi-site and compliance leads: which practices are official or counterparty requirements, and which are vendor platform controls you choose and configure? Mixing the two creates false certainty — and gaps when a claim or audit arrives.

Primary path: inspection criteria reference · audit trail how-to

Official Requirements vs Vendor Controls

In depot language, “digital documentation standards” usually mixes two layers. External requirements come from industry instruments and counterparties: the ISO 6346 container number format; inspection criteria such as IICL-6, UCIRC, and CIC; CSC examination schemes; and contract, carrier, lessor, or insurer procedures for handover evidence. Vendor / platform controls are how photos are captured, linked to a container number, stored, retained, accessed, distributed, and logged. Criteria define what to inspect. Controls determine whether the photo record can still be found and explained later.

Exact photo sets, metadata fields, and retention periods are not a single universal industry rule — they follow the applicable contract and counterparty process. Useful condition records often include identifiable container association, dated capture, and matched views relevant to the disputed item. See the companion reference on container inspection criteria and evidence standards for what the criteria themselves cover — and what they leave to your evidence practice.

A Practical Split: Requirements and Controls

Use this matrix when writing SOPs, selecting software, or answering “are we compliant?” Without the split, teams either over-claim a platform as a standard — or under-invest in the controls that make criteria-backed inspections defensible.

Topic	External / counterparty side	Vendor / platform control side
Container identity	ISO 6346 defines the 11-character container number (owner code, category letter, serial, check digit)	OCR or entry at capture with check-digit verification; retake or manual correction when recognition is wrong; link every photo to that number
What to inspect	IICL-6, UCIRC, CIC, cargo-worthy criteria, CSC / ACEP examination rules	Guided photo sequences and case structure that support the applicable regime — platforms do not replace the criteria
Photo sets & retention	Contract, carrier, lessor, insurer, or internal policy — not a universal “industry photo standard”	Configurable retention, role-based access, searchable archive; align policy to counterparties, not to marketing slogans
Handover & claims evidence	EIR, lease return, and M&R dispute processes set by parties to the move	Container-linked before/after photos, continuous audit of capture/access/distribution, guest or export access when needed
Data protection	GDPR and related law bind the controller’s purposes, lawful basis, and storage limitation — customer responsibility	EU-hosted options, HTTPS, on-device encryption until upload, RBAC, privacy-by-design architecture to support GDPR-governed workflows

What Breaks When Informal Methods Stand In for Controls

A depot processing about 100 containers per day can generate 600+ inspection images daily. When those images live in WhatsApp threads, personal camera rolls, and shared folders — unlinked to a validated container number and without a distribution log — retrieval failure is not a rare edge case. It is the default under time pressure.

Gaps under informal methods

Photos shared without container-number linkage — retrievable only if someone remembers who sent them

No check-digit validation at capture — mis-typed numbers surface when a claim is already live

Manual, unlogged distribution — no reliable answer to “was this sent, to whom, when?”

Evidence scattered across personal devices and chat threads — no single authoritative source

Operational consequences

Records hard to locate weeks later for repair claims or lease disputes

Mis-linked photos become liability rather than evidence

Disputes over whether documentation was provided cannot be closed with facts

Data-protection governance is hard to demonstrate when inspection photos sit on unmanaged personal devices

Why volume matters: At hundreds of images per shift, even a small association-error rate produces enough wrong links to undermine active claims. Peer-reviewed manual data-entry research (Barchard & Pace, 2011, Behavior Research Methods) puts per-field error rates at roughly 1% for skilled operators and up to 4% for average operators — useful context for why validation at capture is a control, not optional polish.

Informal methods as if they were “the standard”

Photos accumulate across devices and chat threads, unlinked to validated container numbers. When a shipping line raises a damage question three weeks after gate-in, the depot may have images it cannot prove belong to that unit — and no log of whether relevant documentation was distributed.

Controls aligned to external requirements

Every photo is linked to a validated container number at capture, stored under shared access rules, and — where distribution rules are configured — dispatched with success or failure logged. When the question arrives, the inspection record and distribution history are retrieved by container number.

Best Practice: Implement Controls Without Confusing Them for Requirements

Six operator steps. External instruments stay authoritative for “what to check”; these steps cover “how evidence is produced and governed.”

Map external obligations

Criteria + contracts per event type

Define capture & linking

Guided sequences, container number

Validate identity

Check digit; retake or correct

Centralise & retain

Access rules + continuous audit

Configure distribution

Rules logged — not assumed

Integrate with DMS / M&R

No parallel photo pool

STEPS 01–02

Separate “what to check” from “how we capture”

Start from the applicable criteria and counterparty procedures, then decide guided photo sequences per inspection type. For structuring capture at depot scale, see how container depots should structure inspection photo workflows.

STEPS 03–04

Make identity and custody of the record controllable

Validate the container number before the record is trusted. Prefer a continuous audit trail of capture, access, edits (original retained when edited), and later changes — defensibility comes from the continuous trail, not from claiming the archive never changes. Retention and legal suitability remain customer policy — see maintaining a container inspection audit trail.

STEPS 05–06

Prove dispatch only where rules exist

Configure who receives which documentation after which events. Log success and failure. Feed evidence into the DMS and M&R systems already in use so compliance is not a second undocumented silo. Depot-vertical context: container depot photo management.

Where the Same Split Shows Up Across Depot Workflows

Event types differ; the pattern does not. Criteria and contracts set expectations. Controls make the photo record usable under those expectations.

Gate-in / gate-out and EIR

Counterparties care about condition at custody change. Controls: container-linked gate photos, searchable archive, distribution logged when rules are configured — see EIR and Autogate for automated gate capture where relevant.

M&R pre- and post-repair

Repair authorisation and billing depend on before/after evidence under the container number. Controls: paired photo sets in one history — not a parallel camera-roll archive.

Reefer PTI

Carriers and service facilities expect PTI documentation. Controls: step photos linked to the unit; integrations such as AEMS only under configured distribution — photo layer, not certification.

Wash before / after

Commissioning parties often want proof of wash condition. Controls: matched before/after sets under the same container number.

Lease return

Lessor criteria (often IICL-6) define damage thresholds. Controls: sequential condition photos at return with capture context retained — GPS when available is capture context, not independent proof of presence.

Multi-depot operations

Enterprise operators need one control pattern across sites. Controls: centralised archive, consistent capture rules, location-aware access — not site-by-site chat folders.

Informal Methods vs Structured Controls

Control need	Informal methods	Structured documentation controls
Container number validation	Accepted as typed; errors found at claim stage	Validated at capture — owner code, serial, check digit; retake or manual correction when wrong
Retrieval under dispute	Search folders, devices, and message threads	History by container number from a shared archive
Distribution evidence	No reliable send log	Configured rules; attempts logged with success or failure
Data-protection governance	Photos on personal devices; weak retention / access story	RBAC, configurable retention, encrypted transport; local copy ~7 days after upload on Checker mobile — not “nothing left on device”
Offline yards	Capture stalls or piles up unmanaged	Offline capture and OCR; sync when connectivity returns
System of record	Manual transfer into DMS / M&R	API / FTP / SFTP so evidence feeds tools already in use

How ConPDS Checker Supports the Controls Side

ConPDS does not invent IICL-6, UCIRC, CIC, or CSC. Checker is the photo-evidence and audit layer multi-site operators use to implement the controls above — alongside the DMS already in place.

Container-linked capture

On-device OCR with ISO 6346 check-digit verification; wrong recognition flagged for retake or manual entry. Photos link to the validated container number.

Capture integrity & originals

Mobile captures retain timestamp, device context, and geolocation when available. Photos cannot be tampered with in flight; once in the system, edits keep the original upload for restore.

Continuous audit trail

Capture, access, distribution, guest access, exports, and integration delivery — plus edits, tags, notes, and later field changes — logged against the user account.

Rule-based distribution

Email, FTP, SFTP, or API under tenant rules — immediate or delayed. Every attempt logged with success or failure. No dispatch unless a rule is configured.

Privacy-by-design hosting

EU-hosted with HTTPS; photos encrypted on-device until upload; role-based access and configurable retention to support GDPR-governed workflows. Customer remains responsible for purposes and policies.

Alongside the DMS

Integrations feed evidence into depot and M&R systems without replacing them. For product-side audit workflows, see audit and compliance documentation.

Frequently Asked Questions

Which practices are official requirements versus vendor controls? ▲

Official or industry-side requirements come from external instruments and counterparties: ISO 6346 for the container number; inspection criteria such as IICL-6, UCIRC, CIC, and CSC examination for what must be checked; and contract, carrier, lessor, or insurer procedures for photo sets, retention, and handover evidence. Vendor or platform controls are how capture, linking, storage, access, distribution logging, and audit history are implemented. Criteria define what to inspect; digital documentation controls determine whether the resulting photo evidence is retrievable and logged when challenged.

Do IICL-6, UCIRC, or CSC mandate a specific photo documentation platform? ▲

No. Those instruments define inspection scope, repair tolerances, or examination schemes. They do not prescribe a named software vendor, a universal photo set, or a single retention period. Exact evidence expectations still follow the applicable contract and counterparty process. Platforms supply capture, container-number linking, retention, and audit controls that make photo evidence usable under those regimes.

Does structured documentation replace our existing DMS? ▲

No. A documentation evidence layer sits alongside the Depot Management System. ConPDS Checker can integrate via REST API, FTP, or SFTP so photo evidence and distribution events feed existing depot records — without displacing how staff use the DMS.

Does the mobile capture app work offline in depot yards? ▲

Yes. ConPDS Checker operates offline for on-device OCR with ISO 6346 check-digit verification and photo capture. Records sync when connectivity returns. Photos are stored encrypted on the device until upload; a local copy is retained for about seven days after successful upload.

How should depots talk about data protection for inspection photos? ▲

Prefer privacy-by-design, EU-hosted storage where applicable, HTTPS in transit, on-device encryption until upload, role-based access, and configurable retention to support GDPR-governed workflows. Do not treat a vendor marketing claim as proof of GDPR compliance — the customer remains responsible for purposes and policies.

Can we prove documentation was delivered during a dispute? ▲

When distribution rules are configured, ConPDS Checker logs distribution attempts — including channel and success or failure — in a continuous audit trail alongside capture, access, guest access, exports, and integration delivery. That log answers whether a record was dispatched; it does not replace the contract rules that define what must be sent.

Can the same documentation controls apply across multiple depot locations? ▲

Yes. Multi-site operators typically need one container-linked archive with consistent capture and access rules, plus location-aware permissions where required. ConPDS Checker supports multi-depot deployments from a centralised dashboard so the same control pattern can apply across sites without separate undocumented photo pools.

Keep Requirements and Controls Distinct — Then Implement Both

External instruments and contracts stay authoritative for what must be checked and which evidence counterparties expect. Platform controls make that evidence linked, retrievable, and logged across every depot in the network. ConPDS Checker supplies the controls layer without replacing the DMS — or inventing the criteria.

When the split is ignored

✗ False certainty: Treating a vendor feature list as if it were IICL-6 or CSC.

✗ Unretrievable photos: Informal methods that cannot answer container-level questions under time pressure.

✗ Unprovable distribution: No configured rules and no send log when a counterparty says “we never received it.”

✗ Governance gaps: Inspection photos on unmanaged personal devices with no retention or access story.

Next: criteria reference · audit trail how-to · Checker audit controls