CATEGORY DEFINITION
Container Repair Evidence System
A container repair evidence system turns repair work into a defensible record: pre-repair baseline, work-in-progress documentation, post-repair completion, spare part serial numbers, work-order context, and counterparty distribution. ConPDS links every repair record to the validated container number and keeps the evidence retrievable when a charge, off-hire claim, or warranty decision is challenged.
Built for M&R teams, repair workshops, reefer facilities, depot operators, leasing-company stakeholders, and shipping-line repair workflows.
No obligations — reply within 1 business day
What Makes Repair Evidence Defensible?
Repair evidence is defensible when it proves the condition before repair, documents the work while it happens, shows the completed state, links the record to the correct container and work order, and preserves the chain of custody from field capture to counterparty review. Photos alone are not enough if they cannot be matched, retrieved, or trusted when challenged.
ConPDS Checker captures repair evidence on standard smartphones, validates the ISO 6346 container number at capture, attaches records to the repair workflow, and distributes structured packages to shipping-line, DMS, M&R, guest portal, email, FTP/SFTP, or API destinations with every distribution event logged.
Pre-repair baseline before tools touch the damage
Work-in-progress evidence tied to the repair line and work order
Post-repair completion state captured before release or gate-out
Spare part serial number capture for reefer, mechanical, and warranty-sensitive repair
Audit trail for capture, review, distribution, retrieval, and counterparty access
Why Repair Charges Get Written Off
Most written-off repair charges are not caused by the repair being wrong. They are caused by the evidence being incomplete, late, misfiled, disconnected from the work order, or impossible to produce quickly enough when the counterparty disputes the line item.
Common Failure Pattern
Pre-repair damage exists in a phone gallery or chat thread
The work order exists in the M&R or depot system without a reliable evidence pointer
Post-repair completion photos are separate from the baseline
The package cannot be reconstructed before the dispute deadline
Evidence-System Response
One container-linked repair record from baseline to completion
Evidence captured during the repair, not assembled afterward
Counterparty distribution logged by user, channel, recipient, and timestamp
Retrieval by container number, work order, depot, date, customer, or repair type
REPAIR EVIDENCE SPINE
One Repair Record From Baseline to Defence
The repair file is strongest when every phase stays tied to the same validated container number and work order, instead of being rebuilt from separate photos, folders, or messages.
tag
Container number + work order
Shared anchor across every repair phase
01
Baseline
Condition before tools touch the damage.
02
Work Order
Repair line, estimate, and operational context.
03
In Progress
Evidence while the repair is being performed.
04
Completion
Post-repair proof before release or gate-out.
05
Package
Counterparty-ready record for claim defence.
The Repair Evidence Lifecycle
01
Baseline
Damage before repair
02
Work Order
Repair context attached
03
In Progress
Repair evidence captured
04
Completion
Post-repair state recorded
05
Defence
Record produced on demand
What the System Must Capture
CONDITION BASELINE
Before the Repair Starts
The pre-repair state proves what was present before the workshop touched the container. Without it, the disputed charge becomes an argument about memory rather than evidence.
REPAIR PROGRESSION
During the Work
Work-in-progress photos prove that the repair line was necessary, performed, and tied to the work order. This is especially important for hidden damage, structural work, and reefer components.
COMPLETION RECORD
Before Release
The finished-condition record closes the repair file and provides evidence for invoicing, shipping-line review, lessor review, warranty decisions, and future condition disputes.
DISTRIBUTION HISTORY
Who Received the Evidence
Every send, export, guest portal view, and system integration event is logged so the operation can prove which counterparty received which record and when.
Built for the Financial Side of Repair Work
Repair evidence sits at the point where operations, finance, claims, and counterparty relationships meet. The system must support the workshop, but it also has to protect the repair revenue line when charges are challenged later.
Repair claim defence
Off-hire disputes
Warranty evidence
Reefer component records
AEMS distribution
DMS integration
Guest portal access
Container Repair Evidence System FAQ
What is a container repair evidence system? ▲
It is the structured system that captures, matches, retains, distributes, and retrieves the evidence behind repair charges. The core record includes pre-repair, in-progress, and post-repair evidence tied to the validated container number and work order.
Does ConPDS replace our M&R system? ▲
No. ConPDS adds the evidence layer underneath the repair workflow and distributes packages into the systems or counterparties that need them, including AEMS, DMS platforms, email, FTP/SFTP, custom APIs, and guest portal access.
Is this only for reefer repair? ▲
No. Reefer repair benefits strongly because technical evidence and spare part serial numbers matter, but the same system applies to dry container repair, structural repair, wash-related damage, lease return repair disputes, and off-hire claim defence.
Turn repair documentation into recoverable evidence.
If contested repair charges, off-hire claims, or AEMS submissions are consuming time and revenue, we can map the evidence workflow that closes the gap.
