What Fleetlane is

Fleetlane is a warranty management system for vehicle manufacturers and their dealer networks. Head office configures how warranty works — claim types, coverage, budgets, who may see and change what — and dealers submit claims within those rules. Head office then adjudicates, and every step is recorded.

The difference is where the process lives. In Fleetlane your warranty process is configuration, not code. Claim types, statuses, field rules, reference data and lifecycle policies are set up per customer and changed through settings, so Fleetlane follows the way your organisation already works rather than asking you to adopt someone else’s.

Who uses it

	What they do in Fleetlane
Head office	Configure claim types, coverage, reference data and access; adjudicate claims; plan and distribute vehicle allocation; manage the dealer network; run recalls.
Dealers	Look up vehicles and their coverage, submit and follow up claims, and discuss them with head office — limited to their own dealership and to what their roles allow.
Your systems	Receive events as claims and vehicles change, supply parts and pricing, and take part in claim lifecycles through actions.

flowchart LR
  HO["Head office"] -->|configures, adjudicates| Fleetlane["Fleetlane"]
  D["Dealers"] -->|vehicles, claims, services| Fleetlane
  AI["AI assistants"] -->|as the signed-in user| Fleetlane
  Fleetlane <-->|policies, actions, results| LE["Lifecycle engine"]
  Fleetlane -->|events| SYS["Your systems"]
  SYS -->|parts and prices| Fleetlane
  LE -->|calls and OData| SYS

What it covers

• Claims & claim types — every claim type is configuration with its own creation mode, field and item policies, pricing, attachments and discussion, with a version recorded at every status change.
• Services — service definitions and service claims.
• Vehicles, warranties & recalls — the vehicle record and ownership history, warranty coverage by model, the vehicle configurator and recall campaigns.
• Budgets & dealer network — the annual vehicle allocation plan, its distribution across dealerships and dealer refinement, plus dealerships, users and invitations.
• Your data — custom fields and reference data such as defect codes, cause codes, coverage types and statuses.
• Access & field control — roles, head office and dealer scope, and field-level rules by role, status and claim type.
• Branding & white-labelling — your logo, brand colours, style and web address.

How it adapts to you

Configurable. Claim types, statuses, coverage and field rules are settings. Two manufacturers can run very different processes on the same product.

Extensible. Your own data model fits through custom fields and reference data. Your own logic and systems take part through the lifecycle engine: every claim and vehicle lifecycle follows a versioned policy that runs actions — rule checks, calls to external systems, custom logic — and moves the record to its next status based on the outcome. See How lifecycles work.

Connectable. Fleetlane sends events as claims and vehicles change, connects to external systems and OData services, and can be used from AI assistants under the signed-in user’s own permissions. See Integrations.

Yours. Fleetlane is white-labelled: your logo, brand colours and look, on a web address of its own, set in Settings rather than built. See Branding & white-labelling.

Safe to adopt. The configured tenant boundary separates each organisation’s data. Access is invite-only through single sign-on, configuration changes are tried in a test lane and promoted after a preview (Lanes), changes are versioned, and lifecycle execution records are append-only. Export, retention and deletion arrangements are confirmed with your operator. See Security & data handling.

Evaluate with your own configuration

Start with getting started, then inspect a vehicle and prepare a claim. Use a test lane with the intended claim types, reference data and dealer permissions. Check that coverage, field rules and lifecycle outcomes fit your process before connecting real systems. The screenshots describe existing local records; they do not certify completed submission, adjudication or delivery flows.