Attendance and shift rosters for shops and branches
Kazee team · · 6 min read
In many shops and branches in Kenya, attendance lives in a register book by the door. The roster is a sheet pinned to the wall, or a photo of that sheet sent to a WhatsApp group on Sunday night. Field staff send "I'm on site" from wherever they are. It works while the owner can see everyone. Add a second branch, a night shift or a team on the road, and the gaps start to show.
This guide covers what Kenyan law asks you to record, how to build a roster people can follow, and how to keep attendance honest across sites you cannot see.
What the law asks you to record
The Employment Act, 2007 sets out a few points that touch attendance and rosters directly.
- Hours are your job to regulate. Section 27 says an employer shall regulate the working hours of each employee in line with the Act and any other written law.
- One rest day in seven. Section 27 also gives every employee at least one rest day in every period of seven days.
- The contract states hours and place. Section 10 lists what a written contract must state, and it includes the place of work and the hours of work.
- Rest days go in the records. Section 74 lists the records an employer must keep for each employee. They include the employee's weekly rest days, next to leave taken and days due.
- Records are kept for inspection. Under section 74, an authorised officer can ask to see the records for any period in the preceding thirty-six months.
Section 27 also points to "any other written law", so check which rules on hours apply to your sector. This is a summary, not legal advice. Check the current text on Kenya Law, or ask your lawyer, before you set a policy.
The roster and the register are two different records
It helps to keep two things apart.
- The roster is the plan: who should work where, and when.
- The attendance record is what happened: who checked in, at what time, at which site.
Most arguments come from mixing the two. A manager reads the roster and assumes the shift was worked. Or someone changes the roster after the week has passed, so it matches what happened, and nobody can see the original plan. Keep the plan, keep the record, and look at the difference every week. Late starts, missed shifts and unplanned overtime all show up there.
Building a roster people can follow
There is no single right pattern. The UK's Health and Safety Executive says there is no single optimal shift system that suits everyone. Its guidance is written for British law, but the advice on shift design is practical anywhere. From its good practice guidelines for shift design:
- Limit runs of work. Keep consecutive work days to a maximum of five to seven, and keep long shifts, night shifts and early morning shifts to two or three in a row.
- Leave time to adjust. Allow two nights of full sleep when someone switches between day and night shifts.
- Think about the journey home. Avoid early morning starts, and fit shift times around public transport. For staff who rely on matatus, a shift that ends after the last one is a real problem.
- Offer some choice. Offer a choice of permanent or rotating shifts, and try to avoid permanent night shifts.
- Keep the workload even. Plan an appropriate and varied workload.
HSE also says employees should be consulted on working hours and shift patterns. It suggests a policy that sets limits on working hours, overtime and shift-swapping, and a reliable way of recording all three. That matters in a small business, where swaps are usually agreed between two colleagues and the manager hears about them later.
A few habits help:
- Publish the roster at the same time every week, so nobody has to ask.
- Make one person responsible for changes. Swaps are fine, but they go through that person and get written down.
- Show the rest day on the roster itself, so you can see at a glance that everyone has one in seven.
- Keep last month's roster. It is part of the story your attendance records tell.
Branches and field teams
When you cannot see the door, attendance needs a little more care.
- Tie check-in to a place. For a shop or a branch, the question is simple: was the person at the site when they checked in? A register book at each branch cannot answer that from head office.
- Decide what counts for field staff. For people who start at a customer's site, agree what "starting work" means. It might be the first job, the depot or a set meeting point.
- Plan for forgotten check-ins. People forget, phones go flat and networks drop. Have a clear way to correct a missed entry, with a manager's approval and a record of why.
- Tell staff what you record. If check-in uses a phone's location, explain what is collected, when, and who sees it. Do this before the first day, not after a dispute.
- Look at the exceptions, not every line. A weekly look at late starts, missed check-ins and corrections tells a manager more than reading the whole register.
Moving off paper and messages
You can do this in a month without stopping work.
- Write down your shifts. Name each shift, its start and end time, and which sites use it. Add your public holidays and your attendance rules, such as how late counts as late.
- Agree the rules with managers. Who approves a correction, who approves a swap, who covers when a manager is away.
- Start with one branch. Run the new way alongside the register book for two weeks.
- Compare the two records. Where they differ, find out why. Usually it is a rule nobody had written down.
- Roll it out site by site, and keep the old register books with your records.
Where Kazee fits
Kazee People is the HR app in the Kazee suite, and it is Live. It holds attendance, shifts and leave in one place. Staff check in and out from the Attendance screen and see their month on a colour-coded calendar. You set attendance rules, holidays and shifts, and can draw geofences around your sites. A check-in from outside a geofence is refused, and HR can see the refused check-ins in a list. If someone forgot to check in, they apply for regularisation and a manager approves it from the Approvals queue. Approval chains and delegations keep requests moving when a manager is away. Staff who use Kazee Chat can also check in from a widget there. HR gets a company-wide attendance report it can export, and the audit logs record who did what and when.
It will not suit everyone. People does not connect to biometric or card readers, so if your attendance depends on a fingerprint machine at the door, it is not the right fit today. The phone app is for Android and is not yet in an app store, though everyone can use People in a web browser. Staff are added through Kazee Central, not imported from a file. And no app will design a fair roster for you. That part stays with you and your managers.
Whichever tool you use, keep the plan and the record apart, and look at the gap between them every week. If you would like to see how attendance and shifts work in Kazee People for a team like yours, book a demo and we will walk you through it.
Sources
- Employment Act, 2007, Kenya Law: sections 10, 27 and 74
- Employment Act, No. 11 of 2007, Revised Edition 2022 (National Council for Law Reporting), copy hosted by the County Assemblies Forum
- Health and Safety Executive (UK), Fatigue: key principles on shift work and working hours
- Health and Safety Executive (UK), Good practice guidelines for shift design, summarised from HSG256