Hours worked become the hours actually worked
Rounded, filled-in-later time almost always rounds up. Measured time doesn't: payroll gets what actually happened, on the same yardstick every month.
Work time tracking for teams working in the field
The timesheet that fills itself in
Your team's Android phone records who was on which site, when they arrived and when they left. Month-end builds itself from that — to the minute.
GDPR-compliant, EU data handling · Hungarian-built and supported · Live in a few days
- Active sites
- 3
- Hours logged today
- 38.5
Béla Kovács Váci út 112 since 6:52
Tímea Nagy Main depot since 7:04
Áron Szabó In transit since 8:20
Gergő Tóth Last seen 9:15 2h ago
On site In transit Unreachable
Map: © OpenStreetMap contributors, © CARTO
- GDPR-compliant, EU data handling
- Hungarian-built and supported
- Hungarian and English UI
- Excel export and API
What produces your attendance sheet today?
In most places: paper, a spreadsheet, or the foreman's memory. All three are written after the fact, and all three get it wrong — usually at the employer's expense.
- Someone fills in the attendance sheet at the end of the week, from memory.
- Nobody can say which site consumed how many hours.
- Travel and idle time appear nowhere at all.
- When something is disputed, there's nothing to point to.
Klip replaces that with measurement. The phone records arrival at a site and departure from it, and the report is built from that. Nobody has to keep anything.
Return
What this saves
Time recorded loosely is wrong in both directions, and the difference stays with someone every month.
You find out what each job really consumed
Once you can see how many hours a project actually took, the next quote isn't guesswork. The year-end accounts shouldn't be the first place a loss-making job shows up.
The time spent compiling it disappears
No more hours each week collecting who was where and typing it into a spreadsheet. This is the easiest line to calculate: the supervisor's hourly rate times the time they spend on it today.
Travel and idle time become visible
Not just who was where, but how much went on travelling and waiting. Those are the two lines a paper attendance sheet never shows — and usually the ones with the most room to improve.
We deliberately don't promise a number: it depends on how many people, how many sites, and how you record it today. On a demo we can work it out from your own figures in a few minutes.
What the system does
Attendance and work time specifically, not general fleet tracking.
Live fleet view
One screen shows who is working right now, who is in transit, who is unreachable and who is on leave, with a map alongside. Mid-day questions stop needing a phone call.
Geofenced work sites
Every site is an address and a radius. Entering and leaving it becomes an attendance event automatically. Bulk-import from a spreadsheet when there are many, and archive projects once they finish.
Battery-conscious tracking
Three modes: continuous sampling, geofence events only (the gentlest), or both together. Set per device, not once for the whole fleet.
Captures offline
No signal on site doesn't mean lost data: the phone queues positions locally and uploads them as soon as it reconnects. The queue survives the app being killed and the device restarting.
Reports by site and by person
The same data in two views: who worked on a given site and for how long, or where one worker spent their week. Both export to Excel.
Roles and permissions
Administrators manage everything; the reporter role can only view. Multi-site companies don't have to hand everyone full access.
Three steps to go live
No server installation, no worker sign-ups, no week of training.
-
Add your work sites
An address or a point on the map, plus a radius — that's a site. When there are many, import them from a spreadsheet in one go.
-
Phones enroll by QR code
Workers don't create accounts or memorise passwords: they scan a QR code generated in the admin panel and the device is configured.
-
The report builds itself
Nothing left to do. Attendance data accumulates continuously, and month-end is one click — Excel export included.
What it looks like
The running system's own screens, with demo data.
Integration
Fits what you already run
Work time data earns its keep where the invoice and the payroll are produced.
Coming
Számlázz.hu and Billingo
Billable hours handed to your invoicing software without retyping.
Coming
API for other systems
Payroll, ERP, project management — attendance data is available machine-to-machine.
Excel export today
Every report downloads in a form you can hand straight to payroll.
Bespoke features on request
Custom fields, a specific report, a fit to a system you already run. Tell us what you need — development is here, not at a product owner abroad.
Integrations marked “coming” are in development. If the timing of one matters to your decision, ask.
Month-end is one click
The same underlying data in two views, depending on whether you're accounting for the project or the person.
| Work site | Hours |
|---|---|
| Váci út 112 6 | 184.5 |
| Main depot 4 | 152.0 |
| Debrecen, Kassai út 3 | 97.5 |
| Szeged, industrial park 2 | 64.0 |
- By site: who worked on a given work site in a period, and for how long.
- By person: where one worker worked and for how long, broken down by day.
- Overtime grace: a tolerance around the schedule so a few minutes' drift doesn't distort the numbers.
- Timezone-correct maths: the day starts and ends in the organisation's own timezone, daylight saving included.
- Excel export from every view, in a form you can hand straight to payroll.
- Closed sites and retired devices stay in the reports for the periods they were active.
Security
This system stores where people go. It is built to match
Not a privacy policy bolted onto an average application. What follows are concrete, checkable technical measures — the ones a serious customer's security review actually asks about.
A separate key per device, revocable instantly
Every phone authenticates with its own key, replaceable from the admin panel in one click. A lost handset means re-issuing nothing across the fleet: that one key is dead, the rest are untouched.
Encrypted on the phone and on the server
The phone keeps its key in Android's encrypted store, and the server holds no recoverable password — login credentials are argon2id hashes, the current OWASP recommendation. Traffic runs over an encrypted channel end to end.
Automatic abuse protection
Login and data upload are throttled separately: password guessing stalls within minutes, and a single misbehaving handset cannot flood the system.
Every admin action logged
Who changed what, and when — searchable after the fact. Useful well beyond disputes: it is the fastest way to find the cause of a misconfiguration.
Expired data removes itself
You set the retention period; a scheduled process does the deleting. Data minimisation isn't a policy document — it runs whether or not anyone remembers it.
Every release goes through an automated test suite
A suite running against a real database checks every change before it ships — isolation, timezone arithmetic and permission handling included. Whether a release can go out isn't decided by a manual read-through.
A subject request — exporting or erasing one worker's complete data — is one click, and stays free in every plan. Producing the legitimate interest assessment and informing employees remains the employer's responsibility; Klip supplies the technical groundwork and the documented behaviour behind it.
Shaped to how you actually work
Klip is built from modules, and which ones are switched on is set per company — a ten-person contractor doesn't need what a multi-site operator needs. Which also means you don't pay for what you don't use.
Work sites
Geofenced site management, with bulk import and project closing.
Leave and absence
Record holiday, sick leave and other absence — reflected correctly in the reports.
Team
Manage multiple administrator and reporter users with roles.
Reports
Site-based and person-based attendance reporting, with Excel export.
In development
Custom fields
Your own data fields on workers, sites and projects — job title, cost centre, subcontractor, whatever your records need. They flow through to the reports and the export.
In development
Leave requests with approval
The worker requests, the manager approves — today only an administrator can book leave.
In development
Hour approval before payroll
Manager sign-off on computed hours before they count as final.
The live fleet view, device management and per-worker data export are always available — those are not up for negotiation. Items marked “in development” are not live yet; if the timing of one matters to your decision, ask on the demo.
Frequently asked questions
What most people ask before rolling it out.
Do workers need to create an account?
No. The device is configured by scanning a QR code that the administrator generates in the web interface. There is no username or password for the worker to forget.
How much battery does it use?
It depends on the tracking mode. Geofence-only is the gentlest: the phone doesn't sample continuously — the operating system notifies it when the device crosses a work site boundary. Continuous mode gives denser data at a higher cost, and hybrid combines the two. The setting is per device.
What happens if there's no signal on site?
Nothing is lost. The phone queues positions in its own local database and uploads them automatically once it reconnects. The queue survives the app being stopped and the device restarting.
Does it track workers outside working hours?
Each device carries the days on which work is expected, and reports follow that schedule. The app also runs with a permanent, visible notification, so it is clear to the worker when the service is active.
Does it work on iPhone?
Not currently — the mobile app is built for Android devices. The web interface of course works in any browser, iPhone included.
What do we need for this to be lawful?
For employee location tracking the employer must carry out a legitimate interest assessment and inform employees in advance; where a works council exists, consulting it is also the employer's responsibility. Klip provides the technical side: purpose-bound collection, a configurable retention period, automatic deletion and one-click fulfilment of subject requests. Drafting the actual legal documents is a job for a legal professional.
Within our company, who sees what?
You decide. Administrators manage everything; the reporter role can only view — it cannot reconfigure a device, rotate a key or delete data. Across multiple sites that lets a local manager have the reports without also having the settings. Every admin action is logged, so who changed what stays searchable after the fact.
If we leave, can we take our data with us?
Yes. The organisation's complete data set can be exported, and deletion can be carried out on request. No lock-in.
Let's look at it on your own sites
In a short online demo we'll walk through how the system would look with your actual locations and schedules. Not a canned slide deck.
Usually answered within one business day.