Container Wash Evidence Layer
Before-and-after wash photos on one container record — ready when the invoice or cleaning certificate is challenged.
Where Wash Documentation Quietly Costs Real Money
Wash documentation is the proof of cleaning quality, the defence against condition disputes, and the record of pre-existing damage on the container at arrival. When that evidence lives on personal devices, in WhatsApp threads, and in shared folders, the cost shows up as disputed invoices, cleaning certificates that get pushed back on, and pre-existing damage the wash station ends up paying for. A disputed wash charge without defensible evidence becomes a direct operational cost.
In many wash stations, documentation is still
The result in active wash operations
A Container-Linked Wash Evidence Workflow — Capture to Audit
ConPDS Checker turns each wash into a container-linked evidence record built for wash station conditions — captured (photo, video, audio) before, during, and after the wash; validated against the ISO 6346 container number; archived in a searchable record; and integrated with the depot management system already in place.
Capture Before and After Wash Photos in the Yard
Wash station staff use the ConPDS Checker mobile app on their existing smartphones or tablets to capture container condition before and after washing — exterior, interior, and any pre-existing damage — in a single structured workflow. No additional hardware required.
For wash operations where a static photo is not sufficient evidence, ConPDS Checker also supports short video clips (up to 30 seconds) and audio notes. In practice this is most useful for: documenting water spray coverage across the full exterior in a single continuous clip; showing post-wash interior drainage where residue or contamination is in dispute; and recording pre-wash arrival condition — odour, cargo remains, or visible contamination — before cleaning begins. For ISO tank and chemical container cleaning, video of valve condition and post-rinse state provides stronger cleaning certificate support than a still photo alone. All video and audio is linked to the same container-specific wash record and logged in the audit trail.
Automatic Container Number Recognition and Validation
The system reads and validates the container number on-device using AI-powered OCR with ISO 6346 check-digit verification (owner code, serial number, and check digit) — including offline. Wrong recognition is flagged, and staff can retake the photo or type the container number in manually, so every wash-stage photo is linked to the correct container record before it reaches the archive. Photos are stored under the validated container reference at capture, reducing manual renaming and documentation errors from the first photo.
Searchable Wash Evidence Archive — Retrievable in Seconds
All pre- and post-wash photos, pre-existing damage records, and container condition notes are stored in a searchable cloud archive organised by container number. The complete wash history builds automatically per container — retrievable in seconds by any office staff member searching the container number in the web dashboard, even months later during customer disputes or quality reviews. Wash records can also support cleaning certificates issued to customers and leasing companies — providing the photo evidence that transforms a certificate from a statement into verifiable proof. This is what container cleaning documentation software is designed to make effortless.
Integration with Depot and Operational Systems
Records connect to existing depot management and M&R systems via API — wash evidence becomes part of the operational record, not a parallel archive. ConPDS Checker does not replace your existing system; it adds the operational evidence layer your current stack is missing.
What an Evidence Layer Provides That Informal Photos Cannot
A photo on a phone may show condition, but without a reliable container link, capture context, and retrieval process, it can be difficult to use when a question arises. A container-indexed before-and-after record retains that context alongside the distribution log.
Defensible Proof for Customers, Shipping Lines, and Lessors
When wash evidence is container-linked and instantly retrievable, the wash station responds to customer enquiries from a position of evidence — not from a phone gallery searched under time pressure. The evidence workflow replaces informal photo sharing with ISO 6346-validated container records that hold up under invoice review and cleaning-certificate validation. For gate-in, repair, and lease return documentation, see how the container depot inspection evidence layer applies the same approach to depot operations.
Built for Fast Capture in Active Wash Environments
Container wash bays are busy, practical environments. ConPDS runs on the smartphones wash station staff already carry — built for fast capture, minimal manual input, and reliable operation regardless of Wi-Fi coverage in the wash bay or yard. Every capture is container-linked the moment it is taken.
Operating Across Active Container Wash and Depot Operations
The workflow runs in container wash stations, depots, and service facilities across Europe, Africa, Australia and the Middle East. Field-tested in operational depot and wash environments since 2013 and refined continuously against the operational reality of wash work.
Security, Retention, and Audit Posture
Technical Specifications
Frequently Asked Questions About the Wash Evidence Layer
Make Wash Evidence Defensible by Default
If your wash station produces before-and-after records every day, the question is not whether you have evidence — it is whether you can produce it on demand for the disputed invoice, the cleaning-certificate challenge, and the pre-existing-damage claim. ConPDS takes that off individual diligence and onto a measurable process.
With informal methods, a before-record taken on a personal device can be difficult to produce when a wash dispute is raised weeks later. With ConPDS, the before-and-after record is searchable by container number, with its capture timestamp and any available device-recorded location retained as context.