A merchandiser in Machakos starts her day at the shutter of a duka that has just opened. There is no office to walk into and no gate to pass. Whatever record exists of her having started work is the one she creates herself, on a handset, standing in the street.
Four weeks later somebody in HR has to turn thirty of those mornings into figures payroll can pay: paid days, unpaid absence, leave taken, allowance-eligible days on route. If the record is thin, the gaps get filled from memory. Get the register wrong and you have not made an administrative error — you have paid somebody incorrectly.
The distance between that first tap on a phone and a payroll run that closes without argument is short to describe and easy to get wrong. It is mostly a matter of writing the rules down, capturing evidence that is honest about what it proves, and giving corrections a proper door instead of a back channel.
Marking the Start of a Day Without a Depot
Office attendance is a by-product of walking through a door. Field attendance has no door. A rep working a beat through Kisumu, a van salesman loading before dawn and an agrovet promoter working upcountry markets each start somewhere different, and the somewhere changes daily. So the first decision is the one most teams skip: what counts as the start of the working day for a person with no depot. There are only a few defensible answers, and the organisation has to pick one and publish it.
- Check-in at the first outlet. Clean for beat-based reps, but it makes travel to the first duka the rep's own time — fine on urban routes, harsh on a long upcountry leg.
- Check-in at a nominated start point. Fairer for reps who travel far before they sell anything, though it needs a rule about what a legitimate start point is, and it may capture a home location.
- Check-in where loading happens. Natural for van sales, and it gives a single anchor that is easy to geofence.
Whichever is chosen, the check-in should carry a GPS stamp and a timestamp taken from verified device time rather than a value the user can edit — and it should survive a dead network. Rural connectivity gaps are real, and so are power interruptions that leave a handset flat by mid-afternoon; a check-in that fails for want of signal near Naivasha is not evidence of absence. Capture locally, queue, and stamp the time of capture alongside the time of sync so the difference stays visible.
Face Check-In and What It Proves
A selfie at the moment of check-in binds the record to a person rather than a handset. That matters, because a phone can be handed over and a colleague can mark a friend present from the wrong side of town. Face capture closes that gap and very little else.
A face at a location at a time proves this person was there then. It does not prove they made a call, spoke to the duka owner, or did anything useful afterwards. Paired with outlet calls, orders and shelf photos, the day becomes legible; on its own it is an identity check.
There is also a handling obligation. Photographs of employees are personal data, and Kenya's Data Protection Act, 2019, administered by the Office of the Data Protection Commissioner, governs how they are collected and how long they are kept. Tell the field force plainly what is captured, restrict who can view it, and set a retention period — before the first selfie rather than after the first complaint.
Geofencing a Job That Moves
A geofence is a boundary around a place plus a rule about what happens when a check-in falls outside it. The mechanic is simple; the tuning decides whether the programme works.
Outlet coordinates are usually captured once, during a survey, then never revisited. Some are wrong from the start — pinned from the pavement opposite, or captured inside a wholesaler's storeroom where the signal bounced. A radius generous enough to absorb that in a dense Nairobi street is far too loose on an open route near Eldoret, where it lets a rep mark a call never made.
So stop treating the fence as a gate. Let the check-in happen, record the measured distance, and surface the exception for a supervisor. A hard block produces one of two outcomes, both bad: work that goes unrecorded, or a flood of overrides that turns the exception path into the normal path. Fences also need maintenance — dukas move, kiosks are demolished, a mini-mart reopens two doors down.
A Morning on a Nakuru Route
Consider a working morning in Nakuru. A rep takes a boda boda to the edge of the estate where his beat begins. The first outlet is a duka whose owner opens late; he waits, then marks his check-in at the shutter. The handset has one bar and loses it as he steps inside, so the check-in sits queued on the device.
He works four dukas and a kiosk along the same stretch, then crosses to an agrovet set back from the road. Its coordinates were captured from the roadside, so his check-in registers a short distance outside the fence; the system records that distance rather than refusing him. At the supermarket after that, signal returns and the morning syncs at once, each record carrying the time it actually happened. By eleven he is on a matatu to a market-day stop his supervisor added the previous evening.
At month-end none of this needs explaining: a full working day, one out-of-fence call with a recorded distance, and a sync gap matching a stretch of road everybody in that branch knows. Change one detail — a hard fence, the agrovet check-in refused — and the day looks incomplete, the supervisor fixes it from memory, and the correction reaches payroll with nothing behind it.
Late Marking and the Grey Zone Between Present and Absent
Two different failures get filed under one word. A rep can be late, genuinely starting after the agreed hour. Or a rep can be on time and mark late, because the phone was charging, the network was down, or the first outlet had not opened. Treating those identically breeds resentment quickly, because the field force knows the difference even when the system does not.
The way through is a written rule with a small number of states: a grace window before a check-in counts as late, a defined half-day threshold, and a rule for a check-in with no matching check-out — the most common defect in field attendance data, because reps finish at the last outlet and forget the closing tap. Decide in advance whether that means a short day, a flagged day, or a day that must be regularised.
These states cascade. Late may or may not reduce pay, but it very often affects eligibility for a daily travel allowance in KSh — money the rep notices. Anything touching an allowance line needs a rule the rep can read.
Leave Under the Employment Act
Leave is where attendance stops being a field problem and becomes a statutory one. Kenya's Employment Act sets out the leave an employer owes — annual leave, sick leave, maternity leave and paternity leave among the heads — and a contract may sit above the statutory floor but never below it. Check the entitlements against the Act itself, not from memory or another market's template.
What field teams get wrong is rarely the entitlement and almost always the ledger. When leave is approved over chat or in a separate file, the attendance register shows an absence while the leave register shows an approved day, and payroll receives two contradictory statements about the same date. The rep is either docked for a day they were owed or paid twice for it.
A working setup holds leave types with their own balances, an accrual rule, an approval route matching the real reporting line, and a link so an approved leave day writes itself into the attendance register rather than being reconciled against it. Weekly rest days and public holidays belong in the same ledger, because a market day worked on a public holiday is a payroll event.
Regularisation: The Exception Path That Has to Exist
Every field attendance programme needs a formal way to correct the record, because the reasons for a broken day are ordinary and endless. The phone died. There was no network all morning on a stretch of the A104. The rep was called into the distributor's office in Thika instead of working the beat.
Regularisation is the door for all of that, and it works when four things are true: the request carries a reason code from a short list rather than free text, so patterns are visible; it carries whatever evidence exists; it routes to a named approver rather than a shared inbox; and it has a cut-off after which the month cannot be reopened. Every corrected day should record the original value, the corrected value, who requested, who approved, and when.
Watch the volume as a health signal. A steady trickle is a system working; a month where a large share of days need correcting is telling you the fences are too tight, the network assumptions are wrong, or the rules do not match the work.
Closing the Month So It Stays Closed
Month-end closure is a sequence, and skipping a step turns payroll week into a rescue operation. Freeze new regularisation requests on the cut-off date. Clear the exception queue — missing check-outs, out-of-fence calls, pending leave approvals. Have supervisors sign off their own teams rather than leaving HR to guess. Then lock the register.
Locking has to mean something. Once locked, a day cannot be quietly edited; anything discovered afterwards becomes an adjustment in the following month, recorded as such, with a reason. That removes any chance that the number payroll used and the number the system shows today are different — which is what makes a month reproducible.
Before the lock, run one arithmetic check per employee: days present, plus approved leave, plus weekly rest days, plus public holidays, plus unpaid absence, should equal the days in the month. When it does not, something is missing or double-counted — far cheaper to find now than after the money has moved.
The Handover to Payroll and Settlement
Payroll does not want an attendance log. It wants a small set of derived figures per employee: paid days, unpaid absence, leave taken by type, allowance-eligible days, and any overtime or holiday working the contract treats separately. Everything else is supporting detail.
From there, gross-to-net is the payroll system's job, not the field application's. Kenyan payroll carries PAYE, which the employer deducts and remits to the Kenya Revenue Authority, the NSSF contribution, and the statutory health deduction to SHIF, the Social Health Insurance Fund administered by the Social Health Authority. That change is exactly why payroll masters, and the rates and bands behind them, should be verified against the current statute rather than an inherited label.
Settlement is the last mile, and it usually splits in two. Salary tends to move by bank transfer, while field allowances and expense reimbursements — the amounts in KSh a rep needs during the month, not after it — commonly settle over M-Pesa. Whichever rails are used, hold the payment reference against the employee and the period it covers, so a query about a short reimbursement is a lookup rather than an investigation.
Where These Programmes Go Wrong
The most common failure is framing. Attendance introduced as surveillance gets treated as an adversary, and a field force that believes it is being policed will find the edges of any system faster than the people who built it. Introduced as the mechanism that gets allowances paid accurately, it gets used. The rest of the failures are structural.
- Rules that live only in the software. If the grace window, the half-day threshold and the allowance rule are not written where a rep can read them, every dispute becomes an argument about what the system did rather than what was agreed.
- Punishing infrastructure. Marking a rep absent because a network dropped or a handset died destroys trust in one month and is rarely recovered.
- Two registers. The application plus a branch administrator's spreadsheet. Payroll then has to choose, and usually chooses the spreadsheet.
- Face capture with no stated purpose. Collecting images without saying why, who sees them, or how long they are kept is an avoidable exposure.
And one quieter than the rest: nobody owns the exception queue. Flags accumulate, clearing them is unrewarded work, and by month-end the queue is too large to review honestly, so it is approved in bulk. That single habit undoes every control above it.
How 1Channel Supports This
1Channel is field sales software, and its attendance capability serves the field workflow rather than replacing an HR or payroll system. Reps mark check-in and check-out from the mobile application with a GPS stamp, optionally with a selfie, against an outlet, a beat or a nominated start point. Capture works without a live connection and syncs when the network returns — which matters on upcountry routes and during power interruptions.
Outlet geofences are configurable, and out-of-boundary marking can be recorded with its measured distance and surfaced as an exception rather than silently blocked. Leave types, balances and approval routing sit alongside the attendance record, so an approved leave day and a marked absence do not contradict each other. Regularisation requests carry a reason and route to an approver, with corrections retaining the original value beside the change. At month-end the register can be reviewed, signed off and exported in the derived form payroll consumes.
Two limits are worth stating plainly. 1Channel does not run payroll, calculate statutory deductions or file anything with the Kenya Revenue Authority; it produces the attendance record a payroll system consumes. And it is not certified against any Kenyan statute — it supports an employer's own Employment Act and data-protection obligations by making the underlying record accurate and auditable.
Key Takeaways
Field attendance in Kenya is a payroll input first and a management tool second. Build it so the month closes on evidence rather than recollection.
- Define the start of the day before configuring anything. First outlet, nominated start point or loading location — pick one, publish it, and make it fair to reps working long upcountry legs as well as dense town beats.
- Let evidence do only what it can do. A GPS stamp and a face check-in prove who was where and when, not that a day's work happened. Pair them with outlet calls, and handle the images under the Data Protection Act, 2019.
- Flag, do not block. Soft geofences that record distance keep work visible; hard fences produce either unrecorded calls or an override queue that swallows the exception process whole.
- Give corrections a formal door and a deadline. Reason codes, a named approver, an audit trail and a hard cut-off are what let a month be locked and a locked month stay reproducible.
- Hand payroll derived figures, not raw logs. Paid days, unpaid absence, leave by type and allowance-eligible days are the interface; PAYE remitted to KRA, NSSF and the statutory health deduction are computed downstream, and settlement over bank or M-Pesa should carry a traceable reference.
None of this needs a large programme. It needs a written policy, one register instead of two, an exception queue somebody owns, and a lock date that is respected.
