Fleet management for vehicles that carry something that matters.
Most fleet software stops at a dot on a map. That is fine until the cargo is a patient, a vaccine consignment or a blood sample, and the question is not only where the vehicle went but whether the compartment held temperature, whether the van was decontaminated afterwards, and whether the driver's PSV badge is still valid.
Priced per fleet · works with GPS hardware you already have · demo on request
Tracking is the easy half. These are the things that decide whether a consignment is accepted and whether a vehicle is roadworthy on the day it is stopped.
Per-compartment temperature and humidity against thresholds you configure, with door-open detection and an alert the moment a reading leaves range — not a discovery at the far end.
Request, dispatch, arrived at pickup, departed, arrived at destination, complete. Every leg timestamped, with trip type, priority and a patient reference where the run is a transfer.
Position, speed, heading and ignition state per vehicle, with named zones that raise an event the moment a vehicle enters or leaves one.
Post-trip decontamination recorded against the trip as a checklist that passed or failed. The trail infection control asks for, kept as a matter of course.
Insurance, inspection and road licence per vehicle; driving licence, PSV badge, defensive driving and medical certificates per driver. The point is the warning, not the record.
Fuel-card reconciliation with price per litre and vendor, and service schedules that fall due on mileage or elapsed days, whichever lands first.
Each of these is a register you can report on, not a field on a form.
Make, model, plate, fleet number, acquisition cost, current mileage, home base, and the three compliance expiries.
Licence and class, PSV badge, defensive driving and medical certificates, each with its own expiry.
Type, priority, requesting department, purpose, pickup and destination, odometer in and out, fuel used, and the full dispatch timeline.
Latitude, longitude, speed, heading, accuracy and ignition state, from the GPS source you already use.
Named zones with a radius and an optional vehicle-type filter, and an event log of every entry and exit.
Readings per compartment with temperature, humidity and door state, against configurable minimum and maximum thresholds.
Speed against the posted limit, severity, and a score penalty that rolls up into a driver scorecard.
Type, severity, location, description, resolution and the cost of each event.
Scheduled and performed work, vendor, cost, and the next due date or mileage.
Where a trip is a patient transfer and the dispatch timeline is part of the clinical record.
Where the consignment is rejected if the cold chain broke, and you need to prove it did not.
Counties, missions and organisations running vehicles across departments with real accountability for cost per kilometre.
Where fuel, maintenance and driver behaviour are the margin, and a geofence tells you a delivery actually arrived.
Nobody should move a whole fleet onto a new system on a promise. A pilot puts a handful of your own vehicles through it for a month, on your routes, with your drivers.
Ideally your awkward ones — the ambulance whose timeline nobody can reconstruct, the van that keeps failing inspection, the cold-chain route that broke last month.
Vehicles, drivers and their expiry dates loaded, your GPS feed connected, geofences drawn around the places that matter. We do this with you rather than emailing instructions.
Your own trips, your own drivers, your own cold-chain readings. At the end you have a month of real data and a straight answer about whether it earns its place.
Not a self-serve one. ProtechFleet is set up against your actual vehicles, drivers and GPS feed, so there is nothing useful to hand you behind a signup button. What we do instead is a pilot: five of your vehicles, running for a month on your own routes, set up with you. At the end you have real data rather than a demo impression.
No. The system records position, speed, heading and ignition state from a GPS source, and is built to take that feed rather than to sell you boxes. Tell us what you already have fitted and we will tell you honestly whether it can feed the system.
Readings are logged per compartment with temperature, humidity and door state, and checked against minimum and maximum thresholds you configure per compartment type. When a reading leaves range the system raises an alert rather than recording it quietly for someone to find later.
Yes — that is one of the cases it was built around. A trip carries a type, a priority and a patient reference, and is stamped at dispatch, arrival at pickup, departure, arrival at destination and completion, so the timeline is a record rather than a recollection.
Every expiry is held against the vehicle or the driver and surfaces before the date, which is the entire point. A register that only tells you something lapsed after it lapsed has not helped anyone.
Yes. The fleet module also exists inside MedSuite for facilities that run their own ambulances, so the transport record and the patient record are not in two unrelated systems. It also runs standalone for fleets with no hospital attached.
Per fleet, by size and by which parts you need — cold chain and dispatch are not relevant to every operator. Ask for a demo and we will quote against your actual fleet.
The vaccine route that keeps breaking, the ambulance whose timeline nobody can reconstruct, the van that failed inspection. Those make the useful demo.