Torek Fleet maintenance app
Updated
The Torek app is an Android application for mechanics and drivers. Defects are logged with photos, work orders are started and finished, inspections are filled in, hours are recorded, and meter readings and fuel fills are entered — next to the machine, rather than in the evening at a desk.
The part that matters most is working offline. Entries go into a queue on the phone and are sent automatically once a connection returns; if the record changed on the server meanwhile, the app shows a conflict instead of quietly overwriting somebody else's work. The browser and the app read and write the same records.
Anything a person can do in a workshop or on a site is written to the phone first and sent afterwards. What queues up:
| Type | What waits in the queue |
|---|---|
| Defects | A new defect, its photos and its comments |
| Work orders | Status changes and comments on the job |
| Time entries | Time started, paused and finished |
| Inspections | A completed pre-use inspection |
| Meter readings | Odometer and engine-hour entries |
| Fuel fills | A fill entered by the driver |
| Trips | A trip started, ended or added later |
If a session expires with entries still queued: nothing is deleted. The queue is set aside, and when the same person signs in again the app asks whether to send it. Half a day of work on a remote site should not depend on whether a token was still valid at the time.
What the app does not do: there is no manager reports screen (only the home-screen counters), no trip-log approval, no creating or editing assets, and none of the office side of fuel — norms, the review queue and imports. All of that is done in a browser, and the calendar in the app is read-only.
For a mechanic it means the start and end of a job are recorded when they happen, not after the shift. For a driver it means a fault leaves the site as a defect with a photo rather than as “something is knocking”. For a manager it means the maintenance reports are built from a real day. Where carrying a phone is impractical, a shared workshop kiosk plays the same role on the shop floor.
Yes. Defects with photos, work-order status changes, comments, time entries, inspections, meter readings, fuel fills and trips are written to the phone and wait in a queue. When a connection appears they are sent automatically — nobody has to press a sync button or remember what was missed.
That is what makes it usable on sites, in quarries and on the road, where signal disappears for half a day. The screen always shows how many entries are still waiting.
Before sending a change the app checks whether the record on the server moved since the phone last read it. If it did, nothing is silently overwritten: the entry is held back as a conflict, and the person decides whether their version wins or is dropped.
Re-sending never creates duplicates. Each queued entry carries its own key, so a connection that dies mid-upload still produces exactly one defect or one work order.
Android devices. The app is delivered to the company as a prepared package, and people sign in with the same credentials they use in the browser — there is no separate registration.
Screens follow permissions: a driver sees their own defects and fuel entries, a mechanic sees their work orders, inspections and time entries.
The local database is encrypted, sign-in tokens live in the device's secure storage, and the app itself can be locked with a PIN or biometrics. Unsent entries are not thrown away when a session expires — they are set aside and offered again once the same person signs back in.
English and Lithuanian. The language follows the phone or can be picked in settings, and dates are written in one format everywhere (YYYY-MM-DD).
Trip logs — yes: the driver starts and ends trips on the phone, submits the day's log and sees their log history. There is no manager reports screen in the app — the full breakdowns, exports and trip-log approval are opened in a browser.
A walkthrough: a defect from the field, a job, and working offline.
Get in touch