Who's this for: Admin, HR Admin

Set up attendance tracking for your DSP: activate it, create check-in policies, review conflicts, and approve time records.

This second onboarding session focuses on Kenjo's attendance tracking: how to enable it, which check-in methods your Delivery Associates and Dispatchers can use, how to set up shifts and breaks, and how to approve time records.

Before your employees can check in, attendance tracking must be enabled both for your company and for each employee.

Once enabled, both you and the employee will see the additional Attendance tab on their profile.

If you have many Delivery Associates, don't enable tracking one by one: use the bulk action instead.

Note: if an employee doesn't have attendance tracking enabled, they can't record their time, regardless of the policy assigned to them.

In each employee's profile (Personal tab), you define how many days per week they work. This setting doesn't change which days they actually work; it changes how Kenjo distributes their contractual weekly hours into daily target hours, as long as you don't have an active shiftplan for that employee. For example, with 38 weekly hours:

Important for Spain: many DSPs also work Saturdays and/or Sundays. If you set 5 days (Monday to Friday) and a driver checks in on a Saturday or Sunday without a shiftplan planning that day, those hours aren't counted as planned time, but as overtime. As long as your shiftplan isn't operational yet, keep the days set to 7 so the system doesn't flag weekend hours that are actually part of your normal operation as "overtime", and periodically compare Kenjo's exported records against your planning (Excel or another tool) to catch discrepancies. Once your shiftplan is active and reflects the real shifts, adjust this setting accordingly.

An attendance policy defines how employees check in and which shift, break, and rest rules apply. Every company starts with a default policy that can't be deleted or renamed, but can be adjusted. Any employee not assigned to another policy automatically falls under it.

The check-in method defines how an employee records their check-in and check-out. You can enable one or several methods per policy:

Important: if you enable a kiosk method (PIN code or QR code) together with Punch clock, employees will be redirected automatically to the kiosk method. If you want to allow check-in via Punch clock, disable the kiosk method. For tracking via API, don't select any check-in method.

It's common to have two very different check-in profiles within the same DSP:

Create a separate policy for each group (see "Create a new policy" below) and, to manage them more easily, group your dispatchers into a team:

An employee can only be assigned to one policy at a time. If your teams need different methods or rules (for example, a kiosk at the station versus mobile check-in for drivers on the road), create a separate policy for each group and assign the relevant employees.

Note: assigning an employee to a policy doesn't automatically enable their attendance tracking. If tracking isn't enabled on their profile (see the previous section), they won't be able to check in even if they're assigned to a policy.

Geolocation lets you check whether your Delivery Associates check in and out within a defined radius around your delivery station or your other locations. It only works with the Time sheet management or Punch clock methods, only from the mobile app, and only if the employee has GPS enabled on their smartphone.

Don't confuse this with "Offices and Locations": geolocation Locations are set up inside the Attendance module itself (Attendance > Settings > Locations) and include coordinates and a check-in radius. They're independent of the Offices and Locations you registered in Settings when you set up your company.

Tip: if your station is in an industrial park or a building without a clear street number, address validation often won't pinpoint the exact spot on the first try. Add the building/plot number if you have it, visually check on the map that the point matches the actual entrance, and if it's still a bit off, use a larger radius (0.5 km or 1 km) so you don't block valid check-ins over a difference of a few meters.

If you operate several stations, add one location for each: every Delivery Associate is only validated against the location assigned to them.

Once geolocation is enabled, your employees see in the app whether they're checking in inside or outside the workplace. As an Admin, on the employee's profile under the Attendance tab, or in the Attendance Summary, you see the status of each check-in with a color:

Keep in mind: if an employee doesn't enable location tracking on their phone, attendance tracking still works as normal; their location simply isn't validated (it shows up grey). Geolocation never blocks a check-in on its own if it's disabled or no locations are configured.

Within the attendance policy you can define rules that automatically flag a conflict when a shift, break, or rest limit is exceeded. Kenjo doesn't block records on its own: an Admin has to review and resolve each conflict manually, and no rule change is retroactive — it only affects new records.

Note: In markets where people don't work on public holidays (for example, Germany, where there's no Amazon delivery on public holidays), this rule helps detect unusual check-ins. In Spain, last-mile delivery often also runs on public holidays. If that's your case, turn off the "Overlap with public holidays" rule so it doesn't generate conflicts on a day that, for your operation, is a normal working day.

Note: the Spanish Workers' Statute (art. 34.3) requires a minimum of 12 hours of rest between the end of one working day and the start of the next. Set this minimum (or a higher one if your collective agreement or your own internal policy requires it, for example for road-safety reasons) in the "Minimum rest between shifts" rule for each policy.

Paid breaks and collective agreements: in Spain, a break may or may not count as effective working time; this usually depends on your sector's collective agreement and your own company policy. For example, a DSP might have a total break of 30 minutes of which only 20 minutes are paid (count as work) and the rest doesn't. Check this with your advisory firm before configuring the "Paid breaks" setting, since an incorrect value can result in unwanted time deductions.

You'll find all conflicts generated by these rules gathered in the Attendance Summary (see the "Use the Attendance Summary" section below).

A salary surcharge automatically calculates a percentage increase (for example, 125% or 150%) on the hourly wage when a given condition is met, for example a delivery on a public holiday or during a specific night shift.

Keep in mind: Kenjo currently only calculates surcharges based on the conditions mentioned above (category, public holiday, day of the week/time). An automatic surcharge from a certain number of overtime hours worked (for example, "from the 9th hour onward") isn't possible yet and must be managed manually.

Before records are sent to payroll, you need to review and approve them; from that point on, employees can no longer edit them.

Tip: approve records regularly before each payroll run. Unapproved records can still be edited, which can cause discrepancies in your Delivery Associates' payroll.

The Attendance Summary shows you at a glance whether your employees are hitting their target hours and where there are open conflicts.

Once you've completed this session, we recommend reviewing the following points:

Why can't an employee record their time?
Check two things: whether attendance tracking is enabled on their profile (Personal > Enable attendance tracking) and whether they're assigned a policy with at least one check-in method. If either one is missing, the tracking feature won't show up for them.

Why do I still see a conflict even though I just changed the rule?
Shift, break, and rest rules aren't retroactive. The new value applies from today onward; records from before the change keep the conflicts generated under the previous rule.

What happens if a Delivery Associate doesn't turn on GPS on their phone?
Attendance tracking works as normal: their location just can't be validated, and the check-in shows up marked in grey. Geolocation never blocks a check-in if the employee doesn't have GPS enabled, unless you've configured blocking for being outside a valid location.

Can I assign an attendance policy to many employees at once?
Yes. Open the policy, go to Manage employees > Assign employees, filter by office, department, or team, and select employees using the checkbox.

Can overtime surcharges be calculated automatically from a certain number of hours?
No. Currently, surcharges can only be linked to a public holiday or specific days/times of the week, not to an overtime-hours threshold. That case has to be managed manually for now.