Condition checks the customer can't dispute
Pre-handover and post-return inspections without booking a yard slot. The customer walks the car on video; you stamp the evidence at session-end with a qualified-TSP timestamp. When a dent shows up six months later, you have the receipts.
Two scenarios, same flow
Lease delivery / dealership pick-up
Driver picks up the car, you walk them through a 5-minute condition check on their phone. Existing scratches are captured + timestamped + anchored to the audit chain. If they report damage on return that's already in the pre-handover pack, the conversation is short.
End-of-lease / vehicle return
Customer returns the car remotely (driveway, not your yard). Walk-around video, panel-by-panel snapshots, comparison with the pre-handover pack from the same session-id family. Damage charges land with cryptographic evidence backing them.
Why a chain matters here
Damage-charge disputes are the single most common driver of customer-experience complaints in vehicle leasing. The complaint is rarely "I damaged it but I shouldn't pay" — it's "you can't prove I damaged it." A timestamped, GPS-stamped video walkthrough at delivery turns that argument into "let's check the chain head" — over in minutes.
| What you capture | Why it cuts disputes |
|---|---|
| Walk-around video | Continuous footage, not 12 cherry-picked stills. Hard to argue the rest of the panel was hidden. |
| Per-panel snapshots | Operator marks specific scratches; whiteboard annotation circles them with the customer watching. |
| GPS + timestamp | Proves the inspection happened at the delivery location at the delivery moment, not "in the yard after a known-good vehicle came back." |
| Customer-signed PDF | PAdES B-T signed report at session-end. Customer's SES click is in the audit chain too. |
Operator workflow at scale
Fleet operators run hundreds of these per day, so the integration surface matters. Mint sessions via the public API from your fleet-management system; subscribe to session.completed webhooks to pull the signed PDF + evidence pack into the customer record automatically. The audit chain is queryable per-session if compliance asks.
What a typical deployment looks like
Leasing companies running 5,000–50,000 vehicles, mid-sized dealership networks, and fleet operators are the natural fit. Before NexBasira the condition-check workflow looks the same on most yards: bring the car in, hand-on-hand walkthrough by yard staff (30–45 minutes per vehicle), paper checklist plus photos on a shared OneDrive that disputes erode within months. When the customer challenges the damage charge six months later, the photos are date-stamped by phone clock and the report is signed by "Yard Operator 4."
After: at delivery and at return, the driver opens a one-shot link on their phone for a 5–10 minute walkaround on video. The operator on the other side circles existing scratches on a shared whiteboard while the driver watches them land — no "I never agreed to that" later. The chain anchors at the qualified TSA, the signed PDF flows into your DMS via the public API. Yard staff time gets reclaimed for the cases that genuinely need a physical inspection (damage above a threshold, mechanical complaints).
Ranges to expect
Pulled from the cost model + pilot conversations. Yours will depend on contract mix and dispute-rate baseline — we'll model your specific volume during the walkthrough.
| Lever | Typical range |
|---|---|
| Inspection cycle time | 30–45 min in-yard → 5–10 min remote |
| Damage-dispute escalation rate | 8–15% (typical leasing baseline) → 1–3% post-chain-of-custody rollout |
| Vehicles processed per FTE per day | 15–25 (yard-bound) → 40–60 (remote-first), depending on session length |
| Annual damage-charge recovery | Improves materially — but the lift is contract-mix-dependent and best modelled against your existing dispute log |
Want a yard-side comparison?
We'll run the same condition check side-by-side: your existing yard process and a 6-minute remote session. Both produce a hand-over pack; only one of them survives a court challenge.