Torek Fleet maintenance software
Updated
Fleet maintenance software keeps a fault from the moment it is spotted to the finished repair as one record: the defect, the work order, the parts used, the mechanic’s hours and the unit’s history.
Torek is built for in-house fleets — trucks, trailers, construction, road and agricultural machinery. Unlike repair-shop software its centre is not a customer invoice but your own upkeep and what it costs; unlike telematics it does not track location, it tracks the work. The product category is known internationally as CMMS. Data is hosted in the European Union.
In most fleets, repair work is organised in three places at once: a spreadsheet, a stack of paper and the mechanic’s memory. With a dozen units that is fine. Somewhere past fifty the same symptoms start showing up:
| Capability | What it gives you in practice |
|---|---|
| Defect capture | The fault is written down where it is noticed — on a phone, with a photo and a severity. Nothing gets lost by the end of the shift. |
| Work orders | A defect becomes a job with an owner, a priority and a due date. The status is visible without asking anyone. |
| Parts and stock | Parts are written off against a specific job rather than in bulk, so you can see what is missing before work starts. |
| Labour time | Mechanic hours sit on each job — the basis for a real repair cost rather than an estimate. |
| Planned maintenance | Reminders from rules: each maintenance rule has one interval — kilometres, engine hours, days or months; when two limits matter, the unit gets two rules, each tracking its own due date. |
| History and reporting | One file per unit: what failed, when, which parts went in and what it cost. |
This is where buyers most often pick the wrong category, because both kinds of software are described in similar words. The difference is structural:
| Repair-shop software | In-house fleet maintenance | |
|---|---|---|
| At the centre | A customer’s vehicle and the invoice for it | Your own unit and its downtime |
| Measure of success | Revenue per job, shop throughput | Less downtime and a lower cost of ownership |
| Typical assets | Mostly passenger cars | Trucks, trailers, road and agricultural machinery |
| What gets counted | Standard repair times and invoices | Engine hours, mileage, parts and labour per unit |
If you do both — your own machines and customer work — Torek has an optional workshop module for the customer side: work acts, invoices and credit notes to customers. Even so, start from whichever side is larger: that is the process the system has to fit first.
If you already run a GPS or telematics platform, you do not need to replace it. It tracks location, routes and sensor data; Torek picks the process up where telematics stops — at the defect, the work order, the parts and the labour — and works out fuel consumption from fill-ups and readings rather than GPS. They are layers, not competitors, and the overlap is small enough that most fleets run both.
The sequence that tends to work: enter the assets, agree that operators log defects from their phones, and only then switch on planned maintenance. Fuel and mileage can follow once the day-to-day entries are reliable — see fuel tracking and trip logs. Fuel consumption is calculated from fill-ups only: between two full tanks, using the odometer or engine-hour reading entered with each fill-up; an approved trip log adds its closing odometer reading to the vehicle’s meter history. Paper forms can run alongside for a while; the switch does not have to happen in one day.
Accounting software records a repair as a line item: how much was spent and when. Maintenance software runs the process behind that line — what broke, who is fixing it, which parts are needed and what has already been done to that particular unit.
In practice they do not replace each other. Most companies keep their accounting system and connect it to the maintenance side, rather than trying to run repairs out of the ledger. Torek exports parts write-offs and supplier invoices to Rivilė or as a universal XLSX or CSV file.
That is exactly what Torek is built for. Repair-shop software revolves around a customer’s vehicle and the invoice issued for it; in your own fleet there is no invoice, there is a cost centre and downtime.
So the number that matters is not revenue per job. It is how often the same fault comes back and what one unit costs to keep running — labour, parts and fuel together.
No. The system runs in a browser, and mechanics get a separate mobile app that works without a connection. On a site with no signal the entry is stored on the device and synchronises once the phone is back online.
Technically, as long as it takes to enter the asset list. In practice the time goes into agreeing who logs a defect and when — a process question rather than a software one, and the one that decides whether the data stays trustworthy.
A walkthrough of your own process — no commitment.
Get in touch