Common questions about Torek

An asset list, a list of users with their roles, and an agreement about who logs a defect and when. There are no technical prerequisites beyond a browser, plus an Android phone for the mechanics.

The longest part is never the data entry — it is that agreement about the process, and that is a company question rather than a software one.

No. The system runs in the browser, and mechanics and drivers get a separate Android app. There is no server to buy, no licence to install and no IT project to run.

Technically, as long as it takes to enter the asset list and the users. In practice the first weeks go into the habit: a fault ends up in the system rather than in a message or a conversation in the yard.

Start with the asset list, which can be entered in the system. Fuel-card statements are uploaded as CSV or Excel (.xlsx) files, and before anything is saved you can see exactly what will be created.

If you have a larger historical file, write to us — we would rather look at its actual structure than promise a result in advance.

Access follows the role. A driver sees their own records and their own fuel entries, a mechanic their own jobs, a manager the whole fleet and the reports.

Every action stays in the audit trail, so it is always clear who changed a record and when.

Yes. Modules are enabled per company, and a module that is off is closed to everyone in that company — the system refuses its requests. Most fleets start with defects and work orders and add fuel, trip logs or parts later.

All data is stored in the European Union.

No. Each company's data is isolated at the database level, and every action is recorded in an audit log.

Yes, regularly. That is one of the reasons a workshop's history is safer in the system than in a notebook or a spreadsheet on one person's laptop.

Yes. Reports and lists export to CSV, XLSX or PDF and can be used outside the system — in accounting, in a spreadsheet or in another application.

We process personal data under the GDPR: every customer signs a data processing agreement (DPA) in which Torek acts as the processor. Data is stored in the European Union, each company's data is isolated at the database level, every action is recorded in an audit log, and role-based permissions and regular backups are in place. Details are in the privacy policy.

Cars, trucks, trailers, road and construction machinery, tools and attachments. Stationary objects can sit alongside them: buildings, machines, warehouses and infrastructure.

For a mixed fleet that means one job queue and one history, whatever the brand or the manufacturer portal.

No. Torek manages repairs and maintenance: defects, work orders, parts, fuel, trip logs and history. Location and route tracking is telematics — in most fleets the two systems are used side by side.

No, and it is not meant to. Torek prepares no VAT returns and keeps no general ledger. What goes to accounting are documents and exports: fuel write-offs, parts write-offs and supplier invoices export to Rivilė (GAMA and ERP formats) or as a universal XLSX or CSV file for other software.

No. A manufacturer portal handles its own brand well, but a mixed fleet has six or eight of them and none holds the shared repair history. Torek is that shared layer.

Each maintenance rule has one interval — kilometres, engine hours, days or months: an oil change every 10,000 km, a roadworthiness test once a year. When two limits matter, the unit gets two rules, each tracking its own due date.

Every day the system builds preventive-maintenance schedules from readings and rules and notifies the people responsible about what is coming up or overdue; a scheduled item becomes a work order in one step, so the service no longer depends on somebody remembering.

A named parts kit for a specific service: the parts that job will need, with quantities. Applied to a work order, the parts are planned and reserved in advance, and the job cannot be closed while any of them is unresolved. A mandatory checklist is kept separately and can block completion too.

Yes, as separate modules. Fuel covers versioned norms, actual against norm, card statement imports and a monthly write-off report; trip logs cover filling in, numbering, submission and approval. Drivers keep trip logs on the phone (works offline); managers approve them in the browser.

Fuel consumption is calculated from fill-ups only: between two full tanks, using the odometer or engine-hour reading entered with each fill-up. Mileage from approved trip logs and the readings entered with fill-ups and services build one meter history per vehicle, and preventive-maintenance due dates are forecast from it.

Cost per asset, maintenance punctuality, work-order cycle time, the ageing of open defects, the most frequent failure causes, and upcoming statutory deadlines such as inspections, insurance and tachograph checks.

Any of them exports to CSV, XLSX or PDF.

Yes. The Android app is built to work offline: entries and photos are stored on the phone and synced when the connection returns. On a site or in a quarry that is often the feature that matters most.

On the phone: a description, severity, the machine and up to eight photos. The record is visible to the manager immediately, and it becomes a work order in one step.

It can be removed, but not erased without a trace. Only the company administrator can do it, and only with a reason; the entry leaves lists and reports, but stays in the removal log and can be restored. A defect that already has a work order cannot be removed.

That is what the workshop kiosk is for — a shared screen on the shop floor with a short PIN to sign in. A mechanic sees their own job queue, marks work started and finished, and can log a defect.

On the phone, time can be run on a timer or entered by hand and linked to a job, and the home screen shows how much has been worked today; in the browser, hours can be entered against the work order. Hours are what make repair costs real — parts alone show half the figure.

Lithuanian and English, both in the browser and in the app, with the same workshop vocabulary in each: defect, work order, engine hours, trip log.

Pricing depends on the number of users and the number of machines, so there is no single figure that fits everyone. Start with a free trial or a walkthrough, and settle the price once the size of the fleet is clear.

Yes. The free trial can be started straight away. A walkthrough is more useful when the fleet is mixed or when a process has to be moved off spreadsheets.

Not a generic presentation but your own process: how one of your machines would look in the system, and how one real fault would travel from the report to the finished job. Thirty minutes is enough.