Skip to main content
REPAIR CLAIM DEFENCE · DISPUTED-CHARGE EVIDENCE

Container Repair Claim Defence & Disputed-Charge Evidence Software

Used by depots, M&R workshops, leasing companies, and shipping-line operations across Europe, Africa, Australia and the Middle East — including operators on lanes where repair charges and off-hire claims are routinely audited or contested.
ConPDS Checker is the evidence layer underneath repair operations. It captures the matched pre-repair, work-in-progress, and post-repair record that turns a contested repair charge or an off-hire claim from opinion into evidence — every photo linked to the ISO 6346-validated container number, the active work order, and the responsible counterparty at the moment of capture.

Stop writing off contested repair line items because the matching evidence is on a phone that has since changed hands. Replace WhatsApp threads, shared folders, and after-the-fact photo hunts with a structured repair record that survives an off-hire dispute, a lessor audit, or a shipping-line claim review months — or years — after the repair was completed.

No obligations — reply within 1 business day · Checker adapts to your M&R operation — work-order system, integration stack, and counterparty mix all shape the workflow, not the other way around.
Field-tested in container M&R operations since 2013
ISO 6346 container number validation at capture
AEMS, DepotMaster, EOS, IMARS, OVMR, FIS integrations

What every written-off repair charge has in common

A repair charge is only as defensible as the matched evidence set behind it. When pre-repair condition lives in a phone gallery, the work order lives in the maintenance system, and the post-repair photos live in a WhatsApp thread, the record cannot be reassembled quickly enough to defend the charge — and a leasing company, shipping line, or insurer disputes the line item by default. The cost lands not on the workshop, but on the operator's repair revenue line and on the leadership team that has to explain the write-off.

In many M&R operations, repair photos are still

Captured on the workshop technician's personal phone — not container-linked
Filed in shared folders by date, not by container number or work order
Sent via WhatsApp, which strips GPS and timestamp metadata in transit
Missing the pre-repair baseline — only finished work was photographed
Disconnected from the repair system — invoiced without an evidence pointer

The result when a charge is contested

help_outline
No baseline — counterparty argues the damage pre-existed custody
receipt_long
No work-order link — counterparty questions whether the repair occurred
construction
No parts evidence — lessor or insurer queries the parts billed
timer_off
Photo retrieval takes hours or days — past the dispute response window
Repair charges are settled on the strength of the evidence trail, not on the strength of the invoice line item. A structured repair record removes the ambiguity at source. For the broader case, see container damage documentation best practices →

A Structured Repair Documentation Workflow — From Pre-Repair to Defensible Record

ConPDS Checker replaces ad-hoc repair photos with a structured workflow built specifically for the repair lifecycle — from pre-repair baseline through work-in-progress to post-repair condition, all linked to the work order at the point of capture.

01
Pre-Repair
02
Link
03
In Progress & Post
04
Distribute
Step 01 — Pre-Repair

Capture the Damage Baseline Before Any Work Begins

Workshop staff photograph the damage area, the surrounding panel context, and any related pre-existing condition before lifting a tool. The pre-repair baseline is the evidence the work order is built on — without it, every subsequent photo loses defensive value when the charge is contested.

Step 02 — Link

Automatic Container Number Validation and Work-Order Linkage

The app reads and validates the container number using AI-powered OCR with ISO 6346 standards (owner code, serial number, check digit), and ties every captured photo to the active work order — container-indexed and work-order-indexed from the first frame, with no manual renaming or filing step.

Step 03 — In Progress & Post

Document Work-in-Progress and Final Condition

Photos are added to the same container record as the repair progresses — parts removed, parts replaced, weld seams, primer, paint, finished surface. The complete chronological repair sequence lives under one container reference, retrievable as a single defensible package.

Step 04 — Distribute

Push to Repair Systems and Counterparties Automatically

Repair packages route automatically to the operational repair system and to the responsible counterparty (lessor, shipping line, insurer) — by rule, on demand, or via secure guest portal. Every distribution event is logged in the audit trail, preserving the chain of custody from field capture to claim settlement.

Maersk AEMS DepotMaster EOS CMA-CGM IMARS MSC OVMR Hapag FIS Custom API · REST · FTP · SFTP

What Defensible Repair Documentation Actually Requires

A photo of finished work proves nothing without the pre-repair baseline, the container link, the work-order pointer, the timestamp, and the distribution log. ConPDS Checker bakes all six into the record at capture — not after the fact.

photo_camera
Pre / In / Post Pairing
Pre-repair baseline, work-in-progress, and finished-condition photos stored chronologically under the same container record — one complete, retrievable repair sequence.
label
ISO-Validated Container Link
Every photo linked to an OCR-validated container number at capture — not filed by date, not renamed manually, not reliant on technician memory.
receipt_long
Work-Order Linkage
Repair photos tied directly to the active work order — invoice line items reference the photographic evidence that supports them.
schedule
Timestamp & GPS Preserved
Capture time and location are preserved end-to-end — the metadata that establishes when and where the repair was performed.
send
Counterparty Distribution Log
Every package sent to a lessor, shipping line, or insurer is logged — who received what, when. Chain of custody preserved from capture to claim review.
archive
Configurable Retention
Retain repair records for the full claim window of every counterparty — set per tenant, enforced automatically, GDPR compliant on EU-hosted infrastructure.

Informal repair photos vs the structured evidence layer

When a repair charge is contested, the operator with the matched evidence layer settles fast and is paid in full. The operator without one writes the line item off, every time. The difference is built into the workflow at the moment of capture — not negotiated months later, when the matching evidence is already gone.

✗ Informal Repair Photo Handling
Photos in WhatsApp threads — not container or work-order linked
No pre-repair baseline — counterparty disputes pre-existing damage
WhatsApp/email compression strips GPS and timestamp metadata
No distribution log — no record of what was sent to which counterparty
Photo retrieval depends on the technician who took the picture
✓ Structured Repair Documentation with ConPDS
Pre / in-progress / post photos linked to validated container and work order
Pre-repair baseline captured before the first tool touches the damage
GPS and timestamp preserved from field capture to archive
Full distribution audit trail — every package, every recipient, every timestamp
Container-number search retrieves the full repair history in seconds

Frequently Asked Questions — Repair Claim Documentation Software

What is container repair claim documentation software?
Repair claim documentation software captures structured photo and metadata evidence of every repair stage — pre-repair condition, work performed, parts replaced, post-repair state — and links it to the ISO 6346-validated container number, the repair work order, and the responsible counterparty (depot, lessor, shipping line, leasing company). It produces a defensible record that survives a contested charge, a lessor audit, or a leasing-company off-hire dispute months after the repair was completed.
How does structured repair documentation help defend a repair charge raised against a counterparty?
A repair charge becomes defensible only when the depot or workshop can produce the matched evidence set — pre-repair damage photos, the work order, parts records, and post-repair condition — all linked to the validated container number with timestamp and GPS preserved. ConPDS Checker builds that paired evidence set automatically at the point of capture, so the full repair record is retrievable in seconds when the dispute arrives.
How does it help dispute a repair charge raised by a lessor or shipping line?
When a lessor or shipping line raises a repair charge after off-hire or return, the operator's only defence is independent photographic evidence of the container's condition at the moment of handover. ConPDS Checker captures that evidence at every transfer point — gate-in, lease return, off-hire — linked to the validated container number with timestamp and GPS metadata intact. The matched pre-handover and post-handover record is what turns a contested charge from opinion into evidence.
Does it integrate with AEMS, DepotMaster, EOS, and other repair systems?
Yes. Repair photo records are pushed automatically to the operational repair system — Maersk AEMS for shipping-line repair workflows, DepotMaster and EOS for depot M&R, and CMA-CGM IMARS, MSC OVMR, Hapag FIS, and others via Custom API. ConPDS Checker does not replace your maintenance system; it adds the structured photo evidence layer attached to every work order.
Can repair documentation be retrieved months later for an audit or dispute?
Yes. All repair documentation is stored in a searchable cloud archive organised by container number, work order reference, and date — retrievable in seconds from the web dashboard regardless of which field worker took the photo or which device was used. Retention periods are configurable per tenant to align with claim windows, leasing contracts, and regulatory requirements.
How does it support distribution to lessors, shipping lines, and insurers?
Structured repair documentation can be distributed automatically by rule (every reefer repair to AEMS, every leased-container repair to the lessor's M&R address) or shared on demand via a secure guest portal scoped to specific containers or work orders. Every distribution event is logged in the audit trail. Lessors, shipping lines, and insurers receive the same independent evidence set, not a forwarded chat thread.
Does the platform comply with GDPR and shipping line data-handling requirements?
Yes. All data is GDPR compliant and stored on EU-hosted infrastructure. Each operator runs in its own secure tenant with role-based access control, configurable retention, and full audit logging of every capture, view, and distribution event. Shipping-line specific data-handling requirements are detailed on the Checker integrations page.
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

Stop writing off repair charges you should be defending

See how ConPDS Checker puts the evidence layer underneath your repair operation — pre-repair baseline before any tool touches the damage, work-in-progress and finished-condition photos linked to the work order, every counterparty distribution logged. The contested-charge conversation moves from opinion to evidence; the repair revenue line stops leaking.