GPS time tracking that records two moments a day
Hours you can defend on a Friday
A driver says he was on site at seven, and all you have is a WhatsApp message and a memory. Time tracking is part of Yipii Mobility, and it puts a record where that argument used to be.
Clock in from a phone
The browser is asked for a position once at clock-in and once at clock-out. Between those two taps Yipii records nothing about where anyone is.
Matched to the site
If the clock-in falls inside the radius of one of your sites, the site name lands on the entry. A crew at Mrieħel and a crew in Gozo separate themselves.
Anomaly flags
A poor GPS fix, a clock-in away from the site, a shift of 16 hours or more. Yipii marks the entry for a human to read and lets it through.
A payroll CSV
Regular, overtime and double-time hours, break hours, employee code and currency, one row per employee for the period.
What GPS time tracking records, and when it stops
Two positions a day, taken from the browser's location prompt: one at clock-in, one at clock-out. Each one carries an accuracy radius in metres, because a phone standing in an open yard usually gets under 10 m while the same phone inside a workshop lands somewhere between 40 and 200 m. That radius is stored on the entry, so whoever reads it later knows how much to trust it. We built it this way on purpose. A record of when someone started and finished is a payroll question, and it does not need a trail of where they went at 11:20.
- One position at clock-in, one at clock-out, nothing during the shift
- Accuracy radius in metres stored against each of the two points
- Nearest geofenced site attached when the fix falls inside its radius
- The person who clocked the entry can see their own hours and positions
Included with Yipii Mobility, the add-on that extends your IoT account. One subscription covers everything in the app, so no feature here is sold on its own. What Yipii Mobility includes
Pending, approved, locked. In that order.
Every entry arrives pending approval. A manager approves or rejects it, and Yipii stamps who did it and when, so a challenge six weeks later has a name against it. Flags ride along with the entry and stay informational: a 16-hour shift or a clock-in 300 m from the site gets marked for a human to read, never refused. Rejecting an entry is the explicit way to hand it back for a correction.
- Approve or reject, with the approver and the timestamp stamped on the entry
- Five flags: low accuracy in, low accuracy out, outside geofence, 16-hour shift, manual entry
- Admins can add a backdated entry, which arrives carrying the manual-entry flag
- Filter to flagged-only and review the handful that need a decision
Three states, and one of them is a one-way door
A pay period is a date range with a status on it. The status decides what can still be changed and what has already gone out the door.
Open
Entries land in the period and stay editable. Approve through the week rather than in one Friday scramble, because approval is what decides who makes the export.
Locked
Locking sweeps every approved entry in the date range into the period and freezes it. Pending and rejected entries are left behind. A locked period can be reopened if something was missed.
Paid
Marked once payroll has actually gone out. A paid period refuses to reopen on its own, so an amendment after that point goes through our support team.
One week, worked out
Pay profiles hold the rate and the rules per employee. Take a profile on €15.00 an hour, an overtime threshold of 40 hours and a multiplier of 1.5. The week comes in at 50 hours.
Thresholds reset on the ISO week, Monday to Sunday, and hours split in clock-in order. Double-time is an optional second tier, commonly 48 hours at a multiplier of 2.0. If the profile carries a default break with auto-deduct switched on, that break comes off every completed clock-out before any of this is worked out.
- Regular, 40 h at €15.00
- €600.00
- Overtime, 10 h at €22.50
- €225.00
- Gross for the week
- €825.00
One CSV out, and the hours attached to the job
The payroll export gives you one row per employee for the period: name, employee code, currency, regular hours, overtime hours, double-time hours, break hours, total hours, the pay against each of those three, gross pay, the entry count, and the period with its start and end dates. Sixteen columns, opened in whatever your bookkeeper already uses. A separate timesheet export carries the operational view instead, with approval status, site, flags and payable hours on every line.
- Sixteen columns, one row per employee, currency named on the row
- Labour hours linked to work orders, next to parts and vendor invoices
- Job costing that shows the labour half of what a repair actually cost
- Timesheet export with approval status, site, flags and payable hours
Where the payroll side stops
Weekly overtime only
The threshold runs on the ISO week. A rule along the lines of anything over 8 hours in a day is not supported, so a crew working 12 hours on Tuesday and 4 on Wednesday reads the same as two 8-hour days. If your agreements are written daily, tell us before you buy rather than after.
Gross pay needs an hourly profile
Pay type can be hourly, salary, or not on payroll. Only hourly produces gross-pay figures, so a salaried person's hours are still tracked and exported while the money columns stay empty. Annual salary is stored for reference and is not used in the calculation.
An unapproved entry misses the run
Locking a period sweeps in approved entries only. Anything still pending or rejected in that date range sits outside the payroll CSV until you reopen the period and approve it. The habit that fixes this is approving through the week instead of on the last afternoon.
One boundary worth stating outright: Yipii records the hours and the two positions, and hands you the export. What you tell your crew about that recording, and the employment agreements the hours are paid against, remain yours.
Frequently asked
Two things, at two moments. At clock-in the browser is asked for a position, and Yipii stores the latitude, the longitude and the accuracy radius the browser reported. The same happens again at clock-out. Nothing is recorded in between: time tracking produces no continuous location trail, no background reporting, and no position while someone is on a break. If the clock-in falls inside the radius of one of your sites, the site name is attached to the entry as well. Those coordinates are visible to the admins and fleet managers on your account, and to the person who clocked the entry.
It depends on where the phone is standing, and Yipii stores the number rather than hiding it. A clear outdoor fix in a yard is usually under 10 m. The same phone inside a workshop or a warehouse commonly lands between 40 and 200 m, because the handset falls back on wifi and cell towers once it loses sight of the sky. Anything worse than 100 m picks up a low-accuracy flag, so the manager reading the timesheet knows how much weight to put on it. A poor fix never stops someone clocking in.
No. Yipii flags it and lets it through. A clock-in outside the radius of the expected site carries an outside-geofence flag, and the same treatment applies to a fix worse than 100 m at either end, a shift of 16 hours or more, and any entry an admin created by hand. All five flags are informational, and none of them block the entry. Blocking a clock-in punishes the person whose phone lost signal in a basement and does nothing about the person who genuinely was somewhere else, so the flag goes to a manager instead.
From a pay profile held against each employee: an hourly rate, a weekly overtime threshold and a multiplier. Take a rate of €15.00 an hour, a threshold of 40 hours and a multiplier of 1.5. A 50-hour week pays 40 hours at €15.00, which is €600.00, plus 10 hours at €22.50, which is €225.00, for €825.00 gross. Thresholds reset on the ISO week, Monday to Sunday, and hours split in clock-in order. Double-time is an optional second tier, commonly 48 hours at a multiplier of 2.0. Daily overtime rules are not supported.
A locked period, yes. Reopening puts the entries back in play so you can approve something that was missed and lock the period again. A period marked paid is a different matter: it refuses to reopen on its own, and an amendment at that stage goes through our support team. That is deliberate, since a paid period is the record of money that has already left the account. Lock at the end of the week, and mark paid once the run has genuinely gone out.
The rest of the picture
Setting up pay profiles, running a period from open through to paid, and the full flag list are written out in the time tracking guide in the Yipii Mobility docs.