Transparency

How the editorial score works

Some product pages carry a score out of 5. This page explains exactly where that number comes from, what it leaves out, and who signs it off.

The short version: most of the score is about what the product does for a fleet. Features, fit for the job and ease of rollout are judgements, and each one quotes the sentence in the review it rests on. Support is read from what the vendor publishes about its own support and onboarding. Price, contract and hardware together count for at most a fifth of the score, and only the ones the vendor publishes are scored. Nothing is shown until the editor approves it. 37 of 38 products show an approved score. 0 more have a draft awaiting the editor, and 1 lack the evidence for one.

What the score is built from

Features is what the product actually ships for the category's main job: how deep each core module goes and how much sits around it, including integrations and an API where the review covers them. A tracker with live maps, geofences and reports but no cameras, compliance or integrations scores lower than a platform that ships all of them. It is judged against five written descriptors and, like every judgement here, stores the review sentence it rests on.

Fit for the core job is a separate question: who the product suits and how well it does the main job for that buyer. A long feature list is no help to the wrong fleet, and a short one can be exactly right for an owner-operator.

Support and onboarding is read from the vendor's own website, help centre and terms, never from review sites: whether there is a support phone line, live chat and email, whether live support is 24/7, whether onboarding or training is included, whether there is a named account manager, a public help centre and published response times. Each fact is stored with the page it came from and the date it was checked. Anything the vendor does not publish earns nothing. A product whose vendor publishes no way to reach support at all gets no score (1 of the 38 products), because a score needs features, fit and support, and support has to come from what the vendor publishes.

Published price. Only a figure the vendor prints on its own pricing page counts. To compare products billed per vehicle, per driver, per asset, per shop or per month on one basis, each is costed for the same reference fleet: 25 vehicles, 25 drivers, one office user, one shop, up to 1,000 deliveries a month. The cheapest base plan for that fleet is ranked against other priced products in the same category. Where the vendor publishes no price, this part is not published by vendor, not scored, and the score is weighted over the parts that are. That is 25 of the 38 products covered here.

Contract and exit. Read from the vendor's own terms: the minimum term, automatic renewal, the notice needed to leave, whether the device is leased, and any early-termination fee. No minimum term scores 5; a default of more than three years scores 1.5 before adjustments. A term the vendor does not publish is not assumed to be short: if the terms still publish an exit clause, such as automatic renewal or a notice period, the clauses are scored from a middle starting point. If the vendor publishes no term and no exit clause, this part is not published by vendor, not scored (10 of the 38 products).

Hardware cost. Whether the device is included, loaned, bought at a stated price or leased under a separate agreement. Software with no device to buy, such as maintenance and routing tools, is not scored on this, and neither is a device whose cost the vendor does not publish.

Ease of rollout, like features and fit, is an editorial judgement. Each judgement picks one of five written descriptors (for example, “productive within days; a plug-in device or a data import”) and stores, word for word, the sentence from the product's own review that supports it. If the review holds no such sentence, the product gets no score rather than a guess. These are judgements from reading vendor documentation, contracts and buyer evidence. The site does not install, trial or test the products, and the score does not say it did.

How the parts are weighted

Features carry the most weight, then fit, then support and ease of rollout. Price, contract and hardware together are held to 20% in every group, with price itself at 8 to 10%. Most vendors here publish no price at all, so a heavy price weight would mostly measure silence. The contract stays in because the vendor terms on this site include four-year defaults and leases that cannot be cancelled. Compliance tools give ease of rollout more weight, because an ELD or camera program fails if drivers will not use it. Maintenance and routing software has no device, so it has no hardware weight.

GroupFeaturesFit for the core jobSupport and onboardingEase of rolloutPublished priceContract and exitHardware cost
Tracking and telematicsGPS fleet tracking, fleet tracking, telematics, fleet management software, EV fleet management, fuel management, government fleets, trucking30%20%15%15%8%7%5%
Compliance and driver safetyELD compliance, driver safety25%20%15%20%8%7%5%
Maintenance, routing and deliveryfleet maintenance, route optimization, dispatch, delivery30%20%15%15%10%10%–

The overall score is the weighted average of the parts that are scored, rounded to one decimal place. When a vendor does not publish its price, contract terms or device cost, that part is left out and the other weights are scaled up in proportion, so a product is not marked down, or up, for a number nobody can see. A missing figure is not evidence of a bad figure. Publishing still pays: a vendor that prints a low price or a short contract earns credit that a quote-only vendor cannot. The panel on each product page lists any part that was not scored.

Who signs it off

Every score starts as a draft. It appears on a page only after the editor, named on the score itself, has read the inputs and the quoted evidence and approved it. A score that later moves by more than 0.3 because a price, a contract or a support fact changed goes back to draft until it is approved again.

There is one score per product and it is the site's own. FleetOpsClub collects no user ratings, so there is no average of reader reviews and no review count behind the number.

What the score does not do

It does not change the order of any list. Category and directory pages are ordered by sponsored placement, then the featured flag, then name, exactly as how rankings work describes.

Money is not an input. Sponsored placement, the featured flag, affiliate status and lead forms are not read when the score is calculated.

It is not a substitute for the review. A 3.4 can be the right product for your fleet and a 4.1 the wrong one; the review says which kind of fleet each product suits.

Where the score appears

On the product's own page, next to the verdict, with each part's basis and the date the vendor's terms and support pages were checked. It is not shown on category, comparison or alternatives lists.

In the page's structured data, an approved score is published as a single editorial Review that links back to this page. A product appears there as a SoftwareApplication only when the vendor publishes a price, because that type requires one. Method version v2.1.