Skip to content

Specialty mobility

The demand you turned away is not in any report.

Rental and specialty fleets need utilisation beside refused demand, fast handover evidence and service dates on the availability board. The data model is car-shaped, so bike and heavy-vehicle gaps are stated up front.

R-SOL-07 is explicitly a fit assessment. Refusal logging is treated as a capability to verify before publication; non-car valuation, damage-map and compliance gaps remain visible.

Best fit
Rental operators and mixed specialty fleets that are mostly cars and light vans, with vehicle-type gaps assessed before a pilot.
Operational job
Track availability beside refused demand, document every handover and return, and keep service and compliance dates on the same unit record.
What you get
A fleet view linking availability, refused demand and service, with vehicle-type gaps stated.

Fit by vehicle type

Where the car-shaped data model holds, and where it does not

Every DMS claiming to handle any vehicle is describing a table with a make and a model in it. The differences are in what the vehicle legally is and how it is priced.

Cars & small vans

What works today

Everything: stock, rental, service, damage, accounting

What is missing

Nothing material

Full fit

Converted LCVs

What works today

Base vehicle, rental, service, damage evidence

What is missing

The conversion itself: body, tail-lift, refrigeration, is not modelled as equipment with its own service life

Partial

Motorcycles

What works today

Stock, sale, workshop jobs, parts

What is missing

Bike-specific identification and valuation data, and a damage map that is not a car silhouette

Partial

Trucks over 3.5 t

What works today

Stock, workshop, parts, accounting

What is missing

Axle configuration, tachograph, driver hours and periodic inspection regimes are a different compliance world

Confirm

Trailers & plant

What works today

Held as units with service and rental history

What is missing

No valuation data, no provenance, and hour-meters are not mileage

Confirm

This table is the most useful thing on the page and the least finished: depth per vehicle type needs product confirmation before any of it is published. A rental operator with eleven refused van bookings can act on it today; a haulier cannot.

System relationship

A connected workflow for specialty mobility

One unit, fifty times a year

A rental week, from the enquiry you refuse to the damage you cannot prove

A dealer hands a car over twice in its life. You do it every few days, which changes which parts have to be fast.

Refused demand is the only number that tells you what to buy

Utilisation tells you how hard the fleet you own is working. It cannot tell you that the fleet is wrong. Eleven van enquiries turned away in a week says buy vans and sell small cars.

Nobody logs a refusal unless it takes one tap, so this is a design problem more than a data problem.

Counter does
One tap: class asked for, dates, why not filled
Omnetic
Keeps refusals next to utilisation, so mix decisions have both halves
You learn
Panel vans at 94% with eleven refusals, small cars at 62% with none

Three people in a hire business

The counter, the yard, and whoever decides what to buy next

Notice there is no salesperson here. That absence is why a dealer page cannot be reused for this audience: the unit is never sold, it is rented until it is worth selling once.

1

Counter staff

Hands a unit over in four minutes with evidence, and logs a refusal in one tap because it is faster than apologising.

2

Fleet controller

Books compliance and service into gaps on the availability board rather than into a booking that already exists.

3

Owner

Buys against refused demand and revenue per unit instead of against last summer's feeling about vans.

What an operator asks first

Evidence

The honest version of this page is mostly a fit assessment

Rental availability, refusals, damage evidence, workshop, accounting

Existing modules doing what they already do. For a car-and-van hire fleet this page needs no new product.

Depth per vehicle type

Motorcycles, trucks, LCV conversions, trailers and plant. The fit table is our best guess and must not be published as fact.

Rental aggregator connectors

Part of the same named-partner list blocking Fastback and the classifieds claims.

Refused-demand capture

The hero rests on it. If one-tap refusal logging is not in Rental today, this page's headline is a roadmap item and must be labelled as one.

Where to start

Step 1

Fit

Tell us the mix. If it is mostly cars and vans, start now; if it is trucks or bikes, we will say what is missing.

Step 2

Availability

Rental on one branch, with refusals logged from day one. Two weeks of no's is usually the surprise.

Step 3

Evidence

Walk-rounds at both ends until it is habit. Damage recovery pays for the rollout before anything else does.

Step 4

Cost per unit

Workshop and Accounting, so revenue and cost land on the unit and the retirement decision has numbers.

Tell us the fleet mix and we will tell you the gaps

For mostly cars and vans, scope a branch. For trucks or bikes, validate what is missing first, including gaps that mean you should wait.

Tell us what you operate
  1. Record the no

    Refused class, dates and reason must take one tap or fleet-mix demand disappears.

  2. Inspect at operational speed

    Handover and return evidence must be fast enough to repeat every few days.

  3. Service on availability

    Maintenance and compliance dates block availability instead of colliding with a booking.